SAP Business Planning and Consolidationdocshare03.docshare.tips/files/24461/244613490.pdf · System Configuration Document SAP Business Planning and Consolidation NW10.0 Page 1 of

System Configuration Document SAP Business Planning and Consolidation NW10.0

Page 1 of 23

System Configuration Document

SAP Business Planning and

Consolidation

Version : Netweaver 10.0

.


Page 2 of 23

TABLE OF CONTENTS 1 INTRODUCTION .................................................................................................................................. 4

1.1 Purpose of Document .................................................................................................................. 4 2 DESIGN PROCESS COMPONENT ........................................................................................................ 4

2.1 Environment Management......................................................................................................... 4 2.2 Model Management .................................................................................................................... 5 2.3 Dimensions used in the Models .................................................................................................. 6 2.3.1 BUDGET_PERIOD ......................................................................................................................... 6 2.3.2 FSI ................................................................................................................................................ 9 2.3.3 ENTITY .......................................................................................................................................... 8 2.3.4 CURRENCY ................................................................................................................................... 7 2.3.5 CONS_GROUP .............................................................................................................................. 7 2.3.6 MOVE_TYPE ................................................................................................................................. 7 2.3.7 PARTNER_ENTITY ....................................................................................................................... 10 2.3.8 PLAN_CYCLE ............................................................................................................................... 10 2.3.9 O_ACCOUNT .............................................................................................................................. 10 2.3.10 PLEVEL ....................................................................................................................................... 11 2.3.11 PRODUCT ................................................................................................................................... 11 2.3.12 BASECURRENCY ......................................................................................................................... 11 2.3.13 R_ENTITY .................................................................................................................................... 11 2.3.14 SCENARIO .................................................................................................................................. 12 2.3.15 SOA_CATEGORY ......................................................................................................................... 12 2.3.16 UOM .......................................................................................................................................... 12 2.3.17 R_ACCOUNT ............................................................................................................................... 12 2.3.18 VERSION ..................................................................................................................................... 13

3 BUSINESS RULES ............................................................................................................................... 14 3.1 Currency Conversion ................................................................................................................. 14 3.1 Automatic Adjustment .............................................................................................................. 17

4 LOGIC ................................................................................................................................................ 19 4.1.1 PREPARE_NEW_DATA.LGF ........................................................................................................ 19 4.1.2 CT_LEGAL.LGF ............................................................................................................................ 22 4.1.3 CONS_LEGAL.LGF ....................................................................................................................... 27 4.1.4 CT_LEGAL_SEG.LGF .................................................................................................................... 31 4.1.5 CONS_LEGAL_SEG.LGF................................................................................................................ 31 4.1.6 GOODWILL.LGF ............................................................................................................................ 31 4.1.7 POST_CONSOL_RECLASS.LGF ..................................................................................................... 31 4.1.8 SEGMENT_RECLASS.LGF ............................................................................................................. 31


Page 3 of 23

5 OVERVIEW OF CONSOLIDATION PROCESS ................................................................................ 37


Page 4 of 23

1 Introduction

This section contains information on the purpose of the document.

1.1 Purpose of Document

System Configuration Document provides details on how the Business Requirements for the project will be

implemented from a technical perspective.

This document provides the technical design specification for the solution components used to provide information

and analysis to the project business users. This technical design document defines on “how” the business

requirements will be addressed by the project from a technical design point of view. This document is based on the

information provided in the BPC solution documents.

Following project testing and defect resolution, this document would be updated and can be used as a reference for

future solution maintenance and enhancement work.

2 Design Process Components

Design process is mainly divided in to three parts

1) Web Interface

2) BPC for Excel

3) Word and Power Point

2.1) Environment Management

Environment Creation: Environment in BPC are always created by copying from an existing Environment.

The Environment is copied from the Environment Shell..

2.2) Model Management

An Environment is consists of one or more Models.

For the purpose of Consolidation following models are used.

Model Name Purpose Model Type

BFS_YTD Used to store financial and

