Use of a BAdI

You have the option of using a Business-Add-In (BAdI) for mapping the accounting objects. If you map subitems to custom subassignments in a BAdI, the system is not able to export the master data for subitems and custom subassignments. For more information, see Exporting Customizing Files for FI-SL Rollups .

Transfer of Subassignments

The EC Consolidation (EC-CS) component maps certain subassignments, such as the transaction type, as subitems of a specific subitem categoryand exports these to the FI‑SL rollup file in the same format.

If the SEM consolidation system (SEM-BCS) uses the same data model as EC‑CS, go to the mapping section of the upload method and assign the source fields Subitem and Subitem Category to their respective target fields.

You can use the characteristics available in SEM-BCS, such as the transaction type, as subassignments . If you do this, create a mapping rule in the upload method that expresses the following: If the source field Subitem Category identifies the subassignment <characteristic> , then move the source field Subitem to the target field <characteristic> . (Here, <characteristic> might represent the transaction type. )

Shifted Fiscal Years

When creating the FI-SL rollup file, the sender system uses the fiscal year variant you have defined in Customizing for SAP Enterprise Controlling at  Consolidation Integration: Preparation for Consolidation Preparations in the Sender System Preparation and Activation of Data Transfer Activate Data Transfer .

If the companies to be consolidated use a different fiscal year variant, when creating the FI‑SL rollup file the sender system automatically converts the periods of the reported financial data to suit the fiscal year variant of the consolidation system.

You can use the automatic conversion in the sender system if you specify the fiscal year variant used in SEM‑BCS when you run Activate Data Transfer .