1

SAP BPC 10 NW MEGA ELITE EnablementCurrency TranslationCustomer Solution Adoption

Why do you need Currency Translation?In big corporations it is quite common to find multicurrency financial modelswhere a large portion of the data is already in the desired reporting currency. Forexample, a US based company may have facilities located in Germany andCanada which require data to be loaded in their local currencies for internalreporting purposes. However, for management and external reporting purposesfinancial statements are prepared only in US Dollars (the reporting currency).SAP BPC version for NW provides standard support for multicurrency translationand reporting. The default configuration expects all data to be loaded in the localcurrency (LC) and then translated into one or more common reporting currenciesdepending on the requirement. However, if a significant portion of the LC data isalso in the main reporting currency used, there are alternative configurationsavailable that can dramatically improve currency conversion time and save diskspace. 2011 SAP AG. All rights reserved.2

Currency ConversionCurrency conversion can be executed in three ways in SAP Business Planning andConsolidation: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 ratesare changed.As part of a standard consolidation cycle, once data for all reporting units has beensubmitted and validated. 2011 SAP AG. All rights reserved.3

Currency Conversion SetupIn order for the standard currency conversion function to work you must have the following itemsin your Environment:Rate model: used to store the currency rates used for translation into the reporting/groupcurrencies. The Rate model must be referenced to the calling model (i.e.: Planning or Legalmodels)Currency type R dimension: stores the reporting and input currencies for your organization.CURRENCY attribute in the Entity type dimension: defines the local (functional) reportingcurrency 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 intranslation of the given account (average, end of month, or none).BUSINESS RULES for currency conversion which define the rates and logic to be applied toeach Account Rate Type.SCRIPT LOGIC TASK to pass to the program the appropriate parameters.An appropriate Data Manager Package to invoke the script logic. 2011 SAP AG. All rights reserved.4

Account DimensionACCOUNT :-Must include the following attribute: RATETYPEExamples:AVG (defined in Rate model)NOTRANS

The value of the RATETYPE attribute must be a valid key member in the rule table for currencytranslation, such as AVG, END, and AVNEND 2011 SAP AG. All rights reserved.5

Entity DimensionENTITY :-Must include the following attribute: CURRENCYExamples: EUR, USD, JPYThe CURRENCY attribute denotes the local currency for the current ENTITY. Forexample, for ENTITY US, the currency is USD; for FRANCE, the currency is EUR. Thevalue of this attribute must be a valid member of the INPUTCURRENCY dimension. 2011 SAP AG. All rights reserved.6

DataSrc DimensionDATASRC/AUDITID :-Must include the following properties: DATASRC_TYPE, IS_CONVERTEDThe DATASRC_TYPE attribute signifies the data source type. The following four valuesare 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 theconversion. When set to Y, members are converted from the local currency to thedesired currency. 2011 SAP AG. All rights reserved.7

RptCurrency DimensionRPTCURRENCY :-Must include the following master data ID: LC-Must include the following properties: CURRENCY_TYPEL (local currency)R (Reporting currency)T (Transaction currency) Optional 2011 SAP AG. All rights reserved.8

Group DimensionGroups/Scopes :-Must include the following master data for CURRENCY_TYPE = N-Must include the following properties: CURRENCY_TYPEG (Group)N (Non group) 2011 SAP AG. All rights reserved.9

Time DimensionTIME :-Must include the following properties: YEAR, PERIOD, TIMEID, MONTHNUMThe YEAR attribute contains the year information of the ID. For example, if the ID is2012.AUG, YEAR is 2012.The PERIOD attribute denotes the period to which the current time belongs. Forexample, if the ID is 2012.AUG, PERIOD is AUG.The TIMEID attribute is a numerical value for the current time. For example, for2012.AUG, the TIMEID is 20120800. 2011 SAP AG. All rights reserved.10

RATE model R_Acct DimensionR_ACCT-Must include an ID for the defined rates: such as AVG, END, etc.-Must include the following properties:ACCTYPEexample: ASTRATETYPEexample: FX 2011 SAP AG. All rights reserved.11

Planning Environment UpBUSINESS RULE[AVG] = Average MonthlyRateOther key formulas:[END] = month end rate[AS_IS] = current value[OPEEND] = OpeningRateAs defined in R_ACCT 2011 SAP AG. All rights reserved.12

