SAP ABAP IMG Activity CFMENU_CX01_1205 (Define Rollup for Data Export from (New) General Ledger)
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ EC-CS (Application Component) Consolidation
     ⤷ FC00 (Package) Cons: General consolidation (cannot be assign.to FC01-FC09)
IMG Activity
ID CFMENU_CX01_1205 Define Rollup for Data Export from (New) General Ledger  
Transaction Code S_SL0_21000015   (empty) 
Created on 20040423    
Customizing Attributes SIMG_CFMENUCX01_1203   Define rollup 
Customizing Activity CFMENU_CX01_1205   Define Rollup for Data Export from (New) General Ledger 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name CFMENU_CX01_1205    

This step shows you how to define rollups for transferring data into the Consolidation component.

If sending and receiving applications reside in the same system, then you only need a rollup for the selection and conversion of the operational (transaction) data. If the sender and receiver reside in different systems, you need an additional rollup for importing the data into the Consolidation system. You define the additional rollup in the IMG step Define Rollup for Data Import.

Notes for the SAP Enhancement

SAP Enhancement FMC10011 offers the function exits discussed below. If applicable, choose the activity Execute Enhancement in this step. Enhancement projects require knowledge of ABAP programming.

  • Function Exit 200: Determine the Data Stream

    The system determines the data stream using:

    • The global parameters when you start the rollup within the monitor
    • The global parameters when you start the rollup directly and status management is activated
    • The reset set of the rollup when you start the rollup directly and status management is deactivated

      If several data streams are active and the system cannot determine the relevant data stream from the parameters, then you need function exit 200 to determine the relevant data stream.

  • Function Exit 210: Output Fields for Erroneous Data Records

    Rollup execution produces an error list. This list contains messages for any errors found, and contains the data records related to each message.

    For easier identification of the data records, the rollup function displays the following key fields from the (new) General Ledger: company code, fiscal year, business area, profit center, account number, transaction currency key, consolidation transaction type, partner company, partner business area, and partner profit center.

  • Function Exit 220: Sender Fields for Organizational Units

    When performing a rollup from the (new) General Ledger, the system attempts to automatically determine the field names of the characteristics company code, business area, controlling area, profit center, partner company, partner business area, account number, and ledger. If this is unsuccessful, you need to supply the field names with the help of function exit 220.

  • Function Exit 230: Sender Fields for Subitems

    In IMG step Define Subitem Categories and Subitems for the integrated data transfer, you determine which account assignments are transferred to the subitem. You can choose the transaction type, functional area, business area, country of customer, cost center, G/L account, and profit center.

    In rollups from the (new) General Ledger, the system attempts to automatically determine the sender field (but not when using "country of customer"). If this is unsuccessful, you need to supply the field names with the help of function exit 230. When using "country of customer", you always must perform this step.

  • Function Exit 240: Processing Value Fields Prior to Update

    This function exit enables you to manipulate the value fields of the rolled data records before these are written to the consolidation database. Here a few sample cases where this might be applicable:

    • If the consolidation frequency of the consolidation group shows quarterly consolidations, it is necessary to accumulate the period values to produce quarterly values. The standard rollup does not support accumulations of values during a transfer. This is where the function exit comes in handy.
    • Conversion of values using special logic

      Function exit 240 is called from the standard exit, which SAP uses for rollups into the Consolidation component. This occurs at the time prior to the update. Thus, the customer exit influences the values directly prior to when the values are written.

  • Function Exit 250: Providing Values for Custom Subassignments

    If you use custom subassignments in Consolidation and you want to fill them using the rollup, you need function exit 250 if:

    • The subassignment belongs to a characteristic compound

      and

    • The independent characteristic is fixed in the breakdown category

For more detail, see the documentation in the Enhancement transaction.

Standard settings

In the standard SAP system, the rollup 0C_PC2CS (sender table GLPCT; receiver table ECMCT) is predefined for the selection of data in the sender structure and for the conversion of the data.

