Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FK (Package) FI-LC Consolidation
IMG Activity
| ID | SIMG_CFMENUORFF1203 | Set up Rollups from User-Defined Ledger |
| Transaction Code | S_ALR_87002646 | IMG Activity: SIMG_CFMENUORFF1203 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORFF1203 | Set up rollups from user-defined ledger |
| Customizing Activity | SIMG_CFMENUORFF1203 | Set up rollups from user-defined ledger |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORFF1203 |
In this step you specify whether company data in this SAP system will be transferred into Consolidation via a rollup. If you choose this transfer method, you will need to make the appropriate settings in th system.
In order to carry out a rollup, data is automatically updated at the time of posting in a ledger of your choice. At a point in time which you have specified, data is selected via a rollup and imported into Consolidation.
A rollup is used in particular when additional account assignments for individual customers are entered in General Ledger Accounting and then need to be transferred to the consolidation processing ledger.
A rollup is imported into the Consolidation database as a UNIX file or PC file.
Besides processing actual data, you can use a rollup to transfer planning data from any ledger into the Consolidation system, where it can processed in a plan version.
Activities
- Select rollup as the transfer procedure
- Specify the parameters for the actual data (these entries are only informational):
- The sender ledger from which the rollup will be created.
- The consolidation version into which the data will be transferred.
- How often the rollup will be imported.
- The name of the rollup for company consolidation.
- The name of the rollup for busienss area consolidation.
- How the rollup will be imported into Consolidation, depending on the system environment.
- Specify the parameters for the plan data (these entries are only informational):
- The sender ledger from which the rollup will be created.
- How often the rollup will be imported.
- How the rollup will be imported into Consolidation, depending on the system environment.
- Specify the following for each sender ledger: the FI-SL plan version, the corresponding consolidation plan version, the name of the rollup for company consolidation and, if applicable, the name of the rollup for business area consolidation.
Note on transport
You cannot transport settings contolling the scope of consolidation and data transfer. You therefore need to make these settings in each client in each system.
Further notes
You should make the necessary settings for a rollup in FI-SL (Special Purpose Ledger) Customizing in the steps described in the chapter Rollup.
Business Attributes
| ASAP Roadmap ID | 255 | Create Interfaces |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUORFF1203 | 0 | HLA0001213 A N HLA0009482 |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| OCCI | T - Individual transaction object | OCCI | 0000000003 | Cons. Integration Settings |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
