Fielder Budget & Forecasting - Technical

Goodman Fielder
BPC Budget & Forecast
Configuration & Administration Guide
March 2014
Liability limited by a scheme approved under Professional Standards Legislation.

Member of Deloitte Touche Tohmatsu Limited
Member of Deloitte Touche
/conversion/tmp/scratch/480088562.docx
Contents
BPC Budget & Forecast 1
Configuration & Administration Guide 1
March 2014 1
1 Document Management 1
1.1 Versions 1
1.2 Related Documents 1
1.3 Stakeholder and Distribution List 1
2 Limitation of our work 3
2.1 General use restriction 3
3 Introduction 4
3.1 Background 4
3.2 Scope of work 4
3.3 Purpose 5
4 BPC Overview 6
4.1 Infrastructure 6
4.2 Model Overview 7
4.3 Dimension Overview 9
4.4 Master Data Maintenance 24
4.5 Transaction Data 32
4.6 Security 33
5 Model Configuration 35
5.1 Sales & TDC Model 35
5.2 CAPEX Model 49
5.3 OVERHEAD Model 51
5.4 Planning Tasks 52
5.5 Plan Integration BPF 55
6 General Administration 57
6.1 Security Set Up 57
6.2 Maintaining dimension properties 60
6.3 Create new versions (Budget & Forecast) 62
6.4 Create a new company 64
6.5 BPF Maintenance 64
Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited, a UK private company limited by guarantee,
and its network of member firms, each of which is a legally separate and independent entity. Please see
www.deloitte.com/au/about for a detailed description of the legal structure of Deloitte Touche Tohmatsu Limited
and its member firms.
© 2014 Deloitte Touche Tohmatsu
6.6 Light Optimization with compression 66
6.7 EPM 67
7 Appendix 71
7.1 Transformation Files 71
7.2 Conversion Files 71
7.3 BPC Security Matrix 71
7.4 Account Mapping (Sales Model) 71
Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited, a UK private company limited by guarantee,
and its network of member firms, each of which is a legally separate and independent entity. Please see
www.deloitte.com/au/about for a detailed description of the legal structure of Deloitte Touche Tohmatsu Limited
and its member firms.
© 2014 Deloitte Touche Tohmatsu
Limitation of our work
1 Document Management
1.1 Versions
Version Date Author(s) Major Changes
V1 07/03/2014 Simona Document Creation (draft)

Benedetti
V2 16/03/2014 Matt Newey Included Sales & TDC model documentation
V3 31/03/2014 Sabine Bennett Final Release

1
1.1 Related Documents

Version Date Author(s) Document Name
V3 31/03/201 Matt Newey Goodman Fielder BPC Allocation - Technical Document

4
V3 31/03/201 Matt Newey Goodman Fielder BPC Data Loads - Administration Guide
4
V3 31/03/201 Danielle Goodman Fielder BPC BAdI Allocation - Technical Document

4 Cullen
V3 31/03/201 Flavio Macedo Goodman Fielder BPC BAdI Disaggregation - Technical Document
4
V3 31/03/201 Danielle Goodman Fielder BPC BAdI Sales Adjustments - Technical Document
4 Cullen
V3 31/03/201 Danielle Goodman Fielder BPC BAdI Sales Calculations - Technical Document
4 Cullen
V1 18/07/201 Sabine Bennett GF Configuration Document – BPC Consolidation (Phase One)

3
1.2 Stakeholder and Distribution List

Stakeholder Group Role / Function Name
GF Finance Project Sponsor Meredith Symons

GF Finance Business Project
Bernard Carbone
Manager
GF Finance SME - Australia Murray Baker
1
GF Finance SME – New Zealand Paul Turnbull

GF Finance SME – APAC Rajesh Sharma
GF Finance SME - Corporate Joy Liu
GF Finance SME - Corporate Jonathan Rudman
GF IT Project Sponsor Paul Williams

GF IT Delivery Manager Tim Austen
GF IT IT Project Manager Rodney Franich
GF IT BI & APO Consultant Ruth Tabeta
GF IT FICO Consultant Nishant Mittal
Deloitte Deloitte Project Manager Shaun Bennett
Deloitte Solution Architect Sabine Bennett
Deloitte BPC Consultant Simona Benedetti
Deloitte BPC Consultant Matt Newey
Deloitte Project Director Bernhard Jantschgi
2
2 Limitation of our work

2.1 General use restriction
This document is prepared solely for the internal use of Goodman Fielder Limit. This report is not
intended to and should not be used or relied upon by anyone else and we accept no duty of care to any
other person or entity. The document has been prepared for the purpose set out in section 3. You
should not refer to or use our name or the advice for any other purpose.
3
3 Introduction
3.1 Background
This configuration document has been prepared by Deloitte Australia for Goodman Fielder (GF) after
the completion of a programme of work to provide Budget and Forecast functionality to the existing
SAP BPC implementation.
The scope of this phase was developed through a series of workshop and design sessions with key
stakeholders. The functional and technical specifications were held in separate sessions with different
stakeholders by different external firms. In addition, the technical design specification was
significantly altered in order to accommodate the business deadline of early 2014. Significant
deviation from the original functional design is to be expected while reading this document.
3.2 Scope of work
The scope of phase includes:
Sales & TDC Model

• Ability to plan by SKU and KAG/Region
• Ability to upload Volumes, Prices and Standard Costs from source systems through BW
• Ability to apply assumptions to Volumes, Prices and Standard Costs (bottom up and top
down)
• Ability to calculate PA, TA, Returns, SWO, Royalties and variable Logistic Costs based off
volumes, and/or manual entry
• Manual entry of Intercompany Sales and COGS not at standard
• Ability to run currency conversion
• Ability to capture comments
• Ability to run reports, aggregate, slice & dice data
CAPEX Model
• Ability to load existing CAPEX and depreciation simulation from source systems through
BW
• Ability to enter new CAPEX and calculate depreciation by asset class
Overheads Model
4
• Ability to load Actuals from source systems through BW
• Manual entry of costs by GL / Cost Centre
• Manual entry of Balance Sheet accounts
• Ability to apply assumptions
• Ability to calculate indirect labour on costs as %
• Ability to enter SKFs (i.e. FTE, Head Count, and other SKF’s required for the Budget Pack)
• Ability to run P&L, Balance Sheet, Cash Flow
• Ability to run P&L by SKU / KAG (BPC or COPA TBC)
Specifically out of scope for this phase

• Detailed Labour Planning
• Detailed Cost Planning (such as Freight, Travel etc)
• CAPEX Initiative Planning
• Strategic Plan
• S&OP processes – including calculation of Standard Cost, Price or Baseline Volumes
• Business Objects Reporting (defined as a separate stream of work)
• Retraction to ECC/BW
• Advertising and Promotion Planning
3.3 Purpose
This document explains the alterations and enhancements made to the system design of SAP BPC by
Deloitte Australia. This document is intended for technical and administration personnel to be read in
conjunction with SAP BPC documentation where all general details and user-end information can be
found. This document does not detail or comment on aspects outside of the scope of work or where
items have been previously documented by prior phases.
The purpose of this document is to:

• Understand the technical aspects of the BPC Phase 2 implementation,
• Understand the required maintenance of the BPC system.
5
4 BPC Overview
4.1 Infrastructure
Production Server
IP Address: 10.1.10.199
URL: http://sa0601s0:1080/sap/bpc/web
Test Server
IP Address: 10.6.2.85
URL: http://bi010:1080/sap/bpc/web
Development Server
IP Address: 10.6.2.143
URL: http://bi001:1080/sap/bpc/web
Software Details
SAP BPC (Business Planning & Consolidation) ABAP 7.31 SP2
EPM 10 Add-In Excel Client SP13 P3
SAP NetWeaver 7.3
6
4.2 Model Overview
The BPC implementation was spread across two phases. The first phase encompassed:
1. Consolidation Cube – holds transaction data for actual and plan versions and executes
consolidation processes
2. Rates Cube – maintains exchange rates for the purposes of currency translation into Group
Currency
3. Ownership Cube – maintains ownership percentages for the purposes of management and
financial consolidation
The second phase encompassed;
1. Sales & TDC Cube - configured for Sales and TDC planning
2. Overhead Cube – configured for OPEX planning and KPI entry
3. CAPEX Cube – configured for CAPEX planning
4. Allocation Cube – maintains allocations rules as a combination of transaction and master
data
Figure 1: Illustration of the BPC functional cubes
MANAGEMENT
REPORTING
SALES & TDC

CONSOLIDATION
PLANNING
BPC Templates & Functions:

BPC Templates & Functions:
· Sales & COGS valuation
· FX Translation
· Scenario Modelling
· Intercompany Eliminations
· New Product Development
· Automatic Adjustments
· Allocations
· Manual Journals
OVERHEAD
PLANNING CAPEX PLANNING
BPC Templates & Functions: BPC Templates & Functions:

· Direct Labour · Capital Expenditure
· Indirect Labour · Depreciation
Finance Sales
SAP BW Data Warehouse
SAP ECC6 / APO / Third Party Systems
7
Figure 2 Illustration of the Data Flow within BPC
Table 1 Summary of all BPC models

Environment Model Data Model Type Remarks
Entry
Mode
GOODMAN CAPEX PER Financial This model allows the budgeting and forecasting
FIELDER of Capital Asset and related Depreciation.
GOODMAN RATE PER Exchange Rates This model stores the FX rates
FIELDER
GOODMAN CONSOLIDATION YTD Consolidation This core model contains consolidation

FIELDER processes, data and structures.
GOODMAN OVERHEAD PER Financial This model allows the budgeting and forecasting
FIELDER of Overhead expenses.
GOODMAN ALLOCATION PER Financial This model allows mapping Overhead data to
FIELDER the Sales model in order to start the Allocation
process.
GOODMAN OWNERSHIP PER Ownership This model stores ownership information

FIELDER
GOODMAN SALES PER Financial This model allows the budgeting and forecasting
FIELDER of
4.3 Dimension Overview

