Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
| Data Element | ACCUM |
| Short Description | Ind.: Add Values? |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | Add |
| Medium | 15 | Add |
| Long | 20 | Add values |
| Heading | 3 | Add |
Documentation
Definition
This indicator shows whether the data to be rolled up should be added to or replace the contents of any records that might exist in the receiver ledger.
Use
Note
If this indicator is NOT set (standard setting), the rollup records of the current run overwrite the records that already exist in the rollup ledger (only the periods for which the rollup is being completed. The remaining records remain unchanged.) Multiple runs of a rollup in one period are thus not a problem, since the values are simply overwritten.
If the indicator is set, the current rollup records are added to the records already present in the rollup ledger. If multiple runs are completed, the totals in the rollup ledger are increased with each run.
The cumulation makes sense if the data from multiple sender ledgers are to be entered in one rollup ledger using rollups. Without cumulation, the second rollup would overwrite the data of the first rollup.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 46C |