Non-Financial Data for the

purpose of Consolidation

Consolidation

OWNERSHIP Used to store Ownership

Details

Ownership

FOREX_CONSOL Reads Exchange rates from

FOREX model based on the

consolidation triggered for a

Exchange Rates


Page 5 of 23

particular scenario and

stores the exchange rate in

FOREX_CONSOL model .

The same exchange rate

prevail in

FOREX_CONSOL model

until the next scenario run.

BFS Used to store financial and

Non-Financial Data for the

purpose of Consolidation on

periodic values from offline

templates

Consolidation

FOREX For storing exchange rates

based on scenario

Model Dimensions Used Dimension Type Reference Dimension BFS_YTD BUDGET_PERIOD TIME-T

(BFS Model share the

same Dimension as

BFS_YTD)

CONS_GROUP GROUP-G

CURRENCY CURRENCY-R

ENTITY ENTITY-E CURRENCY

FSI ACCOUNT-A R_ACCOUNT

MOVE_TYPE SUBTABLES-S

PARTNER_ENTITY INTERCOMPANY-I ENTITY

PLAN_CYCLE USER DEFINED

PLEVEL AUDIT-D

PRODUCT USER DEFINED

SCENARIO USER DEFINED

SOA_CATEGORY USER DEFINED

UOM USER DEFINED

VERSION CATEGORY-C BUDGET_PERIOD

OWNERSHIP BUDGET_PERIOD TIME-T

CONS_GROUP GROUP-G

ENTITY ENTITY-E CURRENCY

O_ACCOUNT ACCOUNT-A

PARTNER_ENTITY INTERCOMPNAY-I



Page 6 of 23

FOREX BASECURRENCY USERDEFINED

BUDGET_PERIOD TIME-T

CURRENCY CURRENCY-R

PLAN_CYCLE USER DEFINED

R_ACCOUNT ACCOUNT-A

R_ENTITY ENTITY-E

SCENARIO USER DEFINED


FOREX_CONSOL BUDGET_PERIOD TIME-T

CURRENCY CURRENCY-R

R_ACCOUNT ACCOUNT-A

R_ENTITY ENTITY-E


DIMENSION:FSI

Key ID Description

ID User Defined Member ID

ACCTYPE

Used to Define Account type for Members

Account type. Can be INC for Income, EXP for Expense, AST for Asset, LEQ for

Liabilities and Equity. The account type cannot be blank.

Based on the account type the data will be saved in the database.

Account Type AST,EXP stores the data with positive sign.

Account Type INC,LEQ stores the data with negative sign.

RATETYPE Used for Currency Conversion. Validated with R_ACCOUNT dimension.

AVG Average Rate

DCACCOUNT DC Account Translation


Page 7 of 23

EDA Post to EDA Account

SACC Same Account Posting

STAT Statistical Items

DIMLIST1 Used to select the Account members in Business Rule.

DIMLIST_CLR Used to select the Account members in Business Rule.

ELIMACC Used for Intercompany Booking and Elimination but in our project we are not using, we found a way to

leverage the same with in Elimination and Adjustment Business rule.

TYPEELIM Used to select the Account members in Business Rule same as DIMLIST

FSI_MAP0 Used to Map to Target FSI when we copy opening of Balance sheet Item from Current Year to Next Year.

FSI_MAP1 Used to Map to Target FSI when we copy opening of Balance sheet Item from Current Year to Next Year.

Condition: If the FSI in FSI_MAP0 and FSI_MAP1 is having the same parent then it will be moved to

FSI_MAP0 in the next year , otherwise it will be moved to FSI_MAP1.

DIMENSION : BUDGET_PERIOD

Key ID Description


BASE_PERIOD

Used to define the month number. Eg. January is 001,002,003….012

LEVEL Used to define the level of the Member. Values are Month, Quarter, Year.

LOAD If the Property value is “Y” then the Actual data from has been loaded for the period.

MONTHNUM Defines the number of the month. Eg. January is “01”