The below table provides an overview of each dimension in BPC. Note that this section comments
only on dimensions that have been used or altered in the second phase.
8
Table 2 Dimension Overview
SALES & ALLOCATION
DIMENSION MAINTENANCE INFO-OBJECT TDC CAPEX OVERHEAD S
A_ACCOUNT MANUAL Y
ASSET_CLASS MANUAL Y
AUDITID MANUAL Y Y Y Y
CAPEX_ACCOUN MANUAL Y
COMPANY MANUAL Y Y Y Y
COST CENTRE LOAD VIA CAPEX 0COSTCENTER Y Y Y
CURRENCY MANUAL Y Y Y
CUSTOMER LOAD VIA SALES&TDC ZCUSTKAG2 Y Y
FLOW MANUAL Y Y
OH_ACCOUNT LOAD VIA OVERHEADS 0COSTELMNT Y
PRODUCT LOAD VIA SALES&TDC ZMATLBPC Y Y
PROFIT CTR MANUAL Y Y Y
PROJECT MANUAL Y
REGION LOAD VIA SALES&TDC 0CUST_GRP5 Y
S_ACCOUNT MANUAL Y
SEGMENT LOAD VIA 0SEGMENT Y Y
CONSOLIDATION
TIME MANUAL Y Y Y Y
VERSION MANUAL Y Y Y Y
4.3.1 A_ACCOUNT
This dimension is use solely by the Allocation cube. It serves no purpose to the transaction data or to
the allocation process and has been included only because it is a BPC requirement that every model
includes an Account dimension. All transaction data is written to A_NONE member.
There are no required properties for this dimension.
4.3.2 ASSET_CLASS
This dimension stores various asset classes which align to the grouping in the Group P&L and
Balance Sheet. Though there are greater variety of asset classes in the SAP Asset module, the data
source provided within BW is based on the GL and the below is reflection of the lowest level of detail
available.
9
Figure 3 Sample of ASSET_CLASS dimension
There are no properties required for this dimension. However, this dimension does interact with the
CAPEX_ACCOUNT. If a new asset class is added in ASSET_CLASS a new property with the same
description needs to be created in CAPEX_ACCOUNT dimension.
4.3.3 AUDITID
This dimension is used to identify the various sources of data that are utilized and to provide an audit
trail for data from source to destination. This dimension was existing from Phase One and the below
relates only to the alterations made for Phase Two. However, a comprehensive list of dimension
properties has been provided.
NOTE
AUDITID is heavily used in the SALES & TDC to drive calculation through BADIs for the disaggregation, adjustments and allocation
functions. All planning AUDITIDs serve a specific purpose that will be described later in this document and, more technically, in a
separate BADI configuration document, listed in Related Documents.
The areas in which analysis is carried out for planning are:

 Initial data input and general adjustments (PLAN_SUBTOTAL)
o PLAN_BW: Data from BW or Flat File upload.
o PLAN_MANUAL: Manual delta adjustments to a constant within BPC
o PLAN_ADJ_RATE: Manual delta adjustments to a rate within BPC
o PLAN_OVERWRITE: Overwrite adjustment to a constant within BPC. Entry
against this AUDITID will trigger a BADI to populate a value in PLAN_NEG
o PLAN_R_OVERWRITE: Overwrite adjustment to a rate within BPC. Entry against
this AUDITID will trigger a BADI to populate a value in PLAN_NEG
o PLAN_NEG: System AUDITID only. Used by a BADI to produce an overwrite
feature.
 Tracking of specific adjustments types (PLAN_ADJ & PLAN_ADJ_PER)

o These AUDITIDs are designed to provide a percentage adjustment to the value from
PLAN_SUBTOTAL.
o These AUDTIDs operate as contra accounts. When a percentage is inputted into an
PLAN_ADJ_PER AUDITID, this triggers a BADI to populate a value in
PLAN_ADJ
 Automatic Allocation (POST_ALLOC)
10
Figure 4 Sample of AUDITID Dimension
The following properties are required:

Table 3 Summary of AUDITID properties
Data Source Description Explanation Maintenance
IS_CONSOL Y/Blank Y = Data will be considered for consolidation. Manual
“Is_Consolidated”
IS_CONVERTED Y/Blank Y = Data will be considered for currency Manual

conversion
“Is_Translated”
DATASRC_TYPE A/I/M A= Automatically calculated Manual
“Data_type” I = Manually input
M= Manual journal
COPYOPENING Y/Blank Y = Included in the balance carry forward Manual
“Selected_in_carry_forward”
ENABLEJRN Y/Blank Y = Journal entries will be allowed Manual
OPENING_DATASRC BCF This property identified the AUDITID of Manual

destination in the Carry Forward process.
“Opening_auditID_in_carry_
forward”
IC_ORIGINE I/C1/C2 etc The property performs the IC Matching. Manual
I=Input
C1= Their Liabilities/Expense
C2= My Liabilities/Expense
Etc.
PALLOC_ACTIVE 1 The property activates the allocation Batches Automated
PALLOC_COMPANY G144,G220 etc This property identified the company assigned Automated
11
for every Batch
PALLOC_DRIVER ZCONA01.00010_INP This property identified the allocation Driver Automated

, etc
PALLOC_BDG_ACCT_LINE ZCONA01.02400_INP Allocation destination account Automated

, etc
PALLOC_SRC_ACCT_RNG Blank=all, GL6*= GL6 Allocation Source Account Range Automated

series
IS_BR2 Y/Blank Y = Triggers BADI to run adjustment for SALES Manual

& TDC model
“IS_ADJ”
IS_COPY Y/Blank Y = Triggers BADI to run adjustment for SALES Manual

& TDC model
“IS_COPY”
IS_INPUT Y/Blank Y - controls formatting on SALES & TDC input Manual

schedules
“IS_INPUT”
4.3.4 CAPEX ACCOUNT

The CAPEX_ACCOUNT will contain the Capital Asset and related Depreciation.
CAPEX accounts are grouped in main 3 categories:

• EXISTING (nodes of GL accounts used to receive existing figures from BW)
• NEW (base level accounts used to receive existing figures from BPC input templates )
• REMOVALS (base level accounts used to receive existing negative figures from BPC input
templates)
12
Figure 5 Sample of CAPEX Account Dimension
The following properties are required for this dimension:

Table 4 Summary of CAPEX_ACCOUNT properties
Property Values Details Maintenance
ACCTYPE INC, EXP, AST ,LEQ This is a mandatory property and the values mentioned are Manual
SAP standard, it can’t be changed or renamed. The
“Account Type”
system determines how to store the data in the database
based on this property.
RATETYPE END,AVG,COPYLG To identify which rate type should be used when doing the Manual
currency conversion.
“Rate Type”
DESTINAITION Y,Z,X This property is used in the Logic Manual

“DEST_CONSOLIDATION” AND “DEST_OVERHEAD” to
identify the accounts figures that we want to move in
Consolidation and in Overhead.
ASSET_CLASS Destination accounts in This property is used in the Logic Manual

1 CONSOLIDATION for “DEST_CONSOLIDATION” AND “DEST_OVERHEAD”. It
example: allows a mapping between accounts+assetclass in Capex
ASSET_CLASS
and specific accounts in Consolidation/Overhead.
2 ZCONA04.00200_INP
ASSET_CLASS
3
ASSET_CLASS
4
13
4.3.5 COMPANY
This dimension will contain SAP company codes and will be manually maintained in BPC. Manual
maintenance was selected was due to the large number of disused company codes within SAP. The
trial balance will be loaded at company level and the group structure (consolidation methods and
percentage) will be maintained at the company level.
Figure 6 Sample of COMPANY dimension
Table 5 Summary of COMPANY properties

CONTROL_LEVEL “Control 1-Basic, 2-Standard, Denotes the level of control the company has to Manual
level” 3-Advanced and 4- satisfy. This is used to manage the Controls.
Comprehensive
CURRENCY AUD, USD, EUR Functional currency of each company Manual
INTCO I_G8111,I_G8134 It is used to link INTCO dimension with the Manual

COMPANY dimension (refer next section for details
“Intercompany_ID”
about INTCO dimension)
OWNER USERID To identify the owner for each company or group of Manual
entities required for Work status management.
“Work_status_ entity_owner” [TEAMID]
REVIEWER, USERID To identify which user or team can access at the BPF Manual
for each company or group of entities.
BPF_SALES, [TEAMID]
BPF_CAPEX,
BPF_OH,
BPF_PLAN_INTEGR
“BPF_entity_ reviewer”
CTRL_CURRENCY_NOT_L Y/N Denotes if the Control will run against the LC. Manual
14
C Blank=N
“Bypass LC in Ctrl”
4.3.6 COST CENTRE

COST_CENTRE dimension members will be derived from 0COSTCENTER in BW
Figure 7 Sample of COST_CENTRE dimension

Table 6 Summary of TIME properties
PROFIT_CTR The default profit centre for the corresponding Automated

cost centre. Used within BPC reports and input
schedules to automatically populate the
PROFIT_CTR dimension
4.3.7 CURRENCY
This dimension stores various reporting currencies such as LC (local currency), USD, EUR, or any
other currency required for currency conversion. Reporting currencies will be translated from local
currency based on the various other setups and business rules.
15
Figure 8 Sample Currency Dimension

Table 7 Summary of CURRENCY properties
Property Description Explanation Maintenance
CURRENCY_TYPE L/R L=Local currency Manual
R=Reporting currency
REPORTING Y Y=Reporting currency Manual
4.3.8 CUSTOMER
This dimension contains the KAG ID as per SAP. The info-object is ZBPCKAG2.
Figure 9 Sample of CUSTOMER dimension
There are no required properties for this dimension. Though it was desired to include properties to
KAG, within BW the attributes are stored against the Customer ID rather than KAG. This means it is
not possible to obtain attributes from SAP at the KAG level.
Industry Type has been included as part of the hierarchy to navigation purposes.
4.3.9 FLOW
This dimension is supplementary to the account dimension and is used to manage the data movements
within a particular account. Since YTD data is loaded in the consolidation model and movements are
not registered, this dimension will be used to capture movements.
16
Figure 10 Sample of FLOW Dimension

FLOW_TYPE Opening – Opening bal This property would be used to identify the Manual
opening, closing Flow members to balance carry
Closing – Closing bal
forward movements.
VARSCP-Movement
ENABLEJRN Y/Blank Y = Journal entries will be allowed Manual
4.3.10 OH_ACCOUNT
The OH_ACCOUNT will contain the Overhead GL Accounts (5,6,7,8,9 series) loaded from BW and
KPI Accounts.
Figure 11 Sample of OH_ACCOUNT dimension
The following properties are required for this dimension:

