SAP Cash Flow Configuration Design Document - v1.0 - APPROVED

SAP Solution Design
Project CASH FLOW

Customer Serco
Solution SAP Business Planning and Consolidation
Netweaver, release 10 (SAP BPC NW 10)
Version 1.0 (Approved)
Authors Ana Sobreira & Frédéric Baranger
Date 8th May 2014
Serco Internal
SAP Cash Flow Configuration Design Document v0.8.docx
Document Control
Version Date Author Notes
v.01-3 14th Marc 2014 Ana Sobreira Template issued and first draft for CF
Design
v.03 26th March 2014 Peter Voss Updates to document to align to SDF
th
v.04 4 April 2014 Ana Sobreira Updates from design walkthrough No
1
v.05 09th April 2014 Martin Wilson SAP review
th
v.05 10 April 2014 Ana Sobreira, SAP review & updates in line with
Frédéric Baranger, requirements document and
Janina Hewitson addiitional feedback.
v.06 16th April 2014 Janina Hewitson Updates during the Design
walkthrough meeting No.2.
v.07 18th /19th April Ana Sobreira, Additions post Design walkthrough.
2014 Frédéric Baranger, Updates on Open Issues.
v.08 Final 22nd April 2014 Janina Hewitson Post Review additions.
v.09 23rd April 2014 Steve Woodhouse Updated post 1st Q&A session
v.091 24th April 2014 Steve Woodhouse Updated post 2nd Q&A session
th
v.092 25 April 2014 Ana Sobreira, Updated post Becky Parsons and
Janina Hewitson Cathy Fagg update
Frédéric Baranger
v.93 28th April 2014 Ana Sobreira Updated post Traceability session
th
v.94 29 April 2014 Ana Sobreira Further updates post Tracebility
Frédéric Baranger session on 28th April 2014 and v0.3 of
Security Design Document updated in
Carly Foreman
appendix
v.95 29th April 2014 Ana Sobreira Update appendices and open issues
Frédéric Baranger as a result of input schedules and
calculations review
Carly Foreman
v.96 Final 1st May 2014 Carly Foreman Update post final review/walkthrough
V1.0 8th May 2014 Steve Woodhouse Updated post PB approval and latest
Approved security architecture doc
Document Location
Location
 Collaboaration Room in OurWorld
 Room = BPC10 Programme
 URL - BPC10 Programme
Printed on 15 September 201906 July 201423 June 2014 Serco Internal

page 2 of 79
Approval
Name Role Date Signature
All Programme Board Members

Barbara Inskip Programme Sponsor / Senior 8th May 14 Prog Board
Responsible Owner (SRO) Mins
James Sinclair Group Reporting Director See above See above
Julie Bryer Finance Process & Controls Director See above See above
Caroline McKinnon Group Reporting Manager See above See above
Tony Sullivan SGS Head of Finance See above See above
Andrew Martin UK&E Head of Finance See above See above
Toby Slater Head of Fin. Planning & See above See above
Transformation
Lester Loh Group IT Director See above See above
Jason Hookey GTD Head of Corp Delivery See above See above
Sheryl Ward GTD PMO Project Assurance See above See above
Stephen GTD PMO Project Support See above See above

Woodhouse
Peter Voss GTD Programme Manager See above See above
Adrian Day GTD Project Manager See above See above
Mark Harper SAP Quality Director and SAP See above See above
Sponsor
Janina Hewitson SAP Project Manager See above See above
Emma France R2R GPO See above See above
Distribution
Name Role
All Programme Board Members (As Above)
All BPC10 Programme Team Members
Emma France, Caroline MacKinnon, Carly Foreman and Cathy Fagg

page 3 of 79
Table of Contents
1. Document Purpose ................................................................................................. 86

2. Management Summary .......................................................................................... 97
3. Scope ................................................................................................................... 108
3.1. In Scope ..................................................................................................... 108
3.2. Out of Scope ............................................................................................ 1210
4. Document Assumptions ...................................................................................... 1412
5. Key Design Decisions ......................................................................................... 1513
6. Dependencies .................................................................................................... 1715
7. To be High Level Process Overview ................................................................... 1816
7.1. Logging into BPC ..................................................................................... 1816
7.2. Monthly process overview ........................................................................ 1816
8. SAP BPC Data Model ......................................................................................... 2018
8.1. SAP BPC Environment ............................................................................. 2018
8.2. SAP BPC Models ..................................................................................... 2018
8.3. SAP BPC Dimensions .............................................................................. 2220
8.3.1. Account Dimension .................................................................................. 2523
8.3.2. Structure of the Chart of Accounts ............................................................ 2624
8.3.3. Flow Dimension ........................................................................................ 3028
8.3.4. Other dimensions ..................................................................................... 3634
9. SAP BPC Data Integration .................................................................................. 3937
9.1. SAP BPC Master Data ............................................................................. 3937
9.1.1. SAP BPC Transactional data.................................................................... 3937
9.1.2. SAP BPC Interface with Hyperion ............................................................ 4341
10. SAP BPC Business Processes ........................................................................... 4543
10.1. Flow calculations ...................................................................................... 4543
10.1.1. Flow F15 (Movement) calculation ............................................................. 4543
10.1.2. Opening Balances .................................................................................... 4543
10.2. Calculations within and between schedules.............................................. 4543
10.3. Equity accounting for JV Entities .............................................................. 4644
10.3.1. Calculation of technical accounts ............................................................. 4745
10.3.2. Data Copy from JVX to JVX_EA ............................................................... 4846
10.3.3. Calculate the SOCI with EA impacts......................................................... 5048
10.3.4. Calculation of the FX impact for Equity Accounting .................................. 5048
10.4. Foreign Currency Conversion ................................................................... 5149
10.4.1. Principles.................................................................................................. 5149
10.4.2. Rates Definition and Rate model .............................................................. 5149
10.4.3. Rule Definition .......................................................................................... 5250

page 4 of 79
10.4.4. FX system calculation............................................................................... 5755

10.4.5. Historical values ....................................................................................... 5755
10.4.6. Consolidation Monitor ............................................................................... 5856
10.5. Validations and Controls........................................................................... 5957
10.5.1. Validation report ....................................................................................... 5957
10.5.2. Master data validation .............................................................................. 6260
11. Schedules........................................................................................................... 6361
Formatted: Default Paragraph Font, Check spelling
11.1. Schedules (Input Forms and Reports) ...................................................... 6361 and grammar
11.1.1. Global design approach............................................................................ 6765 Formatted: Default Paragraph Font, Check spelling
11.1.2. Locking data within schedules: ................................................................. 6866 and grammar
11.1.3. Reports printing capabilities:..................................................................... 6967 Formatted: Default Paragraph Font, Check spelling
and grammar
11.1.4. Offline capabilities .................................................................................... 6967
11.2. Navigation between schedules ................................................................. 6967 and grammar
11.2.1. Business Process Flow ............................................................................ 7068 Formatted: Default Paragraph Font, Check spelling
11.2.2. Quick links from Primary Schedules ......................................................... 7068 and grammar
11.2.3. Quick links from validation report .............................................................. 7169 Formatted: Default Paragraph Font, Check spelling
and grammar
11.3. Drill downs reports.................................................................................... 7270
12. SECURITY ......................................................................................................... 7472 and grammar
12.1. Security .................................................................................................... 7472 Formatted: Default Paragraph Font, Check spelling
and grammar
12.2. Data Work Status ..................................................................................... 7573
13. Enhancements ................................................................................................... 7674 Formatted: Default Paragraph Font, Check spelling
and grammar
14. Data Migration .................................................................................................... 7775
15. Appendices......................................................................................................... 7876 and grammar
15.1. DRAFT calculations within and between schedules .................................. 7876 Formatted: Default Paragraph Font, Check spelling
and grammar
15.2. DRAFT schedules layout .......................................................................... 7876
15.3. Security Architecture and DRAFT Design Document ................................ 7876 Formatted: Default Paragraph Font, Check spelling
and grammar
15.4. Design Strategy for BPC dimensions........................................................ 7876
15.5. Activities for data integration for new flows ............................................... 7876 and grammar
15.6. Statement of Work.................................................................................... 7977 Formatted: Default Paragraph Font, Check spelling
and grammar
1. Document Purpose ................................................................................................... 7
2. Management Summary ............................................................................................ 8 Formatted: Default Paragraph Font, Check spelling
and grammar
3. Scope ....................................................................................................................... 9
3.1. In Scope ......................................................................................................... 9 and grammar
3.2. Out of Scope ................................................................................................ 11 Formatted: Default Paragraph Font, Check spelling
and grammar
4. Document Assumptions .......................................................................................... 13
5. Key Design Decisions ............................................................................................. 14 and grammar
6. Dependencies ........................................................................................................ 16
Formatted: Default Paragraph Font, (Asian) Japanese,
7. To be High Level Process Overview ....................................................................... 17 Check spelling and grammar
7.1. Logging into BPC ......................................................................................... 17 Formatted: Default Paragraph Font, Check spelling
and grammar

page 5 of 79
7.2. Monthly process overview ............................................................................ 17 Formatted ...

8. SAP BPC Data Model ............................................................................................. 19 Formatted ...
8.1. SAP BPC Environment ................................................................................. 19 Formatted ...
8.2. SAP BPC Models ......................................................................................... 19 Formatted ...
8.3. SAP BPC Dimensions .................................................................................. 21 Formatted ...
8.3.1. Account Dimension ...................................................................................... 24 Formatted ...
8.3.2. Structure of the Chart of Accounts ................................................................ 25 Formatted ...
8.3.3. Flow Dimension ............................................................................................ 29 Formatted ...
8.3.4. Other dimensions ......................................................................................... 35 Formatted ...
9. SAP BPC Data Integration ...................................................................................... 38 Formatted ...
9.1. SAP BPC Master Data ................................................................................. 38 Formatted ...
9.1.1. SAP BPC Transactional data........................................................................ 38 Formatted ...
9.1.2. SAP BPC Interface with Hyperion ................................................................ 42 Formatted ...
10. SAP BPC Business Processes ............................................................................... 44 Formatted ...
10.1. Flow calculations .......................................................................................... 44 Formatted ...
10.1.1. Flow F15 (Movement) calculation ................................................................. 44 Formatted ...
10.1.2. Opening Balances ........................................................................................ 44 Formatted ...
10.2. Calculations within and between schedules.................................................. 44 Formatted ...
10.3. Foreign Currency Conversion ....................................................................... 45 Formatted ...
10.3.1. Principles...................................................................................................... 45 Formatted ...
10.3.2. Rates Definition and Rate model .................................................................. 45 Formatted ...
10.3.3. Rule Definition .............................................................................................. 46 Formatted ...
10.3.4. FX system calculation................................................................................... 51 Formatted ...
10.3.5. Historical values ........................................................................................... 51 Formatted ...
10.3.6. Consolidation Monitor ................................................................................... 52 Formatted ...
10.4. Validations and Controls............................................................................... 53 Formatted ...
10.4.1. Validation report ........................................................................................... 53 Formatted ...
10.4.2. Master data validation .................................................................................. 56 Formatted ...
11. Schedules............................................................................................................... 57 Formatted ...
11.1. Schedules (Input Forms and Reports) .......................................................... 57 Formatted ...
11.1.1. Global design approach................................................................................ 61 Formatted ...
11.1.2. Locking data within schedules: ..................................................................... 62 Formatted ...
11.1.3. Reports printing capabilities:......................................................................... 63 Formatted ...
11.1.4. Offline capabilities ........................................................................................ 63 Formatted ...
11.2. Navigation between schedules ..................................................................... 63 Formatted ...
11.2.1. Business Process Flow ................................................................................ 64 Formatted ...
11.2.2. Quick links from Primary Schedules ............................................................. 64 Formatted ...
11.2.3. Quick links from validation report .................................................................. 65 Formatted ...
11.3. Drill downs reports........................................................................................ 66 Formatted ...

page 6 of 79
12. SECURITY ............................................................................................................. 68 Formatted: Default Paragraph Font, Check spelling

and grammar
12.1. Security ........................................................................................................ 68
12.2. Data Work Status ......................................................................................... 69 and grammar
13. Enhancements ....................................................................................................... 70 Formatted: Default Paragraph Font, Check spelling
14. Data Migration ........................................................................................................ 71 and grammar
15. Appendices............................................................................................................. 72 Formatted: Default Paragraph Font, Check spelling

