SAP ABAP Data Element KUMUFLAG (Indicator: Cumulative Allocation)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KALC (Package) Cost Accounting allocations RK-S
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KALC (Package) Cost Accounting allocations RK-S
Basic Data
Data Element | KUMUFLAG |
Short Description | Indicator: Cumulative Allocation |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FLAG | |
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 | Cumulative |
Medium | 15 | Cumulative |
Long | 20 | Cumulative |
Heading | 3 | Cml |
Documentation
Definition
Specifies whether during the processing of the cycle Cumulative Allocation is performed.
Use
If you execute a cycle with the cumulation indicator set to active, then the sender amounts posted up to the current period are allocated based on tracing factors, which are cumulated from period 1 onwards. In the current period, the allocation amounts determined are posted less the amounts allocated in the previous periods.
Cumulative allocation has the following requirements:
- The sender/receiver relationships should be stable within the fiscal year.
In particular, no sender or receiver may be deleted within the fiscal year.
- The allocation should be made using the sender rule "Posted amounts" and the receiver rule "Variable portions".
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in |