Table 8 Summary of OH_ACCOUNT properties
ACCTYPE INC, EXP, AST ,LEQ This is a mandatory property and the values mentioned Automated
are SAP standard, it can’t be changed or renamed. The
“Account Type”
system determines how to store the data in the database
based on this property.
17
RATETYPE END,AVG,COPYLG To identify which rate type should be used when doing Automated
the currency conversion.
“Rate Type”
PARENTH1 This parent is used for the KPI accounts hierarchy. Manual
4.3.11 PRODUCT
This dimension contains the materials numbers from SAP. The info-object is ZMATLBPC.
Figure 12 Sample of PRODUCT dimension
The following properties are required for this dimension. These properties have been added to provide
filtering ability to users within BPC. These properties do not serve any technical purpose.
Table 9 Summary of PRODUCT properties
BASEUNIT As per SAP Automatic
BMT As per SAP Automatic
BRAND As per SAP Automatic
MATERIALID As per SAP Automatic
MATTYPE As per SAP Automatic
PCAT As per SAP Automatic
PSUBCAT As per SAP Automatic
SALESORG As per SAP Automatic
SCALING Manual
SOP As per SAP Automatic
SUBBMT As per SAP Automatic
SUBBRAND As per SAP Automatic
18
4.3.12 PROFIT_CTR
This dimension stores various profit centres. This dimension is manually maintained within BPC by
request of the GFIT team in Phase One. From discussion, there is a significant number of disused
Profit Centres within BW which would be unnecessary within BPC.
Figure 13 Sample of PROFIT_CTR dimension
4.3.13 PROJECT
This dimension stores various projects listed here:
Figure 14 Sample of PROJECT dimension
19
4.3.14 REGION
This dimension stores the region field from SAP. This info-object is called 0CUST_GRP5 within BW.
The region dimension can be a country, state, city, suburb or groupings of geographical locations. A
hierarchy has been overlayed to this to order the region members.
Figure 15 Sample of REGION dimension
4.3.15 S_ACCOUNT
This dimension contains the Sales Account for the SALES & TDC models. The accounts in this
dimension is used as an identifier to determine what the
The S_ACCOUNT are grouped into the following categories

 P&L items (SKF_EBIT)
 Average Accounts (AVG_ALL_ACCOUNTS)
 Volume items (SKF_VOLUME_ACC)
 Rates (SKF_RATES)
The following properties are required for this dimension. Though the below does mention BADIs, this
topic will be cover more comprehensive in a later section.
Table 10 Summary of S_ACCOUNT properties
ACCTYPE INC, EXP, AST ,LEQ This is a mandatory property and as this Manual
dimension is manual, this property needs to
be entered when adding new accounts.
BASE Any S_ACCOUNT Identifies the account used in the BADI Manual
member calculation of BASE x DRIVER
BASE_ACC Any S_ACCOUNT Identifies the account used as a basis for Manual
member disaggregation
BASE_AUDITID Any AUDITID member Identifies the AUDITID used as a basis for the Manual
under PLAN_TOTAL disaggregation
BUDGET PNL, UNT, INP, AVG, Classification of the type of S_ACCOUNT Manual
PRT
PNL – P&L Items
UNT – Volume
INP – Input
AVG - Average Account
20
PRT - Parent
CONSO Any S_ACCOUNT Manual

member
DRIVER Any S_ACCOUNT Identifies the account used in the BADI Manual
member calculation of BASE x DRIVER
IS_AVG Manual
MULTIPLIER 1/-1/BLANK Used by the BADI calculation BASE x DRIVER Manual

to reverse the sign
RATETYPE END,AVG,COPYLG To identify which rate type should be used Manual

when doing the currency conversion.
SCALING Optional, by default Manual
SCRIPT GSV, PA1, PA2, TA1, This field is used by the BADI to identify which Manual
TA2, LOG, COG accounts are calculated. Also used to call the
calculations in order via default script
PARENTH1 Any S_ACCOUNT The primary hierarchy for S_ACCOUNT Manual

member
PARENTH2 Any S_ACCOUNT Second hierarchy used very limitedly. Manual

member
4.3.16 SEGMENT
This dimension member is the Financial Segment used by the Group in group and external reporting.
It was created in Phase One and is used within Phase Two. There has been no alteration between
phases. Segment is derived from PROFIT_CTR and is calculated in in SAP ECC6 or BW and added
to transaction data. This process was design and implemented by GFIT.
Figure 16 Sample of SEGMENT dimension
Table 11 Summary of SEGMENT properties

BWID 0000001000, A transformation property used by transferring Manual

0000002000 data from BPC to BI reporting cubes
4.3.17 TIME
This dimension defines the units of time and how units aggregate. For example 2011.01, 2011.02,
2011.03 represent periods 1, 2, and 3, and the aggregation for these would be 2011.Q1.
It is required to manage the month period as the most granular level of detail for the time dimension.
As a result, the system must support data submission process with monthly details.
21
Based on the above requirements, the time dimension will have the following characteristics:
 Sharing between all Applications.
 Hierarchy organization according to the schema Year  Half Year  Quarter  Month.
 Fiscal year starting 1 July and ending 30 June.

Figure 17 Sample of TIME Dimension
Table 12 Summary of TIME properties

LEVEL MONTH, QUARTER To designate the time granularity Manual
MONTHNUM 1 TO 12 To identify the numerical position of the month in the Manual

Fiscal year, useful for planning purposes
PERIOD Not used Manual
TIMEID 2011101, 2011102 System uses this property to determine next and prior Manual
months for the current month.
YEAR 2011, 2012 Used for reporting purposes Manual
BWID 2011001 To link time code at the BW code Manual
GL_QUARTER 1,2,3,4 This property is used in the logic that copy the actual Manual
into the forecast and it identifies the number of the
quarters of each month.
IS_BEGINNING 1 1= the first month of the year Manual
4.3.18 VERSION
This dimension stores all relevant versions. These include Actual, Forecast, Budget and Strategic
Plan. Versions can also be used for scenarios and what-if analysis.
22
Figure 18 Sample of VERSION dimension
Figure 19 Summary of VERSION properties

CATEGORY_FOR_OPE ACTUAL, FORECAST This value determines from which Version Manual
the opening balance to be bought forward in
the “Balance carry forward” business rule.
COMPARISON ACTUAL, FORECAST Can be used in reports Manual
OPENING_PERIOD “C/Fwd: DEC If opening period is not the previous period, Manual
Opening Period” then it needs to be maintained here. It is
used for balance carry forward.
YEAR 2011 To identify the current financial year Manual
FX_DIFFERENCE_ONLY Not used: FX Simulation Manual
FX_SOURCE_CATEGORY Not used: FX Simulation Manual
OPENING_YEAR 2011 Opening year if other than the previous Manual

period needs to be maintained here, it is
used for carry forward.
GL_FORCAST F01,F02,F03,F04 This property is used in the logic that copy Manual
the actual into the forecast (for
Consolidation only) and it identifies the first,
second, third and fourth forecast.
FORECAST_PLANNING F01,F02,F03,F04 This property is used in the logic that copy Manual
the actual into the forecast (for Planning
only) and it identifies the first, second, third
and fourth forecast.
ALLOC_START_PERIOD Blank,2014001,2014004, This property is used in the Allocation Badi Manual

etc and it identifies the start period for a specific
version. Blank value is used if we want
exclude a version from allocation process.
ALLOC_END_PERIOD Blank,2014012,2015012, This property is used in the Allocation Badi Manual

etc and it identifies the end period for a specific
version. Blank value is used if we want
exclude a version from allocation process.
23
4.4 Master Data Maintenance
4.4.1 Manual Master Data
BPC master data is centrally controlled and maintained. The administrators of the BPC system can
control and maintain this master data via BPC’s administration interface. The administrators will be
able to maintain the dimensions, dimension members and dimension properties via the BPC
administration interface.
Dimensions that are static, such as Time, Currency, are manually maintained by the Administrator in
the BPC application. There are also Dimensions that are specific to BPC and do not exist in ECC or
BW, such as Audit Trail or Flow.
Figure 20 Master Data Maintenance Overview Screen
24
Figure 21 Master Data Maintenance Screen
NOTE
1. The member IDs should be unique within the environment to avoid any potential member conflict
2. All properties must be filled with appropriate information; failing to do this will affect the functionality of the system
3. Some properties are mandatory in each dimension and failing to specify correct value may result in processing errors
4. The updates made will have to be processed before it can take effect
5. Any update to the hierarchy in dimension will reclassify the historical
6. You should logoff and login from Excel Add-in interface to see the changes
4.4.2 Automated Master Data

Dimensions that change frequently, such as Account, Cost_Centre, Region, Product, Customer are
loaded automatically from ECC via BW. Hierarchies for these Dimensions are maintained in SAP
ECC.
The following package links have been configured to import as OH_ACCOUNT/ COST_CENTRE/
PRODUCT/ REGION/CUSTOMER master data into BPC – from the BW info-object. The
parameters, the conversion and transformation files are set as per below.
The conversion and transformation file can be found in appendix of this document.
4.4.2.1 OH_ACCOUNT
DIMENSION INFOOBJECT TRANSFORMATION CONVERSION PACKAGE LINK
OH_ACCOUN 0COSTELMNT 0H_ACCOUNT_MD_0GL_ACCOUNT.XL OH_ACCOUNT.xl

T S s
Parameters
25
Figure 22 Master Data parameter selection for 0COSTELMNT (page 1)
Figure 23 Master Data parameter selection for 0COSTELMNT (page 2)
4.4.2.2 COST CENTRE
DIMENSION INFOOBJECT TRANSFORMATION CONVERSION PACKAGE

LINK
COST_CENTR 0COSTCENTER COST_CENTRE_MD_0COSTCENTER.XLS COST_CENTRE.xl GF MASTER

E s DATA IMPORT
ZSCSTCTR COST_CENTRE_HIER_0COSTCENTER.XL
S
Parameter
26
Figure 24 Master Data parameter selection for 0COSTCENTER & ZSCSTCTR (page 1)
Figure 25 Master Data Selection for 0COSTCENTER (Page 2)
Figure 26 Master Data Selection for 0COSTCENTER (Page 2)
27
Figure 27 Master Data Selection for ZSCSTCTR (Page 2)
4.4.2.3 CUSTOMER

LINK
CUSTOMER ZCUSTKAG2 MD_CUSTKAG2.XLS C_KAG DIM_KAG
Figure 28 Master Data parameter selection for ZCUSTKAG2 (page 1)
28
Figure 29 Master Data parameter selection for ZCUSTKAG2 (page 2)
4.4.2.4 PRODUCT
LINK
PRODUCT ZMATLBPC MD_ZMATLBPC C_PRODUCT DIM_PRODUC

T
29
Figure 30 Master Data parameter selection for ZBPCMATL (page 1)
4.4.2.5 REGION

LINK
REGION 0CUST_GRP5 MD_CUST_GRP5 C_REGION DIM_REGION
30
Figure 31 Master Data parameter selection for 0CUST_GRP5 (page 1)
Figure 32 Master Data parameter selection for 0CUST_GRP5 (page 2)
31
4.5 Transaction Data
An overview of the source of the transaction data is provided below. The conversion and
transformation file can be found in appendix of this document.
Table 13 Summary of Transaction Data per model