RATE model InputCurrency DimensionINPUTCURRENCY-Must include the following properties:MDexample: M or D[Multiply or Divide the rate factor}Blank entrieswill Defaultto M 2011 SAP AG. All rights reserved.13

RATE model R_Entity DimensionR_ENTITY-Must include the following ID: GLOBALKeyword 2011 SAP AG. All rights reserved.14

Currency Conversion ProcessData is sent to the database via a data manager import, data send from an input schedule orjournal entry.Currency translation is either initiated immediately or alternately performed periodically via aData Manager package.For a given record, the source currency is determined from the value in the CURRENCYattribute of the corresponding entity member.The reporting/group currency(s) to be translated to are determined via either the default settingswhen translation occurs at time of entry or alternately via the selection criteria when run via a DataManager package.For the given record, the Rate type is determined from the RATETYPE attribute of the Accounttype dimension.Based on the RATETYPE, the system then determines from the Business rules tables what logicto apply and what Exchange rates should be applied.The function then determines the appropriate rates for translation from the local reportingcurrency of the entity to the desired reporting/group currencies, applies the logic as defined in thebusiness rules and creates the appropriate records with the corresponding reporting/groupcurrencies in the currency dimension. 2011 SAP AG. All rights reserved.15

DimensionattributeACCOUNTRATETYPE (AVG, END, HIST)DATASRC/AUDITIDDATASRC_TYPE (I, M, A)IS_CONVERTED (Y, N, G)ENTITYCURRENCY (local currency forEntity)RPTCURRENCYCURRENCY_TYPE (currency type -Reporting, Local, or Transaction)GROUP/SCOPECURRENCY_TYPE (currency type -Group, or N)TIMEYEARPERIODTIMEIDMONTHNUMINPUTCURRENCY (Rate model)MD (M or D, indicator of multiple ordivide)Attribute Summary 2011 SAP AG. All rights reserved.16

Currency Conversion ProcessIf you do not have a need for currency translation in your Environment, you can disableit by removing the currency translation formula from the Default.lgf file.If this is the case, the model does not need a Currency-type dimension or a Ratemodel, because no currency conversions will be performed.You can either delete the corresponding lines or insert two forward slashes in front of itto comment out the lines. 2011 SAP AG. All rights reserved.17

Script LogicActivitiesCurrency conversion is handled by a delivered program called CURR_CONVERSION. Thisprogram is launched using the logic statement:*RUN_PROGRAM CURR_CONVERSION()Example:*RUN_PROGRAM CURR_CONVERSIONCATEGORY = %C_CATEGORY_SET%CURRENCY = %RPTCURRENCY_SET%TID_RA = %TIME_SET%RATEENTITY = GLOBALENTITY = %ENTITY_SET%*ENDRUN_PROGRAM 2011 SAP AG. All rights reserved.18

Currency Translation Basic principlesCurrency Translation Components :Translation is executed from Data Manager using a Data package In thislogic file, the stored program, CURR_CONVERSION, is called to performthe calculation.The source currency is determined by the value of the CURRENCY attributeof each Entity (USD, EUR)The target currency(s) are the currencies passed into the package duringexecution.The RATETYPE attribute of each account (AVG, END, HIST, ) defines thecurrency translation rule to applyThe rate that is used is defined by the entries in the Currency ConversionBusiness Rules table (typically the rate is determined by a combination ofRatetype + Flow properties)The Currency Rate that will be used to perform the calculation is stored inthe Rate modelThe local currency is translated into the Reporting currency(ies). 2011 SAP AG. All rights reserved.19

Currency Translation Basic principlesHow does the currency translation works :The CURR_CONVERSION program scans all records found in the selecteddata region and translates them according to the RATETYPE attribute assignedto the ACCOUNT specified for each record, based on the following mechanism :All accounts with no RATETYPE will be translated with a factor of 1All accounts with the reserved RATETYPE attribute = NOTRANS will notbe translatedAll other accounts will be translated according to the definitions contained inthe Business Rules Table Currency ConversionWhenever a target currency is selected, the program will search for aRATEENTITY member flagged with the target currency in the CURRENCYattribute. If there is no RATEENTITY flagged as the target currency, the systemwill default to using the RATEENTITY with CURRENCY=. 2011 SAP AG. All rights reserved.20

