a93 Bpc100 Bpd en Xx

Business Process Procedures

SAP NETWEAVER 7.3

SAP Business Planning and Consolidation 10, version for SAP NetWeaverSAP EPM add-in for Microsoft Excel

Web Services Enhancements (WSE) 3.0 for Microsoft .NETOctober 2012

EnglishEnglish Only

SAP Rapid-Deployment Solution for New G/L Financial Planning (A93)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyBusiness Process Documentation

Copyright

2012 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.Icons

IconMeaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type StyleDescription

Example textWords or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example textEmphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXTNames of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example textScreen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXTKeys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example textExact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Contents 61Introduction

71.1Benefits of the SAP rapid-deployment solution for new G/L financial planning

71.2What Is a Rapid-Deployment Solution?

81.3How Do I Use a Rapid-Deployment Solution?

91.4Who Is the Rapid-Deployment Solution For?

101.5About this Business Process Document

122Architecture & Core Data Structures

123The SAP RDS Models

133.1The Planning Model

143.2The Rate Model

144SAP rapid-deployment solution for new G/L financial planning Dimensions

154.1Dimension Types

174.2ACCOUNT

184.3AUDIT_TRAIL

194.4COMPANY_CODE

194.5COST_CENTER

204.6CURRENCY

204.7FLOW

214.8FUNCTIONAL_AREA

214.9INPUTCURRENCY

224.10PROFIT_CENTER

224.11R_ACCOUNT

234.12R_ENTITY

234.13TIME

244.14TRADING_PARTNER

254.15VERSION

255Input Forms

265.1Input Form Style Sheet

265.2Cost Center Input Form (P&L)

305.3Profit Center Input Form (P&L)

335.4Balance Sheet Input Form

365.5Currency Rate Input Form

386Reports

386.1Reports Style Sheet

396.2Trend Report

406.3ECC Reconciliation Report

446.4Comparison Report

487Currency Conversion

487.1FX Trans Script

497.2Business Rules

507.3Reporting Currency

517.4FX Data Manager Package

517.5Update Input Currencies

528Net Result in the Balance Sheet Calculation

528.1Business Rule

528.2Logic Script

538.3Data Manager Package

549Data Requirements

569.1Master Data

589.2Transaction Data

5910Transports

5911Security

6312Appendix

6312.1Changing Dimension Names

6412.2Monthly Set Up

6512.3Delta Loading Transaction Data

1 Introduction

SAP rapid-deployment solution for new G/L financial planning is a business process that is used in companies to: Leverage ECC structures/data in their planning solution. Maintain additional master data/transaction data.

Perform Profit & Loss (P&L) and Balance Sheet (BS) planning and analysis (including automatic flow of net result (P&L) to the balance sheet) in their SAP Business Planning and Consolidation 10.0, version SAP NetWeaver application (BPC.)

Review Actual Profit & Loss and Balance Sheet results in the planning solution.

Compare Actual Profit & Loss and Balance Sheet to Plan/Forecast each month.

Retain historical archives of Plan/Forecast information.

Set the stage to drill-through to Actual ECC-based detail, when required.

SAP rapid-deployment solution for new G/L financial planning (RDS) meets these requirements by:

1. Delivering a best practice ECC-based P&L and Balance Sheet cube design, building upon the common structures in ECC and in SAP Business Planning and Consolidation2. Delivering best practice data integration packages to integrate Actual ECC-based P&L and Balance Sheet master and transaction data into the best practice SAP Business Planning and Consolidation.3. Providing a baseline P&L and Balance Sheet planning solution in SAP Business Planning and Consolidation.

4. Providing an RDS that functions both on a HANA and Non-HANA underlying database.Although the RDS as delivered is a common-denominator solution, one of its core values is the minimal time it takes to configure. The RDS does not contain company-specific or industry-specific content. It provides a foundation upon which required additions can be made.SAP rapid-deployment solution for new G/L financial planning is currently available in English only.

Planning Examples

The goal of the RDS package is to accelerate SAP Business Planning and Consolidation implementations at SAP ECC customers. The objective is to deliver RDS content that meets a common set of requirements. The RDS model can then be expanded by the customer to meet customer-specific and industry-specific requirements.1.1 Benefits of the SAP rapid-deployment solution for new G/L financial planning

The benefit of the RDS is to provide a baseline P&L and Balance Sheet planning solution in SAP Business Planning and Consolidation including:

Best practice data model based on the structures that exist in the SAP GL

Best practice data integration process that allows you to pull data from ECC into BPC

Best practice reports and input forms that leverage the relationships that exist in the SAP GL

The solution was built by SAP, for SAP, using SAPs best-of-breed planning solution, SAP Business Planning and Consolidation. With a predelivered model that is ready to connect to ECC-based structures, customers experience immediate value in their planning solution.1.2 What Is a Rapid-Deployment Solution?A rapid-deployment solution is an offering of software, preconfigured content, and a standard fixed scope service. The underlying software is SAP Business Planning and Consolidation, version 10 for NetWeaver.

The preconfigured content of the SAP rapid-deployment solution for new G/L financial planning includes:

A financial planning model directly derived from ECC-based data structures Preconfigured data integration packages

Baseline planning reporting, including trend, comparison, and reconciliation reports

Baseline planning input forms, including cost center, profit center, and balance sheet input formsThe fixed price service offering standardizes the deployment service. The fixed price service implements the content as-is using the customers own master and transaction data and does not include customer-specific customization.

RDS Asset Types

1.3 How Do I Use a Rapid-Deployment Solution?

The SAP rapid-deployment solution for new G/L financial planning enables end-to-end planning for the planning process. The preconfigured content introduces a starting point for creating plans and analytics required for a typical P&L and Balance Sheet planning process. The standardized service offering helps customers achieve a faster time to value, as well as reduce deployment risk.

The RDS delivers a best practice ECC-based P&L and Balance Sheet cube design by having the common structures modeled in ECC reflected in the SAP Business Planning and Consolidation solution. Key dimension and proposed names in for those dimensions are maintained. Key master data structures and the number and type of master data are mapped. Basic P&L and Balance Sheet structure and best practice reporting are processed in the RDS.

The RDS delivers ECC to SAP Business Planning and Consolidation data integration packages to integrate Actual ECC-based P&L and Balance Sheet master and transaction data into the best practice SAP Business Planning and Consolidation cube, including:

Method to map ECCs key-figure-based model to SAP Business Planning and Consolidations account based model (likely using 0FIGL_C10 (General Ledger (New): Transaction Figures) as a key table for transaction data

Method to update SAP Business Planning and Consolidation master data tables with ECC-based content

Method to transform/convert data between ECC and SAP Business Planning and Consolidation

Method to map local reporting currency in ECC to the SAP Business Planning and Consolidation Currency dimension

Method to map Trading partner in ECC to the SAP Business Planning and Consolidation Intercompany dimension

Method to reconcile the SAP Business Planning and Consolidation Actual data to the SAP NetWeaver BW-based ECC data

SAP Business Planning and Consolidation 10 NW includes standard transaction and master load packages. The intent is to deliver customized transaction (Load GL from ECC) and master data load packages (Load Cost Center Table from ECC) as part of the RDS.1.4 Who Is the Rapid-Deployment Solution For?

The SAP rapid-deployment solution for new G/L financial planning is meant for:

Profit Center planners Cost Center planners

Balance Sheet planners Operations, sales, and finance management team and executives1.5 About this Business Process DocumentThis business process document explains how to use the SAP rapid-deployment solution for new G/L financial planning for the planning business process. This document is specific to the features of the SAP rapid-deployment solution for new G/L financial planning. It assumes familiarity with general business planning and consolidation features and functions as well as standard P&L and Balance Sheet processes and terminology.

Read through this entire guide before implementing the SAP rapid-deployment solution for new G/L financial planning to become familiar with the steps and processes involved.

The RDS allows the customer to analyze their Actual P&L and Balance Sheet, compare it to ECC-based Actuals, and collect a P&L and Balance Sheet forecast/plan. The process requires that the Actual P&L and Balance Sheet are transferred out of ECC and into SAP Business Planning and Consolidation, setting the stage to plan the P&L and Balance Sheet and compare it to Actual. The cycle takes place monthly and involves three key process steps each month:

SAP Business Planning and Consolidation Monthly CycleTo succeed, the RDS relies on the combination of standard elements of the SAP Business Planning and Consolidation, version for NetWeaver stack including:

Standard business content (Infoprovider) for SAP NetWeaver: BW 0F1GL_C10

The native functionalities of SAP Business Planning and Consolidation to load data using Data Manager

A dedicated Planning application in a new environment called PLANNING_SHELL, comprised of common dimensions, templates, and standard business rules, for example foreign currency conversion.General Considerations

This document presents the RDS environment and the associated dimensions for the models PLANNING and RATES.

This document includes two main sections detailing the dimensions and their associated properties as well as a section on currency conversion.

2 Architecture & Core Data StructuresThis document serves as a reference that lists the dimensions and models included in the SAP rapid-deployment solution for new G/L financial planning environment. The dimensions mentioned here are intended to be used as a guide and can vary, depending on the unique requirements of each implementation. The models mentioned here include a general overview only.

Planning RDS Prerequisites and Scope

This diagram shows the load process for new G/L totals data from the ECC source system into InfoCube 0FIGL_C10 using standard business content. This RDS only focuses on loading the data from InfoCube 0FIGL_C10 onwards (red box in the previous diagram).

The extraction from ECC to SAP NetWeaver BW is left to the responsibility of the Client. The load from SAP NetWeaver BW to the application is done using the standard functionality of SAP Business Planning and Consolidation leveraging the Data Manager.3 The SAP RDS Models

The SAP rapid-deployment solution for new G/L financial planning includes two models:

Planning

Rate3.1 The Planning Model

The Planning model contains the Actual data downloaded each month from ECC. It includes input forms used to enter Planning data and their corresponding reports, as follows:Input Forms Plan:

Input P&L by Cost Center.

Input P&L by Profit.

Input Balance Sheet by Profit The input forms are further described in detail in the section Input Forms.

Reports: Reconciliation report: ECC in comparison with BPC.

Variance Analysis: Plan compared with Actual and Year over Year.

TrendThe reports are further described in detail in the section Reports.The Planning model also includes the logic required to run Currency Conversion. Rates for this process are automatically retrieved from the Rate application. The Currency Conversion is detailed in the section entitled Currency Conversion later in this guide. The Planning model also includes the logic to transfer the net result from the P&L to the Balance Sheet. This logic and the related building blocks are detailed in the section entitled Transfer P&L net result to the B/S later in this guide.The Planning model contains the following dimensions:

DimensionDescription

ACCOUNTMembers correspond to Profit & Loss and Balance Sheet accounts such as Revenue, Costs of Sales, and Total Assets.

AUDIT_TRAIL(Secure) A Data Source type dimension that shows where the data is coming from, for example: a source system, input form, adjustment.

COMPANY_CODE(Secure) An Entity type dimension that contains business units

COST_CENTER(Secure) Contains cost centers

CURRENCYContains local currency (LC) and euro (EUR)

FLOWA subtable to the Account dimension, the default member for P&L accounts is F_NONE (No Flow) and F_CLO (Closing Balance) for the Balance Sheet accounts. No detailed flows are included in the RDS.

FUNCTIONAL AREABreaks down data by Functional Area

PROFIT CENTER(Secure) Contains Profit Centers

TIMEContains time periods

TRADING PARTNERContains intercompany members

VERSION(Secure) Contains the types of data tracked, for example ACTUAL and PLAN.

These dimensions are detailed in the SAP rapid-deployment solution for new G/L financial planning Dimensions section.

3.2 The Rate Model

The Rate model contains the exchange rates downloaded each month from ECC. The rates are automatically supplied to the Planning model when Currency Conversion is run.

Users can also enter rates using the Currency Rate input form, detailed in the section entitled Input Forms later in this guide.The Rate model uses the following dimensions:DimensionDescription

INPUTCURRENCYContains all the currencies in which your company does business.

R_ACCOUNTContains the rate types used in currency conversion including AVG and END. AVGFLOW is a type included for currency conversion of the net P&L result in the Balance Sheet.

R_ENTITYContains a generic member GLOBAL

TIME(Secure) Contains time periods

VERSION(Secure) Contains the types of data tracked, for example ACTUAL and PLAN.

The dimensions are described in further detail in the Dimensions section.4 SAP rapid-deployment solution for new G/L financial planning Dimensions

This section summarizes the dimension types and provides a list of the dimensions included within the environment. It also provides additional design details for each dimension. Dimensions are delivered as representative samples with BPC. They can be configured to meet customer needs during implementation. Adding or removing dimensions is possible however requires additional work during configuration.

Templates and reports require modification when dimension types are added or removed. If particular dimensions are not needed, the user should not use that dimension, however also not remove it. Changing names of the dimensions is simple to do during implementation.

Measures is a standard SAP Business Planning and Consolidation dimension with standard usage to display periodic, QTD, or YTD values. It is not detailed further in the following sections.The SAP NETWEAVER BW import excludes leading zeros that are removed from all dimension member IDs for the ACCOUNT, COST_CENTER, PROFIT_CENTER, and TRADING_PARTER dimensions.

The SAP NETWEAVER BW import includes hierarchies for ACCOUNT, COST_CENTER, and PROFIT_CENTER. Other hierarchies are maintained in SAP Business Planning and Consolidation.

The following sections list Properties (called Attributes in SAP NETWEAVER BW) by dimension.

4.1 Dimension Types

SAP Business Planning and Consolidation utilizes a standard set of dimension types many of which have special uses. The dimension types and their uses are summarized as follows:DimensionDimension TypeDescription

ACCOUNTAccountStandard SAP Business Planning and Consolidation dimension. The Account members correspond to various planning key figures like: volumes, revenue, costs, price, and total assets. Account dimension properties are used to define, for example, rollups, standard planning methodologies and grouping criteria.

COMPANY_CODEEntityStandard SAP Business Planning and Consolidation dimension. Contains the business units used to drive the business process. Depending on your model design, the Entity type can be, for example, an operating unit and a geographic entity

AUDIT_TRAILData sourceStandard SAP Business Planning and Consolidation dimension. The data source dimension identifies where the data is coming from, for example, a source system, input forms, adjustments and manual entries.

FLOWSubtableStandard SAP Business Planning and Consolidation dimension. Breaks down account activity or flow. Per standard model setup, this allows you to flow, for example, beginning, ending, additions and deletions, in one account.

VERSIONCategoryStandard SAP Business Planning and Consolidation dimension. Contains the types of data you are going to track, for example, actual, plan and target. Members are set up to store plan versions, for example, BudgetV1 and BudgetV2.

COST_CENTERUser definedCustom SAP Business Planning and Consolidation dimension in the Planning RDS. The COST_CENTER dimension contains Cost Center master data populated from SAP NETWEAVER BW InfoObject 0COSTCENTER.

TRADING_PARTNERIntercompanyStandard SAP Business Planning and Consolidation dimension. Contains the intercompany codes for the entities.

TIMETimeStandard SAP Business Planning and Consolidation dimension. The Time dimension contains the time periods for which data is stored.

FUNCTIONAL_AREAUser definedCustom SAP Business Planning and Consolidation dimension in the Planning RDS. The FUNCTIONAL_AREA dimension contains Functional Area master data populated from SAP NETWEAVER BW InfoObject 0FUNC_AREA.

PROFIT_CENTERUser definedCustom SAP Business Planning and Consolidation dimension in the Planning RDS. The PROFIT_CENTER dimension contains Profit Center master data populated from SAP NETWEAVER BW InfoObject 0PROFITCENTER.

INPUTCURRENCYCurrencyStandard SAP Business Planning and Consolidation dimension. Contains the currencies in which a company does business.

CURRENCYCurrencyStandard SAP Business Planning and Consolidation dimension. Contains the currencies in which a company reports.

R_ACCTAccountStandard SAP Business Planning and Consolidation dimension. Contains the method with which accounts are handled in the Rate model during currency translation with valid entries including AVG and END.

R_ENTITYEntityStandard SAP Business Planning and Consolidation dimension. Contains a generic Global member per standard SAP Business Planning and Consolidation setup.

4.2 ACCOUNT

The members are loaded into SAP Business Planning and Consolidation from the standard SAP NETWEAVER BW InfoObject 0GL_ACCOUNT. The ACCOUNT dimension properties are as follows: The member IDs in the application include a prefix A_ appended to the SAP NETWEAVER BW GL Account ID. Leading zeros are removed.PropertyDescription

ACCTYPEStandard property in SAP Business Planning and Consolidation. Required.

Identifies the RDS account as one of the following:

INC Income

EXP ExpenseAST Assets

LEQ Liabilities and EquityStored against all dimension members to describe account behavior and treatment.

BW_ACCOUNTAccount ID as it appears in SAP NETWEAVER BW.

BW_CHRT_ACCTSThe originating ECC Chart of Accounts

ELIMACCNot required for the Planning RDS.

FIN_STMTDefines the type of Financial Statement the member belongs to. Balance Sheet accounts are defined as BS and Income Statement accounts are defined as PL.

IS_INPUTNot required for the Planning RDS.

RATETYPERate type used for converting the account: for example: AVG for P&L accounts and END for balance sheet accounts. AVGFLOW is used for the net income transfer account in the B/S.

ROW_SOURCEIdentifies whether the record is maintained in SAP NETWEAVER BW or SAP Business Planning and Consolidation.

SCALINGNot required for the Planning RDS.

TYPELIMNot required for the Planning RDS.

4.3 AUDIT_TRAIL

The AUDIT_TRAIL dimension was previously known as Data Source and is still identified as Data Source in some properties. It is managed solely from the Administration Console of SAP Business Planning and Consolidation and not populated from an SAP NETWEAVER BW InfoObject.

PropertyDescription

COPYOPENINGNot required for the Planning RDS.

DATASRC_STAGENot required for the Planning RDS.

DATASRC_TYPEDefines if the member is:

Input (I)

Manual Entry (M)

Automatically (A) generated by a calculation (formula, logic or business rule)DATASRC_TYPE A is a prerequisite for the member included in FX conversion with the IS_CONVERTED.

DIMLISTNot required for the Planning RDS.

IS_CONSOLNot required for the Planning RDS.

IS_CONVERTEDStored on all base dimension members to indicate that a base member is to have currency translation. Valid entries include:

Y Data source is included in currency conversion.

N or blank Data source is excluded from currency conversion.

OPENING_DATASRCNot required for the Planning RDS.


4.4 COMPANY_CODE

The dimension members are loaded from the standard SAP NETWEAVER BW InfoObject 0COMP_CODE. The member IDs in SAP Business Planning and Consolidation include a prefix CO_ appended to the SAP NETWEAVER BW Company Code ID. Leading zeros are removed.PropertyDescription

BPC_TRADING_PARTNERRepresents the Trading_Partner attached to the Company_Code in SAP Business Planning and Consolidation format.

BW_CHRT_ACCTSChart of Accounts associated with the Company Code

BW_COMPANY_CODECompany_Code value as stored in the SAP NETWEAVER BW OFIGL_C10 InfoProvider.

BW_TRADING_PARTNERTrading_Partner value as stored in the SAP NETWEAVER BW OFIGL_C10 InfoProvider.

CONTROL_LEVELNot required for the Planning RDS.

COUNTRYCountry associated with Company_Code

CTRL_CURRENCY_NOT_LCAssociated Level of controls with the Company_Code

CURRENCYInputCurrency value

ELIMNot required for the Planning RDS.

INTCONot required for the Planning RDS.

OWNERNot required for the Planning RDS.



4.5 COST_CENTER

The dimension members are loaded from the standard SAP NETWEAVER BW InfoObject 0COST_CENTER. The member IDs in SAP Business Planning and Consolidation include a prefix CC_ appended to the SAP NETWEAVER BW Company Code ID. Leading zeros are removed.PropertyDescription

BPC_COMPANY_CODERepresents the Company Code attached to the Cost Center in SAP Business Planning and Consolidation format.

BPC_FUNCTIONAL_AREARepresents the Functional Area attached to the Cost Center in SAP Business Planning and Consolidation format.

BPC_PROFIT_CENTERRepresents the Profit Center attached to the Cost Center in SAP Business Planning and Consolidation format.

BW_COMPANY_CODERepresents the Company Code format as stored in SAP NETWEAVER BW.

BW_COST_CENTERRepresents the Cost Center format as stored in SAP NETWEAVER BW.

BW_CO_AREARepresents the CO Area format as stored in SAP NETWEAVER BW.

BW_FUNCTIONAL_AREARepresents the Functional Area format as stored in SAP NETWEAVER BW.

BW_PROFIT_CENTERRepresents the Profit Center format as stored in SAP NETWEAVER BW.

CURRENCYCurrency attached to the Cost Center



4.6 CURRENCY

The Currency dimension members define the currency report views. Its members use the ISO format. Two currencies are delivered with the RDS: EUR and LC.PropertyDescription

CURRENCY_TYPEDefines whether the currency is used for Reporting (R) or Data Entry (L).

ENTITYNot required for the Planning RDS.

REPORTINGDefines whether the currency can be used for reporting (EUR = Y). The default reporting currency is EUR but can be modified as required.

4.7 FLOW

The FLOW dimension is primarily used in Consolidation models to help in preparing the Statement of Cash-Flow. The RDS does not deliver any Cash-Flow statement logic, business rules or templates. As delivered, the FLOW dimension contains two members: F_NONE for P&L accounts and F_CLO for Balance Sheet accounts.PropertyDescription

FLOW_TYPENot required for the Planning RDS.


4.8 FUNCTIONAL_AREA

The FUNCTIONAL_AREA dimension is loaded from the standard SAP NETWEAVER BW InfoObject 0FUNC_AREA. The member IDs in the application include a prefix FA_ appended to the SAP NETWEAVER BW Functional Area ID. Leading zeros are removed.The Functional Area has been added as a dimension even though it is used as a property of the Cost Center and Profit Center dimensions. It enables BPC to handle possible reclassification of Functional Areas and support functional P&L reporting (the combination Account and Functional Area Income Statements).PropertyDescription

BW_FUNCTIONAL_AREARepresents the Functional Area format as stored in SAP NETWEAVER BW.

ROW_SOURCEIdentifies if the record is maintained in SAP NETWEAVER BW or SAP Business Planning and Consolidation.


4.9 INPUTCURRENCY

The INPUTCURRENCY dimension uses the ISO format (for example: USD, AUD, and EUR). A standard set of currencies is provided during the SAP Business Planning and Consolidation installation. Additional currencies can be added or removed to match the requirements.PropertyDescription


MDDefines the conversion method (direct/indirect) (multiply/divide.)

REPORTINGValue of Y defines the currencies used for reporting.

4.10 PROFIT_CENTER

The PROFIT_CENTER dimension is extracted from the standard InfoObject 0PROFIT_CTR. The member IDs in the application include a prefix PC_ appended to the SAP NETWEAVER BW Profit Center ID. Leading zeros are removed.PropertyDescription

BW_CO_AREAControlling Area as stored in SAP NETWEAVER BW.

BW_PCA_DEPTDepartment of the Profit Center as stored in SAP NETWEAVER BW.

BW_PCA_HIENDHierarchy of the Department attached to the Profit Center as stored in SAP NETWEAVER BW.

BW_PROFIT_CENTERProfit Center as stored in SAP NETWEAVER BW.

BW_SEGMENTCharacteristic of Profit Center as stored in SAP NETWEAVER BW.



4.11 R_ACCOUNT

The dimension R_ACCT has a member for each type of rate that is required to be applied. The RDS includes only AVG (Average), END (End of Month), and AVGFLOW. The AVG rate is used for the Income Statement accounts. The END rate is used for the Balance Sheet accounts. The AVGFLOW method is used only to convert one account, the net result in the Balance Sheet.PropertyDescription

ACCTYPEAll accounts are defined as Assets (AST.)

RATETYPEFX for AVG and END; blank for AVGFLOW because it is calculated from the other rates.


4.12 R_ENTITY

R_ENTITY is used in the Rates model only.

PropertyDescription

CONTROL_LEVELNot required for the Planning RDS.

CTRL_CURRENCY_NOT_LCNot required for the Planning RDS.

CURRENCYNot required for the Planning RDS.

4.13 TIME

The TIME dimension is managed solely from the Administration Console in SAP Business Planning and Consolidation and is not populated from an SAP NETWEAVER BW InfoObject.

PropertyDescription

BASE_PERIODNumerical value for the Period

LEVELIndicates the period type.

MONTHNUMRepresents the month number as stored in SAP NETWEAVER BW.

PERIODMonth description in three characters

TIMEIDPeriod format as stored in SAP NETWEAVER BW: YYYYMMM

V_FLAGDefines whether a month appears in the input forms. The value A (Actual) indicates that the month is to be displayed in the input form as read-only. The value P (Plan) indicates that the month is to be displayed in the input form as open for user input. Blank values indicate that the month does not appear. The values are updated throughout the planning cycle by the BPC administrator.

YEARIndicates the calendar year.

4.14 TRADING_PARTNER

The TRADING_PARTNER dimension is loaded from the standard SAP NETWEAVER BW InfoObject 0PCOMPANY. The member IDs in SAP Business Planning and Consolidation include a prefix TP_ appended to the SAP NETWEAVER BW Company ID. Leading zeros are removed. TRADING_PARTNER is an Intercompany type dimension in BPC.

PropertyDescription

BPC_COMPANY_CODERepresents the Company_Code associated with the Trading_Partner in SAP Business Planning and Consolidation format.

BW_COMPANY_CODECompany_Code associated with the Trading_Partner as stored in SAP NETWEAVER BW.

BW_TRADING_PARTNERTrading_Partner as stored in SAP NETWEAVER BW




Configure Intercompany Eliminations

The Planning RDS is not configured for Intercompany Eliminations. Configuration effort is minimized, however, because the RDS includes the TRADING_PARTNER (InterCompany type) dimension in: the RDS Planning model RDS Planning reports and input forms, defaulting to member TP_NONE

Clients who are not performing eliminations ignore the TRADING_PARTNER member.Configuring Intercompany Eliminations is out of scope. This activity is scoped separately.4.15 VERSION

The VERSION dimension represents the BPC-delivered Category dimension. The dimension has been renamed to match the ECC/SAP NETWEAVER BW naming convention.PropertyDescription

CATEGORY_FOR_OPENot required for the Planning RDS.

CC_DEFAULTReferences the default member of the Cost Center dimension.

CC_DIMReferences the Cost Center dimension name.

FA_DEFAULTReferences the default member of the Functional Area dimension.

FX_DIFFERENCE_ONLYNot required for the Planning RDS.

FX_SOURCE_CATEGORYNot required for the Planning RDS.

IS_CONVERTEDIndicates if currency conversion is applied to the member.

OPENING_PERIODNot required for the Planning RDS.

OPENING_YEARNot required for the Planning RDS.

OWN_CATEGORYNot required for the Planning RDS.

OWN_PERIODNot required for the Planning RDS.

OWN_YEARNot required for the Planning RDS.

PC_DEFAULTReferences the default member of the Profit Center dimension.

PC_DIMReferences the Profit Center dimension name.

PLAN_MBR_DESCPlan member description (PLAN used in this RDS)

RATE_CATEGORYNot required for the Planning RDS.

RATE_PERIODNot required for the Planning RDS.

RATE_YEARNot required for the Planning RDS.

STARTMNTHNot required for the Planning RDS

TP_DEFAULTTrading Partner default member

YEARNot required for the Planning RDS.

5 Input Forms

The SAP rapid-deployment solution for new G/L financial planning includes three input forms in the Planning model: Cost Center Input Form (P&L), Profit Center Input Form (P&L), and Balance Sheet Input Form. It also includes an input form in the Rate model: the Currency Rate Input Form. To access the form:EPM Menu: ReportsOpen(Open Server Input Form Folder

The SAP rapid-deployment solution for new G/L financial planning includes the following input forms:

Cost Center Input Form (P&L) Profit Center Input Form (P&L) Balance Sheet Input Form

Currency Rate Input Form 5.1 Input Form Style Sheet

The look and feel of SAP Business Planning and Consolidation input forms are controlled by the EPM Formatting Sheet. Settings entered here are shared across all input forms to give consistency to the workbook behavior and appearance.

5.2 Cost Center Input Form (P&L)The form enables the planner to enter P&L plan data (in the Planning model) for combinations of Cost Centers and Accounts. Each row is required to include a base level Cost Center and base level Account. The user can define the form based on parent level or multiple Cost Centers and Accounts.The local currency of the Cost Center is displayed for the users convenience. The SAP Business Planning and Consolidation administrators configuration of the Time dimension determines the Time periods displayed- often one or more months of actual data and all the months in the planning horizon.If you want to replace a previously existing value with a null value, you are required to enter zero in the cell. If you send a blank cell (instead of a zero) it is not read as a null value.To access the form:EPM add-in for Excel: ReportsOpen(Server Input Forms(RDS_PI_Cost_Center.xltx

For documentation purposes, the following screen does not show all columns.

RDS_PI_Cost_Center.xltxInput Form Design and Formatting

The input form uses the standard style sheet. Yellow shaded cells accept data entry, gray shaded cells do not. Sections of the form are hidden from the user. Other input form design and formatting specifications include: A hidden section of the form contains a table with the dimension IDs, dimension descriptions and dimension default members (if applicable). This table is used as a central location for dimension information to be referenced as needed in other areas of the form. Columns H, I and J are not visible to the user but are a key component of the form. Data is retrieved at the highest level parent for Functional Area, Profit Center and Company Code. The data is sent to base level Functional Area, Profit Center, and Company Code members. The formulas in columns H, I, and J retrieve these members that are dimension properties of Cost Center. Column K, visible to the user, displays the input currency for reference. (Also a dimension property of Cost Center). All four columns (H K) are created by using local members. A fifth local member is used in Row 29 to display the V_Flag value that identifies the column as an Actual or Plan month. The primary visual clue is that the Plan months are yellow shaded. Cell I2 is used to define the Audit_Trail member for saved data (data is retrieved from the parent All_Audit_Trail). This value is hard-coded in the input form. Cells G14:G16 are an essential part of the input form (cell G16 is in gray font). The input form is composed of two reports, one visible to the users (shown in the previous screen capture) and a hidden report (gray font) used to save the data. This method is used because the dimensionality of the data being retrieved (summary) is different from the dimensionality of the data being sent (base). To meet this requirement cells G14:G16 contain EPMCopyRange functionality that overwrites the second report with formulas. The formula is:=IF(ROW()=29,OFFSET(G$1,0,-COLUMN() + MATCH(G15,$28:$28,0)), IF(INDIRECT(G$29&29)="Actual","",EPMSaveData(INDIRECT(G$29&ROW()),,$E16,$F16,$H16,$I16,$J16,G$28,$I$2))) In the first row of the copy range, the formula identifies the corresponding column in the first report. In the remaining rows, the EPMSaveData formula is applied, referencing the corresponding column in the first report. With this methodology the report is dynamic, regardless of the number of Actual and Plan months in the form. Input form maintenance. If the SAP Business Planning and Consolidation administrator modifies the layout of the form (for example: adds more rows at the top), the EPMCopyRange formula is modified to reference the correct rows. Rows 28 and 29 are hard-coded in the formula. They represent the first and second rows of the form. If these rows are moved by the administrator, the formula is updated.The formula also requires that in Row 1 the column letters be entered, and are displayed as follows:

Column Letters in Row 1Context Values

The following table shows the dimensions and context locks used in the form:

DimensionContext Lock

ACCOUNT(no filter)

AUDIT_TRAILALL_AUDIT_TRAIL

COMPANY_CODEALL_COMPANY_CODE

COST_CENTER(no filter)

CURRENCYLC

FLOWF_NONE

FUNCTIONAL_AREAALL_FUNCTIONAL_AREA

PROFIT_CENTERALL_PROFIT_CENTER

TIME(controlled by V_FLAG property)

TRADING_PARTNERTP_NONE

VERSIONPLAN

MEASURESPERIODIC

User Selections for Account and Cost CenterAll Context Pane dimensions are locked or hidden. The planner uses the Account and Cost Center Excel selectors in cells G25 and G26. The user can choose a parent or base level member for both dimensions.

A validation test has been built in for the Account dimension, Being a P&L input form, the user must select a P&L account. If a Balance Sheet account is selected by mistake, the following occurs: Warning 1: The Account selection cell (G26) appears with red fill (conditional formatting) Warning 2: A red message appears in cell K26

It is achieved via the forms validation section: Cell R15 retrieves the FIN_STMT property of the selected account. If it is BS, the warning mechanism is activated.

Cell N16 (and BPC behavior) limits the refresh to one Account/Cost Center row.A screenshot of the validation section is displayed as follows:

Cost Center input form validation section

How to Use the Input Form

1. Select the appropriate Cost Center and Account in cells G25 and G26.

2. Refresh the form.

3. Enter Plan data in the yellow shaded cells.

4. Save the entries.

5. Verify that the message is received indicating successfully saved data.

6. Refresh the form and the Plan data is displayed.How to Maintain the Input Form The administrator can choose the Actual and Plan columns displayed by modifying the V_Flag property of the Time dimension (A for Actual months, P for Plan months). The form automatically enables both a change in the number of displayed months and the Actual vs Plan identification. These Cost_Center properties must be present and up-to-date: BPC_Functional_Area, BPC_Profit_Center, BPC_Company_Code, and Currency. The names of standard and user-defined dimensions can be modified without adverse impact to the input form. However, modifying dimension names requires updating the relevant Version dimension properties CC_DIM, FA_DIM, and/or PC_DIM. The Audit_Trail member for saved data is hardcoded in cell I2 as BPC_INPUT. Any change to this member requires a modification to the template. Cell G16 is formatted as a gray font, locked cell. This formatting is applied to the second (hidden) report through the EPMCopyRange function and a second formatting style sheet5.3 Profit Center Input Form (P&L)This input form is used in the Planning model to enter data by Company Code, Profit Center, and Account for periods identified in the system as plan (specifically TIME property V_FLAG = P). The planner enters plan data for specific Company Code, Profit Center, and Account combinations. Periods containing actuals (specifically TIME property V_FLAG = A) are displayed as reference for the user.Actual data is retrieved at the parent level for Audit Trail, Functional Area, and Trading Partner while plan data is saved to a fixed Audit Trail member, BPC_Input, and user-selected Functional Area and Trading Partner members. If you want to replace a previously existing value with a null value, you are required to enter zero in the cell. If you send a blank cell (instead of a zero) it is not read as a null value.

To access the form:EPM add-in for Excel: ReportsOpen(Server Input Forms(RDS_Profit_Center.xltx


RDS_PI_Profit_Center.xltxForm Layout and Formatting

The input form uses the standard style sheet. Yellow shaded cells accept data entry, gray shaded cells do not.The input form displays Profit Center and Account dimensions in rows and the Time dimension in columns. The Time dimension is filtered using the Time dimension property V_FLAG to display periods set to Actual (A) and Plan (P.)The form has 5 Excel dimensions selectors for Profit Center, Company Code, Account, Functional Area, and Trading Partner. The Profit Center and Account selectors display all members accessible to the planner. The Company Code selector is filtered to limit selection to base level members (CALC=N). Functional Area and Trading Partner selectors: The user can override the defaults (Functional Area FA_NONE and Trading Partner TP_NONE) with another base-level member.Other formatting specifications include:

The hidden section of the report contains a table with the dimension IDs, dimension descriptions and dimension default members (if applicable). This table is used as a central location for dimension information to be referenced as needed in other areas of the report. A local member is used in Row 33 to display to V_Flag value, notifying the user whether the column represents an Actual or Plan month. The primary visual clue is that the Plan months are yellow shaded.Hidden rows are displayed as follows:

Profit Center input form hidden rowsContext Values



ACCOUNT(no filter)


COMPANY_CODE(CALC=N)

COST_CENTERCC_NONE

CURRENCYLC

FLOWF_NONE


PROFIT_CENTER(no filter)

TIME (controlled by V_FLAG property)

TRADING_PARTNERALL_TRADING_PARTNERS

VERSIONPLAN

MEASURESPERIODIC

A validation test has been built in for the Account dimension and consists of: Being a P&L input form, the user must select a P&L account. If a Balance Sheet account is selected by mistake, the following occurs:

Warning 1: The Account selection cell (G28) appears with red fill (conditional formatting)

Warning 2: A red message appears in cell H28

It is achieved via the forms validation section: Cell M15 retrieves the FIN_STMT property of the selected account. If it is BS, the warning mechanism is activated.

Cell M17 (and BPC behavior) limits the refresh to one Account/Profit Center row.A screenshot of the validation section is displayed as follows:

Profit Center input form validation section

How to Use the Input Form1. Select the appropriate Profit Center, Company Code, Account, Functional Area, and Trading Partner.

2. Refresh the form.

3. Enter Plan data in the cells shaded yellow.

4. Choose the Save Data icon.

5. Validate that the message is received indicating successfully saved data.

6. Refresh the form and the Plan data remains.How to Maintain the Input FormThe form dynamically updates the input columns from the TIME dimension V_FLAG property and requires no maintenance within the form itself.If the name of the base-level member of Audit Trail (BPC_Input) used to save data is changed, the input form is modified in cell I5.

5.4 Balance Sheet Input Form

This input form is used in the Planning model to enter data by Company Code, Profit Center, and Account for periods identified in the system as plan (specifically TIME property V_FLAG = P). The planner enters plan data for specific Company Code, Profit Center, and Account combinations. Periods containing actuals (specifically TIME property V_FLAG =A) are displayed as reference for the user.

Actual data is retrieved at the parent level for Audit Trail, Functional Area, and Trading Partner. Plan data is saved to fixed members for these dimensions: Audit Trail (BPC_Input), Functional Area (FA_NONE), and Trading Partner (TP_NONE). If you want to replace a previously existing value with a null value, you are required to enter zero in the cell. If you send a blank cell (instead of a zero) it is not read as a null value.

To access the form:EPM add-in for Excel: ReportsOpen(Server Input Forms(RDS_Balance_Sheet.xltx


RDS_PI_Balance_Sheet.xltxFormatting

The input form uses the standard style sheet. Yellow shaded cells accept data entry, gray shaded cells do not.The balance sheet form displays Profit Center and Account dimensions in rows and the Time dimension in columns. The Time dimension is filtered using the time dimension property V_FLAG to display periods set to Actual (A) and Plan (P).The form has 3 Excel dimension selectors at the top of the report. The Profit Center and Account selectors display all members accessible to the planner. The Company Code selector is filtered to limit selection to base level members (CALC=N).Actual data is retrieved at the parent level for Audit Trail, Functional Area, and Trading Partner. Plan data is saved to fixed members for these dimensions: Audit Trail (BPC_Input), Functional Area (FA_NONE), and Trading Partner (TP_NONE).

Other formatting specifications include:

The hidden section of the report contains a table with the dimension IDs, dimension descriptions and dimension default members (if applicable). This table is used as a central location for dimension information to be referenced as needed in other areas of the form. A local member is used in Row 31 to display to V_Flag value, notifying the user whether the column represents an Actual or Plan month. The primary visual clue is that the Plan months are yellow shaded.Hidden rows are displayed as follows:

Balance Sheet Input Form: hidden rows

Context Values



ACCOUNT(no filter)


COMPANY_CODE(CALC=N)

COST_CENTERCC_NONE

CURRENCYLC

FLOWF_CLO



TIME (controlled by V_FLAG property)


VERSIONPLAN

MEASURESPERIODIC

A validation test has been built in for the Account dimension and consists of: Being a Balance Sheet input form, the user must select a Balance Sheet account. If a P&L account is selected by mistake, the following occurs:

Warning 1: The Account selection cell (G28) appears with red fill (conditional formatting)

Warning 2: A red message appears in cell H28

It is achieved via the forms validation section: Cell M15 retrieves the FIN_STMT property of the selected account. If it is PL, the warning mechanism is activated.

Cell M17 (and BPC behavior) limits the refresh to one Account/Profit Center row.A screenshot of the validation section is displayed as follows:

Balance Sheet input form: validation section

How to Use the Input Form1. Select the appropriate Profit Center, Company Code, and Account 2. Refresh the form.

3. Enter Plan data in the cells shaded yellow.

4. Click the Save Data icon.

5. Validate that the message is received indicating successfully saved data.

6. Refresh the form and the Plan data remains.How to Maintain the Input FormThe form dynamically updates the input columns from the TIME dimension V_FLAG property and requires no maintenance within the form itself.If the names of the base-level members of Audit Trail (BPC_Input), Trading Partner (TP_NONE) and Functional Area (FA_NONE) used to save data are changed, the input form is modified in cells I5, I7 and I12. 5.5 Currency Rate Input FormThis input form is used by an SAP Business Planning and Consolidation administrator in the Rates model to enter currency conversion rates for each input (local) currency used in the system. These values are used in the logic package and/or default logic for currency conversion from input to reporting currency. The form displays only those months open for input in the planning horizon. No actuals are displayed. For every currency, two rate types can be entered (an average rate for P&L accounts and an End of Month rate for Balance Sheet accounts).To access the form:EPM add-in for Excel: ReportsOpen(Server Input Forms(RDS_PI_Currency_Rates.xltx


RDS_PI_Currency_Rates.xltxFormatting

The input form uses the standard style sheet. Yellow shaded cells accept data entry, gray cells do not. Input cells are formatted to use four decimals places, as appropriate for currency rates.The hidden section of the report contains a table with the dimension IDs, dimension descriptions and dimension default members (if applicable). This table is used as a central location for dimension information to be referenced as needed in other areas of the report.Context Values

All dimensions in the Context Pane are locked. The rows are defined by the members of the INPUTCURRENCY and R_ACCOUNT dimension. The columns are defined by the Time dimension V_Flag property (months with a V_Flag value of P are displayed).The following table shows the dimensions and context locks used in the form:


INPUTCURRENCY(row axis is Base Level)

R_ACCOUNT(AVG and END)

R_ENTITYGLOBAL

TIME(controlled by V_FLAG property)

VERSIONPLAN

MEASURESPERIODIC

How to Use the Input Form

1. The input form refreshes upon opening.

2. No changes to the context are necessary.

3. Enter data in the yellow shaded cells.

4. Save the entries.5. Validate the message is received indicating successfully saved data.

6. Refresh the form and the Plan data is displayed.How to Maintain the Input Form

All dimensions in the Rate model are standard dimensions (A, C, E, R, and T). Any changes to the dimension names are automatically accommodated by the input form.

The title of the Input Currency column links to the table in the hidden area. There is no other Excel logic within the input form.6 Reports

The SAP rapid-deployment solution for new G/L financial planning includes the following reports, in the Planning model: Trend Report ECC Reconciliation Report

Comparison Report

These reports are reviewed in the following sections of the BPD.

To open a report:EPM Menu: ReportsOpen(Open Server Report Folder

6.1 Reports Style Sheet

The look and feel of SAP Business Planning and Consolidation reports is controlled by the EPM Formatting Sheet. Settings made here are shared across all reports to give consistency to workbook behavior and appearance.

EPM Report Style Sheet6.2 Trend Report

The report displays a yearly trend for a specific dimension. The columns represent the TIME dimension over 12 months and the rows represent the ACCOUNT dimension.Rows can be updated with any dimension using the Edit Report command in the ribbon or the EPM Pane in the Excel sheet. The user is recommended to maintain TIME dimension in the columns.To access the report:EPM add-in for Excel: ReportsOpen(Server Input Forms(RDS_PO_Trend.xltx


RDS_PO_Trend.xltxFormatting

The Trend report uses the standard report style sheet EPM STYLE SHEET REPORT.The hidden section of the report contains:

A table with the dimension IDs, dimension descriptions, and dimension default members. This table is used as a central location to look up dimension information. A section that determines the row dimension referenced as the row dimension label. If the Administrator changes the layout of report, this formula may require modification (refer to the How to Maintain the Report section)Functionality used to warn users of the potential data issue when displaying a parent level entity in local currency. The combination can result in multiple local currencies aggregating to a parent level entity which can result in inaccurate data. The warning message is displayed as follows:Warning: Aggregated data may not be valid if all underlying Company Codes do not use the same Local Currency

Context Values

No dimensions are locked within the Context Pane, thus providing full flexibility to the user.How to Use the ReportThe Trend Report is flexible so the user can display any dimension by TIME. The user can change the row dimension using the Edit Report command in the ribbon or the EPM Pane in the Excel sheet. The user can drill down on the row dimension to see child level detail.

When the user selects a parent-level value for the Entity dimension and selects Local Currency for the Currency dimension, a warning message appears. The user is warned that aggregated data might not be valid. It is the users responsibility to understand whether the selected parent-level entity has children using different local currencies.How to Maintain the ReportThe formulas in cells B18 and C18 determine which dimension is being used in the Rows and is used to create the column label in cell B29. The formula in cell B18 uses Excels OFFSET function to reference the first row of data in the report, cell B30. If the administrator modifies the layout of the report, the administrator must also verify that the formula in cell B18 continues to reference (via the OFFSET function) the first row of data.6.3 ECC Reconciliation Report

This Planning model report is used to reconcile monthly transaction data loaded into SAP Business Planning and Consolidation with the ECC source system data. The reconciliation report is built to display data in a layout similar to the FC10 transaction code in ECC.To access the form:EPM add-in for Excel: ReportsOpen(Server Input Forms(RDS_PO_ECC_Reconciliation.xltx


RDS_PO_ECC_Reconciliation.xltxFormatting

The reconciliation report uses EPM STYLE SHEET REPORT RR, a modified version of the standard report style sheet. It differs from the standard by displaying data with two decimal places (example XXXX.XX) to match the format of the FC10 financial statement.The reconciliation report displays the Account dimension in rows and the Time dimension in columns. The Account dimension displays the selected members and children. The user can double click to drill down to lower level Accounts. The Time dimension has a fixed layout displaying the two periods selected by the user. Each row displays the Account Type and the absolute difference between Time periods.The hidden section of the report contains:

A table with the dimension IDs, dimension descriptions, and dimension default members. This table is used as a central location to look up dimension information.

Calculations in cells B18 and C18 determine the row dimension label in cell B30. If the administrator changes the layout of report, this formula might require modification (for more information, refer to the How to Maintain the Report section.) Functionality used to warn users of the potential data issue when displaying a parent level entity in local currency. This combination can result in multiple local currencies aggregating to a parent level entity and could result in inaccurate data. The warning message is displayed as follows:Warning: Aggregated data may not be valid if all underlying Company Codes do not use the same Local Currency

Reconciliation report hidden rows

Context Values



ACCOUNT(no filter)

AUDIT_TRAILBW_GL_SOURCE

COMPANY_CODEALL_COMPANY_CODE

COST_CENTERALL_COST_CENTER

CURRENCY(no filter)

FLOWF_TOT


PROFIT_CENTERALL_PROFIT_CENTER

TIME(no filter)


VERSIONACTUAL

MEASURESPERIODIC

How to Use the ReportThe reconciliation report is used on a monthly basis to verify that data loads match ECC, most often by the SAP Business Planning and Consolidation administrator. The report user controls the report data by using:

The Context Pane to select Currency and Measures.

The reports Excel selectors for Time (periods 1 and 2) and Account. The user can double click to drill down to select child level detail. The standard Edit Report function can be used to select multiple Account nodes (for example, to select both Balance Sheet and P&L data).

How to Generate Financial Statements (FC10 in ECC)The FC10 transaction generates a report with 2 columns of YTD data based upon user selections with a difference column for comparison. The following parameters are based on the sample data loaded in BPC as part of the RDS package. The parameters are to be updated to match the source system. For example, the chart of accounts might be different from INT.1. Log in to the ECC system

2. Process transaction FC10.

3. For sample parameters, make the following entries:

Chart of Accounts INT Company code 1000, 0005, 2000, 2400, 2500 Currency Type 30

Financial Statement Version INT and Language - EN Report Year 2009 Reporting Periods 1 -1 Comparison Year 2009, and Comparison Periods 2 - 2

List Output ALV Tree Control4. Press F8 to execute the report.

When the BPC reconciliation report and FC10 report have been generated, the results can be compared. The user can drill down in both reports to identify specific items that do not match.

FC10 Financial Statement

How to compare the results from FC10 to BPC

YTD Format The FC10 transaction reports results in the YTD format for both Balance Sheet and Income Statement accounts. In BPC, Balance Sheet accounts appear in the YTD format for ACCTYPE = AST and LEQ independent of the reports Measure selection. To reconcile Income Statement accounts, compare the BPC YTD measure to ECC or compare the ECC difference column to the BPC PERIODIC measure. Credit Positive - Transaction data for Account Types LEQ and INC have their signs reversed during the BPC data load process (using the Transformation creditpositive parameter.) Therefore, Accounts tagged with LEQ and INC appear with opposite signs between the FC10 transaction and BPC. Currency - The documented FC10 parameters perform the reconciliation at a group currency (currency type = 30) It allows for reconciliation across company codes independent of the specific local currency of each company code. Additional reconciliation is processed at the individual Company Code level by setting currency type to 10 in the FC10 transaction and selecting LC for Currency in BPC. Account detail The user can drill down on both reports Account rows to investigate the underlying child detail.How to Maintain the ReportThe report displays standard dimensions in the rows, columns, and sub titles and enables changes to dimension names. The row dimension is fixed to display the member and children of the user-selected accounts.6.4 Comparison Report

The Comparison Report allows the user to compare Account values by:

TIME: a year-over-year comparison for two selected Versions. VERSION: a Version comparison (for example: Actual and Plan) over two Time periods (selected period compared to prior year).

To access the report:EPM add-in for Excel: ReportsOpen(Server Input Forms(RDS_PO_Comparison.xltx

For documentation purposes, the following screen does not show all the columns.

RDS_PO_Comparison.xltx View 1 - Time Comparison

RDS_PO_Comparison.xltx View 2 - Version Comparison

Formatting

This report uses the standard report style sheet, EPM STYLE SHEET REPORT.

The report uses yellow-shaded Excel selector cells for Time & Version.

The hidden section of the report contains:

A table with the dimension IDs, dimension descriptions, and dimension default members. This table is used as a central location to look up dimension information.

Calculations in cells B18 and C18 determine the row dimension label in cell B31. If the Administrator changes the layout of report, this formula may require modification. Functionality used to warn users of the potential data issue when displaying a parent level entity in local currency. This combination can result in multiple local currencies aggregating to a parent level entity and could result in inaccurate data. The warning message is displayed as follows:Warning: Aggregated data may not be valid if all underlying Company Codes do not use the same Local Currency

Comparison Report: hidden rowsContext Values



ACCOUNT(row axis)

AUDIT_TRAIL(no filter)

COMPANY_CODE(no filter)

COST_CENTER(no filter)

CURRENCY(no filter)

FLOW(no filter)

FUNCTIONAL_AREA(no filter)


TIME(column axis)

TRADING_PARTNER(no filter)

VERSION(column axis)

MEASURES(no filter)

How to Use the Report

The user selects the two Versions for comparison and the Time period (the prior year period is derived from this selection).The report provides two types of comparisons:

Time Comparison: by default the report compares the selected Time period to the same period of the previous year for both selected Versions. For example, this view compares Actual current year to Actual last year and compares Plan current year to Plan last year. Version Comparison: To compare two Versions for the same Time periods, the user can change the column axis dimension order so Time is before Version. In this view, the report can compare Actual to Plan for the selected Time period and for the same period last year. To modify the dimension order, use Edit Report in the ribbon or the EPM Pane in the Excel sheet.

Column Axis Layout for View 1 - Time Comparison

Column Axis Layout for View 2 - Version ComparisonThe user can drill down on the row dimension to see child level detail.

How to Maintain the ReportThe report displays standard dimensions in the rows, columns, and sub titles and enables changes to dimension names.7 Currency ConversionThe Financial Planning Rapid Deployment Solution (RDS) uses a custom adaptation of the generic Currency Conversion capability delivered with the application. The RDS conversion translates Plan data only. It is expected that Actuals are converted within ECC and loaded into the RDS.Rates are entered in the Rate model by downloading from SAP NETWEAVER BW or manual entry using an input form.

Planning data is entered in the Planning model in Local Currency (LC). When the data is sent, the Currency Conversion logic is automatically triggered via Default Logic. It can also be triggered by using a Data Manager package.7.1 FX Trans Script

The Currency Conversion Function referenced in the Default Logic script The Currency Conversion logic referenced in the FX Restatement Data Manager package (for more information refer to section 7.4 of this document).7.2 Business Rules

The currency conversion business rule defines how the data loaded are converted for a specific flow (F_NONE by AVG for P&L accounts, F_CLO by END for Balance Sheet accounts) or account (AVGFLOW method for net income in the BS).

A view of the three implemented methods:

The AVG method converts the F_NONE flow using an average rate. It is used for P&L accounts.

The END method converts the F_CLO flow using a period end rate. It is used for BS accounts:

The AVGFLOW method is only used by the net income in the BS account. It converts the closing flow at an average rate (as it is a P&L account), however to ensure that the balance sheet remains in balance, it also calculates a CTA (currency translation adjustment).

The CTA account used is A_CTAdj. It is the calculated difference between the currency translation of net income by ending and average rates.

7.3 Reporting Currency

The RDS package employs a single reporting currency of euro (EUR). It can be modified to another single currency as required. The three-step process to modify the reporting currency:1. Currency dimension. Add the replacement currency member to the Currency dimension. Delete the existing EUR dimension member. Update the REPORTING property of the new currency member to Y and set its CURRENCY_TYPE property to R.The following screen capture displays the RDS Currency dimension setup. To use another currency as the reporting currency, replace EUR.

2. Inputcurrency Dimension: For the new reporting currency, set the REPORTING property of the member to Y. Remove the Y REPORTING property from the EUR member. (If the new reporting currency was not previously a member of INPUTCURRENCY, it has to be added).

3. Update the currency conversion rates via the Currency Rate input form as required. 7.4 FX Data Manager Package

In addition to being triggered by Default Logic, the currency conversion logic can be run via the Data Manager Package, FX_Restatement, located in the RDS Packages package group. When running the package, the user specifies the data to be translated by Company Code.

7.5 Update Input Currencies

The INPUTCURRENCY dimension members define the local currencies used for planning purposes. The RDS package includes 14 local currencies; local currencies can be modified as required. Each COMPANY_CODE is assigned one INPUTCURRENCY dimension member. After modifying local currency dimension members (if necessary), the translation rates can be submitted using the Currency Rate input form.8 Net Result in the Balance Sheet CalculationThe RDS supports both P&L and Balance Sheet (BS) planning. A real-life sample calculation is included to transfer the net income result from the P&L to the balance sheet for the Version, Plan. The RDS assumes that actuals loaded from the ECC already incorporate this calculation. The user can add other similar calculations.The individual elements used to set up this sample transfer discussed in the following sections.

8.1 Business Rule

The following account-based calculation rule has been implemented:Net income (P&L account A_NET_INCOME, flow F_NONE) is periodically transferred to a specially created account (A_RE_YTDNetIncome). The Flow value is set as F_CLO (balance sheet account). The Audit Trail is set as BPC_CALC (differentiates calculated values from input and loaded values).

The Account A_RE_YTDNetIncome is assigned the Rowsource property of BPC.

8.2 Logic ScriptThe following logic script zeros out the CTA account, calls the business rule previously described and executes a currency conversion to ensure that the new calculated account is converted.

8.3 Data Manager PackageA RDS Business Rules Data Manager package has been created to execute the calculation.

When running the package, the user specifies the Time and Version. In the shipped version of the RDS, the user would select Version: Plan and Time: March 2009 through December 2009. It is adjusted based on user customizations and planning horizon.

9 Data Requirements Delta transaction data is imported from the SAP NETWEAVER BW SAP Business Planning and Consolidation staging cube ZFIGL10P. Imported data is filtered through Transformation and Conversion files, to assure proper formatting in the application as follows:

Transformation between InfoCubes 0FIGL_C10 and ZFIGLC10P

The Staging InfoCube ZFIGLC10P is populated from the standard business content InfoCube 0FIGL_C10.

Mapping InfoCube 0FIGL_C10 to the Staging Cube ZFIGLC10PThe following diagram shows the end to end data flow for the SAP Business Planning and Consolidation to SAP NETWEAVER BW delta load:

End to End Data Flow9.1 Master Data

Master data, including Attributes, Texts, and Hierarchies, are loaded from standard new G/L business content. The following objects are loaded:SAP NETWEAVER BW Source InfoObjectSAP Business Planning and Consolidation target DimensionType of data loaded

0GL_ACCOUNTACCOUNTAttribute, Text, Hierarchy

0COMP_CODECOMPANY_CODEAttribute, Text

0FUNC_AREAFUNCTIONAL_AREAAttribute, Text

0PCOMPANYTRADING_PARTNERAttribute, Text

0COSTCENTERCOST_CENTERAttribute, Text, Hierarchy

0PROFIT_CTRPROFIT_CENTERAttribute, Text, Hierarchy

The customer is responsible for ensuring the SAP NETWEAVER BW Source InfoObjects are loaded with the most recent Attribute, Text, and Hierarchy master data.Conversion and Transformation Files

The Master Data import requires dimension-specific Conversion files and Transformation files to filter and format the data in the application. The following table shows the Conversion and Transformation files that are delivered with the RDS:

DimensionConversion and Transformation Files

ACCOUNT BW_ACCOUNT_HIER_TFORM.xls

BW_ACCOUNT_TFORM.xls

BW_ACCOUNT_HIER_CONV.xls

BW_ACCOUNT_CONV.xls

COMPANY_CODE BW_COMPANY_CODE_ TFORM.xls

BW_COMPANY_CODE_CONV.xls

COST_CENTER BW_COST_CENTER_TFORM.xls

BW_COST_CENTER_HIER_TFORM.xls

BW_COST_CENTER_CONV.xls

BW_COST_CENTER_HIER_CONV.xls

FUNCTIONAL_AREA BW_ FUNCTIONAL_AR EA_TFORM.xls

BW_ FUNCTIONAL_AREA_CONV.xls

PROFIT_CENTER BW_ PROFIT_CENTER_TFORM.xls

BW_PROFIT_CENTER_HIER_TFORM.xls

BW_PROFIT_CENTER_CONV.xls

BW_PROFIT_CENTER_HIER_CONV.xls

TRADING_PARTNER BW_ TRADING_PARTNER_TFORM.xls

BW_ TRADING_PARTNER_CONV.xls

9.2 Transaction Data

The transaction data is loaded from the SAP NETWEAVER BW InfoCube ZFIGLC10P. This InfoCube is custom built in SAP NETWEAVER BW and acts as a staging cube for SAP Business Planning and Consolidation data. The cube sources its data via a delta process from the SAP NETWEAVER BW standard Business Content for New G/L totals data. The totals data is loaded from the underlying SAP ECC system.

Transaction Data FlowThe SAP NETWEAVER BW standard business content provides InfoCube 0FIGL_C10 from which the data is loaded into the staging cube. It is the responsibility of the customer to ensure the cube 0FIGL_C10 has been activated. Depending on the customer needs, it is loaded periodically with the latest transaction data.InfoCube 0FIGL_C10 and the underlying data model are enhanced by adding the Trading Partner (InfoObject 0PCOMPANY).

Planning RDS Prerequisites and ScopeThe previous diagram displays the load process for New G/L totals data from the ECC source system into InfoCube 0FIGL_C10 using standard business content. This RDS focuses only on loading the data from InfoCube 0FIGL_C10 onwards (red box in the previous diagram).The extraction from ECC to SAP NETWEAVER BW is the clients responsibility. The load from SAP NETWEAVER BW to the application uses the standard functionality of SAP Business Planning and Consolidation leveraging the Data Manager.10 Transports

The following approach is recommended to move the functionality created as part of this RDS into a client system:All SAP Business Planning and Consolidation developments are moved by using the backup and recovery tool transaction UJBR. UJBR allows moving only objects that were generated through the application. The RDS covers the creation of a staging cube and custom InfoObjects; these objects are moved using standard SAP NetWeaver BW transport functionality. They could also be manually created in SAP NETWEAVER BW.For additional information on the use of the backup and recovery tool and the importing and/or extracting of data refer to the building block configuration guides associated with the RDS.11 Security

The Financial Planning Rapid Deployment Solution is delivered with three generic roles that define access to SAP Business Planning and Consolidation. These roles are:

SAP Business Planning and Consolidation Administrator

SAP Business Planning and Consolidation Planner

SAP Business Planning and Consolidation AnalystThe following tables show all application tasks, broken out by the folders in which the tasks appear by selecting:Application administrative screenSecurity(Tasks Profiles(Tasks

The columns indicate the three initial roles defined in RDS security.

The roles and their associated tasks are offered as points of departure to build the required client-specific security.

In the following tables, X indicates that a specified Task/Role is enabled. Blank indicates that a specified Task/Role is not enabled.Administration Tasks

TaskAdministratorPlannerAnalyst

Manage ModelsX

Manage EnvironmentsX

Manage Business RulesX

Manage DimensionsX

Manage Data Locks and Work StatusX

Manage Environment StatusX

Manage Drill ThroughsX

Manage Document TypesX

View ModelsX

View EnvironmentsX

View Business RulesX

View DimensionsXXX

View Data Locks and Work StatusX

View Drill ThroughsX

View Document TypesX

Analysis and Collection

TaskAdministratorPlannerAnalyst

Manage TemplatesX

Use Input Forms and Save DataXX

Run Drill Throughs XXX

AuditTaskAdministratorPlannerAnalyst

Manage AuditX

View Audit SettingsX

Business Process FlowsTaskAdministratorPlannerAnalyst

Use BPFsXX

Manage BPFsX

View BPF SettingsX

Collaboration/CommentsTaskAdministratorPlannerAnalyst

Use Offline DistributionX

Use Offline CollectionX

Administer CommentsX

Edit CommentsXX

Data ManagerTaskAdministratorPlannerAnalyst

Run Admin PackagesX

Edit PackagesX

Edit Transformation FilesX

Edit Conversion FilesX

Edit Delta InitializationX

Cancel Any User PackagesX

Edit Package Schedules for Any UsersX

Run PackagesX

Folder Access/JournalTaskAdministratorPlannerAnalyst

Edit Contents of Public FolderX

Manage JournalsX

Edit JournalsX

Post JournalsX

View JournalsX

Unpost JournalsX

Lock/Unlock JournalX

Reopen JournalsX

View Journal TemplatesX

Publish/System ReportsTaskAdministratorPlannerAnalyst

Edit Book Distribution TemplatesX

Publish and Delete BooksX

Run Documents from EPM add-inX

Run Audit ReportsX

Run Comment ReportsX

Run Work Status ReportsX

Run Security ReportsX

System Security/Web Reporting/Web Service/Work StatusTaskAdministratorPlannerAnalyst

Manage SecurityX

Use System When OfflineX

View SecurityX

Edit DocumentsX

Edit ReportsX

Administer DocumentsX

Edit WorkspacesX

Edit DashboardsX

Access application from FIM and SSMX

Use Work StatusXX

Secure Dimensions

In the Planning model the following dimensions are secure, as delivered in the Planning RDS:

AUDIT_TRAIL

COMPANY_CODE

COST_CENTER

PROFIT_CENTER

VERSION

In the Rates model the following dimensions are secure, as delivered in the Planning RDS:

TIME

VERSION

Each secure dimension is required to be referenced in a Data Access Profile in order for a user to have Read or Read/Write access to that dimension. If a users Data Access Profile omits a secure dimension, the user is not able to access the model.

SAP Business Planning and Consolidation administrators can create or modify Data Access Profiles in the application Administration tab:Application Administrative tabSecurity(Data Access Profiles

Data Access Profile Notes: To support planning, the user may need to set up Data Access Profiles with the following considerations:

Users have write access to the NONE members of each secure dimension. For example, COST_CENTER is a secure dimension but users have to be able to write to member CC_NONE. Users have appropriate write access to the correct COST_CENTER, PROFIT_CENTER and COMPANY_CODE combinations since these three dimensions are typically linked in defining valid data entry records. For example, if Cost Center CC_10001000 is linked to Profit Center PC_100100 and Company Code CO_1000, a user requires write access to all three members to enter a valid data record.12 Appendix12.1 Changing Dimension Names

User may employ the dimensions delivered with the Planning RDS however may not want to use the default dimension names. For example, users may prefer to call the FUNCTIONAL_AREA dimension BUSINESS_UNIT. It can be renamed the dimension by copying the old dimension and using the new name on the copy.VERSION Dimension Property EditsProperty values are required to be edited in the VERSION dimension the user changes the names of the:

COST_CENTER dimension FUNCTIONAL_AREA dimension

PROFIT_CENTER dimensionThe VERSION dimension properties CC-DIM, FA_DIM, and PC_DIM must reflect the respective dimension names used in the RDS. It enables the RDS-delivered input forms and reports to dynamically reflect the name changes without requiring edit.12.2 Monthly Set UpThe following details the steps the BPC administrator takes each month to update the RDS with the most recent actuals and to prepare the system for new monthly planning:1. Using the SAP Business Planning and Consolidation Administration console, add a new Plan member in the VERSION dimension (for example: Plan_2012.FEB). 2. Process the Version dimension.3. Set security so the administrator can write to the new Version member in both the Planning and Rates models.4. Log on to the Planning model in Excel.5. Run a standard SAP Business Planning and Consolidation Data Manager package, to copy the existing Version PLAN to the destination Plan member (for example: Plan_2012.FEB).6. Set read-only security to the new Version member in both the Planning and Rates models. Long-term, users are recommended to develop a data archiving strategy so that the Planning model does not become burdened with multiple views of plans. Long-term archiving is not covered in the standard planning RDS build.7. Import Master Data using the application Data Manager Package Links for ACCOUNT, COMPANY_CODE, COST_CENTER, FINCTIONAL_AREA, PROFIT_CENTER, and TRADING_PARTNER. 8. Process each dimension after importing Master Data.

9. Decide on modifying transaction data for the new planning horizon. Options include:

Leveraging standard SAP Business Planning and Consolidation Data Manager to copy data into the new planning period at the end of the planning horizon. Leveraging the standard Data Manager clear package to clear out planning data from the recent month that is next to be updated with Actuals. Leveraging standard Data Manager to copy data from a full set or subset of data from an archived planning version and type.10. Schedule or import Actual transaction data for the most recent closed period. The Data Manager Delta Initialization can be used to filter the transaction data import as desired.11. Validate the SAP Business Planning and Consolidation data against the SAP NETWEAVER BW source systems using standard reporting techniques.

12. Update currency conversion rates in the Rates model.13. Update the V_FLAG property values in the Time dimension. The property value A indicates an actual period. The property value P indicates a planning period, as shown in the following screen capture.

14. Process the dimension.

Time Dimension V_FLAG Property

12.3 Delta Loading Transaction DataAfter the initial load of Transaction data into the Planning and Rate models, the user is required to load updated data on a monthly basis. The most efficient way to accomplish the load is to use the Delta Transaction Load. It can be configured to load only the transaction data entered after the previous delta load.The Planning RDS is delivered with a Delta Load definition that is set up for the initial (first) transaction data load in SAP Business Planning and Consolidation. The BPC administrator uses the Data Manager to execute the initial load. The following steps detail how to run the initial Delta Load as delivered in the Planning RDS and how to edit it for subsequent monthly data loads:Running the Initial Delta Load

1. To run the initial Delta Load, navigate to:

EPM add-in for Excel, Data Manager Tab, Data Manager GroupRun Package(Run Package Link

2. Verify that the Run Package Link dialog box is displayed.3. From the Package Link name select Transactional DELTA BW Data load and choose Run.

4. The Transactional Delta BW Data load dialog box is displayed. Select Next Finish. A confirmation message is displayed. 5. Select View Status. The Package Link Status screen indicates Succeed.

6. Confirm the data load by running a report in SAP Business Planning and Consolidation.Editing the Delta Load for Monthly PlanningAfter the Delta load has been used for the initial transaction data load, it can be edited it so the next execution Delta loads only the desired transaction data.1. To access the following Organize Delta Initialization dialog box, navigate to:

EPM add-in for Excel, Data Manager TabOrganize(Organize Delta Initialization

2. On the Organize menu, select New. The New Delta Initialization dialog box is displayed.

3. Enter a desired Name, for example: Monthly Delta Load, and a Description, which could contain the month of loading.Do not use a month-specific Name. In subsequent months the user is able to rename the Delta load when changing the filter. Description is not edited each month.

4. Use the Folder icon beside the InfoProvider field to display a list of available SAP NETWEAVER BW InfoProviders.5. Select ZFIGLC10P and choose OK.

6. In the Dimension/Field, select Fiscal year/period. Filtering can be processed by any available criteria and in this example, it is filtered by month.

7. Make the following entries: Attribute ID (default) and the Operator =.8. Select Low Value field and enter 2012001 (representing January 2012, in this example.)

9. Select the ellipses icon beside the Transformation File field to display a list of available Transformation Files. 10. Select BW_ZFIGLC10P_TFORM.XLS and choose Open.11. Enter a checkmark in the Trigger full load at first run option. It creates the time stamp that is read by the next Delta load.

Use this option only for the first Delta load. Unselect the checkbox for all subsequent Delta loads.

12. Save your entries

13. Enter a name for the file and save your entries again.14. To execute the new Delta load, run the Data Manager package link as previously detailed. SAP AG

Page 9 of 68

_1118216528.bin