MODEL PERIODICITY DETAILS
CAPEX Monthly A part of CAPEX values will be loaded directly from BW

Info Cubes (ZCCA_M02) which is feed from SAP ECC or
third party systems.
All the APAC companies that are not present in BW , will

enter data manually via input schedules or through a flat
file loading directly in BPC.
RATE Monthly These will be entered manually via input templates directly
in BPC.
OVERHEAD Monthly A part of OVERHEAD values will be loaded directly from

BW Info Cubes (ZCCA_M02) which is feed from SAP ECC
or third party systems.
All the APAC companies that are not present in BW, will
enter data manually via input schedules or trough a flat file
loading directly in BPC.
SALES Monthly There are two BW data sources for this model.
ZBPC_M05 is a multi-provider that provides Volume and

dollar values amounts
Z0BPCR8S is a DSO that provide rates only.
ALLOCATION Yearly Allocation data will be entered manually via input

schedules or through a flat file loading directly in BPC.
4.5.1 CAPEX
MODEL DATA SOURCE TRANSFORMATION CONVERSION PACKAGE

LINK
CAPEX ZCCA_M02 ZCCA_M02 TRANSFORMATION ZCCA_M02 GF

FILE TRANSACTIO
N DATA
ZCCA_M02 TRANSFORMATION
IMPORT
FILE_OPERNING
4.5.2 OVERHEAD
MODEL DATA SOURCE TRANSFORMATION CONVERSION PACKAGE

LINK
OVERHEAD ZCCA_M02 ZCCA_M02 TRANSACTION ZCCA_M02 GF

FIGURES FOR BPC TRANSACTIO
N DATA
32
IMPORT
4.5.3 SALES
MODEL DATA SOURCE TRANSFORMATION CONVERSION PACKAGE LINK
SALES ZBPC_M05 TD_ZBPC_M05 C_ZBPC_M05 TD_SALES_ACTUAL

S
TD_ZBPC_M05_VOLUME
TD_SALES_PLAN
_VOLUME
SALES ZOBPCR8S TD_ZOBPCR8S C_ZBPC_M05 TD_SALES_ACTUAL

S
TD_ZOBPCR8S_PRICE
TD_SALES_PLAN
TD_ZOBPCR8S_STANDARD_COS
_PRICE
T
TD_SALES_PLAN
TD_ZOBPCR8S_TA_PA
_STANDARD_COST
TD_ZOBPCR8S_VOLUMES
TD_SALE_PLAN_TA
_PA
TD_SALES_PLAN
_VOLUME
4.6 Security
In keeping with SAP Best Practice, Goodman Fielder security for BPC is designed to be administered
by assigning Users to predefined Teams.
Table 14 Security Options
Term Description
Users Security is managed by assignment of users to Teams.
This allows:
Access to Applications
Access to Team Input Schedules
Access to Team Reports
Access to execute DM Packages (Currency Conversion etc)
Read-Only/Read-Write access to specific Dimension Members
Team Defines a collection of access based on assigned
Data Access Profiles and Task Profiles
Team folders also control access to input schedules
Task Profile Defines access to technical tasks in BPC.
E.g. Save Data

Execute DM Package
Data Access Profile Defines Read-Only or Read-Write access to data stored against specified Dimension
Members.
33
E.g. Read-Only access to specific Company
Read-Write access to specific Company
4.6.1 Security Matrix

It has been decided that Data Access Profiles will be controlled by the Company dimension.
The Task Profiles are split into 3 categories:
 Administrator_TASK (ALLTASK) can perform all administration activities and has

read/write access to all the companies and versions
 User_Task (ENTRY TASK) can perform all activities apart from administration activities,
has read access to all companies and write access to some companies and versions
 ReadOnly_Task (DATA VIEW) can perform all activities apart from administration
activities and has only read access to all companies and versions
The security matrix provided by GF has been attached as an appendix.
Figure 33 Security Admin Screen
34
5 Model Configuration
5.1 Sales & TDC Model
5.1.1 Purpose of the model
Sales & TDC model involves the calculation of P&L lines down to CBM. This process involves
loading rates and base amounts for the majority of the P&L lines and calculating a result within BPC.
Users are able to alter these rates and base amounts and the impact of the change flows through the
P&L. These calculations will be defined further in this section.
This involves the following components
 Selling Price
 Sales Volumes (BUM)
 GSV
 Promotional Allowances
 Trade Allowances
 COGS at Standard
 COGS Variances
 Logistics Costs
 Royalties Costs
 Currency Conversion
 Transfer results to Finance model
5.1.2 Business Process Flow

Due to difference between system and processes between markets, each market has their own BPF.
The differences only relate to the Data Loads step and once the data is loaded, it is expected that the
process would be relatively consistent across markets.
5.1.2.1 Australia
In this step, Australia loads all data from BW with the exception of Standard Costs.
Data Loads
NAME ACTIVITIES ENVIRONMENT LINK CARRIED OUT
DESCRIPTION BY
Data Load Load Version Actual DATA TD_SALES_ACTUAL USERS

from BW (ALL) MANAGEMENT
Data Load Load Version Plan DATA TD_SALES_PLAN_PRICE USERS

from BW (Price) MANAGEMENT
35
Data Load Load Version Plan DATA TD_SALES_PLAN_VOLUME USERS
from BW (Volume) MANAGEMENT
Data Load Load Version Plan DATA TD_SALES_PLAN_TA_PA USERS

from BW (TA & PA) MANAGEMENT
Upload Flat Download Data from DATA Export Transaction data to flat file USERS
Files BPC (optional) MANAGEMENT
Upload Flat Upload Plan Version DATA Data upload USERS

Files File (Standard Cost) MANAGEMENT
Upload Data Upload Plan Version DATA TD_FLAT_FILE USERS

From Flat File Data (Standard MANAGEMENT
Cost)
Run Initial Run Initial Plan DATA 15_SCRIPT_DEFAULT USERS

Plan Calculations MANAGEMENT
Calculations
Review Data Review Data Inputs EXCEL BPC_S_RW_03 – ACCOUNT INPUT BY USERS
PRODUCT
Review Data Review P&L EXCEL BPC_S_RW_02 – P&L OVERVIEW USERS
Copy to Copy to Working DATA 07_COPY_VERSION USERS

Working Version MANAGEMENT
Version
Copy Actuals Run Copy Actual DATA 10_COPY_ACTUAL USERS

to Working Process MANAGEMENT
Version
Planning Process
LINK
ACTIVITIES CARRIED OUT
NAME DESCRIPTION ENVIRONMENT BY
Complete Complete Sales EXCEL BPC_S_RW_01 - Sales USERS

Sales Model Model
Complete Complete COGS EXCEL BPC_S_RW_01 - COGS USERS

TDC Model
Complete Complete EXCEL BPC_S_RW_01 - LOGISTICS USERS

TDC Model LOGISTICS
Complete Complete EXCEL BPC_S_RW_01 - ROYALTIES USERS

TDC Model ROYALTIES
Review Open Review P&L EXCEL BPC_S_R_02 – P&L Overview USERS

Reports
Run Unit Run Unit Conversion DATA UNIT_CONVERSION USERS

Conversion MANAGEMENT
Run Unit Review Unit EXCEL UNIT_CONVERSION USERS

Conversion Conversion Report
36
Run FX Run FX Translation DATA 01_CURRENCY_CONVERSION USERS
Translation MANAGEMENT
Run FX Review P&L EXCEL BPC_S_R_02 – P&L Overview USERS

Translation
5.1.2.2 New Zealand

In this step, New Zealand loads all data from BW.
Data Loads
DESCRIPTION BY

Data Load Load Version Plan DATA TD_SALES_PLAN_PRICE USERS

from BW (Price) MANAGEMENT
Data Load Load Version Plan DATA TD_SALES_PLAN_VOLUME USERS

from BW (Volume) MANAGEMENT
Data Load Load Version Plan DATA TD_SALES_PLAN_TA_PA USERS

from BW (TA & PA) MANAGEMENT
Data Load Load Version Plan DATA TD_SALES_PLAN_STANDARD_COST USERS

from BW (Standard Cost) MANAGEMENT

Files File (IF REQUIRED) MANAGEMENT
Upload Data Upload Plan Version DATA TD_FLAT_FILE USERS

From Flat File Data (IF MANAGEMENT
REQUIRED)

Calculations
PRODUCT

Version

Version
Planning Process
37
LINK

Sales Model Model

TDC Model

TDC Model LOGISTICS

TDC Model ROYALTIES

Reports




Translation
5.1.2.3 APAC
APAC has three types of companies. Those on SAP which will operate like New Zealand, those on
Syspro that have Actual version data available in BW, and Philippines that have no form of data
integration. A single BPF has been provided with all options. Users are able to use the options that are
relevant to their needs.
Data Loads
DESCRIPTION BY