Currency Translation Basic principlesThe translation principles used in the legal model:P&L accounts are typically translated at the YTD average rateBalance Sheet accounts, however use a number of different principles:Flows (increase, decrease, merger, etc) are translated at the YTD average rate and a CurrencyTranslation Account (CTA) is calculated for each flow:CTA on opening will typically point to flow: F_CTAO CTA on flows will typically point to flow: F_CTAFEquities are translated using the historic rateEach equity account has an opening which value which retrieved from theprevious year. CTAs calculated on the current year are accumulated onthe translation reserves account. This account is transferred on thefollowing years and is consequently made of all historical CTAs generatedon equity accounts.The current year result in the balance sheet is translated at the average rateThe gap between the average rate and the closing rate is posted on adesignated CTA account.The corresponding CTA account is transferred to the following year andautomatically posted to the translation reserves account. 2011 SAP AG. All rights reserved.21

Currency Translation Business Rules Table 2011 SAP AG. All rights reserved.22

Currency Translation Business Rules TableSupporting fields in the Conversion Business Rule :ID - RateType attribute : Listed from the account dimension or from theRATETYPE attribute of Account dimension 2011 SAP AG. All rights reserved.23

Currency Translation Business Rules TableSource Flow column is used to restrict the currency translation of average rate to one or many Flowdimension members. In this exercise, the currency translation for AVG rate types is restricted to closingbalance records.Destination Account column is used to specify which account to post the currency translation results to.When left blank the destination account is the same as the source account.Destination Flow column is similar in concept to the Destination Account but for the Flow Dimensioninstead of the Account Dimension.Formula. Formula syntax exists to perform mathematical operations. In this case, the formula is simply tofind the AVG rate type in the Rate Model and use it in the currency translation calculation to translate localcurrency records (reporting currency LC) into group and reporting currency records.Force closing column will automatically carry forward the calculation into the closing flow. Since this ruleonly applies to the closing flow (i.e. Source Flow = Balance), this flag is left blank. Otherwise, recordswould double up.Periodic Calc column is used to restrict the currency translation to a period movements instead of a year-to-date accumulated amounts within a Reporting Model that is defined with a Data Entry Mode as YTD.Entity Fx Type column is used to restrict currency translation to a specific Entity based on the attributeFX_TYPE in the Entity dimension. This field is not used in this exercise. 2011 SAP AG. All rights reserved.24

Currency Translation Dimension PropertiesSupporting properties in the DATASRC/AUDITID dimension :DATASRC_TYPE : I for Input, M for Manual adjustment, A for Automatic adj. orelimination, L for LevelIS_CONVERTED : Y : Conversion from Local Currency to Reporting and Group Currencies N : No conversion at all, figures are entered directly in the Group Currencies G : Figures are entered directly in Reporting Currencies and only converted toGroup CurrenciesSupporting properties in the CURRENCY dimension :CURRENCY_TYPE : L for Local Currency, R for Reporting Currency, T forTransaction CurrencySupporting properties in the GROUP/SCOPE dimension :CURRENCY_TYPE : G for Group currency, N for Non Group 2011 SAP AG. All rights reserved.25

Example:Currency ConversionWe want to run a currency conversion for a grossasset account with movement (Flows): 2011 SAP AG. All rights reserved.26

Currency Conversion: Assign Rate Type to AccountAccount dimension : RATETYPEMust be a valid Ratetype from the Currency conversion rules (Business rules table). 2011 SAP AG. All rights reserved.27

Currency ConversionBusiness Rules: Currency conversion rules 2011 SAP AG. All rights reserved.28

Currency Conversion: Business Rule DefinitionNOTE: Screen shot from older version.

Currency Conversion Example 1F_CTAO Currency Translation Adjustment 2011 SAP AG. All rights reserved.30

Currency Conversion Example 1F_CTAF Currency Translation Adjustment 2011 SAP AG. All rights reserved.31

Currency Conversion Example 1F_CLO Closing 2011 SAP AG. All rights reserved.32

IDDescriptionLocal CCYF_OPEOpening1000F_CTAOCTA OpeningF_INCIncrease200F_DECDecreaseF_CTAFCTA FlowsF_TOTClosing1200Currency Conversion Example 2How to run a currency conversion for a fixed asset account with movements(flows) :F_CLOClosing1200 2011 SAP AG. All rights reserved.33

Currency Conversion Example 2Account dimension : attribute RatetypeMust be a valid Ratetype from the FXTRANS Currency ConversionsBusiness Rule 2011 SAP AG. All rights reserved.34