and grammar
15.1. DRAFT calculations within and between schedules...................................... 72
15.2. DRAFT schedules layout .............................................................................. 72 and grammar
15.3. Security Architecture and DRAFT Design Document .................................... 72 Formatted: Default Paragraph Font, Check spelling
15.4. Design Strategy for BPC dimensions............................................................ 72 and grammar
15.5. Activities for data integration for new flows ................................................... 72 Formatted: Default Paragraph Font, Check spelling
and grammar
15.6. Statement of Work........................................................................................ 73
and grammar

and grammar

and grammar

and grammar

and grammar

and grammar

and grammar

and grammar

and grammar

and grammar

and grammar

and grammar

and grammar

and grammar

and grammar

and grammar

and grammar

page 7 of 79
1. Document Purpose
The purpose of this document is to describe the both the Solution Design and
Configuration Rationale used to meet the requirements for the CASH FLOW solution
which will be implemented in the SAP Business Planning and Consolidation
application (BPC), Netweaver version in release 10 (BPC10).
In 2011 Serco initiated a SAP BPC implementation and some processes from that
project are already in place. On the previous implementation, two separate
applications (models) had been configured; one for Cash Flow and another one
for Consolidation. On this project, the Consolidation and Cash Flow applications
will be merged into the same model, which is already created and named
‘Consolidation’.
Once this document is approved, it will be become the base reference document
for the build and final project sign off. Any changes to this document after
approval will be subject to the agreed change control process as described in the
BPC10 Programme PID.

page 8 of 79
2. Management Summary
In January 2011, Serco initiated the Halogen Programme to rationalise, standardise

and stream-line financial budgeting, forecasting and reporting processes across
the company, utilising SAP BPC (Business Planning and Consolidation v7.5) and BW
(SAP Business Warehouse v 7.01).
The Programme set out to deliver three project streams; (1) 2012 Commitment, (2)
Management Reporting Packs and (3) Quarterly Re-Forecasting. Bluefin Solutions,
a UK based SAP BI Specialist system integrator was chosen as the prime
implementation partner to implement the Serco requirements on BPC 7.5.
Due to various technical and design reasons, the programme encountered a
number of BPC performance and usability issues that resulted in project delays
and budget overspend as well as the programme team not delivering on the full
original scope. The three specific deliverables that were not completed were:-
a. Ability to do Indirect Cash Flow reporting in BPC

b. Ability to do Balance Sheet planning
c. Ability to do Quarterly Re-Forecasting in BPC.
Cash Flow Reporting was originally part of 2012 Commitment Project, but because
of general performance issues, this deliverable was later moved to the Reporting
Project. When the Indirect Cash Flow solution was released, it was deemed
unusable by the business, because of the long waiting times users experienced
when saving data within the input schedules.
With the combination of all of the BPC performance and usability issues that
resulted, Serco initiated an escalation with SAP in December 2012 to request SAP
to help resolve these issues. During the escalation period, SAP reviewed amongst
other things, the Indirect Cash Flow Reporting process that was configured for
Serco, i.e. Input schedules, Cash Flow calculations and Cash Flow reporting with a
specific focus on trying to improve the save times for input schedules.
On completion of the Cash Flow design review in June 2013, a set of design
change recommendations were made by SAP. Serco have accepted SAP’s
proposal to upgrade to SAP’s latest BI planning and reporting platform (BPC v10)
and the redesign and delivery of the Indirect Cash Flow reporting solution in BPC
NetWeaver 10.

page 9 of 79
3. Scope
3.1. In Scope
The Project scope is as follows:

 Implement a new Chart of Accounts, which is aligned to ECC and manually
maintained in the short term. It will use the same ID (codification) of ECC
CoA. This new CoA will replace the StarterKit CoA currently used in the
Consolidation model.
 Due to the requirement to change configuration in ECC to activate Group
Accounts and design a financial statement version for loading CoA into
BPC, integration will be implemented in the future by Serco.
 Implement new Flows.

The number of ‘real’ flows has been reduced because the same flows can
be re-used across multiple schedules using different descriptions.
 Implement all 37 Hyperion Enterprise schedules currently used by the
Business users to input and analyse data. These are listed below:
1. Income statement
2. Balance Sheet
3. Cash Flow
4. Free Cash Flow
5. Net Debt
6. Revenue
7. Cost of Sales
8. Administration Expenses
9. Investment Revenue
10. Tax charge
11. Goodwill
12. Other Intangible assets
13. Property, plant and equipment
14. Subsidiaries Investment
15. Joint Ventures Investment
16. Associates Investment
17. Retirement Benefit Schemes
18. Loans
19. Intercompany Loans
20. Trade and other receivables
21. Tax
22. Derivatives

page 10 of 79
23. Inventories
24. Trade and other payables
25. Finance lease obligations
26. Non-recourse loans
27. Provisions
28. Reserves
29. Acquisitions
30. Disposals
31. Transfers from/(to)
32. Sector & Geographical - Segmental Information
33. Headcount
34. Operating leases
35. Capital commitments
36. Aged debtors / Bad debt provision
37. Long term contracts
 Drill Down reports by detailed Entity level.

 Links between schedules.
 Cash Flow, Free Cash Flow, Net Debt calculations and other calculations
between schedules.
 Currency translation, including some specific FX rates on schedules.
 Intercompany turnover elimination is already calculated before data
upload into Cash Flow cube (SAP BPC consolidation model). It is in the
scope of this project to guarantee the mapping of calculations already
done with the new CoA and Flow.
 Validations and controls to ensure the accuracy and consistency of the
data values.
 For a specific limited period SAP BPC NW 10 should have the ability to
transfer data, inputted by users in BPC, into Hyperion. The main objective of
this functionality is to enable a parallel run and avoid users having to input
data twice.
 The ability to run Hyperion Enterprise and BPC in parallel (i.e. load and input
data) post 2014 will still be available, if required.
 Cash Flow project will run on SERCO_FPRS environment in the Consolidation
model. Other models are not in scope. If there are any changes in the
Consolidation model for shared objects such as dimensions, then the
impact on other models will need to be assessed.
 The Cash Flow solution will be able to provide Cash Flow reporting for any
category e.g. actual, budget, forecast or any new category that’s
introduced at later date.

page 11 of 79
 User prompted calculations

One of the key criteria for the project is that users will not need to ‘push’ any
calculation buttons. The calculations will be run automatically when the
data is saved by the user, using a writeback BADI.
 Consolidation Monitor
Consolidation Monitor is functionality delivered in BPC NW 10. This a
workspace for monitoring the consolidation progress for a specific
consolidation scope, for a given category, period group or sub group.
Consolidation monitor is a key component in executing incremental
processing since it communicates the timestamps to the consolidation
engine. The monitor can be used to execute the currency translation at
group or entity level.
 Data export to Hyperion – BHI
BHI tool will not technically change but an additional mapping between
SAP BPC consolidation model for accounts, flow dimensions, Hyperion
accounts, and sub accounts is needed. Several additional properties on
account dimension will be created and maintained for this purpose. This is
needed for a specific limited period after Go Live (during parallel running),
and for the benefit of end users to eliminate the need to enter same data
twice (SAP BPC and Hyperion).
 Business Process Flows

To access the Schedules (currently 37), the users will use a Business Process
Flow and then navigate from schedule to schedule using quick links.
Related to this issue there is an open issue because users shouldn’t be able
to close business process flows before ending their activities.
3.2. Out of Scope
Any other changes required, that are not referred to in the previous section (3.1),
will be considered out of scope.
Examples of items out of scope are:
 Dimensions in the Consolidation model, apart from CoA, Flows, Entity and
ConsoScope will not be changed. For example Interco, Time, etc. It is
possible there may be changes in the future due to new requirements
arising, such as from the Intercompany matching project, but they are not
currently in the Cash Flow scope.
 Data integration processes, such as master data and transactional data will
use the Cash Flow model processes, which are already in place.
 Security model
This will be developed by Serco and the design will be specified in an
additional document, which for consistency and review purposes only is
included as an Appendix and referenced in Section 12.
 Data Audit.
This is not being used in Hyperion system and will not be used in BPC
Consolidation as it will impact system performance.

page 12 of 79
 Journals functionality
This has not been identified as a requirement. As business policy is to post
journals at source. Data export to Hyperion.
 BHI tool will not change technically. BHI will continue to be used to do the
transformation between BPC Consolidation accounts and flows with
Hyperion accounts and sub-accounts. The report already created in BPC to
send data into Hyperion will be used. Any alternative, such as to generate
a flat file from SAP BPC and upload into Hyperion is out of scope. More
detail about this integration can be found in chapter 9.3 - SAP BPC
Interface with Hyperion.
 Control Monitor
SAP BPC NW 10 provides standard functionality called “Control Monitor” to
validate data. The Control monitor will not be used as it requires the user to
trigger the validation calculations. Instead when data is saved by the user
the validation calculations will be automatically triggered eliminating the
requirement for this part of the control monitor functionality. A single report
has been written to allow users to validate their data.
 Functional Area in consolidation model

Functional area is out of scope in Consolidation model because having the
same group of accounts for the cost of sales and the admin expenses is not
a common practice, and not recommended in BPC CoA. The detailed
analysis of pros and cons of using functional area in Consolidation model
can be found in document Design Strategy for BPC, COA, Flows &
dimensions_FINALV3.pptx
 Work status
Work status will be used as it is. No changes on configuration will be done in
the current project. Some detailed information how it is currently used is
described in chapter 12.2. Any other processes not explicitly defined herein
are not in scope.
 System administration activities such as backups, availability, capacity etc

will not be changed as a result of this project.

page 13 of 79
4. Document Assumptions
In order to run the Cash Flow project on SAP BPC NW 10, the previous solution
implemented in SAP BPC NW 7.5 has been upgraded into SAP BPC NW 10 release.
Cash Flow will be designed at profit centre level with approximately 1,300 entities.
This is different to Hyperion Enterprise application which only has about 325 entities.
For this reason, there is no requirement to change the Entity dimension.
Serco will provide the historical currency values. The original ‘Consolidation’
model in SAP BPC NW 7.5 and upgraded to SAP BPC NW 10 will not be used in
production as a configured model. It will only be used to send data to Hyperion.
There will be two data processes used 1) uploading data into BPC model and 2)
sending data to the Hyperion application.
The original plan was to implement the new Chart of Accounts and Flow members
in SAP BPC NW 7.5 productive environment prior to Cash Flow project going live on
SAP BPC NW 10. However, due to a number of constraints, the plans have
changed. It is now planned to implement the Chart of Accounts and Flows in BPC
NW 10 by the end of August 2014. The objective is to validate data prior to Go
Live. Due to the requirement to change configuration in ECC to activate Group
Accounts and design a financial statement version for loading CoA into BPC,
integration will be implemented in the future.
The Cash Flow project will run on the Consolidation model in the SERCO_FPRS
environment. Other models are not in scope. If there are any changes in the
Consolidation model for shared objects such as dimensions, then the impact on
other models will need to be assessed.

page 14 of 79
5. Key Design Decisions
The Cash Flow project is not a solution created from the scratch, but builds on the
previous implementation. It will exploit the current existing solution, which is already
integrated with source systems (Actual model) and target systems (Hyperion).
The solution will consist of accounts and flows that currently exist as accounts and
sub-accounts in Hyperion Enterprise.
This project is focused on:
 A new Chart of Accounts aligned with ECC
 New implementation of flows
 37 new reports and input forms
 New calculations
 Validation report with validation formulae
 Currency translation and carry forward rules.
All others components remains as they are now. Examples of that are other
dimensions (Entity, Time, Category…), data integration and security. The design of
BPC Cash Flow is solution is based on the Hyperion process e.g. schedules,
accounts and flows. The plan is to decommission Hyperion as primary
consolidation system in March 2015 which will be post go-live (end of September)
of the Cash Flow, Interco Matching and Consolidation (Equity Accounting &
Contracts) Implementation.
Summary of the key design decisions
 Use a Write Back BADI to perform calculations automatically during the
update of the cube to improve performance of schedules.
 Schedules (reports and Input forms) will be created in full static mode (hard
coded) to have the best performance possible when opening or refreshing
the data. Using automatic expansion can be time consuming and does not
fit well with the specific combination of accounts and flows required in the
consolidation schedules. With static reports, Excel formatting can be used
directly in the report cells and this has better performance than automatic
formatting.
The benefit will be improved performance, although this does mean the
manual maintenance of the reports and input schedules. Adding a new
account will involve manually inserting a new row or new column in the
report.
 Drill Down schedules will be dynamic on the columns (entity and currency)
and not the rows (accounts and flows).
 Revenues will be shown as credit (negative values) and expenditures as
debit (positive value). Revenue accounts are also stored as negative
values in ECC.