Data Load Load Price (SAP DATA TD_SALES_PLAN_PRICE USERS

from BW ONLY) MANAGEMENT
Data Load Load Volume (SAP DATA TD_SALES_PLAN_VOLUME USERS

Data Load Load TA & PA (SAP DATA TD_SALES_PLAN_TA_PA USERS

Data Load Load Standard Cost DATA TD_SALES_PLAN_STANDARD_COST USERS

from BW (SAP ONLY) MANAGEMENT
38

Files File (Actual) MANAGEMENT

Files File (Price) MANAGEMENT

Files File (Volume) MANAGEMENT

Files File (Standard Cost) MANAGEMENT

Files File (TA & PA) MANAGEMENT
Upload Data Upload Data From DATA TD_FLAT_FILE USERS

From Flat File Flat File MANAGEMENT

Calculations
PRODUCT

Version

Version
Planning Process
LINK

Sales Model Model

TDC Model

TDC Model LOGISTICS

TDC Model ROYALTIES

Reports

39


Translation
5.1.3 Data Sources

There are two BW data sources for this model. Both data sources are “key figure” format, which
require greater and static transformation to transfer data to BPC, which is an “Account” model format.
The transformation files have been described in more detail below.
The first data source is the multi-provider, ZBPC_M05, and this provides transaction data for dollar
value and volume amounts. This is primarily used when upload Actual version from BW, where BPC
does not perform any calculations.
The second data source is a DSO, ZOBPCR8S, and this provides all rates for the model. And this data
source is primarily used by the Plan versions.
5.1.4 Transformation Files

As mentioned above, the data sources provided in BW are based on a key figure format and in order
to transfer data to BPC the transformation file must transform the data to an Account model format.
This transformation is achieved via a MVAL formula, available within BPC. What this formula does
is map a key figure column in BW to an Account member in BPC. The consequence is that this
mapping is hardcoded as part of the transformation file; meaning that new accounts may not
automatically flow to BPC, and if different combinations of key figures are required there must be a
separate transformation file for each combination. Which key figures that are selected is controlled by
the transformation file. This is reason as to why there are multiple transformation files and packages
in the Sales & TDC model.
A mapping of key figures to BPC Account members has been attached as an appendix, rather than
added in the below section.
5.1.4.1 TD_ZBPC_M05
This transformation file is only used for the Actual version, via the Package Link,
TD_SALES_ACTUALS. It maps:
 All P&L items down to EBIT
 All Volumes amounts
SALES ZBPC_M05 TD_ZBPC_M05 C_ZBPC_M05 TD_SALES_ACTUAL

S
5.1.4.2 TD_ZOBPCR8S
40
This transformation file is only used for the Actual version, via the Package Link,
TD_SALES_ACTUALS. It maps:
 All Rates
Note that rates are loaded for the Actual version to provide a comparative only, and are not intended
for any calculations.
SALES ZOBPCR8S TD_ZOBPCR8S C_ZBPC_M05 TD_SALES_ACTUAL

S
5.1.4.3 TD_ZBPC_M05_VOLUME
This transformation file is used as part of the planning process. It maps:

 All Volumes amounts
SALES ZBPC_M05 TD_ZBPC_M05_VOLUME C_ZBPC_M05 TD_SALES_PLAN

_VOLUME
5.1.4.4 TD_ZOBPCR8S_PRICE

 Price
SALES ZOBPCR8S TD_ZOBPCR8S_PRICE C_ZBPC_M05 TD_SALES_PLAN

_PRICE
5.1.4.5 TD_ZOBPCR8S_STANDARD_COST

 Standard Cost rates
SALES ZOBPCR8S TD_ZOBPCR8S_STANDARD_COS C_ZBPC_M05 TD_SALES_PLAN

T _STANDARD_COST
41
5.1.4.6 TD_ZOBPCR8S_TA_PA

 TA & PA rates
SALES ZOBPCR8S TD_ZOBPCR8S_TA_PA C_ZBPC_M05 TD_SALE_PLAN_TA
_PA
5.1.4.7 TD_ZOBPCR8S_VOLUMES

 Alternative measure rates
SALES ZOBPCR8S TD_ZOBPCR8S_VOLUMES C_ZBPC_M05 TD_SALES_PLAN

_VOLUME
5.1.5 Script Logic

Script logic has been included as part of this model. The below table lists summaries and explains the
available logic.
SCRIPT LOGIC DESCRIPTION EXECUTION METHOD
DEFAULT Default logic, in this model, is primarily used to call BADIs Called automatically when
(discussed in the next section) for the adjustments functions and saving data
planning calculations. Note that the order In which these BADIs
are called is important. The order is:
1. BPC_ADJUSTMENT
2. BPC_SALES_GEN_CALS
a. COGS, LOG, GSV
b. PA1, TA1
3. PATA.LGF
4. BPC_SALES_GEN_CALS
a. PA2, TA2
Why is the order important?
The results of some calculations feed into the preceding

calculations.
COPY_ACTUAL This script copies the ACTUAL version into the correct forecast Added as part of the BPF and
version for the correct number of periods. For example, for 3+9 added as part of Data
Forecast, this script copies in first three periods of Actual. Manager
Note that there must the data loaded into the Actual version for the
correct periods for the data to be copied. This script does not load
42
data from BW.
It is currently setup for quarterly forecast, if a rolling monthly

forecast is required, this script can be altered by repeating the
quarter calculation and restricting per month. Alternative, it may be
just as easy to use the standard BPC copy function.
Maintenance
This script requires maintenance of a property, called

“FORECAST_PLANNING”, in the VERSION dimension. Valid
options are F01 – F04, which defined the selection criteria of the
script.
COPY_VERSION This script is a simplified version of the standard copy function in Added as part of the BPF and
BPC. It only provides users with the filter options of COMPANY, added as part of Data
TIME, VERSION FROM and VERISON TO. Manager
Alternatively, the standard BPC copy function can be used.
FEED This script transfers data from the SALES model to the Added as part of the BPF for
CONSOLIDATION model. Users are able to select COMPANY, Administrators and added as
CURRENCY, TIME & VERSION. part of Data Manager
Key features are:
1. Skips dimensions missing from Consolidation model

2. Add dimension missing from the Sales & TDC model
3. Look up “CONSO” property to find C_ACCOUNT
destinations
4. Translate time from periodic to YTD
Maintenance
This script requires maintenance of a property, called “CONSOL”,

in the S_ACCOUNT dimension. When transferring data, members
need to be base (children) members, however, in the SALE & TDC
the members that are needed to be transferred happen to be
parents. To overcome this the “CONSOL” property is used as a
reference to identify all the children accounts that need to be
transferred and to the account that is required in C_ACCOUNT.
FXTRANS This script translates from Local Currency to Group Currency for Added as part of the BPF and
this model. This is a standard program within BPC and has been added as part of Data
restricted to provide AUD and NZD translations. Manager
Dependent System
BI reporting does connect to the Sales & TDC model as a data

source. This script must be run in order to have the data available
in Local and Group currency within BI reporting.
OH_SALE_ALLOC This script calls a BADI for the allocation process. This is the first Added as part of the BPF for
step of the allocation, in which, the BADI allocates Overheads Administrators and added as
costs elements to the Sales & TDC model. part of Data Manager
The allocation process has been documented as a separate

document. See the Related Document section for more details
OH_REVERSE_ALLOC This script calls a BADI for the allocation process. This is the Added as part of the BPF for
S second step of the allocation, in which, the BADI writes back the Administrators and added as
negative amount to the Overheads model of what was allocated to part of Data Manager
a separate AUDITID. This results in users having the ability to see
43
pre and post allocation within the OVERHEADS model.
The allocation process has been documented as a separate

document. See the Related Document section for more details
PATA This script calculates Net Invoice Value. This was left as a script, Called as part of default logic.
rather than, translated into a BADI in case it needs to be updated
in the future.
VOLUME This script calculates the alterative measures of volume. All Added as part of the BPF and
CONVERSION volume calculations or volume changes within the model are added as part of Data
based around BUM. When BUM is finalised this process is Manager
designed to apply a rate to BUM and calculate the alternative
measure of volume.
5.1.6 BADIs
To provide non-standard functionality to facilitate the budgeting process, there are three incorporated
BADIs in the Sales & TDC model. Note that the allocation process has been detailed in a separate
document and is not covered in this section.
This section details the function aspects of the BADIs, setup within BPC and on-going maintenance.
The technical aspects of the BADIs have been documented separately due to their technical nature and
different audience.
There are three types of BADI used in the Sales & TDC models:
BADI DESCRIPTION EXECUTION METHOD
DISAGGREGATION This BADI enables users to plan at a high-level of CUSTOMER, Added to standard
PRODUCT, REGION, PROFIT_CTR and SEGMENT, and have functionality, this feature is
the inputted value flow down to the base members. The inputted permanently on within the
value will be disaggregated or copied down depending on setup SALES & TDC model.
configuration of AUDITID and write back according to properties in
S_ACCOUNT.
SALES ADJUSTMENTS This BADI enables differing adjustment functionality within the Called as part of Default Logic
model. Users are able to over-write or percentage change
depending on the AUDITID they write data to.
SALE CALCULATIONS This BADI drives the calculation of Base x Driver within Called as part of Default Logic
S_ACCOUNT. This is maintained through three properties in the
S_ACCOUNT dimension.
5.1.6.1 Disaggregation BADI
The disaggregation BADI enables users to plan at a high-level of CUSTOMER, PRODUCT,

REGION, SEGMENT and PROFIT CENTRE, and have the inputted value flow down to the base
members. The inputted value will be disaggregated or copied down depending on setup configuration
of AUDITID and write back according to properties in S_ACCOUNT.
There are number of reasons that this disaggregation feature was included as part of this model:
1. Requested by users and added to scope via the Steering Committee
2. The large number of SKUs incorporated into the PRODUCT dimension, made budgeting at
the lowest level impracticable
44
3. Markets/Business Units budget at varying combinations of CUSTOMER, PRODUCT and
REGION. For example, APAC and Route businesses focus budgeting activities primarily
around the REGION/PRODUCT dimensions, whereas other businesses focus on
CUSTOMER/PRODUCT dimensions
4. Budgeting process does not require PROFIT_CTR and SEGMENT, however is require for
reporting.
Functional Capability
 DIMENSION SELECTION: Users are able to enter data any level of the hierarchy for
Product, Customer, Region, Segment and Profit Centre. All other dimensions need to be at
the lowest base member.
Table 15 Summary of dimension variables passed to Disaggregation BADI

DIMENSION VALUES SENT TO BADI
AUDITID use exact value passed in
COMPANY use exact value passed in
PROFIT_CTR select children of dimension value passed in
CURRENCY use exact value passed in
CUSTOMER select children of dimension value passed in
PRODUCT select children of dimension value passed in
REGION select children of dimension value passed in
SEGMENT select children of dimension value passed in
S_ACCOUNT use exact value passed in
TIME use exact value passed in
VERSION use exact value passed in
SIGNEDDATA calculated
 DISAGGREGATION OR COPY DOWN: Users are able to disaggregate data or copy

down data. This is determined by the AUDITID member that the data is entered against and
a property in the AUDITID dimension.
Table 16 Summary of functionality

FUNCTION SETUP
DISAGGREGATION This is set as DEFAULT
When a value is entered against an AUDITID underneath the node, “PLAN_TOTAL”, the value will be
spread across all base members. This is used for accounts, like VOLUME.
COPY DOWN This is determined by a property, called “IS_COPY” in the AUDITID dimension.
When IS_COPY = Y, then any value entered at a top level will be copied to the base members.
This is used for accounts, such as, price, rates or percentage changes.
45
 REFERENCE DATASET: The entered value is then disaggregated or copied down
according to a reference dataset. This dataset is maintained per account using two properties
in the S_ACCOUNT dimension, “BASE_ACC” and “BASE_AUDITID”. By defining these
two properties, each account can select the S_ACCOUNT and AUDITID members to base
the disaggregation on.
The reference dataset will determine the members of the CUSTOMER, PRODUCT,
REGION, SEGMENT and PROFIT CENTRE dimension as well as provide a basis of the
amount to write back to each combination.
Table 17 S_ACCOUNT properties to define reference dataset for the Disaggregation Logic
PROPERTY DESCRIPTION
BASE_ACC A property to define which S_ACCOUNT member to base disaggregation or copy down
on.
Valid Inputs
Any Parent or Child of the S_ACCOUNT dimension.
BASE_AUDITID A property to define which AUDITID member to base disaggregation or copy down on.
Valid Inputs
Any Parent or Child of AUDITID dimension under “PLAN_TOTAL”
NOTE
Each S_ACCOUNT member must have both of the above properties populated otherwise any attempt to save data to that
member will result in an error message.
 NO REFERNECE DATASET AVAILABLE: If no reference dataset is found, then value

will then be copied down or disaggregated equally against all valid dimension combinations.
NOTE
In some instances where a value is attempted to be saved back and there is no reference data, the system can run out of internal
memory and the process fails. This has only has been observed in the Development and Test environments in situations where
a value was entered at the highest level of all possible dimensions and there was no reference data available. This problem
should not occur in the Production environment where there should be greater data available and where the system has greater
capacity. If this does occur, it is recommended to review the reference data properties to determine if they are still appropriate
and have the BASIS team review the internal memory parameters.
5.1.6.2 Sales Adjustment BADI
This BADI enables two types of adjustments within the SALES & TDC model. This BADI is called
via Default logic.
The first type of adjustment is an overwrite feature, in which, users are able to input a new value to
overwrite the value in PLAN_BASE. There are two available overwrite AUDITID to allow for a rate
adjustment or a disaggregation adjustment.
Table 18 AUDITID used in the OVERWRITE Function
AUDITID DESCRIPTION
PLAN_OVERWRITE This AUDITID provides an overwrite feature that will disaggregate the entered amount (as
described above).This is designed to work with volume and dollar value accounts. Once a value is
entered into this AUDITID the BADI will populate PLAN_NEG with the negative amount of
PLAN_BASE.
No required maintenance. The BADI is hardcoded to select this AUDITID.
PLAN_R_OVERWRITE This AUDITID provides an overwrite feature that will copy down the entered amount (as described
46
above). This is designed to work primarily with rates, price and percentages. Once a value is
entered into this AUDITID the BADI will populate PLAN_NEG with the negative amount of
PLAN_BASE.
Maintenance
The BADI is hardcoded to select this AUDITID. However, the copy down feature is controlled via
“IS_COPY” property in the AUDITID dimension. Review the above section for more details.
PLAN_NEG When an entry has been inputted into PLAN_OVERWRITE or PLAN_R_OVERWRITE the BADI
will populate this field with the negative amount of PLAN_BASE. This will offset PLAN_BASE to
zero and the PLAN_SUBTOTAL will now equal the overwrite amount. This overwrite amount will
flow to all dependent calculations within the model.
If PLAN_OVERWRITE or PLAN_R_OVERWRITE is altered to equal zero, PLAN_NEG will equal

zero and PLAN_SUBTOTAL will equal the amount in PLAN_BASE.
No required maintenance. The BADI is hardcoded to select this AUDITID.
The second type of adjustment is a percentage adjustment, in which, users enter a percentage against
an AUDITID and this applied against PLAN_SUBTOTAL. This function requires two AUDITIDs to
operate. The first AUDITID holds the entered percentage which triggers a calculation and saves the
result into a new AUDITID.
Table 19 AUDITIDs used in the percentage change Function

AUDITID DESCRIPTION
PLAN_ADJ#_PER This AUDITID holds a percentage that is to be applied against PLAN_TOTAL. For example, if a
user enters 50% the calculation would be PLAN_SUBTOTAL x 50%.
These AUDITID sit outside of the PLAN_TOTAL hierarchy.
Once a value is entered into this ID, the BADI will look for the ID with the same first nine
characters. For example, the percentage is entered into PLAN_ADJ1_PER the result will be saved
in PLAN_ADJ1.
PLAN_ADJ# This AUDITID receives the result from the BADI.
Maintenance
There is a property called, “IS_BR12” that triggers the execution of the BADI. When IS_BR12 =
“Y”, then calculation will operate.
5.1.6.3 Sales Calculation BADI
Originally these sales calculations were sitting as script logic in default, meaning that they would
calculate every time that data was saved and resulted in poor performance. To overcome this
performance issue, these scripts were translated into BADIs and use S_ACCOUNT properties to
control the calculations.
All the sales calculations follow the same formula.
Budget Line=Base x Driver x Multiplier
Where Budget Line, Base, Driver and Multiplier are all parameters found within the S_ACCOUNT
dimension.
47
Table 20 S_ACCOUNT members that feed the SALES CALCULATIONS
S_ACCOUNT PROPERTY DESCRIPTION
BUDGET LINE This is the ID of the S_ACCOUNT dimension that will receive the result of the calculation
BASE This is a property of the Budget Line ID.
This provides the Base, like GSV or Net Volume, of the calculation.
DRIVER This is a property of the Budget Line ID.
Generally a Rate per the Base, like Price or TA rate. This input also drives what AUDITID the data
will be written back to.
MULTIPLIER This is a property of the Budget Line ID.
This has been configured to be a 1 or -1 in order to alter the signage of the result as needed.
SCRIPT This is a property of the Budget Line ID.
This is a 3 character length property that is used to group and class the type of calculation. Some
calculations depend on other calculations be execute first. These calculations are called in order
via default logic.
Table 21 Calculations configured as part of implementation

SCRIPT BUDGET LINE BASE DRIVER MULTIPLIER
COGS SKF_COGS_STANDARD_LABOUR SKF_VOLUME_NET SKF_COST_LABOUR 1
COGS SKF_COGS_STANDARD_MATERIAL SKF_VOLUME_NET SKF_COST_MATERIAL 1
COGS SKF_COGS_STANDARD_OVERHEAD SKF_VOLUME_NET SKF_COST_OVERHEAD 1
COGS SKF_COGS_STANDARD_PACKAGING SKF_VOLUME_WAST SKF_COST_PACKAGING 1

E
COGS SKF_COGS_WASTE_LABOUR SKF_VOLUME_WAST SKF_COST_LABOUR 1

E
COGS SKF_COGS_WASTE_MATERIAL SKF_VOLUME_WAST SKF_COST_MATERIAL 1

E
COGS SKF_COGS_WASTE_OVERHEAD SKF_VOLUME_WAST SKF_COST_OVERHEAD 1

E
COGS SKF_COGS_WASTE_PACKAGING SKF_VOLUME_WAST SKF_COST_PACKAGING 1

E
GSV ZCONA01.000010_INP SKF_VOLUME_NET SKF_PRICE -1
GSV SKF_TRO SKF_VOLUME_NET SKF_TRO_RATE 1
LOG SKF_COST_VAR_COMMISSIONS SKF_VOLUME_NET SKF_LOG_RATE_COMMISSION 1

S
LOG SKF_COST_VAR_DEPOT SKF_VOLUME_NET SKF_LOG_RATE_DEPOT 1
LOG SKF_COST_VAR_LABOUR SKF_VOLUME_NET SKF_LOG_RATE_LABOUR 1
LOG SKF_COST_VAR_TRANSPORT SKF_VOLUME_NET SKF_LOG_RATE_TRANSPORT 1
LOG SKF_COST_VAR_WAREHOUSE SKF_VOLUME_NET SKF_LOG_RATE_WAREHOUSE 1
PA1 SKF_PA_V_ OFFINVOICE ZCONA01.000010_INP SKF_PA_R_OFFINVOICE 1
PA2 SKF_PA_V_ DEFERRED SKF_INVOICE_VAL SKF_PA_R_DEFERRED 1
TA1 SKF_TA_V_ OFFINVOICE ZCONA01.000010_INP SKF_TA_R_OFFINVOICE 1
48
TA2 SKF_TA_V_ DEFERRED SKF_INVOICE_VAL SKF_TA_R_DEFERRED 1
5.2 CAPEX Model

This model captures high-level CAPEX for the purpose of budget to calculate additional expenditure
and associated depreciation. It does not supplement the CAPEX planning and approval process, such
as the “wish-list” or comprehensive CAPEX reporting.
The model will load existing capital assets and associated depreciation schedule from BW. Then the
model will cater for additional assets to be entered and calculated the associated depreciation based on
standard percentage per asset class. Asset removals will be catered by manual input of the asset at
cost, accumulated depreciation and the associated depreciation expense that was loaded from BW.

A Business Process Flow (BPF) is a web-based user interface (UI) that is used to guide users through
a sequence of activities in a process. Users can access their activities from the Web Client and use the
workspaces with hyperlinks to jump into other workspaces or into Excel.
Preparation
NAME ACTIVITIES ENVIRONMENT LINK CARRIE
DESCRIPTION D OUT
BY
Set Assumptions Input schedule to EXCEL BPC_IS_04 - DEPRECIATION_RATE.xls FINANCE

maintain the depreciation ADMIN
rates
Existing Assets Automatic data loading DATA 1)Package link: “GF Transaction Data FINANCE
Loading from BW(ZCCA_M02) to MANAGER Import ADMIN
BPC of existing accounts
2)Package: ””05_TRANSACTION DATA
LOADING”
Overview Report Excel report to verify the EXCEL BPC_RP_01 - OVERVIEW_CAPEX.xls FINANCE
data loading ADMIN
Existing Assets BPC template to enter EXCEL BPC_IS_03 - EXISTING_ASSET.xls FINANCE

