Skip to Content
SAP Business Planning and Consolidation, version for the Microsoft platform

The Checklist to Run BPC Consolidation

- Here the term ‘Elimination Rules’ refers to Automatic
Adjustment Rules in each application, rather than business rule library.


-Normal steps to run consolidation:

1, Run Ownership calculation package for current TIME/CATEGORY/GROUP

2, Run Currency Translation

3, Run Consolidation

- though it has already been accpeted as common sense,following
points need to be understood.

1,Normally speaking, consolidation is always the last step.

2,All data generated by consolidation package under those 'Destination Data Sources' should NOT be touched any more. Otherwise you have to re-run consolidation once again in order to adjust the result.

3, Of course, if you have touched the source data in current
TIME/CATEGORY/GROUP, 
you must re-run consolidation package again to get the correct result.

Master data checking:

DimensionsCheckings for C/TCheckings for Automatic Adjustment (Consolidation)
A (Account)O Property RATETYPE must be maintained correctly with the corresonding field in conversion rules.

O Account hierarchy is properly maintained, as parent nodes in hierarchies can be used in elimination rules.

O Values in property TYPELIM can be used in elimination rules as well. Make sure they are matching.

A (Account) - ownership cube

O Property IS_INPUT must be maintained carefully. Consolidation only cares those members with this property set to

    TRUE.

O Normally, we need the following members:

    - PGROUP

      * It is used to present hierarchy in ownership cube. A record under PRGROUP with non-zero value in key figure,

          means current entity belongs to the current group. In release 7.0, you MUST enter those relationships for all

          parent groups of an entity, including direct and indirect parents. Starting from release 7.5, you only have to

          enter those records for direct parents. Indirect relationships can be calculated automatically in OWNERSHIP

          CALCULATION.

      *  You can create an alternative member ID for this purpose. But you have to define it in the parameter

          ORG_ACCOUNTOWN of your current consolidation application.

    - METHOD

      This is a keyword. You MUST maintain methods for all parent groups of an entity.

    - POWN/PCON/PCTRL

      Ownership records under those accounts represent share percentage on an entity under EACH parent group.

D (Data source)

O Property DATASRC_TYPE is properly maintained for EACH data source member. Only following types are allowed:
    - I: for Input
    - M: for Manual entry
    - A: for Automatic Adjustment.

O Property IS_CONVERTED is properly maintained for EACH data source member. Only following types are allowed:
    -N: this data source will be ingored.
    - Y: this data source will be converted.
    - G: the transaction data with this data source is filled with group currency.

O Property DATASRC_TYPE is properly maintained for EACH data source member. Only following types are allowed:
    - I: for Input
    - M: for Manual entry
    - A: for Automatic Adjustment.
      (All destination data source in elimination rules must have this type.)
    - L: for delta posting (see DATASRC_LEVEL of group dimension below for more details)

O Property IS_CONSOLE must be set to TRUE for all members involved in Automatic Adjustment.
    - For members you want to take as 'Destination Data Source', you MUST set IS_CONSOLE to TRUE.
      Otherwise consolidation result can be generated again and again even if you don't have new data posted.
O Values in property DATASRC_ORIG can be used in elimination rules. Make sure they are matching.

E (Entity)O If property FX_TYPE is maintained, then the transaction data for this entity will apply the conversion rules with the same FX_TYPE value.

O Property INTCO MUST be maintained for EACH member, as long as INTCO dimension is there in the application.

O Set ELIM to TRUE ONLY for members for US Elimination. Those members are ignored by consolidation.

I (Intercompany, INTCO)

O Maintain ENTITY property properly for EACH member.

O I_NONE must be created as a base-level member in this dimension.

S (Subtables, i.e. Flow)

O Property FLOW_TYPE must be maintained properly for some important flows.

    Normally the following types of flows are REQUIRED in order to run consolidation:

    - OPENING

    - CLOSING

    - VARSCP

  It's better to have the following flow types as well, only one flow for each type:

    - VARSCPMETH

    - VARSCPPERC

    - VARSCPNEW

    - VARSCPLEAV

