XXX SAP Program - BW

Business Blueprint - Branch Office ERP BW Development

Author:
Owner: IBM
Customer: XXX

Document: 44949657.doc Date: 11/13/2010

Owner: IBM Version: v4.0
Status: final
Page 1 of 9
 XXX SAP Program - BW

Document History

Document Location
This is a snapshot of an on-line document. Paper copies are valid only on the day they are printed. Refer
to the author if you are in any doubt about the currency of this document.

The source of the document will be found in /opt/scribd/conversion/tmp/scratch2474/44949657.doc

Revision History
Date of this revision: 2008-03-13 Date of next revision

Revision Revision Summary of Changes Changes

Number Date marked
V1.0 2007-10-12 First draft ready for internal review
V2.0 2007-10-19 Updated after initial discussion with Customer
V3.0 2007-10-22 Updated with comments from Inger and Henrik
V4.0 2008-03-13 Removed Inventory reports and Trading partner; Updated
Authorizations chapter.

Approvals
This document requires following approvals. Signed approval forms are filed in the Quality section of the
PCB.

Name Title
(Name) (title)

Distribution
This document has been distributed to

Name Title
(name) (title)

Document: 44949657.doc Date: 11/13/2010

Owner: IBM Version: v4.0
Status: final
Page 2 of 9
 XXX SAP Program - BW

Contents
1. Introduction....................................................................................................................4
1.1 Identification.......................................................................................................................................4
1.2 Description.........................................................................................................................................4
1.3 Organisation.......................................................................................................................................4
1.4 Time Plan...........................................................................................................................................4
1.5 Purpose..............................................................................................................................................4
1.6 References.........................................................................................................................................4
1.7 Notation..............................................................................................................................................5
1.8 Abbreviations.....................................................................................................................................5
2. Business Requirement Definitions.................................................................................6
2.1 Specifications.....................................................................................................................................6
2.1.1 Branch Office transactions...........................................................................................................6
2.2 Report Specification...........................................................................................................................7
2.3 Characteristics...................................................................................................................................7
2.3.1 Characteristic n............................................................................................................................7
2.4 Key Figures........................................................................................................................................7
2.4.1 KeyFigure n.................................................................................................................................7
2.5 Authorization concept.........................................................................................................................8
3. Approval criteria.............................................................................................................9
3.1.1 Branch office test scenario..........................................................................................................9
3.1.2 Testing new Branch office specific trigrams.................................................................................9
3.1.3 Currency conversion....................................................................................................................9

Document: 44949657.doc Date: 11/13/2010

Owner: IBM Version: v4.0
Status: final
Page 3 of 9
 XXX SAP Program - BW

1. Introduction

1.1 Identification
This document contains the business requirements for the Branch Office ERP BW development. A
separate System Blueprint will describe the technical requirements to deliver the functionality.
Requirements exceeding what’s stated in this document will be handled via a Change Request
procedure.

1.2 Description
This document describes the business demands for the Branch Office ERP BW project that covers FI and
Inventory Management reporting areas. The project will follow the BW Guidelines, which state the rules
for design, development, documentation, test and integration in the BW landscape.

1.3 Organisation
Project Member Organization Responsibility
Henrik Josefsson/ Inger XXX ITM Responsible
Martinsson
Madhuchanda Pandit IBM Project Manager
Rajeev Kumar IBM Architect
Irmantas Joksas IBM Senior Developer

1.4 Time Plan

The project will follow the time plan of testing for branch offices Iraq and Jordon in Jan 2008, the technical
go-live is planned in Mid Jan 2008.

1.5 Purpose
The purpose of this document is to describe the demands that will be implemented in the Branch Office
ERP BW solution in BW. The need for this is two-fold: on one hand, the XXX business representatives
should review the document and agree on the common and identical understanding of the demands with
the IBM implementation team and on the other hand, serve as a starting point in order to be able to create
the System Blueprint which is going to be the baseline for the implementation of the Branch Office ERP
project. This document and the referenced report specifications will have to be signed-off by the business
before development can begin.

1.6 References
N/A

Document: 44949657.doc Date: 11/13/2010

Owner: IBM Version: v4.0
Status: final
Page 4 of 9
 XXX SAP Program - BW

1.7 Notation
N/A

1.8 Abbreviations
BO – Branch office

Document: 44949657.doc Date: 11/13/2010

Owner: IBM Version: v4.0
Status: final
Page 5 of 9
 XXX SAP Program - BW

2. Business Requirement Definitions

The business requirements are based on RFS document and follow-up meetings and workshops. The
business objects (characteristics and key figures) defined in this section is elements derived from the
RFS document. This means that the business objects specified will be covered by a combination of key
figures and characteristics.

2.1 Specifications
In order to support the Branch Office solution the BW development has been identified.

Secure that BO CBS EAB transactions can be combined with BO ONE MUS transactions in the flow
CBS/MUS-P50-SBYN-Local ECON-ECON-P50.
Requirement is described below.

2.1.1 Branch Office transactions

Each Branch office (BO) will be set up with as a separate company code in MUS, having its own Balance
Sheet and Profit & Loss. During period end closing, BO project costs and billing are transferred from the
BO project to the EAB project/PSF order. Before the transfer, the BO project is settled to a P/L account in
FI in order not to create ‘double counting’ of the project costs/billing. The total Balance Sheet and Profit &
Loss from the BO company code should be uploaded to BW. Net Sales, COS and order booked is always
only reported from EAB, never from the BO.
Branch Office transactions coming from EAB must be possible to identify in BW.
No new reports should be created.
Secure that the BO currency concept works together with the BW Finance Guideline EDW currency
handling.