manual input data manually (only for ADMIN
APAC companies)
New and Remove Assets

DESCRIPTION D OUT
BY
New Asset input and BPC template to enter EXCEL 1)TEMPLATE: “BPC_IS_01 – USERS
automatic “NEW ASSETS” and run ASSET_ADDITIONS.xls”
depreciation. automatic depreciation
calculation.
Asset Removals BPC template to enter EXCEL “BPC_IS_02 – ASSET_REMOVALS.xls” USERS
49
“ASSET REMOVALS”.
Currency Conversion
DESCRIPTION D OUT
BY
Currency Translation Automatic package to DATA 04_FX_TRANSLATION USERS

perform the Currency MANAGEMENT
Conversion rules
OR WEB
Check Currency BPC report to verify EXCEL BPC_RP_02 - USERS

Translation translated results CURRENCY_CONVERSION_CHECK.xl
s
5.2.3 Script Logic

DEFAULT This script copies the ACTUAL version into the correct forecast Default
version for the correct number of periods. For example, for 3+9
Forecast, this script copies in first three periods of Actual.
data from BW.

Maintenance

script.
DEPRECIATION
5.3 OVERHEAD Model

The OVERHEAD model will capture all cost elements for all overheads cost centres that do not roll
up into Standard Cost. The OVERHEAD model will show all cost elements and highlight which ones
are available for input. The greyed out cost elements are either populated using other models, such as
sales, or not required for budget.
Once the OVERHEADS model is complete, the costs will be allocated via the allocation process.
KPI entry have been included as part of this model and feed into the BI reporting model.
50
Preparation
DESCRIPTION D OUT
BY
Set Assumptions Input schedule to EXCEL BPC_IS_02_BUDGET_SCHEDULE_KPI.x FINANCE