O Property SUBTABLES_ORIG can be used in elimination rules. Make sure they are matching.

G or R (group)

- for 7.0, group shares the same

  dimension with R, i.e. currency

- for 7.5 and later, group has a

  separate dimension type

O Property GROUP_CURRENCY is the identifier of group dimension. In release 7, customers can create a user-defined
    dimension dedicatedly for groups. This property can tell us the right group dimension in this case.

O Property ENTITY is the dummy entity for the group member. If you want to stage data from all entities under the
    group into this dummy entity, you must maintain it carefully.

O Property STORE_GROUP_CURRENCY is used to decided whether the extra records for Group dimension with currency value should be saved.

O Property GROUP_CURRENCY is the identifier of group dimension. In release 7, customers can create a user-defined

    dimension dedicatedly for groups. This property can tell us the right group dimension in this case.

O Property PARENT_GROUP, or the property specified in the parameter ORG_PARENTPROPERTY of OWNERSHIP

    application. It is used to represent group hierarchy used in consolidation. If this parameter is NOT set, we take

    hierarchy from OWNERSHIP cube.

O Property ENTITY is the dummy entity for the group member. If you want to stage data from all entities under the

    group into this dummy entity, you must maintain it carefully.

O When you run consolidation on top group, some times you don't want to post full values. You just want to post

    the difference against the sub-groups. In this case, set TRUE to DATASRC_LEVEL property.

O When CONSO_TYPE is set for a group (as a string), only lines with the same string set in the same field in the

    elimination rule table are valid for that group.

T (Time)

O The following properties must be maintained:

    - TIMEID

    - YEAR

    - PERIOD

    - MONTHNUM

O The following properties must be maintained:

    - TIMEID

    - YEAR

    - PERIOD

    - MONTHNUM

Ownership cube checking:

Checkings for C/TCheckings for Automatic Adjustment

O After ownership calculation, for each entity, there must be same number of records
    under the following account:
    - PGROUP
    - METHOD
    - POWN
    For each direct or indirect parent group, we MUST have one record for each of accounts above for an entity.

O One and only one holding company can be defined per group.

Rate cube checking:

Checkings for C/TCheckings for Automatic Adjustment
O One base currency should be maintained with key figure equals to 1 for all periods. And all key figures for other currencies represent the ratio to this base currency.

Method, Elimination Rules &Rule Library checking:

Checkings for C/TCheckings for Automatic Adjustment

O The value for RATETYPE should be maintained. And the rule only applies to those records whose ACCOUNT has the same RATETYPE value.

O The formula of the rules only support the following types:
    - [END] or [AVG] or other values maintained in the RATE cube.
    - [OPEEND] OR [OPEAVG] represent the value for the last period of previous year.
    - [AS_IS] means copy the value directly without translation.
    - the format such as A+B, A-B, A*-1. (Here A and B mean the values mention above, such as [END]-[OPEEND]

O If there's one rule maintained with DEST_ACCOUNT and DEST_FLOW, while the flag 'PERIODIC' is also set, then there must be another rule maintained with all the same values, but leave the DEST_ACCOUNT and DEST_FLOW empty.

O One and only one method can be defined with type 'H' (holding) in method table.

O Values set in Elimination Rules must be in line with master data records in dimensions. Find more details above in master data checklist.

O If you are making use of 'Entity Property Filter' in the elimination header, please make sure that the value you have filled into this field is a valid property name in BOTH entity and INTCO dimensions. Let's say you have a property called 'LOB' in both dimensions. And for the elimination line with 'Entity Property Filter' filled with 'LOB', we only take data with entity and INTCO with the same values in property 'LOB'.

O Member IDs of ownership account other than PGROUP or METHOD, whose IS_INPUT is set to TRUE, can be used in
    here in Rule Library tables. Records must be there with those ownership accounts in current TIME/CATEGORY/GROUP.
    In addition, we support prefix 'P' and 'I_P' with those ownership accounts.

O In Rule Library, we only support the formulas of types below:
    - A + B
    - A - B
    - A * B
    - MIN(A, B)
    - MAX(A, B)
    We don't support nested formulas either.