Académique Documents
Professionnel Documents
Culture Documents
Author:
Owner: IBM
Customer: XXX
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.
Revision History
Date of this revision: 2008-03-13 Date of next revision
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)
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
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.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
1.7 Notation
N/A
1.8 Abbreviations
BO – Branch office
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.
All changes what need to be done and described in this document influence only reports in the table
provided below.
2.3 Characteristics
2.3.1 Characteristic n
XXX Approved Object definition
2.4.1 KeyFigure n
XXX Approved Object definition
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:
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.
The MU/BO finance roles above (bullets) access in controlled on company code and profit center basis.
The MU/BO finance roles above (bullets) access in controlled on profit center basis.
The MU/BO finance roles above (bullets) access in controlled on cost center basis.
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).
3. Approval criteria