NEXT Stores the value of Next Period member ID to the current ID Member

PERIOD This property has a value of say JAN,FEB,MAR, and so on.

PREV Stores the value of Previous period member ID to the current ID Member


Page 8 of 23

TIMEID Is the id used by the BPC program for copying and consolidation. Defined in the order of [Year +month+3

digit number in sequential order]

YEAR Used to store the year value for the Member ID

Dimension: CONS_GROUP

Key ID Description


CONSO_TYPE

Specifies which set of rules to apply to a group. Refers to group type filter

in Adjustments and Eliminations

CURRENCY_TYPE Used for the currency conversion.

N – Non-group

G – Group

DATASRC_LEVEL Stores the consolidation differences resulting from different % or methods

along the group hierarchy. We have not used this Property.

ENTITY Blank or a valid entity ID. This is used to define the link between the Group

and the Entity or to indicate the Entity where the aggregation should be

stored.

If this property is filled with a valid entity ID, and the property

STORE_ENTITY is set to Y, the results of the currency conversion for the

current Group are also copied into this Entity. (Length = 20)

GROUP_CURRENCY This can be any valid reporting currency, and is used for currency

conversion.

This property can only be used on Currency members with the property

CURRENCY_TYPE of G and, in this case, it must contain a valid ID from

the Currency dimension with the property CURRENCY_TYPE value of R.

(Length = 20)


Page 9 of 23

PARENT_GROUP Must be a valid ID from the Groups dimension. If you want to do the

consolidation by level, you must indicate here the higher level from the

group. If you want to use this property to define the hierarchy, enter the

same code as the ID for your top group. If this property is blank, the

dynamic hierarchy from the ownership application is used. (Length = 20)

STAGE_ONLY This property controls the way the converted values are saved when

performing a multilevel conversion of groups.

This property can only take the values Y, E, or N (blank).

STORE_ENTITY Y

If you want to store in the ID entered in the Entity property.

Blank

If you do not want to store in the ID entered in the Entity property.

STORE_GROUP_CURR Used for currency translation.

Y (or blank)

By default the results of the translation into a Group currency are

written in both the Group member and in the Currency member of

the currency dimension.

N

If only the Group member is to be stored, set this property to N.

ENABLEJRN Enable to Pass Journal Entries.

Dimension:CURRENCY


Page 10 of 23

Key ID Description

ID User Defined Member ID for currency

CURRENCY_TYPE

Identifies the local currency member (L) versus reporting currency members

(R) or transaction currency member (T).

ENTITY A 32-character field that can either be left blank or contain a valid member

name of the entity dimension associated to the current model. The ENTITY

property is validated against the entity dimension, and blank fields are allowed.

REPORTING Y is the value for Reporting

MD If direct exchange rate is maintained then it can have the value of “M”.

Indirect exchange rate then it can have the value of “D”

Dimension : ENTITY

Key ID Description

ID The Entities results used for Consolidation

CURRENCY Local currency of the entity

INTCO Defines the corresponding intercompany member for an entity

CTRL_CURRENCY_NOT_LC Specifies the Reporting Currency dimension member against which a

data control is performed. A control is an individual check for data

accuracy and consistency. Controls are enabled or disabled at the

model level.

The following are valid values:

Y – The generic LC (local currency) member is used.

N – The entity currency property is used, for example, EUR.

This can be used when loading pre-translated data from a

source system where currency translation has already been

performed.

If no value is set, the default value is Y.


Page 11 of 23

CONTROL_LEVEL

Specifies the controls that are relevant to an entity when a control set

(a group of controls) is executed.

The following are valid values:

Level 1 – Basic controls

Level 2 – Standard controls

Level 3 – Advanced controls

Level 4 – Comprehensive controls

If 4 is selected, all controls having a level from 1 to 4 are executed. If

blank or 0, no control is applicable.

ELIM

Defines whether the entity is used to store the intercompany

elimination for a given node in the hierarchy. Valid values are Y or N.

FX_TYPE

Defines the subset of Currency Conversion rules to apply to the entity,