All changes what need to be done and described in this document influence only reports in the table
provided below.

Reporting area Report name

FIRE MR
MRMU
MRPA
ECUST
KAINVBU
EB01
EI02
EB05
EI04
PCA BU MU Analysis Local Currency
BU MU Analysis Group Currency
Cost Center Analysis
COPA COPA Details
Internal Orders Internal orders analysis

Document: 44949657.doc Date: 11/13/2010

Owner: IBM Version: v4.0
Status: final
Page 6 of 9
 XXX SAP Program - BW

Projects Analytical Report (Projects Local)

2.1.1.1 Company code hierarchy

EAB users should be able to analyze EAB aggregated data while at the same time have possibilities to
view data of each BO, which makes it necessary to create this relationship in a hierarchy for Company
Code. This would enable users with access to EAB (2500) to open the hierarchy and find the BO’s listed
in the nodes below. This hierarchy should be included in the affected reports (table in the 2.1.1). New
trigrams will be created for each BO. ECON interface queries need to be adjusted to include branch office
company codes and the new trigrams.

2.1.1.2 Interface Queries

Interface queries to ECON must be checked for presence of trading partner and updated if necessary.
The new trigrams also must be included into interface queries.
Each BO will be allocated to one common trigram called BOA in Local ECON. In ECON each BO should
have its ‘own’ trigram.

2.1.1.3 Double Counting

Double counting of Branch Office data must be avoided in the EAB company code. That is responsibility
of R\3 side programs created by BO ONE project.

2.1.1.4 Currency translation

In the FIRE reports and PCA reports, the currency conversion for Brach offices should be performed for
the period balance (“Period balance” = “Feb balance” – “Jan balance”) and not for the YTD balance. (I.e.
In Feb closing Jan balance should be calculated with Jan rates and Feb balance should be calculated
with Feb rate. This is different from the concept used for other companies where In Feb YTD balance is
calculated with Feb rate.). BO should use OCAC rates for both PL and BS accounts. Currency of BOs
transactions should be converted to EAB reporting currency (SEK) regardless of BO high inflation
indicator.
There must be full traceability from Local Econ/Econ to BW reports.

2.2 Report Specification

2.3 Characteristics

2.3.1 Characteristic n
XXX Approved Object definition

2.4 Key Figures

2.4.1 KeyFigure n
XXX Approved Object definition

Document: 44949657.doc Date: 11/13/2010

Owner: IBM Version: v4.0
Status: final
Page 7 of 9
 XXX SAP Program - BW

2.5 Authorization concept

No changes to the existing authorization concept should be necessary, and the present roles should be
possible to use, with the addition of the new Branch Office company codes to the EAB users and BO
users.
It should be possible to view the BO companies from the regular Finance roles

 MU Controller
 Local Period End Closing
 Project Controller
 Local Controller

It should also be possible for branch office users to view the slice of data that is transferred from the BO
via the interface to EAB, without seeing large parts of EAB. The BO user must also be able to view EAB
data that is within their responsibility are such as: The BO project leader must be able to view the total
EAB project/PSF order structure (including contract) created in the EAB company code. The BO project
leader will be defined as “responsible person” on the WBS element in EAB company code. The BO
project controller must be able to view projects/PSF orders in EAB within the BO responsibility area and
BO local and MU controller must be able to view OPEX costs in EAB company code (2500 or 2800)
allocated to their branch/MU.

Suggested R&A high level logic for BO user access to "MU (Market Unit) and BO share" of EAB data:

 For project reports:

The BO project mgr access is controlled by reponsible person field in the MUS/ONE project and the CBS
project. The BO project controller and BO local controller access is controlled on profit center basis.

 For FIRE reports:

The MU/BO finance roles above (bullets) access in controlled on company code and profit center basis.

 For Profic Center reports:

The MU/BO finance roles above (bullets) access in controlled on profit center basis.

 For Cost Center reports:

The MU/BO finance roles above (bullets) access in controlled on cost center basis.

 For OPEX/Internal orders:

The MU/BO finance roles above (bullets) access in controlled on cost center basis. There is a concern
that EAB CBS cost center structure for the relevant cost centers in this area exists only on an aggregated
level (EMEA or similar).

Document: 44949657.doc Date: 11/13/2010

Owner: IBM Version: v4.0
Status: final
Page 8 of 9
 XXX SAP Program - BW

3. Approval criteria

3.1.1 Branch office test scenario

Run any FIRE or PCA report from table provided in 2.1.1
In report selection screen restrict company code to 2500 (EAB).
Execute report.
User must receive report results he is authorized to see. EAB user can see EAB results plus part of BO
data. BO user must see BO data plus part of EAB
Open company code hierarchy.
Under Company code 2500 (EAB) user must see list of BO’s values he is authorized to see.
This test scenario is applied to the reports mentioned in table in section 2.1.1.

3.1.2 Testing new Branch office specific trigrams

All FIRE reports should be tested to check that the branch office company codes come upto one common
trigram in Local ECON and have their own trigrams in ECON.
Import data from BW into ECON and ECON Local. Check trigrams and data.

3.1.3 Currency conversion

Correctness of currency conversion can be checked by taking numbers from MUS/CBS systems and
performing currency conversions manually. The entire flow from MUS/CBS systems up to ECON should
be checked. The calculated SEK value in BW must be exactly the same as the SEK value transferred to
ECON. There must be full traceability from local ECON/ECON to BW.

Document: 44949657.doc Date: 11/13/2010

Owner: IBM Version: v4.0
Status: final
Page 9 of 9