SAP ABAP IMG Activity SIMG_CFMENUCX01_1203 (Define Rollup for Data Exports)
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 SIMG_CFMENUCX01_1203 Define Rollup for Data Exports  
Transaction Code S_ALR_87002629   IMG Activity 
Created on 19981222    
Customizing Attributes SIMG_CFMENUCX01_1203   Define rollup 
Customizing Activity SIMG_CFMENUCX01_1203   Define Rollup 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUCX01_1203    

In this step you find out how to define rollups for transferring data into the Consolidation application.

If sending and receiving applications reside in the same system, then you only need a rollup selecting and converting the operational (transaction) data. If the applications reside in different systems, you also 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 Imports.

Note on the SAP Enhancement

The SAP enhancement FMC10011 features the function exits described later. If applicable, choose the activity Execute the Enhancement in this step. Note that ABAP knowledge is needed for carrying out enhancement projects.

  • Function Exit 200: Determine the Data Stream

    The system determines the data stream as follows:

    • from the global parameters when you start the rollup within the monitor
    • from the global parameters when you start the rollup directly and status management is activated
    • from 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, you then 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 that are encountered, along with the relevant data records to each message.

    For easier identification of the data records, the system displays for each record the values of certain key fields. In the standard SAP system, these output fields are defined for the following sender tables: ECMCT, GLPCT, GLT3, GLT0, GLFUNCT, and GLFLEXT.
    For example, a rollup from the sender table GLPCT shows the following key fields: RBUKRS, RYEAR, KOKRS, RPRCTR, RACCT, RTCUR, RASSC, and SPRCTR.

    You need function exit 210 if:

    • You want to define other output fields for the sender tables listed above, or
    • You want to execute rollups from other sender tables
  • Function Exit 220: Sender Fields for Organizational Units

    During a rollup, the system tries to find the sender fields within the sender tables using data elements. Following is a list of the data elements the system uses to access the characteristics:

    Characteristic    Data Element
    company code     BUKRS
    company     RCOMP_D
    business area     GSBER
    controlling area     KOKRS
    profit center     PRCTR
    partner company     RASSC
    partner business area     PARGB
    partner profit center     PPRCTR
    G/L account or cost element     RACCT
    ledger     RLDNR

    This can be false for certain characteristics with some sender tables. For example, in the sender table FILCT the G/L account coincides with the characteristic consolidation item. Therefore, the system should not access the data element RACCT, but instead must access the data element RITEM.

    You must use function exit 220 to determine these discrepancies.

  • Function Exit 230: Sender Fields for Subitems

    In IMG step Define subitem categories 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.

  • Function Exit 240: Processing Value Fields Prior to the Update

    This function exit lets you 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 then necessary to accumulate the period values to produce quarterly values. The standard rollup does not support an accumulation of values that are being transferred. This is where the function exit comes in handy.
    • Conversion of values using special logic

      Function exit 240 is called up from the standard exit, which SAP uses for rollups into the SAP component consolidation. This occurs at the time of 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:

    • subassignments are part of 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 rollup a different sender table, e.g., for GLT3, define the rollup analogous to rollup 0C_PC2CS with the respective sender table and field movements.

As the sender table, you can select a local table (containing company codes) and a global table (containing companies). For global tables there is an additional standard exit SC1 for receiver field RCOMP (see below for more information on standard exits).

Activities

Check the predefined rollups and define additional ones, if needed, for selecting and converting the operational data. Each rollup requires a header and a sequence.

Rollup Header

  1. Enter the totals table from the transaction application as the sender table (for example the totals table GLPCT for Profit Center Accounting) 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, if a rollup is repeated.

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

    • Ledger
    • Record type
    • Version

      The reset set can sometimes be used 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, in the reset set, besides the characteristics ledger, record type, and version, you also need todetermine the characteristics dimension and consolidation chart of accounts. Note that these characteristics may only have one value in each set, so that the data stream can be uniquely identified. The reset set must also 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: See also the documentation on function exit 200 for SAP enhancement FMC10011.

  3. To roll the data, also specify both the Exit and the rollup set:
    • During processing, the exit specified in the rollup header reads the relevant internal table to determine data streams, ID combination rules, financial statement (FS) items and so on. Insert standard exit SC1.
    • The rollup set determines the data to be selected from the sender structure. By double-clicking on the rollup set field, you access set maintenance. Note that for reasons of performance you need to specify at least one of the characteristics Ledger, Record Type, Version and Company Code.
      • Note: If you use a rollup to collect operational data from Profit Center Accounting, keep this limitation in mind: In the rollup set for selecting the data, you may only specify company codes from controlling areas that carry the profit center ledger (ledger 8A) with the same valuation.
      Background: The valuation of a profit center ledger is valid for a single controlling area. If you select data from company codes that are assigned to different controlling areas, these data records can be valuated differently. However, the rollup assumes that all data records share the same valuation. Rollups cannot process different valuations.

Rollup Sequence

Define the rollup sequence. For each sequence, define the field movement and specify the receiver ledger. By double-clicking on the "Field movement" field, can access a maintenance function:

  1. Specify the receiver fields.

    Typically these will be 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 and/or an exit for every receiver field:
    • Standard SAP exits for
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 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMENUCX01_1203 0 HLA0100204 Data Collection from R/3 Systems 
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 GL21 00000004 Create Rollup 
GL21 T - Individual transaction object GL22 00000003 Change Rollup 
GL21 T - Individual transaction object GL23 00000002 Display Rollup 
GL21 T - Individual transaction object GL24 00000001 Delete Rollup 
CMOD L - Logical transport object CMOD EC-CS:01PA Execute Enhancement 
History
Last changed by/on SAP  19990428 
SAP Release Created in