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.......................................................................................................4
4.4 Input definition .........................................................................................................4
4.5 Output definition.......................................................................................................4
4.6 Input definition .........................................................................................................4
4.7 Input definition .........................................................................................................5
4.8 User interface ..........................................................................................................5
4.9 Device to be used for accessing the program................................................................5
4.10 Assumptions............................................................................................................5
4.11 Preconditions...........................................................................................................5
4.12 Authorisation ...........................................................................................................5
4.13 Transaction code definition ........................................................................................5
5 Open points in Business/User specification .........................................................................5
6 Appendix .......................................................................................................................5

Page 1 of 5
1 GENERAL

2 BLUEPRINT REFERENCE

3 MASTER DATA REQUIRED

4 FUNCTIONAL SPECIFICATION

4.1 Functional Development Description

4.2 Input definition

The user will use the custom transaction code ZPS001 the below screen has to appear

S. No Field Description SAP reference Remarks

BOMQS HEADER Items

1 Project No Mandatory field fetch the data from

ZPP023_T

2 Project type Mandatory Field fetch the data from

ZPP023_T

3 Engg.Cont. Master Auto populate from custom table Project

type master

4 Project Display the data form table

description ZPP023_T_PROJ_MA for field
PROJ_CODE read the description fields
PROJECT_DESCRIP_1,
PROJECT_DESCRIP_2 ,
PROJECT_DESCRIP_3,
PROJECT_DESCRIP_4
5 Type Description Display the data for the type from the
custom table project master

6 REV No Auto populate

7 Created on System date display (auto populated by

the system)
8 Changed on Date System date display (auto populated by
the system)
Page 2 of 5
9 Description Long Text input field has to be provided
ITEM HEADER fields

9 Item No Item No, 1 , 2, 3, etc will be populated by

the system

10 Structure F4 help has to be provided fetch the data

Category from Custom configuration table

11 Description Display the description for the structure

category from the custom configuration
table

12 L2 Qty Numeric entry

ITEM DETAIL Fields

14 Item No Item No, 10,20,30 etc has to be populated

by the system

8 Structure F4 help has to be provided fetch the data

from Custom configuration table

9 Structure Display the description for the structure

Description category from the custom configuration
table

SUB-ITEM Fields

12 Item No Item detail Item No, for Item number 10

above these are the detail items
101,102,103,104 etc has to be populated
by the system

Page 3 of 5
 13 Structure code F4 help should be available for fetch the
data from BOM-Header table

14 Description Fetch from the BOM-Header

15 BOM Status Pass the MATNR obtained above in

MAST table and read STLNR, Pass the
STLNR in table STKO and fetch STLST.
This will be a runtime display field

4.3 Output definition

After maintaining all the data the user will save the screen while saving a running reference number has
to be generated and stored Number format 700000 to 799999.

4.4 Input definition

The user will use ZPS002 to edit the data stored earlier

4.5 Output definition

Fetch the data with respect to Project No. type and BOM-QS No. and display it in the same screen as
input screen

Save the updated/Added/Modified data in the table and maintain the revised data with respect to
revision No. deletion authorization should not be provided. If the user wishes to delete some line
item feasibility to flag it as deleted has to be provided.

In the change mode the user might edit the existing data or Add new data that is the Structure category,
Structure , Structure codes etc , if the user wants to Add the data use the create logic to derive the data
required to create .

4.6 Input definition

Page 4 of 5
The user will use ZPS002 to view the data with the phantom weight (MS and HT) and BNA weight the
user will be able to view the data in Adobe PDF and print it

4.7 Input definition

4.8 User interface

-

4.9 Device to be used for accessing the program

4.10 Assumptions

4.11 Preconditions

4.12 Authorisation

The fields L2 Qty will be maintained by separate department and rest of the data will be
maintained by separate department so authorization control to edit the fields by individual
department has to be in place

4.13 Transaction code definition

5 OPEN POINTS IN BUSINESS/USER SPECIFICATION

Sr. Description Responsible Open Status

No. Person Date

6 APPENDIX

Page 5 of 5