page 15 of 79
In order to align with ECC, the following settings for ACCTYPE will be
implemented in BPC.
ACCTYPE Accounts Database Display in Excel
EXP Revenues (-) (-)
EXP Expenditures + +
AST Assets + +
AST Liabilities (-) (-)

page 16 of 79
6. Dependencies
Ref Dependencies Detail
Cash Flow project is running in parallel with Upgrade project (technical

Upgrade upgrade Project from BW AS ABAP 7.01 to 7.31 and BPC 7.5). The
1 project to BPC upgrade project needs to complete the upgrade/migration before
10 starting the build activities for Cash Flow in Sandbox and Development
environment.
Cash Flow project will upload data from Actual model and therefore
any changes needed for Consolidation will also impact Actual model.
2 Source systems
This will be the process until Serco are able to go live with a new BADI
implementation in BW.
New project to be delivered by Serco to change the location of

calculations for JV, Profit Shares, Foreign Exchange from BPC Actuals to
BW. This is planned to be delivered in August and will have the
following impacts:
New change
3 Design needs to be impacted assessed by SAP for impact on Cash Flow
to BADI project.
The changes (calculations and flow of data between BW & BPC
Consolidation, previously BPC actual and BPC Consolidation) will need
to be regression tested by Serco before Go-Live.
Shared Some dimensions are shared between Actual and Consolidation model.
4 Changes on these dimensions impact both models.
dimensions
Security must be reviewed. It is out of scope because it is the

5 Security
responsibility of Serco to develop the new Security for Cash Flow.
Business Serco will need to review and update all impacted processes eg. Flow
6 and CoA changes, changes to schedules, reports and calculations.
Processes
Serco business is dependent on the implementation of the

Consolidation
7 Consolidation project (Interco Matching, Equity Accounting, Contracts)
Project going live in parallel with Cash Flow project.
Serco business is dependent on the implementation of additional

changes made in Hyperion which accommodates new accounting
Hyperion BAU changes before UAT and again before Go Live.
8
Changes
These changes are subject to review by SAP and if required will follow
the standard CR process.

page 17 of 79
7. To be High Level Process Overview
7.1. Logging into BPC
Access to BPC will be via Citrix, when the user logs into BPC EPM Add-in they will be
able to select Consolidation Model.
7.2. Monthly process overview
1. Update Master Data in SAP BPC application. All members are updated
manually, e.g. Accounts, Flows, entities.
2. Transactional data is uploaded from ECC -> BW -> Actual model. Some
calculations e.g. profit share and JV are made in Actual model.
3. Transactional data is uploaded into SAP BPC Consolidation model using a
data manager package that calls a BADI named
“COPY_TO_CONSOLIDATION” in Actual model. When data is uploaded
from Actual model, the currency translation package is also run.
4. End users enter data using input forms.
5. The calculations will be run automatically when the data is uploaded into
Consolidation model and when data is saved by the user using input forms.
6. Currency translation will be run on demand using Consolidation monitor.
7. Run Validation report.
8. Run reports.
9. Send data into Hyperion application using an EPM Add In reports. This is to
be used for a specific limited period after Go Live, for a parallel run.
10. Lock data for all entities, category data and the period.
Security will apply to the overall process.

page 18 of 79

page 19 of 79
8. SAP BPC Data Model

8.1. SAP BPC Environment
The BPC environment is the top level organisational object in SAP BPC application.
An environment contains one or several models and stores all data from each
model. Master data is created using dimension objects and they are created at
environment level. One model can share one or more dimensions with other
models within the environment.
The project will be developed in the current SERCO_FPRS environment.
This project will run in SAP BPC NW 10. This environment was created in release 7.5
and will be migrated to SAP BPC NW 10.
8.2. SAP BPC Models
There are two different types of models.
Reporting models typically store data and process at particular business process.
Examples of these models are planning model, consolidation model. Reporting
type models can be defined as ‘Reporting - Financial’ or ‘Reporting-
Consolidation’ or ‘Reporting-Standard’ type.
Drivers and Rate models store data to support reporting models. These models
can be defined as ‘Drivers and Rates – Exchange Rates’ or as ‘Drivers and Rates –
Ownership’ or ‘Drivers and Rates – Generic’.
On SAP BPC application only base level members are stored in the database.
Base level members are values entered in local currency. As translated values are
also stored in the system in both Group currency (GBP) and Regional currencies
these values are also base level members.
Parent level data is calculated on the fly when the reports are refreshed.
SERCO_FPRS environment has nine configured models.
There are four Reporting models:
 Actual In use.
 Budget Not in use. At the moment is redundant with Actual model.
All planned data is held in actual model.
 Cash Flow Not in use and will not be used for Cash Flow project
 Consolidation To be used for Cash Flow project
There are five Drivers and Rate models:
 B_Ownership1 Assigned to ‘Actual’ model

Stores consolidation information (methods and consolidation rates) for joint
ventures.
 Ownership Assigned to ‘Consolidation’ model
 Profit Share Not in use. This was created to be used by Consolidation
model.

page 20 of 79
 ProfitShare_New Used by Actual model.

Stores consolidation information (methods and consolidation rates) for profit
shares.
 Rates In use by ‘Actual’ and ‘Consolidation’ model for rates
Only two reporting models are being used; Actual model for management
reporting and Consolidation model to send data to Hyperion application.
The CASHFLOW project will use the existing ‘Consolidation’ model. All changes
carried out in the SERCO_FPRS environment will be documented. Although the
‘Actual’ model is not part of the Cash flow project it will still be referenced in this
document. This is because some of the dimensions are shared across the
environment including ‘Actual’ and ‘Consolidation’ model.
The Consolidation model is created as ‘Reporting-Consolidation’ type and it utilises

two other models, the Rates model to run exchange rate calculations and the
Ownership model for scope definitions. The Cash Flow project will use these three
existing models.
 Consolidation
 Rate
 Ownership
Consolidation model
 The Consolidation model will be used to store Cash Flow transactional data.
Defined as ‘Reporting – Consolidation’ type.
 Data Entry mode is already defined as Year to date - YTD
 It is using ‘Rates’ model for exchange rate functionality.
 It has an assigned Ownership model
 Dimensions currently in use and to be used in this model will be detailed in

next chapter.
 No changes will be done on Consolidation model definition. Cash Flow

project will use it as it is defined.
 Transactional data is uploaded from Actual model into Consolidation

model. Some calculations such as profit share and JV are made before
data is uploaded into Consolidation model.
 Consolidation model will also be used in the future project for Consolidation
purposes.

page 21 of 79
Rate model
 This model is configured as ‘Drivers and Rates – Exchange Rates’ type and
the main objective is to store exchange rates for currency conversion
process in reporting models (financial or consolidation reporting models).
 This model is being used by Consolidation model and also for other models
configured in SERCO_FPRS environment such as ‘Actual’ and ‘Budget’
model.
 No changes will to be done on this model.
 Dimensions used in this model will be detailed in next chapter
Ownership model
 This model supports the consolidation process for ‘Reporting-Consolidation’

type. It stores group structure, consolidation methods and consolidation
rates.
 Ownership Model is assigned to ‘Consolidation’.
 No structural change will be done on this model in the scope of Cash Flow
project. There will be changes to data.
 Dimensions in use in this model will be detailed in next chapter, just for
information as they will not be changed.
8.3. SAP BPC Dimensions
A dimension is a collection of related members which represents one aspect of

one business. It can be accounts, products, currency, etc.
BPC has ten different types of dimensions:
Type A – Account
Type C – Category
Type D – Audit ID
Type E – Entity
Type G – Group
Type I – Intercompany
Type R – Currency

page 22 of 79
Type S - Subtables
Type T – Time
Type U – User defined
The following table details all dimensions that are used by Consolidation, Rate and
Ownership models. The fifth column identifies dimensions used in Consolidation
model, column number six identifies dimensions used in Rate model and the last
column identifies dimensions used in Ownership model.
Dimension Reference Models

Dimension Description
Type Dimension
Consolidation Rates Ownership
Account A - Account Account RateID x
RateID A – Account Rate ID x
Ownership
OwnAccount A – Account x
accounts
AuditID D- Audit Trace Audit ID x
Categories for
Category C – Category Time x x x
Planning
Consolidation
ConsoScope G- Groups x x
perimeters
Currency R – Currency Currency x
InputCurrency R – Currency Input Currencies x
Entity E - Entity Reporting Entity InputCurrency x x x
Rate Entity E - Entity Rate Entity Currency x
Positions and
Flow S- Subtables movements x
analysis
Intercompany I- Intercompany Intercompany Entity x x x
Time T- Time Time periods x x x
New dimension for Cash Flow project
Analysis U- User Defined Memo x
We will not detail all dimensions that exits in Actual model, but the following list are
dimensions that are shared by Consolidation and Actual model:
 Category
 ConsoScope
 Flow
 Currency
 Time

page 23 of 79
The ‘Actual’ model has a different Chart of Account (dimension A_Account),

different Audit ID (dimension B_Audit_ID), different entities (dimension B_Entity) and
different Intercompany entities (dimension B_INTERCO).
In the following table identifies secure dimensions by model considering

Consolidation, Rate and Ownership models:
A secured dimension is a dimension used for restricting access to a user to that

specific dimension. For example “Entity” dimension is a secure dimension which
means that users can be set to have the following access:
 read data only

 write and read data,
 deny access
Secure Dimensions Table (AS IS configuration):
Dimension Description Description Consolidation Rate Ownership

ID
Account A - Account Account
RateID A - Account Rate ID
Ownership
OwnAccount A - Account
accounts
Trace AUDIT
X
AuditID D- Audit ID
Categories for
X
Category C - Category Planning
Consolidation
X
ConsoScope G- Groups perimeters
Currency R - Currency Currency
Input
InputCurrency R - Currency Currencies
Reporting
X x
Entity E - Entity Entity
Rate Entity E - Entity Rate Entity x
Positions and
movements
Flow S- Subtables analysis
Intercompany I- Intercompany Intercompany
Analysis U-User Defined Memo
Changes on Security or Data Access profiles are defined by Serco and are
detailed in the attached Appendix.
Considering Cash Flow project scope only Account dimension and Flow Dimension
will be changed. Other dimensions will be kept as they are.

page 24 of 79
8.3.1. Account Dimension

This Dimension will contain the Chart of Accounts (CoA) for consolidation model.
Implement a new Chart of Accounts, which is aligned to ECC and manually

maintained in the short term. It will use the same ID (codification) of ECC CoA. This
new CoA will replace the StarterKit CoA currently used in the Consolidation model.
Due to the requirement to change configuration in ECC to activate Group

integration will be implemented in the future.
The detail codification is as follow:
 All base members use the Serco ECC 6 digits codification

 For total accounts, the suffix ‘T’ allows the user to distinguish between total
accounts and base-level accounts. For example, account 100000T –
Goodwill is the parent of account 100000M – Goodwill and 101000M - Commented [EF1]: We later state we're now using an
Goodwill, Impair. attribute rather than suffix for multiple accounts
 Income statement accounts are split between Costs of Sales and
Administration accounts. Accounts with the suffix “C” are the Cost of sales
accounts. Accounts with the suffix “A” are the Admin accounts. For
example account 780268_C- COS - Insurance has Cost of sales insurance
costs while account 780268_A - Admin Expenses – Insurance has the
insurance costs for administration expenses.
 Technical accounts have last two digits ‘_T’. For example account
520000_T- System Exchange or 547000_T- Equity of joint ventures, excl FX.
These accounts are BPC technical account for BPC calculation purposes.
They don’t have any ECC account correspondence.
 All accounts beginning with ‘9’ are specific BPC accounts like Cash Flow,
Free Cash Flow…not ECC source accounts. To prevent duplication the SAP
BPC system is not using accounts which the first three digits are ‘995’. This
codification is used by ECC for data take on purposes but they will not be
used in SAP BPC. Serco will review the option to include notional accounts
in ECC at a later date which will form part of automation project previously
mentioned.
Only Consolidation model uses this dimension.
Regarding account matching between ECC and BPC we can have the followings
situation:
 One ECC to one account BPC account;

 Multiple ECC accounts to one BPC account
SAP BPC users need to know when one BPC account has multiple source accounts
in ECC. To achieve this requirement a new property (called MUTLIPLE_ACC) is being
added in account dimension, that will be filled with an ‘M’ for BPC accounts
sourced by several ECC accounts. This property will be empty if the source is one
ECC account to one BPC account. The MULTIPLE_ACC property will be displayed
alongside the account id in all reports and input schedules.
This information is not identified in BPC account codification because this can
change quite often.