maintain the KPI data. ls ADMIN
Actual/Forecast Automatic data loading DATA 1)Package link: “GF Transaction Data FINANCE
loading from BW(ZCCA_M02) to MANAGER Import”” ADMIN
BPC.
2)Package: “03_IMPORT_TX_DATA”
Overview Report Excel report to verify the EXCEL BPC_RP_01_OPEX.xls FINANCE

data loading ADMIN
APAC manual BPC template to enter EXCEL BPC_IS_03_OPEX_ACTUAL_APAC.xls FINANCE

input data manually (only for ADMIN
APAC companies)
Cost Centre Activities

DESCRIPTION D OUT
BY
Actual/Forecast BPC report to check the EXCEL BPC_RP_01_OPEX.xls USERS

Reviewing ACTUAL loading
Budget Data Entry BPC template to enter EXCEL BPC_IS_01_OPEX_BUDGET.xls USERS

budget data.
Currency Conversion
NAME ACTIVITIES ENVIRONMEN LINK CARRIE
DESCRIPTION T D OUT
BY
Currency Automatic package to DATA 01_CURRENCY_CONVERSION USERS

Translation perform the Currency MANAGEMEN
Conversion rules T
OR WEB
Check Currency BPC report to verify EXCEL BPC_RP_02_CURRENCY_CONVERSION.x USERS

Translation translated results ls
5.3.3 Script Logic

DEFAULT This script copies the ACTUAL version into the correct forecast Default
version for the correct number of periods. For example, for 3+9
Forecast, this script copies in first three periods of Actual.
51
data from BW.

Maintenance

script.
5.4 Planning Tasks

5.4.1 Copy Actual Data to Forecast
In order to populate the Actual Data in the Forecast versions a script has been created rather than
using the standard BPC copy function. This script uses a property, called “FORECAST_PLANNING”
in the VERSION dimension to identify which forecast periods should be populated with which
periods.
For the CAPEX and OVERHEAD model, this logic has been included as “DEFAULT” Script Logic.
When loading ACTUAL data from BW to BPC, default logic will run automatically in order to copy
values from ACTUAL to the right forecast version (F2014.01,F2014.02 etc.).
In the SALES & TDC model this is called via a data manager package in order to improve
performance.
Table 22 Copy Actual to Forecast scripts

MODEL NAME OF COPY VERSION SCRIPT
CAPEX DEFAULT
OVERHEAD DEFAULT
SALES COPY_ACTUAL.LFG (CALLED VIA THE SALES BPF)
5.4.2 Copy from STAGE version to working version

In order to simplify on-going maintenance of transformation and conversion files within each model,
all Plan Version uploads from BW will be loaded to F_STAGE (Forecast versions) and B_STAGE
(Budget versions). This was decided in consultation with GFIT, and the main advantage was a simpler
approach for end-users and reduced BPC maintenance for GFIT.
Once data has been loaded into BPC, end-users must copy the data into the correct working version. A
simple package has been created to copy values from B_STAGE/F_STAGE (in selection) to the
working version (B2014F/F2014.01,F2014.02 etc. to specify in the second prompt) the period of
origin is the same of destination. This has been added to the BPF of each model.
Alternatively, users are able to use the BPC standard copy function.
Table 23 Copy STAGE version to working version
MODEL NAME OF COPY VERSION SCRIPT
CAPEX COPY_VERISON
52
OVERHEAD COPY_VERISON
SALES COPY_VERISON
5.4.3 Currency Conversion

The Currency Conversion calculation is set in the Currency Translation Rule. The Account dimension
(of each model: CAPEX, OVERHEAD and SALES&TDC) has the Ratetype property that is used to
select accounts in the currency translation business rules thereby acting as an account grouping
mechanism.
To create a currency translation rule, you first select an ID. The IDs are the Rate Type property values
in the Account dimension. Then, the fields of the rule need to be configured based on the desired
translation.
This function operates the same as Phase One with the exception of “COPYLC” rate type. In some
situations currency conversion is not appropriate for all Accounts. For example, KPI like Headcount
or FTE. COPYLC rate type simply copies the Local Currency to the Group Currency; meaning that
Local Currency and Group Currency equal.
Figure 34 Administration screen for BUSINESS RULES
Figure 35 Maintenance Screen for Rate Types
53
Figure 36 Example of Rate Type maintenance
The package can be executed from the BPC Office client as per below or through the BPF provided in
each model.
Figure 37 Currency Conversion Package in Data Manager
5.5 Plan Integration BPF

The Plan Integration Business Process Flow is a list of activities that controls the final approval of
data in the models, work status and transfer of data between models.
The below explains the Plan Integration BPF in detail.
Approving CAPEX
NAME ACTIVITIES ENVIRONMENT LINK CARRIED OUT BY
DESCRIPTION
Work Status Web prompt to set up WEB Work status FINANCE ADMIN
Work Status
Work Status Report Excel report to verify EXCEL BPC_RP_03 – FINANCE ADMIN
Work Status WORK STAUS.xls
Feed data to Data Manager DATA MANAGEMENT 02_FEED DATA TO FINANCE ADMIN
Consolidation model package to feed data CONSOLIDATION
into Consolidation MODEL
model
Overhead model package to feed data OVERHEAD
into Overhead model. MODEL
54
Approving OVERHEAD
DESCRIPTION
Work Status Web prompt to set WEB Work status FINANCE ADMIN
up Work Status
Work Status Excel report to EXCEL BPC_RP_03_WORK_STATUS.xl FINANCE ADMIN

Report verify Work Status (OVERHEAD) s
Allocation Template used to EXCEL 01_IS - GF ALLOCATION UI.xls FINANCE ADMIN

Mapping set up the mapping (ALLOCATION)
rules and mapping
transaction data.
Allocation Input Input template to EXCEL 02_IS - ALLOCATION MAPPING FINANCE ADMIN
schedule send and check (ALLOCATION) INPUT TEMPLATE.xls
mapping
transaction data.
Allocation report Excel report to EXCEL 01_RP_BPC - ALLOCATION FINANCE ADMIN

verify data pre and (ALLOCATION) CHECK.xls
post Allocation
Allocation Data Manager DATA 08_OH_SALES_ALLOC FINANCE ADMIN

package to run MANAGEMENT
Allocation (SALES)
Approving SALES & TDC

DESCRIPTION
Work Status Web prompt to set up WEB Work status FINANCE ADMIN
Work Status
Work Status Report Excel report to verify EXCEL BPC_S_R_03 - FINANCE ADMIN
Work Status WORK_STATUS.xls
m
Consolidation model package to feed data CONSOLIDATION
into Consolidation MODEL
model
Balance Sheet
DESCRIPTION
Assumptions Input Form to maintain EXCEL BPC_RW_08 – FINANCE ADMIN

DSO,DPO and Inventory ASSUMPTIONS
turnover INPUT.XLS
Balance Sheet Entry Excel Input Form used to EXCEL BPC_RW_03 – FINANCE ADMIN
55
send Balance Sheet data PLAN BALANCE
in Consolidation SHEET INPUT.XLS
Account Excel Input /Report Form EXCEL BPC_RW_09 – FINANCE ADMIN

Payable/Receivable PLANNING
used to calculate the
Inv. Turnover BALANCE SHEET
Account
RATIO.XLS
Payable/Receivable and
Inv. Turnover
56
6 General Administration
6.1 Security Set Up
On the front end side in SAP BPC 10 there is no change in security except that the users are
NetWeaver users whereas in MS version they are Active Directory users.
Figure 38 Security Administration Screen
You can access all the views related to the security topics under the security domain in the left side
panel of the administration workspace.
 Users
 Teams
 Task Profiles
 Data Access Profiles
6.1.1 User Management

The user management screen lists all users and allows you to add a new user or delete an existing
user. The properties of the users are taken from BW and cannot be changed in BPC.
57
Figure 39 User Maintenance screen

Figure 40 Making alterations to Users configuration
6.1.2 Team Management

The team management screen has a list of the teams and allows you to create or delete a team. You
can create a team without any users assigned to it.
58
Figure 41 Teams Maintenance Screen
Figure 42 Making alterations to Teams configuration
6.1.3 Task Profile Management

In the task profile management screen, you can create a task profile from scratch or copy an existing
one. You can also edit and delete a task profile.
Figure 43 Task Profile Maintenance Screen
59
6.1.4 Data Access Profile
The list of all the data access profiles created in this Environment is shown above. From this list you
can create a data access profile from scratch or copy an existing one. You can also edit and delete a
data access profile (multiple deletion is allowed). In addition to the ID and description of a data access
profile, you can see how many teams and users have this data access profile.
Figure 44 Data Access Profile Maintenance Screen
Figure 45 Making alterations to Data Access Profiles
6.2 Maintaining dimension properties

Launch Planning and Consolidation Administration
60
Click on the Dimensions under Dimensions and Models
To edit the dimension members select the dimension you want to edit and press edit members button.
61
Update the members of the dimension and save.
Select the particular dimension need to update or create new properties and click on the Edit structure
button. Add the new properties or update the existing properties, save and close.
6.3 Create new versions (Budget & Forecast)

1. Navigate to the BPC administration Web Page and open the ‘Dimensions’ Tab. Open the
VERSION Dimension.
62
2. Maintain the property GL_FORCAST if the new member is a FORECAST member (F01,
F02, F03 or F04).
3. Maintain the property OPENING_PERIOD “C/Fwd: Opening Period”: it always has to be
“DEC”.
4. Maintain the property YEAR with the reference Year
5. Maintain the property START_MNTH “Starting month” : it need to be always “1”.
6. Maintain the property ALLOCATION_END_PERIOD : it need to be with this format
“2014012”(YYYYMMM).
7. Maintain the property ALLOCATION_OPEN_PERIOD : : it need to be with this format
“2014001”(YYYYMMM).
8. Maintain the property GL_FORECAST : : it need to be maintained just for forecast versions
with these values : F01,F02,F03,F04. It need to be unique, this means that when we create a
new forecast for example “F2015.01” we have to assign F01 at this one and remove the old
value from F2014.01.
9. Maintain the property FORECAST_PLANNING : : it need to be maintained just for forecast
versions with these values : F01,F02,F03,F04. It doesn’t need to be unique, this means that
when we create a new forecast for example “F2015.01” we have to assign F01 at this one and
we can leave the old value from F2014.01.
10. Click Process
63
6.4 Create a new company
Where a new company code has been created in SAP, this will automatically flow through to BPC.
With the exception of a few prerequisites:
1. Create COMPANY in BPC administration

