Hierarchy
EA-FIN (Software Component) EA-FIN⤷
FI (Application Component) Financial Accounting⤷
FERC (Package) IS-U/FERC: Regulatory Reporting
Basic Data
| Data Element | FE_PATHS_MAX |
| Short Description | Maximal number of paths for one source object |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | INT4 | 4-byte integer, integer number with sign |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Max. paths |
| Medium | 15 | Max. path no. |
| Long | 23 | Maximal number of paths |
| Heading | 10 | Max. paths |
Documentation
Definition
When the flow of cost trace procedure is analyzing a new source object it is keeping all paths starting on this object in an internal table. This is done for performance reasons because many subpaths are shared by the final paths.
For a considerably high number of paths you could exceed the technical memory limits. This would trigger a short dump and terminate the procedure. The exact number is dependent on your memory configuration and typically around 1 million records.
To avoid the runtime error you can set this limit. When exceeding it the system adds an error message to the log and starts processing the next sender.
Default
If you do not maintain the parameter then a default value of 100.000 records is considered.
Note
Long before you reach the technical limits you already have created so many paths that the final percentages for most or even all of the final objects are so small that only a couple of cents or maybe not even 1 penny are traced to most of the final objects. Such a source object should always be treated as a clearing object.
History
| Last changed by/on | SAP | 20030704 |
| SAP Release Created in |