page 25 of 79
Example 1:
January 2014: This 720000 account should have one ‘M’ in BPC MULTIPLE_ACC
property because it maps to multiple accounts in ECC.
February 2014: The 720000 account in BPC is no longer a multiple account. The
account property value ‘M’ in MUTLPLE_ACC will be removed. The additional
required account (720010) is created in BPC with no value in MULTPLE_ACC
property.
As data is loaded YTD, the movements resulting in the above scenario can be
visualised in the table below.
Account ID YTD January YTD February MTH February
720000 15 30 15
720010 N/A 20 20
Total 50 35
Example 2:
January 2014: We have two accounts, 720000 & 720010 mapped one to one
between SAP ECC and BPC.
February 2014: Accounts 720000 & 720010 will now be mapped to the multiple
account 720000. Account 720000 will have its account property MULTIPLE_ACC
value updated to be ‘M’.
As data is loaded YTD, the movements resulting in the above scenario can be
visualised in the table below.
Account ID YTD January YTD February MTH February
720000 15 50 35
720010 10 N/A (10)
Total 25 50 25
On doing these changes the business will need to ensure that any changes
required to schedules, calculations, reports etc are updated accordingly.
8.3.2. Structure of the Chart of Accounts

The chart of accounts is organised into three parallel hierarchies. Accounts are
always included in a parent member account by populating the PARENTH1 field in
the ACCOUNT dimension.
The detailed BPC Consolidation Chart of Accounts will be subject to further review
and sign off by the business.

page 26 of 79
An example of the three hierarchies being utilised is in the schedule, Other

Intangible Assets.
Hierarchy 1 has the totals for Intangible Assets - Under construction, another total for
Intangible Assets - In use and a total Intangible Assets – Leased. This hierarchy has a
similar codification as base level accounts with the ‘T’ meaning total in the end.
Examples of this figure are 100800T – Total AUC, 100820T – Total In Use and 100840T –
Total LEASED.
Hierarchy 2 has the total for Software, total for licences and franchises, total of
development and expenditure, the total of customer relationships and the total
pension related intangible. This hierarchy is using a different codification. As these
accounts are calculated accounts, they begin with ‘9’.
Hierarchy 3 is for the net book value calculation. For example net book value for
software in use will be account 950210. This account will be parent for account 1
100200M – Software in use (costs) and also parent of account 101400M - Software in
use (amortisation).
Account dimension properties:
Property Name Description
ID Unique BPC Identifier
Description Account member description
Describes the type of an Account; Income, Expense, Asset,

Liability/Equity. Determines signage. This is a required account property.
Account type
‘Assets’ will be used for all Balance Sheet accounts;
‘Expenses’ will be used for all P&L accounts

page 27 of 79
Rate type Determines currency conversion behaviour. This is a required property
Allows display values in thousands in reporting. This is a required

Scaling
property
To group accounts for reporting purposes. It does not have any BPC
Schedule
specific purpose
TYPELIM Used in Business rules. Not used for Cash Flow.
Used in script logic to distinguish Balance Sheet and Income statements

GROUP
accounts.
This property will indicate when one BPC account has multiple sourcing
accounts in ECC. The values will be:
MULTIPLE_ACC
 Empty: One ECC to one account BPC account
 ‘M’: Multiple ECC accounts to one BPC account

PARENTH1
Hierarchy 1
PARENTH2
Hierarchy 2
PARENTH3 Hierarchy 3
To achieve a parallel run with Hyperion during a limited time period we will have 83
additional properties in the account dimension to map Cash Flow COA (Account
dimension) with Hyperion Accounts and sub accounts.
Not all these properties are detailed in this document, but some examples are
show in the following table.
Flag as ‘X’ or empty. This means account is relevant to Hyperion

HYPRELEVANT
interface
Identifies which Hyperion Account and Sub account is mapping with

HYPMAP_F01
the specific account and flow F01

HYPMAP_F05
….

page 28 of 79

HYPMAP_F99
Example of property mapping with Hyperion:
Data filled in 112500M account and in flow F01, will be uploaded into Hyperion in
account/sub account PPE30.21
Data filled in 112500M account and in flow F20, will be uploaded into Hyperion in
account/sub account PPE20.21
A property by flow is created. Mapping is done with combination of account

members and flow members into Hyperion Account and Sub account.
Some properties will be deleted, as they will not be used:
German language. Not used. SAP BPC NW language translation

LANGUAGE_GE should be done according to logon language. It will not be used in
CF project
French language. Not used. SAP BPC NW language translation

LANGUAGE_FR should be done according to logon language. It will not be used CF
project
Could be used as selection in business rules. It will not be used in

DIMLIST_DEST
CF project
ELIMACC It is used in US elimination process. It will not be used in CF project
Starter Kit property. Use in Starter Kit input forms for formatting
purposes (Section 11 – Schedules) and also master data validation
(Section 10.3.2 – Master data validation).
FLOWAN This property is deleted from account dimension due to performance
reasons.
The way formatting and locks will be done in schedules is detailed in
Section 11 – Schedules.
Starter Kit property for Cash Flow Starter Kit calculation. New
CFS
calculations are out of scope of this project.
UPROFILE Starter Kit property in Starter Kit input forms
ISINTERCO Starter Kit property used in Starter Kit input forms

page 29 of 79
STYLE For formatting proposes in previous release (BPC 7.5)
Not used in BPC 10 NW. Formulas are configured in a different

place, not in dimension property. To use formulas, configure, ‘Allow
FORMULA
formula’ in dimension. Formulas will not be activated in Account
dimension for Cash Flow project.
Could be used as selection in business rules. They will not be used

DIMLIST_ACTR
by Cash Flow project.
FLOWANSECURE They will not be used by Cash Flow project.
FLOW15 They will not be used by Cash Flow project.
ZDEL They will not be used by Cash Flow project.
NEWCASHRELEVANT They will not be used by Cash Flow project.
NEW_CASHFLOW They will not be used by Cash Flow project.
Properties can be added if needed in future processes.
Account dimension is used by Consolidation model and there will be no impact in

other models.
8.3.3. Flow Dimension

Flow dimension is S-Subtables type and is used to detail account movements
detail, to track opening versus closing balance.
One of the main objectives for Cash Flow project is to re-define Flow dimension.
Consolidation and Actual models share the flow dimension. Changes on this
dimension will affect both models.
The number of financial flows has been greatly reduced from 76 to 40. To do so we
now use the same flows across the schedules but changed the description of the
flows according to the schedule.
The new flow dimension includes a group of 40 financial flows for the Balance
sheet accounts, plus additional non-financial flows for several groups of sub-
accounts to give detailed information in some schedules such as Acquisitions,
Disposals, Transfers, Sector & Geog, Leasehold commitments and Aged Debtors
Regarding flows members ID’s, we will have the following situation:
 ID’s existent that will not be used anymore

 New ID’s that will be created in BPC system

page 30 of 79
 ID’s that will be kept with same meaning

 ID’s that will change the meaning
Update members in BPC Sandbox:
1. Serco, with assistance from SAP, will delete flows that are no longer used
and that have no data. These will not be used and will be replaced by new
flows.
2. New ID’s that don’t exist will be created
3. ID’s that already exists and will have a new meaning will be updated in
Sandbox with the new meaning.
This is a shared dimension between Actual Model and Consolidations Model. Until
January 2015 we will keep the new flows in a separate group with the parent
member END, and the old flows still used in the actual model in another group of
flows named as old_flows.
The members of this dimension, representing the real flows, will have the following
codification:
 F00 until F99: Flows for Balance Sheet account. All these flows excluding
Flow F99 will have the same parent ‘END’.
ID Description Parent
F00 Opening position END
F50 Reclassification END
F22 Transfer from END
F23 Addition from other subsidiary END
F24 Reclassifications from / (to) OIA END
F75 Transfer (to) END
F76 Disposal (to) other subsidiary END
F77 Reclassifications from / (to) PPE END
F01 Arising on acquisition END
F98 Eliminated on disposal END
F20 Additions END
F26 Additions - def inc / oth acc END
F27 Additions - non-recourse loans END
F25 Increase in depreciation END
F30 Disposals END
F35 Decrease in depreciation END
F40 Interest capitalised END

page 31 of 79
F45 Other movements END
F55 Revaluation END
F60 Impairment END
F65 Exceptional write down of assets END
F80 FX – System END
F81 FX - Unrealised non-current (income statement) END
F82 FX - Unrealised current (income statement) END
F83 FX - Realised non-current (income statement) END
F84 FX - Realised current (income statement) END
F85 FX - Unrealised (hedging reserve) END
F86 FX - Realised (hedging reserve) END
F87 FX - Unrealised (input reserve) END
F88 FX - Realised (input reserve) END
F89 FX – Input END
F10 Net (profit) / loss for the period END
F11 Transfer to income END
F05 Dividends paid by JV's END
F06 Dividends paid by OC's END
F07 Dividends paid by MI's END
F08 Dividends paid by Group plc END
END Period End Closing
F99 Closing position
F15 Movement END
 F99 is a standalone flow and is not a child because F99 is the closing
balance which is validated against the aggregated value on END Flow;
PL99: Flows for Income Statement accounts, Cash flow and Free cash flow
accounts, Headcount, Capital Commitments and Long Term Contracts
 Flows which codification begins with ‘MAT…’ or ‘A’ or ‘B’ or ‘W’ are for
detailed maturity. For example, schedules ‘Loans (18)’, and ‘Finance Lease
obligations (25)’ and ‘Leasehold commitments (34)’ use these flows.
 Flows that have the first 3 digits as ‘SEC’, ‘PUB’ or ‘GEO are used by
schedule ‘Sector & Geog - Segmental Information (32)’
 Flows that have the first 3 digits as ‘ACQ’ are used in Acquisitions (29)
schedule.
 Flows that have the first 3 digits as ‘DIS’ are used in Disposals (30) schedule.
 Flows that have the first 3 digits as ‘TRA’ are used in Transfers (31) schedule.

page 32 of 79
 All movements’ flows have a PARENTH2 named MVT in order to get

automatically these flows in the calculations.
 All movements’ flows have a PARENTH2 named MVT in order to get
automatically these flows in the calculations.
The Flow dimension will have two hierarchies. The second hierarchy is used for
Acquisitions (schedule 29) and Transfers (schedule 31). The second hierarchy is
needed because this information is required for the Hyperion interface.
Consolidation and Actual models share flow dimension. Changes on this

dimension will affect both models.
Flow dimension properties:
Description Flow member description
Opening and closing types are used in Balance

Flow type carry forward
DIMLISTFLOWS Kept but it will be not used for Cash Flow.
SUBTABLES_ORIG Used in currency conversion rules
CALC_F15 Used in flow F15 calculation
*HYPRELEVANT Hyperion account and sub account map
*HYPRELEVANT will be kept during Hyperion parallel run. Afterwards this property
will be removed.
Some flow properties will be deleted, as they will not be used. The table below
describes the reason for not using the property.
German language. Not used. SAP BPC NW language translation should be

LANGUAGE_GE
done according to logon language

page 33 of 79
French language. Not used. SAP BPC NW language translation should be

LANGUAGE_FR
done according to logon language
FLOW_DOC Starter Kit property used in starter kit input forms.
This property is always empty in Flow dimension. When created it have no

IS_INPUT
values. We will not use it in Cash Flow project.
Balanced Starter Kit property for Dashboard control report
Used in currency conversion rules. In the new configuration it will not be

SUBTABLES_ORIG2
used in Cash Flow.
UPROFILE Starter Kit property used in Starter Kit input forms.
Analysis Dimension
This is a new dimension in the Cash Flow project to support some detailed
information not available on the account or flow dimension, such as the
investments for subsidiaries, associates or JVs. This dimension has been created as
user defined dimension and its purpose is to detail some schedules information.
This is similar to sub accounts in Hyperion.
Schedules that are using this dimension are:

 Goodwill (11) Detailed by transaction
 Subsidiaries investments (14) Detailed by subsidiary
 Joint Ventures Investments (15) Detailed by Joint Ventures
 Associates investments (16) Detailed by Associates
 Acquisitions (29) Detailed by acquisition
 Disposals (30) Detailed by disposal
 Transfers from (to) (31) Detailed by transfer
 Long Term Contracts (37) Detailed by contract
Below is an Example of one schedule using analysis dimension.

page 34 of 79
The purpose of analysis dimension in this report is to get the detail of subsidiaries
investments by subsidiary.
Analysis dimension properties:
Description Analysis description
PARENTH1 Analysis hierarchy 1
PARENTH2 Analysis hierarchy 2
A technical member named OFFSET will be part of TOT_GWD to offset the values loaded
on ‘Group Other adjs” member.
All goodwill transactions have a 2nd parent in Hierarchy 2. This technical parent named
“GOODWILL_T” will be used by the Write back BADI to use all goodwill transaction as
source of the OFFSET calculation.
ConsoScope
This dimension is used to define the groups of the consolidation perimeters (groups
of entities) which are displayed in the Consolidation Monitor.
The following ConsoScopes currently exist:
ConsoScope