Currency Conversion Example 2 2011 SAP AG. All rights reserved.35

PeriodEndAvgN-11.20N1.301.25IDDescriptionLocal CCYEURF_OPEOpening10001200F_CTAOCTA Opening100F_INCIncrease200250F_DECDecreaseF_CTAFCTA Flows10F_TOTClosing12001560Currency Conversion Example 2Formula1000 * 1.201000 * (1.30-1.20)200 * 1.25200 * (1.30-1.25)F_CLOClosing120015601200 * 1.30 2011 SAP AG. All rights reserved.36

IDDescriptionLocal CCYF_OPEOpening1000F_INCIncrease200F_DECDecreaseF_TOTClosing1200Currency Conversion Example 3Currency translation for equity accountsEach movement is translated and cumulated into the closing value (forceclosing option)Movements can be translated using a rate (Avg / End) or the translated valuecan be entered manually (AS_IS).Example: uses the same values and rates than for the Fixed Asset exampleRetained EarningsF_CLOClosing1200 2011 SAP AG. All rights reserved.37

Currency Conversion Example 3The following Business Rules Table shows the parameters for a standard equitycurrency conversion (HIST_EQ1) 2011 SAP AG. All rights reserved.38

IDDescriptionLocal CCYEURF_OPEOpening10001100F_INCIncrease200250F_DECDecreaseF_TOTClosing12001350IDDescriptionLocal CCYEURF_OPEOpening50F_CTAOCTA Opening150F_CTAFCTA Flows10F_TOTClosing210Currency Conversion Example 3The currency translation generates the following outputRetained EarningsFormulataken over from last period200 * 1.25F_CLOClosing120013501100+250CTA on EquityFormulataken over from last period1000 * 1.30 - 1100 -50200 * (1.30-1.25)F_CLOClosing21050+200+10 2011 SAP AG. All rights reserved.39

Exercise 2011 SAP AG. All rights reserved.40

ExerciseThe Source Flow column has additional entries for flows Opening, Increase, andOther in addition to Balance. The Exercise applies a dual flow concept forbalance sheet accounts where closing balances are broken down by openingbalances and movements to those balances. As this concept does not apply toprofit and loss accounts, the AVG rate type did not have this additionalconfiguration.The Formula syntax of [CLO] will look up the CLO rate type in the Rate Model anduse it in the currency translation calculation to translate local currency records(reporting currency LC) into group and reporting currency records. 2011 SAP AG. All rights reserved.41

Exercise 2011 SAP AG. All rights reserved.42

Exercise 2011 SAP AG. All rights reserved.43

ExerciseThe first two records for source flows Opening and Increase are used to translatethe Retained Earnings account (Account dimension member BS214 has a ratetype of HIST).The Opening flow should be translated at the spot rate for the beginning of theperiod for the beginning balance. For sake of simplicity, we are setting exchangerate for the beginning balance the same as the closing balance by using the formula[CLO]. Had we loaded rates into the prior year end (i.e. December 2009) we couldhave used the formula [OPECLO]. The opening value of any rate can be specifiedby adding the prefix OPE to the rate type itself.The Increase flow should be translated at an average rate to reflect the profit andloss impact on Retained Earnings (i.e. the current period movement for RetainedEarnings). 2011 SAP AG. All rights reserved.44

Exercise CTA impactThe next three of the four records are to calculate the currency translationadjustment (or CTA) impact (i.e. the equity plug to bring the balance sheet backinto balance after different exchange rates are applied to the balance sheet).The F_Total flow is a calculated member that sums Opening and Increasetogether. Had the formula for both Opening and Increase been translated usingthe CLO rate type, the balance sheet would have been brought back into balance.As a result, the F_Total for retained earnings is multiplied at the closing rate andstored on the currency translation adjustment account (BS213).In order to avoid double counting retained earnings in the CTA plug (BS213), thecalculations associated with the first two table entries for retained earnings(Opening and Increase) need to be backed out of BS213 (CTA plug). The lasttwo configuration entries achieve just that by multiplying the derived CTA plug valueby -1.As none of these flows deal with the closing flow (i.e. the value Balance), theForce Closing flag is checked off in order to copy all the calculations also into theclosing flow in order to have a complete closing trial balance.The FX_TYPE attribute is used to copy the local currency records to the reporting 2011 SAP AG. by reserved.45currency All rightsusing the keyword COPYLC for the US entity alone.