where FX_TYPE matches the Entity FX Type property of the rules.

Dimension : MOVE_TYPE

Key ID Description

ID User Defined Member ID for Movement

FLOW_TYPE OPENING – opening

TRANSLOPE – change diff on opening

ALLOCINC – allocation

MERGER – merger

INCOME – net income from the period

CHANGE – variation.

TRANSFER – transfer

TRANSFLOW – translation change on flow

VARSCP – variation in scope (generic)

VARSCPMETH – variation in scope method

VARSCPPERC – variation in scope percentage

VARSCPNEW – variation in scope; new company

VARSCPLEAV – variation in scope sold company

CLOSING – closing

NONE – no flow


Page 12 of 23

Blank – all other flows

DIMLIST1 Used to group the flows for several business rules




Dimension : O_ACCOUNT

Key ID Description

ID User Defined Member ID for defining the Ownership Account

ACCTYPE This property can have the following values:

INC for income

EXP for expense

AST for asset

LEQ for liabilities and equity

IS_INPUT Flag for ownership accounts to be used in Method-based multipliers.

Dimension : PARTNER_ENTITY

Key ID Description

ID Property Value of INTCO used in Entity Dimension

ENTITY Member ID value of Entity Dimension

Dimension : PLAN_CYCLE

Key ID Description

ID User Defined Member


Page 13 of 23

Dimension : PLEVEL

Key ID Description


COPYOPENING Flag used to filter data sources when running carry forward (CopyOpening).

DATASRC_STAGE Defines to which Audit member consolidation adjustments from lower

groups are inherited in higher groups (Parent groups).

DIMLIST1 Property used to create a grouping of data sources which can later be used as

filters in Automatic Adjustments and Eliminations business rules.

DIMLIST2 Property used to create a grouping of data sources which can later be used as

filters in Automatic Adjustments and Eliminations business rules.

DATASRC_TYPE

Specifies whether a data source is used for Input (I), Manual Adjustments

(M) or Automatic Adjustments Eliminations (A).

IC_ORIGINE Used in IC Data

IS_CONSOL Blank

Used for top adjustments of consolidated amounts

Y

Standard setting to consolidate data

IS_CONVERTED Y

The data source is converted.

N

The data source is not converted

OPENING_DATASRC Blank

The data source is the same as the source member


Page 14 of 23

Non-blank

Contains the ID of the desired destination data source for the copy

Dimension :R_ACCOUNT

Key ID Description

ID Id is the property value of RATETYPE in Account Dimension

ACCTYPE This property can have the following values:

INC for income

EXP for expense

AST for asset

LEQ for liabilities and equity

RATETYPE AVG Average Rate

DCACCOUNT DC Account Translation

EDA Post to EDA Account

SACC Same Account Posting

STAT Statistical Items

Dimension :R_ENTITY

Key ID Description

ID User Difined Member ,Entity used in the Script Logic for currency conversion program.

The value used is Entity=Global

Dimension :SCENARIO

Key ID Description

ID User Defined Member to define High and Low of Exchange rate scenarios.

Dimension: PRODUCT


Page 15 of 23

Key ID Description

ID User Defined Member to define Products

Dimension:BASECURRENCY

Key ID Description


Dimension :SOA_CATEGORY

Key ID Description


Dimension :UOM

Key ID Description


Dimension :VERSION

Key ID Description


CATEGORY_OPE Blank

The category for the opening balances is the same.

Not blank

The ID of the category from which to read the opening balances.

Used in the copy Program.


Page 16 of 23

RATE_CATEGORY The category from which the rates are read.

Used Group Budget version (00) Exchange Rates used for PCG Budget Version(320).


Page 17 of 23

3. Business Rules:

Business Rules are a table based logic that provides the flexibility to customize certain delivered functions to meet

specific business needs.

Following Business Rules used for Consolidation.

Currency Translation Rule

Eliminations and Adjustments Rule for Legal Consolidation

Business Rules for Currency Conversion :

