SAP BPC 10.0 TRAINING VIDEOS WITH PROJECT CAL ME 91-8106855785

Currency Translation

Why do you need Currency Translation?
In big corporations it is quite common to find multicurrency financial models where a
large portion of the data is already in the desired reporting currency. For example, a
US based company may have facilities located in Germany and Canada which
require data to be loaded in their local currencies for internal reporting purposes.
However, for management and external reporting purposes financial statements are
prepared only in US Dollars (the reporting currency).
SAP BPC version for NW provides standard support for multicurrency translation
and reporting. The default configuration expects all data to be loaded in the local
currency (LC) and then translated into one or more common reporting currencies
depending on the requirement. However, if a significant portion of the LC data is
also in the main reporting currency used, there are alternative configurations
available that can dramatically improve currency conversion time and save disk

Currency Conversion
Currency conversion can be executed in three ways in SAP Business Planning and
Consolidation:
„ Automatically with each data submission (Default Logic).
„ Schedule as a separate task via a Data Manager package.
„ Through the consolidation monitor ( for consolidation type model only)
„ Examples of where the Data Manager method would be utilized would include:
„ Periodically (i.e. at the end of the day when all data has been entered).
„ After data import/loads.
„ Recalculate and update translated values on all existing data when conversion
rates are changed.
„ As part of a standard consolidation cycle, once data for all reporting units has
been submitted and validated.
Currency Conversion Setup
In order for the standard currency conversion function to work you must have the
following items in your Environment:
„ Rate model: used to store the currency rates used for translation into the reporting/group
currencies. The Rate model must be referenced to the calling model (i.e.: Planning or Legal
models)
„ Currency type “R” dimension: stores the reporting and input currencies for your organization.
„ CURRENCY attribute in the Entity type dimension: defines the local (functional) reporting
currency of the input/submitted values for the entity member.
„ Group dimension: stores one Member with the attribute “CURRENCY_TYPE” set to “N”.
„ RATETYPE attribute in the Account dimension: determines the rate and logic to be used in
translation of the given account (average, end of month, or none).
„ BUSINESS RULES for currency conversion which define the rates and logic to be applied to
each Account Rate Type.
„ SCRIPT LOGIC TASK to pass to the program the appropriate parameters.
„ An appropriate Data Manager Package to invoke the script logic.

Account Dimension
ACCOUNT :
-Must include the following attribute: RATETYPE
Examples:  AVG (defined in Rate model)
NOTRANS
<blank>
The value of the RATETYPE attribute must be a valid key member in the rule table for
currency translation, such as AVG, END, and ENDFL
Entity Dimension
ENTITY :
-Must include the following attribute: CURRENCY
Examples: EUR, USD, JPY
The CURRENCY attribute denotes the local currency for the current ENTITY. For
example, for ENTITY US, the currency is USD; for FRANCE, the currency is EUR. The
value of this attribute must be a valid member of the INPUTCURRENCY dimension.

DataSrc Dimension
DATASRC :
-Must include the following properties: DATASRC_TYPE, IS_CONVERTED
The DATASRC_TYPE attribute signifies the data source type. The following four values
are available:
I (input)
M (manual adjustment)
L (datasrc level, for consolidation only)
A (automatic adjustment or elimination)
When the IS_CONVERTED attribute is set to N or blank, members are ignored in the
conversion. When set to Y, members are converted from the local currency to the
desired currency.
RptCurrency Dimension
RPTCURRENCY :
-Must include the following master data ID: “LC”
-Must include the following properties: CURRENCY_TYPE
L (local currency)
R (Reporting currency)
T (Transaction currency) Optional

Group Dimension
Groups :
-Must include the following master data for CURRENCY_TYPE = “N”
-Must include the following properties: CURRENCY_TYPE
G (Group currency)
N (Non group)

Time Dimension
TIME :
-Must include the following properties: YEAR, PERIOD, TIMEID, MONTHNUM
The YEAR attribute contains the year information of the ID. For example, if the ID is
2008.AUG, YEAR is 2008.
The PERIOD attribute denotes the period to which the current time belongs. For
example, if the ID is 2008.AUG, PERIOD is AUG.
The TIMEID attribute is a numerical value for the current time. For example, for
2008.AUG, the TIMEID is 20080800.

RATE model – R_Acct Dimension
R_ACCT
-Must include an ID for the defined rates: such as “AVG”, “END”, etc.
-Must include the following properties:
ACCTYPE example: “AST”
RATETYPE example: “FX

Planning Environment Up
BUSINESS RULE
[AVG] = Ave Monthly Rate
Other key formulas:
[END] = month end rate
[AS_IS] = current rate
[HIST] = historical rate
As defined in “R_ACCT


RATE model – InputCurrency Dimension
INPUTCURRENCY
-Must include the following properties:
MD example: “M” or “D”
[Multiply or Divide the rate factor}
Blank entries
will Default to
“M”


RATE model – R_Entity Dimension
R_ENTITY
-Must include the following ID: “GLOBAL”
Keyword