Document Control

Table of contents
1 General .........................................................................................................................2
2 BLUEPRINT REFERENCE.................................................................................................2
3 MASTER DATA REQUIRED..............................................................................................2
4 Functional Specification......................................................................................................2
4.1 Functional Development Description ...........................................................................2
4.2 Input Definition.........................................................................................................2
4.3 Output definition.......................................................................................................3
4.4 User interface ..........................................................................................................3
4.5 Device to be used for accessing the program................................................................3
4.6 Assumptions............................................................................................................4
4.7 Preconditions...........................................................................................................4
4.8 Authorisation ...........................................................................................................4
4.9 Transaction code definition ........................................................................................4
5 Open points in Business/User specification...............................................................................4
6 Appendix ........................................................................................................................4

Page 1 of 4
1 GENERAL
Apart from the L2 projects (for which Letter of Acceptance is received) the Finance team adds the
following project details in the Annual Planning:

2 BLUEPRINT REFERENCE

3 MASTER DATA REQUIRED

L1, Book & Bill projects are to be created as WBS elements in ERP

4 FUNCTIONAL SPECIFICATION

4.1 Functional Development Description

An input form should allow user to plan data related to L1 and book and bill project on the basis of
different dimension CO.Code/Period/Business Area/Region/Profit Center/WBS/Plant/Currency /Cost
Element. On saving, the data should be written back to the project planning model.

4.2 Input Definition

SL.NO Dimension Description Variable

1 Co. Code Represents the legal entity in BPC X

Represents the individual month. Will be maintained as
MM.YYYY. The report can be executed with a period
dimension member or a hierarchy member. If a hierarchy
2 Period X
member is used, then the columns of the output should
have all the periods that are part of that hierarchy
member
Represents the individual Projects, Factory, SBU &
Corporate Departments. The SBU will be represented as
group of Profit Centers. The report can be executed with
3 Profit Center a Profit Center dimension member or a hierarchy X
member. If a hierarchy member is used, then the rows of
the output should have all the Profit Centers that are part
of that hierarchy member

4 Project Represents the individual project X

Cost Object derived from CPM/PS where Revenue &

Costs are planned at Activity/Material level. The report
can be executed with a WBS dimension member or a
5 WBS X
hierarchy member. If a hierarchy member is used, then
the Rows of the output should have all the WBS Elements
that are part of that hierarchy member

Page 2 of 4
 6 Category Category represent different plan version X

Object Currency & Controlling Area Currency (Object

7 Currency Currency = Co Code Currency). The planning will be done X
in the local/object currency (Company code currency).

Represents the various GL accounts for Revenues and

Costs. The report can be executed with an Account
Account
dimension member or a hierarchy member. If a hierarchy
8 (Cost X
member is used, then the Rows of the output should
Elements)
have all the Cost elements that are part of that hierarchy
member.
9 Value Key Figure representing the Revenue or Costs

4.3 Output definition

Based on the selection of the context:

Header details:

Company code
Category
Currency

Row Dimensions:
Project
WBS Element
Cost Element

Column Dimensions:

Periods

In the Input form, it is also possible to bring the description of the dimension member where necessary.
On saving, the data should be updated back to the ACDOCP.

4.4 User interface

- Excel Sheet

4.5 Device to be used for accessing the program

Page 3 of 4
 4.6 Assumptions

4.7 Preconditions
The L1 projects and the Book and Bill projects are to be created as WBS elements in ERP.

4.8 Authorisation
Authorizations will be provided to the SBU Finance team to update the plan values only
pertaining to the projects / profit centres for which they are responsible.

4.9 Transaction code definition

NA

5 OPEN POINTS IN BUSINESS/USER SPECIFICATION

S.No. Description Responsible Open Date Status

Person

6 APPENDIX

Page 4 of 4