page 35 of 79
G_NONE - Group (all data)

Description
P_PC1000SE - Serco Only (excluding JVs) Management Roll-Up
P_PC89000 - Joint Ventures
P_SercoJV - Serco Management Entity Structure
P_Share - Profit Share Percentages
TOCORRECTDHVIEW - Correct the Dynamic Hierarchy Data View
ConsoScope dimension will be updated to support the Consolidation perimeter

Groups used in the Consolidation Monitor.
To have the same Entity hierarchies existing in the Entity dimension in the
Consolidation Monitor two pre-requisites must be completed:
 Create all groups and sub groups (Entity parents) in the ConsoScope
dimension.
 Create the group and sub group hierarchy using the property
“PARENT_GROUP” in the ConsoScope dimension.
 Organise the child/parent relationship of each consolidation perimeter
(entity organisation) between the base entities and the groups using the
Ownership Manager functionality in Consolidation Central (BPC Web
interface).
 Five structures (Management, Management Excl JV’s, JV’s, Statutory and
Equity Accounting).
 Note: Include a simple example of how a profit centre rolls up using
hierarchy in ConsoScope.
 ConsoScope to be updated from Entity Dimension via flat file.
 For example, for Management structure 300 hierarchy nodes need to be
created.
This will be maintained manually for each period and each consolidation
perimeter. Copy functionality will allow copying of a consolidation perimeter
from one period to another.
8.3.4. Other dimensions

For the remaining dimensions we will not detail all properties as we will not change
them on this Cash Flow project. A brief summary of other dimensions is described
below.
RateID
This is the account of Rate model. This dimension contains the different types of rates
that assigned to the account in Account dimension, property Rate type

page 36 of 79
OwnAccount
This is the account of Ownership model. It consists on the ownership elimination

methods, percentages as well percent control and percent ownership.
B_Ownershipb1 and Ownership models share this dimension.
AuditID
An AuditID member identifies the origin of values such as input, eliminations.

All input data will be filled with ID ‘Input’
Historical values stored on the Group and Regional Reporting currencies use
“HIST_VAL” member.
Category
Category dimension contains members such as Actual etc.
Cash Flow project just uses Actual member.
Currency
This dimension is the report currency; it contains the currencies in which Serco can
run Cash Flow reports. The flowing currencies exist in this dimension:
ID Description Reporting Currency Level
GBP British Pound Group
USD US dollar Regional
AUD Australian Dollar Regional
HKD Hong Kong Dollar Regional
AED Arab Emirates Dirham Regional
EURO Euro Regional
INR Indian Rupees Regional
LC Local Currency Local
InputCurrency
This currency type dimension is used by Rate model and it has all Serco currencies.
In rate cube input currencies have rates to be used on exchange rate conversion
in Consolidation model.

page 37 of 79
83 different currencies are configured in the system.
Entity
This dimension contains the business entities that are used to drive business
process.
Entities on consolidation model correspond to the profit centre.
The entity hierarchies have to be organised similar to the Entity organisations in
Hyperion Enterprise.
 H1 : Management (By management responsibility)
 H2 : Management XJV (Same as Management but without the joint
ventures entities) – does not currently exist
 H3 : JV (Only the joint ventures) – does not currently exist
 H4 : Statutory (By Legal Entity)
 H5 : EA (Equity Accounting) for Joint Ventures (To be scoped as an
additional CR)
The Management excluding XJV hierarchy will be used in the Free cash flow
report. The total free cash flow value excludes the values coming from the joint
ventures.
Rate Entity
This dimension is the entities dimension of Rates model. Generally the GLOBAL
member against which the default rates by input currency must be input. Specific
rates per company can be used.
Intercompany
This dimension contains the intercompany ID’s for entities (trading partners)
Cash Flow project will always use Intercompany member NONE.
Time
This dimension contains the time periods for which we store data.

page 38 of 79
9. SAP BPC Data Integration

9.1. SAP BPC Master Data
Master data are the members of dimensions. Some examples are members of
account dimension, profit centres or other members of entity dimension.
Update Master Data manually in SAP BPC application: Accounts, Flows, and
entities.
Due to the requirement to change configuration in ECC to activate Group
integration will be implemented in the future and is not represented in the above
process. Serco will decide where to setup the BPC account structure in ECC
application to enable members and main hierarchy of Account dimension to be
automatically transferred into the SAP BPC Consolidation model. The automation
of this process will be done in a future project.
No changes will be done on master data maintenance in Cash Flow project.
Any manually or automatically changes to be done in Entity master data at the

time of go live, such as updating Management hierarchy or statutory hierarchy, will
be done by Serco team
9.1.1. SAP BPC Transactional data

The following diagram shows the global AS IS data flow process implemented at
Serco.
AS IS

page 39 of 79
TO BE – No change (without BW BADI)
We will use the current process for loading data from ACTUAL to CONSOLIDATION
which is done both automatically on an hourly basis and manually on demand.
The data flow process will be maintained as it is, apart from step 4 (BHI interface)
which will be removed. Before it can be deleted, a parallel run will be done with
SAP BPC Cash Flow project and Hyperion Enterprise application.
For the first Cash Flow run in SAP BPC production step 4 is still required.
The scope of this project is adopting the current model with new Chart of
Accounts and Flows.
It is a SAP recommendation that the BPC consolidation model should be sourced
directly by BW and not from the Actual model. The only reason there is a feed
from the ACTUAL model is that the calculations executed in the Actuals model are
required in the Consolidation model. When all these calculations are in BW
(dependant on Serco delivering the project to move BADI’s from BPC Actual to
BW), then the data can be loaded directly from BW to Consolidation model.

page 40 of 79
TO BE IN THE FUTURE (Post build and UAT & BADI move)
This diagram illustrates the position post BADI move.
After a successful period of parallel running of BPC Consolidation and Hyperion

Enterprise (September to December 2014), Hyperion Enterprise will no longer be
loaded from BPC Consolidation by BHI.
Flows
Dimension Flow in Consolidation model is shared with Actual model. The required
mapping changes between ECC movements types and flows is maintained in BW
using table “ZBPC_Flow_Map“. All Balance Sheet accounts will only be loaded
using flow ‘F99’ except ‘Other intangible assets’, ‘Property Plant & Equipment’ &
‘Goodwill’ where movements will be loaded from ECC ‘Fixed Asset’, any changes
to these three schedules will need to be carried out in source system. This will
ensure any data entered correctly by the user will not be over written.
Account
Actual model uses A_Account dimension, but the Consolidation model uses
Account dimension. A_Account members are mapped to Account members.
This mapping is done in dimension A_Account with property
CASHFLOW_ACCOUNT.
The data uploads into SAP BPC Consolidation model use a data manager
package that calls a BADI called COPY_TO_CONSOLIDATION.
System is scheduled to automatically load data from Actuals to consolidation on
an hourly basis as it is currently in production environment.

page 41 of 79
Super User can push data manually on demand.

Each time data is loaded from actuals to consolidation a BADI will execute all
calculations including validation formulas.
Analysis
Mapping between Actual and Consolidation

Analysis dimension is mandatory and will be defaulted to “Analysis none”.
That new dimension in BPC Consolidation needs to be added in the BADI interface
between ACTUAL and CONSOLIDATION named COPY_TO_CONSOLIDATION.
Actual data being loaded to consolidation will need to be mapped to the proper
Analysis members in the Consolidation model. This mapping will be derived from a
new property being added to Actuals account dimension.
Schedule
The Goodwill information loaded from ACTUAL to CONSOLIDATION will be stored
on the “Group Other adjs” member, and then after the Trial Balance check, will be
split between the different detailed transactions.
Due to the automatic load on an hourly basis into the “Group Other adjs”
member, an additional technical member must offset all the transactions’ values
in order to have a correct aggregated value for the Total Goodwill.
OFFSET = -([trans1]+[trans2]+…[transN])
“Group Other adjs” member can’t be used by users as this member stores the
automatic load from source system.
”OFFSET” member has the sum of all values inputted by users on Trans1,
Trans2,…TransN members.
Goodwill hierarchy
Total
Goodwill
Group
Other Adjs
OFFSET
Trans1
Trans2
TransN

page 42 of 79
9.1.2. SAP BPC Interface with Hyperion

Step 4 of data flow diagram describes how data is transferred from Consolidation
model into Hyperion application. This process runs on demand and is called the
BHI interface (BPC Hyperion Interface).
This process will be kept for the first run in production to achieve a parallel run with
SAP BPC Cash Flow project and Hyperion Enterprise application.
Users will enter data in the SAP BPC Cash Flow model and this data is transferred
into Hyperion system in YTD format. However, this is not true for all data detail. To
avoid changing BHI interface (to introduce the Analysis dimension in BHI
configuration) some schedules will have data restrictions.
No analysis detail will be sent via BHI. These schedules have analysis dimension but
data will be populated only to the default analysis. Goodwill (11): No detail by
entity / total value sent to GOTH
 Subsidiaries investments (14):No detail by subsidiary / total value sent to
SU01 (To be created in Hyperion)
 Joint Ventures Investments (15):No detail by Joint Ventures / total value sent
to GOTH
 Associates investments (16):No detail by Associates / total value sent to
ASS0
We will not be sending data for the following:
 Acquisitions (29): Disposals (30):
 Transfers from (to) (31) and
 Long Term Contracts (37):
The first step of this interface is to run the report ‘SUBMIT.XLS in the SAP BPC
Consolidation model. Running this report will give the user access to BHI Interface
as currently used. SAP will not be changing this report or the process.
When opening the report, users select the following items.
Category This must always be ACTUAL
Entity select from H_Entity list
Time Time period
Currency is locked so users can only upload in local currency (LC).

page 43 of 79
Each base level Hyperion entity is loaded individually.

After the report has opened, a macro button ‘Submit to enterprise’ and all
displayed data will be loaded.
This report reads all accounts that have property ‘HYPRELEVANT’ = Y and all flows
that have property ‘HYPRELEVANT’ = Y. Apart from these two properties, 83
additional properties on account dimension are used to map Cash Flow COA
(Account dimension) with Hyperion accounts and sub accounts.
The Cash Flow project is designed at profit centre level, with approximately 1,300
entities, which is an increase on the Hyperion Enterprise application of 325 entities.
There is always at least one profit centre which corresponds to each Hyperion
Entity.

page 44 of 79
10. SAP BPC Business Processes

The system will provide several types of calculations performed on demand or
automatically:
 Flow calculations
 Opening Balances
 Calculations between schedules
 Foreign currency conversion
 Validation formulas
10.1. Flow calculations

10.1.1. Flow F15 (Movement) calculation
For all Working Capital accounts, the net variation (i.e closing balance – [opening
balance + specific flows]) is calculated in flow F15. This calculation is included in
the Write Back BADI logic, which enables a real time calculation whenever data is
saved in the schedules.
For all other Balance Sheet accounts, the net variation must be distributed on
relevant flows in the corresponding schedule. When saving new values, the
movement flow (F15) is calculated again and must be zero in the schedule (forms
basis of the validation report).
Formula:
[F15]= [F99] – ([F00] + [F50] + [F22] …. All specific flows … [F08])
BPC property value in the Flow dimension will identify all movement flows in order
to simplify the maintenance of the [F15] formula in the Write back BADI, ie this will
not require manual maintenance.
10.1.2. Opening Balances

For input data, the calculation of opening balances is executed centrally by using
the “CopyOpening” Data Management Package with the Carry Forward Rules.
This package allows the admin user to populate the opening balance of the
current period from the prior year-end closing balance in order to ensure the flow
consistency over time periods.
 Source account All Balance Sheet accounts

 Source flow F99 – Closing balance
 Destination flow F00 – Opening balance
 AuditID type Input
10.2. Calculations within and between schedules

All calculations in the schedules get data from other schedules. These calculations
are executed when the users save their data.

page 45 of 79
In order to optimise performance, the Write Back BADI functionality of BPC

Netweaver is utilised.
Each time a user sends data from the BPC schedule (Save data button) the
Writeback Badi analyses the set of records sent and executes only the calculations
where these records (combination of an account and a flow) are involved. The
calculation engine is designed in such a way it does not need to run all
calculations each time data is sent.
The complete list of calculations is available in the appendix 16.1, Calculations

within and between schedules.
10.3. Equity accounting for JV Entities Formatted: Heading 2
Serco needs to provide financial statement based on an equity accounting method.