Exercise FX typeAs none of these flows deal with the closing flow (i.e. the value Balance), theForce Closing flag is checked off in order to copy all the calculations also into theclosing flow in order to have a complete closing trial balance.The FX_TYPE attribute is used to copy the local currency records to the reportingcurrency by using the keyword COPYLC for the US entity alone. 2011 SAP AG. All rights reserved.46

Exercise 2011 SAP AG. All rights reserved.47

ExerciseThe highlighted Balance Sheet total (BS000) shows that Assets equals Liabilities plusEquities before and after currency translation and would be out of balance if not for theCurrency Translation Reserves account (BS213) also known as the CTA plug.Both Currency Translation Reserves (and CTA plug) and Retained Earnings (BS213 andBS214, respectively) are highlighted to illustrate the following:Retained Earnings is the only account to create an out of balance situation (i.e. every otherbalance sheet account is translated using the rate type CLO while Retained Earnings usesHIST.The CTA plug is the result of the currency translation process in addition to the translationfrom local currency (GBP) to reporting currency (EUR).The database columns represents different valuations across two dimensions:Local currency (GBP as defined in currency attribute of the Entity member) versusReporting currency (EUR).Flow where there are two parallel valuations:A closing flow (value Balance) representing ending balances for each account (balance sheet andincome statement). 2011 SAP AG. All rights reserved.48

ExerciseA breakdown of the closing flow representing the opening balance (i.e. the value Opening)and periodic movements (e.g. the value Increase) for balance sheet accounts only (sincebalance sheet accounts are year-to-date amounts while profit and loss are periodicamounts).Note that the flow F_Total is a calculated member of all the flows except the closing flowin order to reconcile against the closing flow (they should always equal). Note that thecurrency translation Business Rules depend on this flow breakdown in order to translatethe opening balance of Retained Earnings at the opening spot rate (i.e. 18 GBP times aspot rate of 1.25 equals 22.50 EUR) and the periodic movements from net profit at anaverage rate (i.e. 5 GBP times an average rate of 1.5 equals 7.50 EUR)The last highlighted calculation columns represents reconciliation columns that perform thecurrency translation calculation within the spreadsheet itself by reference the exchange ratesloaded from the database in another report and Excel tab. In this example, a cell namedAVG_GBP_to_USD contains the average rate of 1.5 and multiplies it by 5 (the net profit inRetained Earnings for the period). The result in the calculation columns are the same in thedatabase (in this case 7.50). 2011 SAP AG. All rights reserved.49

Exercise 2011 SAP AG. All rights reserved.50

Exercise 2011 SAP AG. All rights reserved.51

ExerciseCurrency translation triangulates exchange rates on a base currency (in this caseUSD).As a result, the database stores rates under each currency instead of currency pairs(i.e. there is no From and To currencies specified in the rate tables as is the casewith SAP ERP rate table TCURR).In exercise example, the local currency is GBP for Entity UK and the reportingcurrency is EUR. As a result, the GBP to EUR rate is a calculated one. Thecalculation is as follows:Look up the GBP to USD rate in the database (for AVG this is 1.875 and for CLOthis is 1.6875).Calculate the inverse rate for EUR to USD (1/1.25 is .8 for AVG and 1/1.35 is.740741 for CLO).Multiply the GBP to USD rate by the inverse rate for EUR to USD (1.875 * .8 is 1.5for AVG and 1.6875 * .740471 is 1.25 for CLO. 2011 SAP AG. All rights reserved.52

Exercise Currency ConversionDataSrc Dimension: 2011 SAP AG. All rights reserved.53

Exercise Currency ConversionEntity Dimension: 2011 SAP AG. All rights reserved.54

Exercise Currency ConversionGroup Dimension: 2011 SAP AG. All rights reserved.55

Exercise Currency ConversionR_ACCT Account Dimension:R_ENTITY Entity Dimension: 2011 SAP AG. All rights reserved.56

Exercise Currency ConversionInputCurrency Dimension: 2011 SAP AG. All rights reserved.57

Exercise Currency ConversionScript Logic: 2011 SAP AG. All rights reserved.58

2011 SAP AG. All rights reservedBusiness Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalNo part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may beDecisions, Web Intelligence, Xcelsius, and other Business Objects products and serviceschanged without prior notice.mentioned herein as well as their respective logos are trademarks or registered trademarksof Business Objects Software Ltd. Business Objects is an SAP company.Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts and services mentioned herein as well as their respective logos are trademarks orMicrosoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoftregistered trademarks of Sybase, Inc. Sybase is an SAP company.Corporation.All other product and service names mentioned are the trademarks of their respectiveIBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,companies. Data contained in this document serves informational purposes only. NationalSystem z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,product specifications may vary.z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,The information in this document is proprietary to SAP. No part of this document may beOpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,reproduced, copied, or transmitted in any form or for any purpose without the express priorRETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,written permission of SAP AG.Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registeredThis document is a preliminary version and not subject to your license agreement or anytrademarks of IBM Corporation.other agreement with SAP. This document contains only intended strategies, developments,Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.and functionalities of the SAP product and is not intended to be binding upon SAP to anyparticular course of business, product strategy, and/or development. Please note that thisAdobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks ordocument is subject to change and may be changed by SAP at any time without notice.registered trademarks of Adobe Systems Incorporated in the United States and/or othercountries.SAP assumes no responsibility for errors or omissions in this document. SAP does notwarrant the accuracy or completeness of the information, text, graphics, links, or other itemsOracle is a registered trademark of Oracle Corporation.contained within this material. This document is provided without a warranty of any kind,UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.either express or implied, including but not limited to the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems, Inc.SAP shall have no liability for damages of any kind including without limitation direct,special, indirect, or consequential damages that may result from the use of these materials.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, WorldThis limitation shall not apply in cases of intent or gross negligence.Wide Web Consortium, Massachusetts Institute of Technology.The statutory liability for personal injury and defective products is not affected. SAP has noJava is a registered trademark of Sun Microsystems, Inc.control over the information that you may access through the use of hot links contained inJavaScript is a registered trademark of Sun Microsystems, Inc., used under license forthese materials and does not endorse your use of third-party Web pages nor provide anytechnology invented and implemented by Netscape.warranty whatsoever relating to third-party Web pages.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries. 2011 SAP AG. All rights reserved.59

2011 SAP AG. Alle Rechte vorbehalten.Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zuJava ist eine eingetragene Marke von Sun Microsystems, Inc.welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftlicheJavaScript ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter derGenehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene InformationenLizenz der von Netscape entwickelten und implementierten Technologie.knnen ohne vorherige Ankndigung gendert werden.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte knnenStreamWork und weitere im Text erwhnte SAP-Produkte und Dienstleistungen sowie dieSoftwarekomponenten auch anderer Softwarehersteller enthalten.entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschlandund anderen Lndern.Microsoft, Windows, Excel, Outlook, und PowerPoint sind eingetragene Marken derMicrosoft Corporation.Business Objects und das Business-Objects-Logo, BusinessObjects, Crystal Reports,IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,Crystal Decisions, Web Intelligence, Xcelsius und andere im Text erwhnte Business-Objects-Produkte und Dienstleistungen sowie die entsprechenden Logos sind Marken oderSystem z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,eingetragene Marken der Business Objects Software Ltd. Business Objects ist einUnternehmen der SAP AG.PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,Sybase und Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere und weitere im TextRETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,erwhnte Sybase-Produkte und -Dienstleistungen sowie die entsprechenden Logos sindIntelligent Miner, WebSphere, Netfinity, Tivoli und Informix sind Marken oder eingetrageneMarken oder eingetragene Marken der Sybase Inc. Sybase ist ein Unternehmen der SAPMarken der IBM Corporation.AG.Linux ist eine eingetragene Marke von Linus Torvalds in den USA und anderen Lndern.Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligenAdobe, das Adobe-Logo, Acrobat, PostScript und Reader sind Marken oder eingetrageneFirmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuMarken von Adobe Systems Incorporated in den USA und/oder anderen Lndern.Informationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen.Oracle ist eine eingetragene Marke der Oracle Corporation.Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe undVervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und inUNIX, X/Open, OSF/1 und Motif sind eingetragene Marken der Open Group.welcher Form auch immer, nur mit ausdrcklicher schriftlicher Genehmigung durch SAP AGCitrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame und MultiWin sindgestattet.Marken oder eingetragene Marken von Citrix Systems, Inc.HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C, WorldWide Web Consortium, Massachusetts Institute of Technology. 2011 SAP AG. All rights reserved.60