2. Create reference INTERCO in BPC administration
3. Maintain ownership structure
4. Create new INPUT_CURRENCY if required and enter exchange rates into BPC
5. Set up security (create new team or add this company to an existing team, maintain BPF
access through the properties)
It is always easiest to create new members by copying an existing members (in reference to ENTITY
and INTCO) to ensure all necessary properties are maintained.
6.5 BPF Maintenance

6.5.1 How to create a BPF Instance
Once the BPF template has been defined saved and validated, the administrator can deploy instances
for execution.
To create a new instance click + New
Creating an instance is a 4 step process:

1. Select the process template
2. Select the context that the instance will be identified with.
3. Review and update the assignments, use the change performer and change reviewer options
to reselect new individuals.
4. Review all selections. You have the option to start the instance immediately if desired.
64
6.5.2 How to suspend and archive a BPF Instance
Suspend stops the current instance and removes it from the activity list of all users regardless of
whether it is completed or not.
Archive removes the instance from the administrator screen and allows the time period and version
combination to be re-used.
An Administrator would need to perform this step in the following situations:

1. If the Administrator has made a change to the BPF. Changes are not automatically loaded
into “Active” BPFs. If the change is required immediately then the active instances must be
suspended, archive and re-initiated.
2. General maintenance to clear activities from end-users lists
3. General maintenance to clear instances from the administrator’s screen.
To remove an old BPF

1. Click on Process Instances
2. Highlight the desired instance to archive

3. Press Suspend from the options. This will stop the instance and remove the instance from the
activities list of all
4. Then Archive to remove complete (There is no way of getting the BPF after this step)
6.5.3 General questions about BPF

 What does the time-period selection do when selected as part of the BPF instance?
 Will the system therefore block any prior period for write mode to protect the actual?
Answer to both of the above: The time period that is selected is only for reference purposes, it does
not impact/run any other function
1. Uploading data - controlled through the data manager package filters. The BPF has no impact on
what you can select.
2. Change write or read modes - This is controlled through work status. The BPF has no impact on the
work status setting.

65
 Do we need to define how this will work in practice? ie are we going to use Qtr periods
to define the instance
This is a business decision. If be the most logical to align the timeperiod to the Qtr that you are doing.
That is,
Forecast 3 + 9 = 2014.003 or Qtr 1
Forecast 6 + 6 = 2014.006 or Qtr 2
Forecast 9 + 3 = 2014.009 or Qtr 3
Budget 2015 = 2015.001 or Q4<---remember this controls the time selection in your report

If you went to a rolling monthly process, it would just a monthly process.

 If you delete an instance it only deletes the activities but keeps the data
Correct, all the deletion does is remove the list of activities from the main menu, data remains exactly
as is. The words used by BPC are "Suspend" and "Archive" a BPF, as it does not "delete" anything.
 If you create a new instance with a deleted period, does it overwrite the existing data?
No, the data is not impacted by the creation of a new instance with the same timeperiod. It will start at
the first step of the BPF, yet users can skip ahead by just selecting "Complete".

Outside of UAT, changing the BPF mid-process would be unusual and a rare occurence. It is just that
we are making changes and these changes will not update already commenced BPFs. This is by
design, so you can work on an update to a BPF without impacting users.
6.6 Light Optimization with compression

Compresses database and aggregates data, rebuilds indexes and rebuilds statistics. There is no set
recommendation as to the frequency, however it is generally recommended that these (index/statistics)
tasks be executed after the load process to provide satisfactory performance for reporting and input
schedule updates.
66
6.7 EPM
The EPM add-in is an add-in to Microsoft Office Excel, Microsoft Office Word and Microsoft Office
PowerPoint. The EPM add-in is designed to give access to SAP Business Objects EPM Solutions'
product data, transforming that data in real time into a form which supports reporting and providing
reporting and delivery tools.
6.7.1 Re-activating the EPM Add-in

If the EPM add-in has been deactivated, you can re-activate it.
1. In Microsoft Office Excel 2007, click the Office button, then click the Excel Options button.
2. In the Excel Options dialog box, select Add-Ins.
3. Select Disabled Items from the Manage drop-down menu and click the Go button.
67
4. In the Disabled Items dialog box, select the SAP BusinessObjects EPM Solutions, add-in for
Microsoft Office and click the Enable button.
5. Click the Close button.
NOTE
You can also quickly re-activate the EPM add-in by executing the AddinManager.exe from the installation folder and selecting
Enabled from the dialog box that opens.
6.7.2 Report and Input Schedule Design

Every Model has the Reports and Input Schedules Stored in the Company Reports\Input
ScheduleGOODMAN_FIELDER
6.7.3 Report and Input Schedule Protection

Each Report is protected. To change, the password is ‘bpc’.
To see all the components of a BPC report, open the report in Excel, select the View tab and tick the
‘Headings’ box.
Select the top row of the report and right click, drag upwards, then right click ‘Unhide’
Several design features are below.
68
6.7.4 Report Format
6.7.5 Input Schedule Format
Context dimensions are locked against users changing. Any Dimensions not selectable by users in the
report or Input Schedule are locked in the Context.
69
The ‘Hide’ option has been enabled for dimensions in the Context Options.
70
7 Appendix
The below items are files that have be provided as part of the implementation and are true and correct
at the time of writing. Note that readers should be aware that these are copies of live files which may
have been altered after they have been attached here.
7.1 Transformation Files
ZCCA_M02 ZCCA_M02 ZCCA_M02_TRANSA TD_ZBPC_M05_VOLU TD_ZOBPCR8S_PRIC

TRANSFORMATION FILE.XLS
TRANSFORMATION FILE_OPENING.XLS
CTION FIGURES FOR BPC.XLS
ME.xls E.xls
TD_ZOBPCR8S_STA TD_ZOBPCR8S_TA_P TD_ZOBPCR8S_VOL

NDARD_COST.xls A.xls UME.xls
7.2 Conversion Files
ZCCA_M02.XLS ZCCA_M02.XLS
7.3 BPC Security Matrix
Security Audit -
Teams.csv
7.4 Account Mapping (Sales Model)
BW TO BPC
MAPPING 14032014.xlsx
71

Fielder Budget &amp; Forecasting - Technical

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fielder Budget &amp; Forecasting - Technical

Uploaded by

Copyright:

Available Formats

Goodman Fielder

BPC Budget & Forecast

Configuration & Administration Guide

Liability limited by a scheme approved under Professional Standards Legislation.

Version Date Author(s) Major Changes

V1 07/03/2014 Simona Document Creation (draft)

V2 16/03/2014 Matt Newey Included Sales & TDC model documentation

V3 31/03/2014 Sabine Bennett Final Release

1.1 Related Documents

V3 31/03/201 Matt Newey Goodman Fielder BPC Allocation - Technical Document

V3 31/03/201 Danielle Goodman Fielder BPC BAdI Allocation - Technical Document

V1 18/07/201 Sabine Bennett GF Configuration Document – BPC Consolidation (Phase One)

1.2 Stakeholder and Distribution List

GF Finance Project Sponsor Meredith Symons

GF Finance SME – New Zealand Paul Turnbull

GF IT Project Sponsor Paul Williams

2 Limitation of our work

3.2 Scope of work

The scope of phase includes:

Sales & TDC Model

Specifically out of scope for this phase

The purpose of this document is to:

The second phase encompassed;

Figure 1: Illustration of the BPC functional cubes

SALES & TDC

BPC Templates & Functions:

BPC Templates & Functions: BPC Templates & Functions:

SAP BW Data Warehouse

SAP ECC6 / APO / Third Party Systems

Table 1 Summary of all BPC models

GOODMAN CONSOLIDATION YTD Consolidation This core model contains consolidation

GOODMAN OWNERSHIP PER Ownership This model stores ownership information

4.3 Dimension Overview

DIMENSION MAINTENANCE INFO-OBJECT TDC CAPEX OVERHEAD S

COST CENTRE LOAD VIA CAPEX 0COSTCENTER Y Y Y

CUSTOMER LOAD VIA SALES&TDC ZCUSTKAG2 Y Y

OH_ACCOUNT LOAD VIA OVERHEADS 0COSTELMNT Y

PRODUCT LOAD VIA SALES&TDC ZMATLBPC Y Y

PROFIT CTR MANUAL Y Y Y

REGION LOAD VIA SALES&TDC 0CUST_GRP5 Y

SEGMENT LOAD VIA 0SEGMENT Y Y

The areas in which analysis is carried out for planning are:

 Tracking of specific adjustments types (PLAN_ADJ & PLAN_ADJ_PER)

The following properties are required:

IS_CONSOL Y/Blank Y = Data will be considered for consolidation. Manual

IS_CONVERTED Y/Blank Y = Data will be considered for currency Manual

DATASRC_TYPE A/I/M A= Automatically calculated Manual

“Data_type” I = Manually input

COPYOPENING Y/Blank Y = Included in the balance carry forward Manual

ENABLEJRN Y/Blank Y = Journal entries will be allowed Manual

OPENING_DATASRC BCF This property identified the AUDITID of Manual

IC_ORIGINE I/C1/C2 etc The property performs the IC Matching. Manual

C1= Their Liabilities/Expense

PALLOC_ACTIVE 1 The property activates the allocation Batches Automated

PALLOC_DRIVER ZCONA01.00010_INP This property identified the allocation Driver Automated

PALLOC_BDG_ACCT_LINE ZCONA01.02400_INP Allocation destination account Automated

PALLOC_SRC_ACCT_RNG Blank=all, GL6*= GL6 Allocation Source Account Range Automated

IS_BR2 Y/Blank Y = Triggers BADI to run adjustment for SALES Manual

IS_COPY Y/Blank Y = Triggers BADI to run adjustment for SALES Manual

IS_INPUT Y/Blank Y - controls formatting on SALES & TDC input Manual

4.3.4 CAPEX ACCOUNT

CAPEX accounts are grouped in main 3 categories:

The following properties are required for this dimension:

DESTINAITION Y,Z,X This property is used in the Logic Manual

Fielder Budget & Forecasting - Technical

Fielder Budget & Forecasting - Technical