If you want to roll up data from the (new) General Ledger, you define the rollup analogous to rollup 0C_PC2CS with the respective sender table and field movements.

Activities

Follow these steps if you want to define a rollup from the (new) General Ledger:

Rollup Header

  1. Specify the totals table from the (new) General Ledger as the sender table, and the Consolidation totals table (ECMCT) as the receiver table.
  2. Enter the reset set.

    When a rollup is started, the reset set resets to zero those value fields in the receiver table that will be filled by the rollup. This is essential, for example, when a rollup is repeated.

    By double-clicking on the reset set field, you can access the set maintenance function. In the entries you define the value fields for the set. For performance reasons, the set must contain entries for the following dimensions, as a minimum:

    • Ledger
    • Record type
    • Version

      You may also want to use the reset set to determine the relevant data stream for the rollup. For example, you might have multiple data streams activated in Customizing; however, the rollup can only populate one data stream. Therefore, besides the characteristics ledger, record type and version, in the reset set you also need to determine the characteristics dimension and consolidation chart of accounts. Note that these characteristics may only have one value in each set to ensure that the data stream can be uniquely identified. Furthermore, the reset set must contain the characteristic posting level. Specify the posting level that was used to write the data to the totals database of Consolidation (the default is " ").

      Note: Also read the explanations for function exit 200 in SAP Enhancement FMC10011.

  3. To roll the data, specify both the Exit and the rollup set:
    • The Exit specified in the rollup header reads the relevant internal tables for postprocessing of the rollup, for example, data streams, ID combination rules, financial statement items, and so on.
    • The rollup set determines the maximum amount of data from the sender structure to be selected. By double-clicking, you go to set maintenance. Note that for performance reasons you need to specify at least one of the characteristics ledger, record type, version, and company code.

Rollup Sequence

Define the rollup sequence. For each sequence, specify the field movement and the receiver ledger. Double-click to maintain the field movements:

  1. Specify the receiver fields.

    Typically these are the fields for the consolidation unit, partner unit, dimension, consolidation chart of accounts, FS item, record type, version, subitem category, and subitem.

  2. Specify a sender field or Exit for each receiver field:
    • Standard SAP exits for converting the sender data exist for some receiver fields. For example, the G/L accounts must be converted to the financial statement items of Consoldation. Generally speaking, you should retain these standard exits (listed later).
      • However, for one or more receiver fields you can embed special logic using a user exit. If you do this, you replace the standard exit with a customer exit that contains the following:
      - Custom special logic
      - A call to the standard exit at the end of the special logic
      In user exits you must ensure the correct sequence of the rollup exits. You will find comprehensive information on this subject in SAP Note 111140.
    • For receiver fields without a standard SAP exit, you specify either the sender field, a substitution process, or a user exit.
    • For receiver fields with standard SAP exits, you cannot specify a substitution process. Although you can specify a sender field, this only serves informational purposes, except when the following applies: For custom subassignments that don't belong to a compound or whose independent characteristic is not fixed in the breakdown category, you must specify the sender field for each receiver field and also specify SC8 as the standard exit. When dealing with compound custom subassignments whose independent characteristic is fixed in the breakdown category, you do not specify a sender field: instead you specify standard exit SC8. (See also remarks to function exit 250 in SAP enhancement FMC10011).

The following exits are predefined in the standard system:

  • SC1

    Processes the company from the global sender tables, except ECMCT. This exit is not applicable to rollups that have the (new) General Ledger as t

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
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
GL21 T - Individual transaction object FAGL21 00000004 Create Rollup (General Ledger) 
GL21 T - Individual transaction object FAGL22 00000003 Change Rollup (General Ledger) 
GL21 T - Individual transaction object FAGL23 00000002 Display Rollup (General Ledger) 
GL21 T - Individual transaction object FAGL24 00000001 Delete Rollup (General Ledger) 
CMOD L - Logical transport object CMOD EC-CS:01PA Execute Enhancement 
History
Last changed by/on SAP  20040428 
SAP Release Created in 500