Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-SL-SL (Application Component) Basic Functions⤷
GBRU (Package) FI-SL rollup
Basic Data
| Data Element | ROLL_PART |
| Short Description | Summarize partner object |
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 | Summ.Part. |
| Medium | 18 | Summarize partner |
| Long | 40 | Summarize partner object by level |
| Heading | 2 | SP |
Documentation
Definition
The area manager is not always interested in knowing from which END COST CENTER he/she has taken activities, but rather from which AREA these debits stem.
Using this indicator you can control if the summarized data contains end cost centers as sender cost centers/source cost centers or area cost centers.
If this indicator is set, then the sender cost centers and the source cost centers will be summarized bottom-up, parallel to the cost centers to be summarized in the hierarchy when the summarization is executed.
This additional summarization effect significantly improves the processing time when the report is later output.
Example:
B1
!
------------------------------
! !
B2 B3
! !
--------- ----------
! ! ! !
E1 E2 E3 E4
Cost center E1 debits E3 with 1000.- USD.
Records in the database after the summarization:
a) without parallel summarization
Cost center Sender cost center D/C Amount
B3 E1 S 1000
B2 E3 H -1000
b) with parallel summarization
Cost center Sender cost center D/C Amount
B3 B2 S 1000
B2 B3 H -1000
History
| Last changed by/on | SAP | 19950401 |
| SAP Release Created in | 470 |
