SAP ABAP IMG Activity SIMG_CFMENUORFF_4110 (Perform System-Internal Transfer of Data)
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_CFMENUORFF_4110 Perform System-Internal Transfer of Data  
Transaction Code S_ALR_87002448   IMG Activity: SIMG_CFMENUORFF_4110 
Created on 19981222    
Customizing Attributes SIMG_CFMENUORFF_4110   Transfer data within R/3 
Customizing Activity SIMG_CFMENUORFF_4110   Transfer data within R/3 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUORFF_4110    

This step lets you subsequently post FI documents to the consolidation staging ledger 09.

To be able to do this:

  • You need to use periodic extract (only subsequent posting to the consolidation staging ledger 09 is feasible and possible).
  • The documents must exist in the FI system and not have been archived.

You can subsequently post the following:

  • General Ledger Accounting documents
  • documents which originate in Asset Accounting
  • documents which originate in Inventory Accounting or Sales and Distribution

Before you post the documents you need to activate the data tranfer procedure. The data is posted to the ledger(s) assigned to the company code or company.

Requirements

You should have activated the data transfer procedure in the chapter "General Specifications" -> Scope of Consolidation and Data Transfer.

Recommendation

SAP recommends that you post all application activities in one step. To do this:

  • do not make entries in the fields "Activity" and "Document origin",
  • flag the indicator "Also transfer MM and SD documents".

Caution

You should not post documents which have already been posted to the ledger. You can run a check first to establish which documents have been posted (see below).

Activities

  1. Specify company code, business year and period for the update.
  2. Do not specify the activity and document origin. All the possible combinations will then be taken into account on posting.

    Only specify the activity and document origin if you want to limit posting to documents from General Ledger Accounting, Asset Accounting, Inventory Accounting or Sales and Distribution:

    • To post General Ledger Accounting documents, enter "RFBU" as the activity and "BKPF" as the document origin.
    • To post Asset Accounting documents, enter "RFBU" as the activity and "AMBU" as the document origin.
    • To post Inventory Accounting documents, make no entry for the activity and enter "MKPF" and "RMRP" as the document origin (in two runs).
    • To post Sales and Distribution documents, make no entry for the activity and enter "VBRK" as the document origin.
  3. If required, limit the posting to ranges of document numbers, document data, posting or entry data.
  4. Specify whether you want a test run or a production run.
  5. Make sure that you have selected the option to check the data records which already exist.

    Note that journal entries cannot be recorded when using periodic extract.

    If you post FI documents several times to a ledger without using this check, you must ensure that data is not duplicated.

  6. Specify whether you want FI documents originating in Inventory Accounting or Sales and Distribution to be posted.

    NOTE: If you are posting documents from these applications to consolidation ledgers, you cannot limit the transfer to activities or document origins in General Ledger Accounting or Asset Accounting. You can only limit to documents originating in Inventory Accounting or Sales and Distribution. You would need to do this, for example, if you posted documents from General Ledger Accounting or Asset Accounting in the first run without flagging the indicator, and then want to post documents from MM and SD.

  7. Specify whether you want the trading partner account assignment and group account to be taken from the master data. This is necessary if the information is not contained in the FI documents to be posted because the master data was not complete at the time of posting.

    If you copy the additional account assignment "customer country" to Consolidation when using realtime update you must set the relevant flag. This is because the additional account assignment "customer country" is read from the master data of the customer concerned when you post the FI document, and is not contained in the document itself.

  8. Specify whether you want the Consolidation transaction types to be posted with the documents. This is necessary if no Asset Accounting transaction types were assigned to Consolidation transaction types at the time of posting.

Further notes

See also the topic "Creating Initial Data Sets in the Consolidation Staging Ledger and Consolidation Processing Ledger" in the section "General Aspects of Consolidation" of the FI manual "Preparations for Consolidation..." (SAP Library)

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 1   Mandatory 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_CFMENUORFF_4110 0 HLA0001215 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
IMGDUMMY D - Dummy object OCN1 425 FI-LC: Repost FI data 
History
Last changed by/on SAP  20050214 
SAP Release Created in