Rule : AVG

Rule : DCACCOUNT (Currency Translation for DC Accounts)

Rule : SACC (Post Forex Difference to same account with different movement type)

Rule : STAT(Statistical Items)


Page 18 of 23

Rule: CASH (Currency Conversion for Cash Flow items)

Methods :

Method based Multipliers

Elimination and Adjustment Rules :


Page 19 of 23

4. Logic Scripts:

The following Logic scripts used for consolidation purpose.

1) PREPARE_NEW_DATA.LGF – Before Consol Process Starts

2) FXTRANS_YTD.LGF – Currency Translation

3) CONSOLIDATION.LGF – Consolidation

4) RECLASSIFICATION.LGF – Custom adjustments to reported data

PREPARE_NEW_DATA.LGF

BADI Used PREPARE_DATA

Class ZCL_BFS_CONSOLIDATION

Method PREPARE_DATA

Purpose Reads the periodic values from BFS and writes YTD values to

BFS_YTD for the entire plan cycle and also does reclassification of

segment to PT9000 based on the Property value of FSI belonging to

“CONS_INV,CONS_EQU,CONS_EQU_R,RECLASS” AND currency

conversion in reporting currency only for the Balance Sheet FSI as per

script provided.

Copy opening only for LC of *

Prepare Data Script :

CT_LEGAL.LGF

Script used in CT_LEGAL.LGF

FXTRANS_YTD.LGF

BADI Used BFS_CONSOL


Page 20 of 23


Method IF_UJ_CUSTOM_LOGIC~EXECUTE( check for different modes)

Purpose

Script used in FXTRANS_YTD.LGF

CT_LEGAL_SEG.LGF

*SELECT(%CONS_GROUP%,SEGMENT,CONS_GROUP,ID=%CONS_GROUP_SET%)

*INCLUDE FXTRANS_YTD.LGF

Purpose it to execute currency translation for segment based on the property of SEGMENT in

CONS_GROUP dimension.

CONS_LEGAL.LGF

*SELECT(%CONS_GROUP%,ID,CONS_GROUP,ID=%CONS_GROUP_SET%)

*INCLUDE CONSOLIDATION.LGF

Purpose it to execute consolidation for Legal Groups

CONS_LEGAL_SEG.LGF

*SELECT(%CONS_GROUP%,SEGMENT,CONS_GROUP,ID=%CONS_GROUP_SET%)

*INCLUDE CONSOLIDATION.LGF

Purpose it to execute consolidation for segment based on the property of SEGMENT in CONS_GROUP

dimension.

CONSOLIDATION.LGF


Class

Mode STEP3

Purpose


Page 21 of 23

Script used in Consolidation.

Logic Explanation:

Mode Description

STEP3 In Step 3 we read the data from Period 12 of Last year and copy

opening to next year, we also carry the opening movements upto

Period 12 of Next year

STEP5 In Step 5 we read the data from period 12 of Budget year and Copy

opening to next forecast years

GOODWILL.LGF



Method

Mode

Purpose

Script used in GOODWILL.LGF

POST_CONSOL_RECLASS.LGF

- Purpose

CR_RECLASS.LGF

Purpose of the document is reclass the for entity 0001 and 0119 Corporate &Others Elimination


Page 22 of 23

happening at BS000 reclassing to BS430,BS400and bringing back original segment for the Dividend

Income

SEGMENT_RECLASS.LGF

Script used in SEGMENT_RECLASS.LGF

Journal Template:

Journal Template allows the user to pass adjustment entry. We are allowing the users to pass entry in

both Pre console and post console.

Pre console entry is passed at BFS Model which contains periodic values.

Post console entry is passed at BFS_YTD which is YTD values and at group level entry.

Journal Template is Model Specific.

Overview of Consolidation Process :


Page 23 of 23

Documents

SAP Business Planning and Consolidationdocshare03.docshare.tips/files/24461/244613490.pdf · System Configuration Document SAP Business Planning and Consolidation NW10.0 Page 1 of