Hierarchy

⤷

⤷

⤷

Basic Data
Data Element | EP_PER_SEGMENT |
Short Description | Allocation: Save Line Items per Segment |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1 | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | LI/Segment |
Medium | 15 | LI per Segment |
Long | 20 | LI per Segment |
Heading | 24 | Line Items per Segment |
Documentation
Definition
If you activate this flag, then in a test run the line items generated are stored in table INDX both online and in the background. These line items can then be evaluated using program RKALEPEX.
You can store an extract for each cycle/start date/segment. If the same cycle is executed for a different period, the previous extract is overwritten. This function is available for both actual and plan cycles.
Use
This function should be used if you want to undertake special line item evaluations of background runs. You should note that the data volume created can be very high. Delete extracts you no longer require promptly using program RKALEPDE.
The runtime of the cycle deteriorates if you store the line items. You should use this function, therefore, only as long as it is needed for evaluation purposes.
Dependencies
You can also store a results list extract for a cycle run (the 'Save Extract' indicator). The results lists are then stored as for an online execution, and can be displayed again using extract management. This option does not, however, allow you to go to the line item report again.
Example
History
Last changed by/on | SAP | 20110901 |
SAP Release Created in | 606 |