Show TOC

Function documentationConsolidation Application Setup Locate this document in the navigation structure

 

This function enables you to create applications and set application parameters required to run consolidations.

Prerequisites

A consolidation application set is created, application set parameters are defined, dimensions, and members have been set up.

Features

Three applications are required: Rate, Ownership, and Consolidation.

Note Note

In the NetWeaver version of the system, an application is equivalent to an InfoCube.

End of the note.
Creating the Rate Application

The currency conversion process makes use of a rate application. Where the appropriate, the system searches exchange rates for each relevant currency. The name for this cube is user-defined, but here it is referred to as the rate application.

Note Note

The master data (dimensions) can be shared by applications within an application set. However, for the rate application, to fulfill certain consolidation requirements, R_Acct (Account dimension) and R_Entity (Entity dimension) are used only by the rate application.

End of the note.

The following dimensions are required in the rate application:

  • R_Acct (A): This details the different types of rate (Average, End-of-period, and so on)

  • R_Entity (E): This stores multiple tables of rates, if required; otherwise the R_Entity dimension may just be limited to one dummy member, typically named GLOBAL

  • InputCurrency (R): This stores each applicable local currency

  • Time (T) and C_Category (C): These can be shared by all applications in a consolidation

Creating the Ownership Application

The ownership application defines ownership details, such as the consolidation scope, method, percentage of shares owned by the holding company or groups, and so on. For the ownership application, the only dimension that is specific for the ownership cube is Ownership Account (O_Acct). For the consolidation engine, it is necessary to set up several required members, including:

  • PGROUP: This defines which companies are consolidated in each group

  • Method: This defines the consolidation method

  • POWN: This defines the percentage of ownership (how much they are owned by the group)

  • PCON: This defines the percentage of consolidation

  • PCTRL: This defines the percentage of control (how much they are controlled by the group)

For the ownership application, the dimensions Time, Category, Entity, Groups, and IntCo are shared by the ownership and legal consolidation application to be created.

The following is the list of all the dimensions required for the ownership application:

  • O_Acct (A)

  • C_Category (C)

  • Entity (E)

  • Time (T)

  • Intco (I)

  • Groups(R)

The name of this application can be user-defined, but the relationship linkage between the ownership application and the consolidation engine must be set up in the application parameter settings. (See the next section.)

Setting Application Parameters

You can set application parameters by choosing   BPC Administration (Web)   Set Application Parameters  . You can then change the current view and set it to the consolidation cube.

Key ID

Description

ORG_ACCOUNTOWN

The member ID of the Ownership Account (O_Acct) Dimension that controls the position of a consolidation entity within the group.

For example, PGROUP.

ORG_PARENTPROPERTY

(Ownership application only)

This parameter is used with dynamic hierarchy for legal applications when defining consolidation hierarchies. The value set here must match the name of property in GROUPS dimension in the legal consolidation application to store the ownership data.

Value must be PARENT_GROUP.

ORG_INTCO

This parameter should be a member ID in the INTCO dimension in the ownership application if you are using dynamic hierarchies.

For example, I_NONE.

ORG_ACCOUNTLIST

The ID of the member that stores the value of METHOD, Ownership percentage, and percentage of consolidation in the Ownership Account (O_Acct) Dimension. For example, these could be METHOD, POWN, and PCON.
Creating the Consolidation Application

You must assign the rate and ownership applications just created as reference applications to the consolidation application. In the creation process, you create a new application, name it and set the application type to Consolidation. You define the corresponding rate and ownership applications to be referenced. You then add the consolidation business rules that you want to implement.

The following is the list of all the dimensions required for a legal application:

  • C_Acct (A)

  • C_Category (C)

  • C_Datasrc (D)

  • Flow (S)

  • Groups (R)

  • Entity (E)

  • Intco (I)

  • Time (T)

Note Note

When the consolidation type application is created and the business rule Automatic Adjustments has been selected, the business rule library tables are activated and shown in the Admin Console. You should define method and rule in the business rule library, which includes the Method Library, Elimination Rule and Rule formula tables, as only Automatic Adjustment (such as Minority posting, Investment adjustment) use those Elimination rules and formulas for the calculation of actual postings. See Consolidation Rules, Methods, and Formulas.

End of the note.

In the NetWeaver version of the system, before the consolidation type application has been created, you cannot display the rules, and the predefined library table content is stored in the following ABAP database tables:

  • Method: UJP_Method

  • Rule Header:UJP_RULEH

  • Rule Formula: UJP_RULE

You can then select the dimensions for a legal consolidation and set the dimensions to be included in the application. You can also set the Secured dimension option for member access control. Under most situations, the Entity and Category dimensions are secured dimensions. The Group dimension stores both group currency and reporting currency, as well as consolidation groups.