This Equity Accounting method applied only on the Joint ventures entities.
Entity transformation
To do so, a group of calculations must be executed to copy data from JV entities to JV
entities adjusted for Equity accounting.
This implies that a second JV entity structure must be implemented to store the Equity
Accounting values. The copy of data will be done to a one to one basis.
The global process for the equity accounting is divided in 3 steps:

page 46 of 79
Step 01: Calculation of technical accounts with a weighting calculation

Step 02: Copy data from JVX entities to JVX_EA entities
Step 03: Calculate the SOCI accounts with the Equity Account impacts
10.3.1. Calculation of technical accounts

A group of technical accounts used only for the Equity Accounting process must be
calculated before they are copied to JVX_EA entities
These accounts are from the Sector & Geographic segmental information schedule (32)
except calculation 14
Calculation 1: Formatted Table

[ACCOUNT].[913010_EA],[FLOW].[SEC01] =
([ACCOUNT].[913010_SEC]),([FLOW].[SEC01])/([ACCOUNT].[913010_SEC]),([FLOW].[TOT_ Formatted: Right: -0.07"
SEC])*(([ACCOUNT].[898000T],[FLOW].[F99])- ([ACCOUNT].[
913020_SEC],[FLOW].[SEC_NONE]) Formatted: Font: (Default) Courier New
Calculation 2:
([ACCOUNT].[913010_SEC]),([FLOW].[SEC02])/([ACCOUNT].[913010_SEC]),([FLOW].[TOT
_SEC])*(([ACCOUNT].[898000T],[FLOW].[F99])- ([ACCOUNT].[
913020_SEC],[FLOW].[SEC_NONE])
Calculation 3:
Calculation 4:
Calculation 5:
[ACCOUNT].[250000_SEC_EA],[FLOW].[SEC01] =
[ACCOUNT].[250000T_SEC],[FLOW].[SEC01]/[ACCOUNT].[
250000T_SEC],[FLOW].[TOT_SEC]*[ACCOUNT].[NETASSET],[FLOW].[F99]
Calculation 6:
Calculation 7:

page 47 of 79
Calculation 8:
Calculation 9:
Calculation 10:
[ACCOUNT].[250000_GEO_EA],[FLOW].[GEO01] =
[ACCOUNT].[250000T_GEO],[FLOW].[GEO01]/[ACCOUNT].[
250000T_GEO],[FLOW].[TOT_GEO]*[ACCOUNT].[NETASSET],[FLOW].[F99]
Calculation 11:
Calculation 12:
Calculation 13:
Calculation 14:
[ACCOUNT].[500000T_EA], [FLOW].[F99] = Formatted: Font: (Default) Courier New
[ACCOUNT].[500000T],[FLOW].[F99]-[ACCOUNT].[BALANCE],[FLOW].[F99]
10.3.2. Data Copy from JVX to JVX_EA

A group of accounts are copied from the JV entities to the Equity Accounting JV entities.
Account Source Flow Source Entity Source Account Flow Entity

Destination Destination Destination
898000T PL99 JVX 892500 PL99 JVX_EA
500000T F65 JVX 916355_EA PL99 JVX_EA
570010 F65 JVX 916455_EA PL99 JVX_EA
NETASSET F99 JVX 125000 F99 JVX_EA
500000T_EA F99 JVX 918010 F99 JVX_EA
Reserves
500000T F00 JVX 918010 F00 JVX_EA

page 48 of 79
500000T F50 JVX 918010 F50 JVX_EA
500000T F01 JVX 918010 F01 JVX_EA
500000T F98 JVX 918010 F98 JVX_EA
500000T F35 JVX 918010 F35 JVX_EA
500000T F20 JVX 918010 F20 JVX_EA
500000T F25 JVX 918010 F25 JVX_EA
500000T F30 JVX 918010 F30 JVX_EA
500000T F55 JVX 918010 F55 JVX_EA
500000T F81 JVX 918010 F81 JVX_EA
500000T F85 JVX 918010 F85 JVX_EA
500000T F86 JVX 918010 F86 JVX_EA
500000T F83 JVX 918010 F83 JVX_EA
500000T F60 JVX 918010 F60 JVX_EA
500000T F40 JVX 918010 F40 JVX_EA
500000T F65 JVX 918010 F65 JVX_EA
500000T F22 JVX 918010 F22 JVX_EA
500000T F75 JVX 918010 F75 JVX_EA
500000T F88 JVX 918010 F88 JVX_EA
500000T F87 JVX 918010 F87 JVX_EA
500000T F11 JVX 918010 F11 JVX_EA
500000T F05 JVX 918010 F05 JVX_EA
500000T F06 JVX 918010 F06 JVX_EA
500000T F07 JVX 918010 F07 JVX_EA
500000T F08 JVX 918010 F08 JVX_EA
500000T F89 JVX 918010 F89 JVX_EA
500000T F80 JVX 918010 F80 JVX_EA
SECTORS
913010_EA SEC01 JVX 913010_SEC SEC01 JVX_EA
250000_SEC_EA SEC01 JVX 250000T_SEC SEC01 JVX_EA

page 49 of 79
250000_GEO_EA GEO01 JVX 250000T_SEC GEO01 JVX_EA
500000T_EA F99 JVX 918010 F99 JVX_EA
10.3.3. Calculate the SOCI with EA impacts

Once the data has been copies to the EA JV entities, the comprehensive income of the
year is calculated using the EA values in the Income Statement schedule
10.3.4. Calculation of the FX impact for Equity Accounting Formatted: Heading 3
Once all data has been copied to JV EA entities, the currency translation BPC package
will compute the Equity Accounting FX impact.
This value is stored on flow F79 and account 918010.
The rule is described in the Calculation design document section “FX Calculations”.

page 50 of 79
10.3.10.4. Foreign Currency Conversion

The Foreign Currency Conversion method in BPC is different to Hyperion for P&L.
Hyperion is cumulative average and BPC is average any currency other than local
currency will show differences between the two systems.
10.3.1.10.4.1. Principles
The Income Statement accounts are converted using the average rate of the
reporting period.
Balance Sheet account are converted using the period-end rate, excepted
investments and equity accounts which are maintained at their historical
acquisition value.
The currency translation will convert all local currency values into translated values
for Group currency (GBP) and Regional currency which is dependent on the
entity.
As some transaction values need to be entered at their historical value, such as

the acquisitions, these values are inputted directly in the Regional or Group
Reporting currencies and will not be converted from the local currency values.
Currency translation can be executed in either the consolidation monitor (see

Section 10.3.6) or using the data manager package (called FX Translation) within
the EPM add-in within Excel.
During data loading process the currency exchange conversion will be included
after the calculations and before the validations.
As described on chapter 7 we will run currency translation after manual data

input.
10.3.2.10.4.2. Rates Definition and Rate model

The following RATES are defined and must be entered in the RATES model.
 AVG average rate

 END closing rate

page 51 of 79
The RATES model stores all currency exchange rates for all currencies, specified in
the dimension INPUTCURRENCY, for each Period of the TIME dimension and each
Category of the CATEGORY dimension.
10.3.3.10.4.3. Rule Definition

The currency conversion rules are configured by using the RATETYPE property of
the ACCOUNT dimension in order to associate groups of accounts to identical
conversion behaviours.
Accounts General translation rule RATETYPE

Property
Income Statement accounts Average rate (AVG) AVER
Balance Sheet accounts F00 Opening balance : (OPENEND) AVNEND

(closing balance) translated
using the closing rate Closing balance : @ closing rate (END)
Movements : average rate (AVG)
(11) Goodwill F00 (OPENEND) AVNEND1
F99 (END)
F50 (Maintained at historical value => AS_IS formula)

page 52 of 79
F25 (AVG)
F45 (AVG)
F55 (AVG)
F60 (AVG)
F65 (AVG)
F15 (AVG)
(12) Other Intangible Assets F00 (OPENEND) AVNEND2
(13) Property, Plant and F99 (END)

Equipment
F20 (AVG)
F26 (AVG)
F27 (AVG)
F25 (AVG)
F30 (AVG)
F45 (AVG)
F55 (AVG)
F65 (AVG)
F15 (AVG)
(14) Subsidiaries Investment F00 (OPENEND) AVNEND3
(15) Joint Ventures Investment F99 (END)

page 53 of 79
(16) Associates Investment F50 (Maintained at historical value => AS_IS formula)
F60 (AVG)
F81 (AVG)
F15 (AVG)
(18) Loans F00 (OPENEND) AVNEND4
F99 (END)
F50 (AVG)
F20 (AVG)
F30 (AVG)
F40 (AVG)
F60 (AVG)
F81 (AVG)
F83 (AVG)
F85 (AVG)
F86 (AVG)
F87 (AVG)
F88 (AVG)
F15 (AVG)
(19) Intercompany loans F00 (OPENEND) AVNEND5
F99 (END)
F50 (AVG)

page 54 of 79
F40 (AVG)
F60 (AVG)
F81 (AVG)
F82(AVG)
F83 (AVG)
F84 (AVG)
F85 (AVG)
F86 (AVG)
F87 (AVG)
F88 (AVG)
F15 (AVG)
(20) Trade and other F00 (OPENEND) AVNEND6

receivables
F99 (END)
(21) Tax
F50 (AVG)
(22) Derivatives
(23) Inventories
(24) Trade and other
payables F22 (Maintained at historical value => AS_IS formula)
(25) Finance lease obligations F75 (Maintained at historical value => AS_IS formula)
(26) Non recourse loans F20 (AVG)
(27) Provisions F26 (AVG)
F27 (AVG)
F25 (AVG)
F30 (AVG)
F35 (AVG)
F40 (AVG)
F45 (AVG)
F55 (AVG)
F60 (AVG)
F65 (AVG)
F81 (AVG)

page 55 of 79
F15 (AVG)
(28) Reserves F00 (OPENEND) AVNEND7
F99 (END)
F50 (AVG)
F24 (AVG)
F77 (AVG)
F35 (AVG)
F55 (AVG)
F60 (AVG)
F65 (AVG)
F81 (AVG)
F83 (AVG)
F85 (AVG)
F86 (AVG)
F87 (AVG)
F88 (AVG)
F89 (AVG)
F10 (AVG)
F11 (AVG)
F05 (DIV)
F06 (DIV)
F07 (DIV)
F08 (DIV)
F15 (AVG)
(17) Retirement Benefit AVNEND8 Formatted: Space After: 0 pt, Line spacing: 1.5 lines

page 56 of 79
10.3.4.10.4.4. FX system calculation

The currency difference resulting from the translation of movements at average
rate and the translation of closing balance at closing rate, is recorded in the
original account on flow F80-FX system calculation
This calculates the FX rate impact between the opening rate value and the
closing rate value.
 For all Balance sheet accounts

 On converted values only (All Group and Regional currencies)
FX system = (Closing – Opening)-(sum of all other flows)
[F80] = ([F99] (@Closing rate) - [F00] (@Opening rate) - ([F01] + [F50] + …. [F15]
(@Average rate)
This calculation has to be executed after the Currency translation.
The system translation reserve calculation is detailed in Appendix I.
10.3.5.10.4.5. Historical values

Child rates are used in Hyperion Enterprise to store transaction values at a specific
rate (historical rate) in each Entity. However, In BPC the users will input directly the
transaction values in the Group or Regional currencies (GBP, USD, AUD…) in each
profit centre.
Before Go-Live there will need to be a one off exercise performed by Serco to
populate the historical values at a profit centre level, where one Hyperion entity
has more than one profit centre mapped, the values in Hyperion will need to be
split between profit centres.
In the schedules, the accounts with historical values have a data link to enable
drill through to another small input schedule. It will be the same drill through report
for all historical values as the report will pick the selected account when the user
double clicks on the cell.

page 57 of 79
The following input schedule will allow the users to enter and save the historical
values for the selected account. Like any other schedule saving the historical data
will trigger all calculations and validation formulas.
Historical values are stored on the Group and Regional Reporting currencies (GBP,
USD, and AUD…) and on the AUDITID member “HIST_VAL”. It is best practice to
keep the historical values separate on a different AUDITID, so that they can be
filtered easily from the database, to assist with reporting or to copy them. It is also
more secure.
Converted values are stored on GBP/INPUT data slice, whereas historical values
are stored on GBP/HIST_VAL
In order to keep the historical values unchanged and not translated by the FX
translation logic, the AS-IS formula is used for the “HIST_VALUE” ACCTYPE in the FX
Translation Business Rule.
10.3.6.10.4.6. Consolidation Monitor

To run currency translation we will use the consolidation monitor which is new
functionality available in SAP BPC NW 10. It can be run at any point in the
selected hierarchy based on security, period and category. We will have 5
different groups that will be configured in ConsoScope dimension as previously
described in master data chapter. The following picture shows an example of the
consolidation monitor showing the currency translation by Serco statutory
structure:
The following picture shows the consolidation monitor showing the currency
translation by Serco Management structure:

page 58 of 79
The Consolidation Monitor will allow the user to see if any of the children entities
below a parent entity selected are impacted by any new input data and
therefore a currency translation is required. The status “To be executed” will
indicate that the currency translation needs to be performed due to a new input
data. The status “Done” will indicate the currency translation has been performed
and that no changes in the data have impacted the entity.
10.4.10.5. Validations and Controls

10.4.1.10.5.1. Validation report
Before the Cash Flow process can be completed, it is important to check for
completeness and accuracy of the data. In the validation report ‘context’ (point
of view), user can select any member of any dimension (eg Entity, Currency,
Period etc) to review the report. User can run the report at any ‘Entity’ level from
the ‘Entity’ Hierarchy based on their user access profile.
The validations in BPC were created using the following process:
 analysed the current Hyperion report
 replicated validation controls and formulas where possible
 rationalised validation controls and formulas where required
 addressed any gaps in validation controls and formulas as a result of the
above.
Structure of the Report

This report will have two sections a Summary Section and Detail Section.
Summary
The summary section will hold a static list of schedules which will summarise the
relevant validations. Below is the current layout for the summary section.
 Primary schedules
Cash Flow (3)
Free cash flow (4)
 Supporting schedules for inc/exp

page 59 of 79
Revenue and Minority Interest (6)

 Supporting schedules for balance sheet
Goodwill (11)
Other Intangible Assets (12)
OIA Other Intangible Assets) to/from PPE (Property, Plant and Equi) (12/13)
Property, Plant and Equipment (13)
Investments (reports 14/15/16)
Retirement Benefit Schemes (17)
Loans (18)
Intercompany Loans (19)
Tax (21)
Derivatives (22)
Finance Lease Obligations (25)
Non-recourse Loans (26)
Provisions (27)
Reserves (28)
 Acquisitions / Disposals
Acquisitions (29)
Disposals (30)
 Transfers from / (to)
Transfers from / (to) (31)
 Additional schedules for quarter end
Sector & Geog - Segmental info (32)
Aged debtors / Bad debt provision (36)
Detail
This contains validations by schedule or several schedules together. Validations by
schedules check consistency of data in database making comparison across
schedules. For example, one Hyperion validation for Goodwill (11) schedule is
shown below.
This validation checks that the value in the Balance Sheet account used in
Goodwill (11) schedule has the same value as the account in Income Statement
schedule.
In the new Cash Flow design this validation will be as follows.

page 60 of 79
The value in Balance Sheet account for 101000M - Goodwill, Impair with flow F60 – Commented [EF2]: Incorrect
Impairment is the same value on Income Statement account 820070, Flow PL99.
An example of one validation for multiple schedules is shown below. The three
investments schedules are Subsidiaries Investment (14), Joint Ventures Investment
(15) and Associates Investment (16)
Hyperion:
This validation checks that value in one specific Account/sub account on

schedule Subsidiaries Investment (14) + one specific Account/sub account on
schedule Joint Ventures Investment (15) + one specific Account/sub account on
schedule Associates Investment (16) has the same value of account filled in
Income Statement for Investments impairment.
In general, Hyperion validation uses formulae that check that one account or a set
of several accounts have the same value of another account or a set of several
accounts.
In the new Cash Flow design this validation will be:
This validation will verify that the sum of accounts 120000 + 121000 + 122000 using
flow F60 is the same value as Income Statement account 820025, Flow PL99.
In the future BPC NW 10 application, these validation will be done by account,
flow and analysis dimension.
This validation report will use control accounts as technical accounts to validate
data consistency. These calculations will be included in the writeback BADI.
All detail validation requirements are available on excel file attached on
Appendix II Link to Schedules layout detail, sheet VALQ413 (2).
In SAP BPC NW 10 there is a new functionality that uses Control Monitor to validate
data. However, it has been decided to use a variant of a Hyperion report instead,
because the users will be familiar with this and don’t need to run any button.
Control monitor requires the user to trigger the validation calculations, the
proposed calculations update automatically on data entry.

page 61 of 79
10.4.2.10.5.2. Master data validation

The master data validation concept prevents users from saving and loading
incorrect combinations of dimensions members. This configuration is done in the
backend system (BW) and is environment specific.
The Account dimension already has some validation configured. The following
figure shows a print screen with configuration done in Sandbox system,
Environment Serco_FPRS.
Validation 1
All Income Statement accounts only use flow PL99.
Validation 2
Balance Sheet accounts cannot use flow PL99.
Validation 3
This is for valid flows for Balance Sheet accounts. This validation uses a BADI called
BADI_UJ_VALIDATION_RULE_LOGIC, that validates against FLOWAN property of
Account.
This validation will not be continued in the Cash Flow project due performance
reasons.
Serco will need to introduce a robust process to validate changes to mitigate the
risk of lack of validation due to a change.
Only validations 1 and 2 will be used in the new Cash Flow project.
Validation 1
Assign all Income Statements accounts [600000 - 909999]. Income statement
accounts have the interval between 600000 and 899999. All accounts beginning
with ‘9’ are specific BPC accounts such as Cash Flow and Free Cash Flow.
ECC also uses accounts beginning by ‘9’. The ECC codification is that the first
three digits begin with ‘995’. This codification will not be used in SAP BPC.
Validation 2
Assign all Balance Sheet Accounts [100000 - 599999].

page 62 of 79
11. Schedules
11.1. Schedules (Input Forms and Reports)
The Cash Flow project has Schedules (currently 37) in scope. All these schedules
are detailed by entity (see Section 11.3)
The link for schedules detail layout is available on the Appendix III Link to
Schedules layout detail at the end of this document.
The primary schedules are:
 Income Statement (1)

 Balance sheet (2)
 Cash Flow (3)
 Free cash flow (4)
 Net Debt (5)
Supporting schedule for Income and Expenditures
 Revenue and Minority Interest (6)

 Cost of Sales (7)
 Administration Expenses (8)
 Investment Revenue / Finance Costs (9)
 Tax Charge (10)
Supporting schedules for Balance Sheet
 Goodwill (11)
 Other Intangible Assets (12)
 Property, plant and equipment (13)
 Subsidiaries Investment (14)
 Joint Ventures Investment (15)
 Associates Investment (16)
 Retirement Benefit Schemes (17)
 Loans (18)
 Intercompany Loans (19)
 Trade and other receivables (20)
 Tax (21)
 Derivatives (22)
 Inventories (23)
 Trade and other payables (24)
 Finance lease obligations (25)
 Non recourse loans (26)
 Provisions (27)
 Reserves (28)
Acquisitions / Disposals
 Acquisitions (29)
 Disposals (30)

page 63 of 79
Transfers from / (to)
 Transfers from/(to) (31)
Additional schedules for quarter end
 Sector & Geog – Segmental info (32)

 Headcount (33)
 Leasehold Commitments (34)
 Capital Commitments (35)
 Aged debtors / Bad debt provision (36)
 Long term Contracts (37)
Validation reports
 Validation Report – Q4 2013: this is detailed in the previous chapter (10.4)
The following schedules will be used as input forms only by Super Users. All other
users will have view only access.
 Income Statement (1)

 Balance sheet (2)
 Cash Flow (3)
 Free cash flow (4)
 Revenue and Minority Interest (6)
 Cost of Sales (7)
 Administration Expenses (8)
 Investment Revenue / Finance Costs (9)
 Tax Charge (10)
 Goodwill (11)
 Other Intangible Assets (12)
 Property, plant and equipment (13)
 Validation Report
In SAP BPC system schedules are either Input Forms or Reports.
 Input form is a schedule where data can be entered and saved to the
database
 Reports only retrieve data from database (none in scope for Serco)
These schedules are reports because users will not use them to save data. Data in
these schedules are only uploaded from source system, from BW to Actual and
then from Actual to Consolidation.
The following example shows part of the Balance Sheet.

page 64 of 79
Figure: Part of Balance Sheet
In the data area, there are two different colours.
Legend
Data is locked. The user cannot change this data. This is

applicable to data from previous year, parent members or invalid
member’s combination.
Super Users only can change this data. This data comes from
‘Actual’ model. If this data needs to be changed then the data
will be uploaded again by super users from Actual model.
Reports will have two macro buttons.
Button to refresh data
Button to close the report
Schedules that will be SAP BPC end user input forms:

 Net Debt (5)
 Subsidiaries Investment (14)
 Joint Ventures Investment (15)
 Associates Investment (16)
 Retirement Benefit Schemes (17)
 Loans (18)
 Intercompany Loans (19)
 Trade and other receivables (20)
 Tax (21)

page 65 of 79
 Derivatives (22)
 Inventories (23)
 Trade and other payables (24)
 Finance lease obligations (25)
 Non recourse loans (26)
 Provisions (27)
 Reserves (28)
 Acquisitions (29)
 Disposals (30)
 Transfers from/(to) (31)
 Sector & Geog – Segmental info (32)
 Headcount (33)
 Leasehold Commitments (34)
 Capital Commitments (35)
 Aged debtors / Bad debt provision (36)
 Long term Contracts (37)
These schedules are input forms because they are used to send data to the
database. Using EPM_Add_In events, a validation will be created which prevents
the data being saved if:
 Currency <> LC (Local currency)

 AuditID <> Input
 Check that no data has been checked in the invalid cell.
Example of one Input Form:
Figure: Part of Inventories input form
Legend
Data is locked. The user cannot change this data. This is applicable
to data from previous year, parent members or invalid member’s
combination.
Only super Users can change this data.
Users can fill with data and send data into data base

page 66 of 79
These are calculated members with calculation rules and cannot

be edited.
The reports will have three macro buttons.
Button to refresh data
Button to close the report
Button to send data to database
11.1.1. Global design approach

The implementation of the schedules will be done with the EPM Add-in for BPC 10
NW.
Similar to Hyperion system which have a ‘current view’, SAP BPC has the Context.
Context allows user to select a member of each dimension except the ones
protected (e.g. ConsoScope, all input data have to be inputted on the G_NONE
member). For example:
Dimension Example of Members
Time January 2014
Entity C_PC80000 (GRP Serco

Group)
Currency LC, GBP, USD Commented [EF3]: There's no colouring
The ones that are unprotected are designated in the Schedules design document
as orange colour, and the ones that are protected are uncoloured (Excel
document).
Data can only be sent to the database at base level, if user runs a report at a non
base level member they will not be able to save to database.
Each schedule will be built in an individual Excel file (report or input form). All
schedules will show current period and comparative period which will be prior
year end.
One of the business requirements is to have different descriptions for the same
flow. For example, flow 20 – Additions in the schedules (18) - Loans and (19)
Intercompany Loans should be named as ‘Advances’, in schedule (20) - Trade
and other receivables should be named as ‘Interest receivable’ and in schedule
(24)Trade and other payables’ should be named as ‘Interest (payable)’.
This business requirement can be achieved in two different ways:

page 67 of 79
 Using properties in flow dimension, creating a property by schedule. It will

mean around 20 additional properties. This is a standard way to achieve this
requirement in release SAP BPC 7.5.
 Using the new functionality available in BPC NW 10, EPM Add in. This
functionality enables a different description to be shown for a specific
member of one dimension in the report.
Using 20 additional properties in flow dimension could generate performance

issues. Because of the performance concerns, the Cash Flow project will use the
new functionality available in SAP BPC NW 10, creating the different description at
reporting level.
In general, the schedules will be static with no expansions, especially for the
schedules with combinations of flows and accounts. Primarily, this will provide a
better performance but it will also easily maintain the formatting colour of the cells
(see below for the colour legend). As referred on Section 8.3.1 (Account dimension
details) property FLOWAN will not be used anymore for formatting purposes due
performance reasons.
Some schedules will be dynamic with a column expansion, especially those using
the Analysis dimension in column. (Subsidiaries, JV and associates investments).
VBA script will be used for the Close and Refresh button. When closing the
schedule a prompt message will ask the user to save the data before closing the
schedule.
11.1.2. Locking data within schedules:
All schedules will be password locked except some areas to input data (light
yellow cells). This will prevent data entry at invalid combinations of accounts and
flows.
The following cell colours are available within schedules:
Calculated cell: locked
Invalid cell: locked
Input data cell: unlocked for Super User only
Input data cell: unlocked
Only ‘super users’ will have access to the password, which will unlock these cells.
Data locked for ‘normal’ users can’t be changed by them but they can see the
data, if they have the correct security profile.
It is best practice not to secure the account dimension. The way to avoid users
entering data in certain account and flow combinations is by locking cells at
report level. We will not use master data validation due performance reasons as
explained in Section 10.3.2 – Master data validation. The risk to this solution is that if
users create their own reports they can send incorrect data to the database. To

page 68 of 79
mitigate this risk for each account and flow where there should be no data input
there will be a line on an additional validation report. The validations will be
grouped by schedule and summarised at the top of the report, this enables the
user and reviewer to see quickly if there is data on combinations of accounts and
flows where there should not be.
Pending a formal change request process the work on this report will start if
approved.
11.1.3. Reports printing capabilities:
It is a native functionality to print schedules individually. All 37 individual schedules

and all 37 drill down schedules and reports (expanded by entity) can also be
printed individually.
We will use Book Publication Template functionality to enable the printing of

schedules together or as a set of all 37 drill down schedules (expanded by entity).
The first page will contain a numbered list of the Schedules (currently 37). The first
page will be an Excel BPC report.
The output format for Publication can be a printer (all printers available in Serco
Citrix profile including XPS) or a PDF document.
All reports, outputs contain the following header information: Date, Time,
Schedule number and name, Serco logo, Category description, CV entity, CV
currency, CV time period.
All reports, outputs contain the following footer information: CV entity code, CV
account code, Filename, CV category code, user ID, Printed time and date, page
number and Serco in Confidence.
11.1.4. Offline capabilities

The standard offline functionality of BPC allows users to save any schedule or
report to any drive based on the users Citrix profile.
Using the offline functionality will allow users to view the schedules and reports
outside the BPC application.
Only a VBA custom development can generate automatically an offline workbook

with all Schedules (currently 37) in individual tabs. This VBA development will open
individually each schedule, setting it off line and copying it in a new workbook to
be saved locally.
11.2. Navigation between schedules
All input forms have a link to drill to the Validation report.

page 69 of 79
11.2.1. Business Process Flow

To access the Schedules (currently 37), the users will use a Business Process Flow
and then navigate from schedule to schedule using quick links. Open Issue - there
is a current issue of users not following through the process until the end and
closing the process before final step is finished. SAP to investigate, if it’s possible to
get around this standard BPC process.
11.2.2. Quick links from Primary Schedules
Some reports will have links that allow users to open other schedules to get detail
information. Schedules with links to other schedules are listed below.
Balance Sheet has links to:
 Data Link to Goodwill (11)

 Data Link to Other Intangible Asset (12)
 Data Link to Property Plant Equipment (13)
 Data Link to Retirement Benefit Schemes (17)
 Data Link to Loans (18)
 Data Link to Interco Loans (19)
 Data Link to Trade and other Receivable (20)
 Data Link to Tax (21)
 Data Link to Derivatives (22)
 Data Link to Inventories (23)
 Data Link to Trade and other Payable (24)
 Data Link to Finance Lease Obligations (25)
 Data Link to Non Recourse Loans (26)
 Data Link to Provisions (27)
Income statement has links to:
 Data Link to Revenue and Minority Interest (6)

 Data Link to Cost of Sales (7)
 Data Link to Admin Expenses (8)
 Data Link to investment revenue (9)
 Data Link to Tax Charge (10)
Cost of Sales has links to:
 Data Link to Retirement Benefit Scheme (17)
Administration Expenses have links to:
 Data Link to Retirement Benefit Scheme (17)

page 70 of 79
11.2.3. Quick links from validation report
From Validation report we will have the following links to:
Primary schedules
 03 - Cash Flow
 04 - Free cash flow
Supporting schedules for inc/exp
 01 - Income statement
 06 - Revenue and Minority Interest
Supporting schedules for balance sheet
 02 - Balance Sheet
 11 - Goodwill
 12 - Other Intangible Assets
 13 - Property, Plant and Equipment
 14 - Subsidiaries Investment
 15 - JV Investment
 16 - Associates Investment
 17 - Retirement Benefit Schemes
 18 - Loans
 19 - Intercompany Loans
 21 - Tax
 22 - Derivatives
 25 - Finance Lease Obligations
 26 - Non-recourse Loans
 27 - Provisions
 28 - Reserves
Acquisitions / Disposals
 29 - Acquisitions
 30 - Disposals
Transfers from / (to)
 31 - Transfers from / (to)
Additional schedules for quarter end
 32 - Sector & Geog - Segmental info

 36 - Aged debtors / Bad debt provision
For example, Balance Sheet, user can check the value of Goodwill for flow F99 for
the entity and time selected.

page 71 of 79
The EPM Add – In Quick Link will be used to achieve this requirement. In the
Balance Sheet example a quick link will be create in Balance Sheet report to
guide users through the detailed analysis.
11.3. Drill downs reports

All schedules and the validation reports have the functionality to drill-down
through the entity and currency dimensions. This means that a user only has to
select the parent member in the Entity dimension in schedule context to get the
entities details below that parent item. By using a quick link in the main schedule
(one for each account above the account description), the user will open a similar
report with the same flows in rows, the same context in page, but with the
selected account and with the detailed data information by entity and currency
in column.
It will be then possible to drill down from any parent entity with in the columns and
to have a break down with all the direct dependant entities and by currency
(Local currency, Group currency and Regional currency). If we use the “no data
suppress” functionality it will only show columns with data.

page 72 of 79
The exception to these drill down reports are schedules Acquisitions (29) and
Transfers from/ (to) (31). The drill down information will be accessible from within
the schedules using the native drill down functionality in BPC.

page 73 of 79
12. SECURITY
12.1. Security
Security principles for consolidation will follow the same general rules in place now
for ACTUAL and conform to current process and method in Hyperion.
For the detail surrounding its build and architecture please refer to the Security
build and Architecture documents in the appendices.
IDM (identity management):

New users will only get access post completion of the current new user process,
this process checks membership of AD(Ourworld) access to ECC where
applicable, SAP BW and SAP BPC.
SAP ECC roles have no impact in SAP BPC whatsoever, (BPC deny profiles WILL be
applied by the BAU team in SAP BW to reduce rights granted by SAP ECC), see
next section.
SAP BPC users are not permitted access unless trained, and training being
confirmed.
The user will be set up in SAP BW first with roles from ECC, CSI will add additional
specific roles for SAP BPC, the BAU team will then take the SR and add the
technical ID’s for the roles below:
Teams, Data Access Profiles, Task Profiles
Access within the system:

User access to entities is governed by their team membership the team will be
linked to a data access and task profile.
Example: a member of Team T_PC80000 has one data access profile and one task
profile attached.
The data access profile permits the user to see PC80000 (Group) and will also allow
visibility exclusively of all children to that parent right to the lowest member.
Unlike Hyperion – users cannot see any structure whatsoever of entities not in their
approved area.
Deny data access profiles are used where particular entities within a previously
granted area must be excluded from the users view – example AWE within 80702.
In consolidation ConsoScope will also be listed in the same data access profile
allowing access at the same level – PC80000 with the same effect.
Finally a task profile will also be attached – this gives the user rights in terms of
actions they can undertake within the view granted by the data access profile,
these actions will include the ability to send data back to the data base and the
ability to consolidate.

page 74 of 79
12.2. Data Work Status
ALL of the rules applied in Security are further controlled by work status. User ability
to WRITE data is limited by work status settings against entities. Also the system’s
ability to update data by Deltas is governed by work status.
Step 1: DEFAULT WORK STATE: Users and data packages are allowed to WRITE data
to entities with this setting
Step2: APPROVED: Users and data packages have no rights to WRITE data, users
can still READ data (governed by their security)
Serco locks work status (moves to APPROVED) at divisional levels, UNDERREVIEW
and SUBMITTED are not used but configured.
Work status is controlled fully by the BAU team in conjunction with Group
Reporting.
Locking/unlocking is only carried out on their explicit request.

page 75 of 79
13. Enhancements
In order to run the SAP BPC NW application, some logic needs to be defined.
Different types of logic are available
 Logic script
 Writeback BADI
This logic is referred to in specific sections when it is used. For example, in Controls
and Validation, it is referred to as a BADI implementation. Cash Flow calculations
will also use a BADI.
As Calculation rules are mostly simple (additions and subtractions) we will define
them as entries in a Z Table. This table gives all detailed information (Source,
destination, operator) needed to perform the calculations and will be easily
maintainable by the admin team. New calculation rules can be added without
changing any ABAP code.
The code logic that calculates the accounts’ values, with the help of the Z table
calculation rules, will be called in two different occasions:
-by a write back BADI when the user saves the data from the Input Schedule: only
the calculations for the data sent are calculated. The system will compare what is
currently in the database with what has been sent via an input form. Only data
changed will be calculated, this is the Delta mode.
-by another method that is executed just after loading data: all the calculation
rules defined in the Z Table are executed.

page 76 of 79
14. Data Migration
For historical data population in the ‘Consolidation’ model, data from ‘Actual’
model needs to be transferred into the new model at Profit Centre level and at
local currency using the new Chart of Accounts and Flows.
The data migration will include:
 Prior year end Balance Sheet
 January to Go Live month Balance Sheet and Income Statement
 One-off exercise to create all base data currently held in Hyperion
Enterprise entity level and transfer to SAP BPC at Profit Centre level.
Before go-live Serco shall prepare data at a Profit Centre Level for the following
historical value data for Regional and Group Reporting Currencies for loading into
the Cash Flow Application:
 Prior year end closing Balance Sheet (loaded in local currency)

 Prior month YTD Income Statement and Balance Sheet (loaded in local
currency)
 Current month YTD Income Statement and Balance Sheet (loaded in local
currency)
 Prior month YTD input data for Cash Flow, free cash flow and net debt (created
in local currency)
 Current month YTD input data for Cash Flow, free cash flow and net debt
(created in local currency)
 Prior year end historical values (created in both reporting and regional
currencies)
 Prior month YTD historical values (created in both reporting and regional
currencies)
 Current month YTD historical values (created in both reporting and regional
currencies)
SAP shall review the historical value data for Regional and Group Reporting
Currencies once loaded for completeness only.
All data migration activities will be detailed in the cut over document.

page 77 of 79
15. Appendices
15.1. DRAFT calculations within and between schedules
These are the calculations to perform in the schedules to populate certain

combinations of accounts and flows.
Below is the list of calculations for each schedule.
Cash Flow
Configuration Design for Calculations.docx
15.2. DRAFT schedules layout
Design Document
Cash Flow Schedules v.95.xlsx
15.3. Security Architecture and DRAFT Design Document
BPC 10 SDF Security GTD BPC Security

Architecture template v2.0Design v0 3.doc
Approved.doc
15.4. Design Strategy for BPC dimensions
Design Strategy for

BPC, COA, Flows & dimensions.pptx
15.5. Activities for data integration for new flows

page 78 of 79
15.6. Statement of Work
BPC Cash Flow

SOW.pdf

page 79 of 79

SAP Cash Flow Configuration Design Document - v1.0 - APPROVED

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SAP Cash Flow Configuration Design Document - v1.0 - APPROVED

Hochgeladen von

Copyright:

Verfügbare Formate

SAP Solution Design

Project CASH FLOW

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

All Programme Board Members

Caroline McKinnon Group Reporting Manager See above See above

Tony Sullivan SGS Head of Finance See above See above

Andrew Martin UK&E Head of Finance See above See above

Stephen GTD PMO Project Support See above See above

Adrian Day GTD Project Manager See above See above

Emma France R2R GPO See above See above

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

1. Document Purpose ................................................................................................. 86

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

10.4.4. FX system calculation............................................................................... 5755

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

7.2. Monthly process overview ............................................................................ 17 Formatted ...

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

12. SECURITY ............................................................................................................. 68 Formatted: Default Paragraph Font, Check spelling

15. Appendices............................................................................................................. 72 Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Formatted: Default Paragraph Font, Check spelling

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

In January 2011, Serco initiated the Halogen Programme to rationalise, standardise

a. Ability to do Indirect Cash Flow reporting in BPC

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

The Project scope is as follows:

 Implement new Flows.

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

 Drill Down reports by detailed Entity level.

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

 User prompted calculations

 Business Process Flows

3.2. Out of Scope

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

 Functional Area in consolidation model

 System administration activities such as backups, availability, capacity etc

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

5. Key Design Decisions

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

ACCTYPE Accounts Database Display in Excel

EXP Revenues (-) (-)

AST Liabilities (-) (-)

Printed on 15 September 201906 July 201423 June 2014 Serco Internal

Cash Flow project is running in parallel with Upgrade project (technical

New project to be delivered by Serco to change the location of

Security must be reviewed. It is out of scope because it is the