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.........................................................................................................3
4.3 Output definition.......................................................................................................4
4.4 User interface ..........................................................................................................4
4.5 Device to be used for accessing the program................................................................4
4.6 Assumptions............................................................................................................4
4.7 Preconditions...........................................................................................................4
4.8 Authorizations ..........................................................................................................5
4.9 Transaction code definition ........................................................................................5
5 Open points in business/user specification ..........................................................................5
6 Appendix .......................................................................................................................5

Page 1 of 5
1 GENERAL

Engineering master is prepared for each project and contains unique engineering data. The
engineering master data is prepared by Engineering department and is shared with project site.
Based on the engineering department inputs, engineering master data is uploaded for the project.
For the project, engineering master preparation activity is initiated along with the check survey.
At the completion of check survey, engineering master data is revised, if required. Such revisions
are maintained for reference. Engineering master captures quantities based on XXX type, Body
extension and Soil data. It calculates the estimated quantities for excavation, concreting, rebar,
stub setting, backfilling. XXX schedule uses engineering master data as a basis.

2 BLUEPRINT REFERENCE

MRP 01.03

3 MASTER DATA REQUIRED

Project wise Engineering master data from Engineering department will be stored in master
table (Z_PS_ENGMST)

4 FUNCTIONAL SPECIFICATION

4.1 Functional Development Description

Engineering master is a custom program developed for specific business requirement. It will be
project specific and unique to the project. Access to engineering master data will be controlled.

Engineering master custom table - Z_PS_ENGMST.

(This table will be used for storing the data entered by the user)

The following fields will be available in the custom table,

S. No Field Description UoM SAP reference Field format

1 Project Number - PROJ_ PSPID XX-X
2 WBS - PRPS_POSID XX-X--
3 XXX type - ZTWTY XX
4 Body extension - ZEMBDEX
5 Leg A extension - ZLGT1
6 Leg B extension - ZLGT2
7 Leg C extension - ZLGT3
8 Leg D extension - ZLGT4
9 Soil type - ZSOTY
10 Foundation type - ZFDNT XX
11 Excavation volume 1 m3 ZEXC1 .
12 Excavation volume 2 m3 ZEXC2 .
13 Excavation volume 3 m3 ZEXC3 .
14 Excavation volume 4 m3 ZEXC4 .
15 Excavation volume 5 m3 ZEXC5 .
16 Excavation volume 6 m3 ZEXC6 .
17 Excavation volume 7 m3 ZEXC7 .
18 Excavation volume 8 m3 ZEXC8 .
19 Cement bags each ZCMT1 .XX
Page 2 of 5
 20 Concreting type 1 m3 ZCNR1 .
21 Concreting type 2 m3 ZCNR2 .
22 Concreting type 3 m3 ZCNR3 .
23 Concreting type 4 m3 ZCNR4 .
24 Rebar MT ZRBR .
25 Rebar type 1 MT ZRBR1 .
26 Rebar type 2 MT ZRBR2 .
27 Rebar type 3 MT ZRBR3 .
28 Rebar type 4 MT ZRBR4 .
29 Rebar type 5 MT ZRBR5 .
30 Stub setting MT ZSTB1 .
31 Back filling m3 ZBKFL .
32 XXX erection MT ZTRER .
33 Revision number - ZENRV0001 External number range
34 Date - ZDATE System date

X - Alphanumeric

Please maintain “WBS + XXX type + Body extension + Soil type” as a primary key for this custom
table.

The data in this table will be stored project wise. The engineering master data will have version
control. Date and Revision number needs to be stored in the above table.

4.2 Input Definition

For the custom table based report, selection screen will have project ID, Date and Revision number.
Date should be proposed as ‘system date’, assigned by the program automatically. Revision
number should be a running number, assigned by the program automatically.

Submit button will be available for confirming the above data. Once confirmed, user will get an
access to line items.

Input option for excel upload should be provided for uploading the data, directly into custom
table. For both creation and change, one TCODE needs to be created.

Custom transaction will be available for maintaining/uploading the data in Engineering master
for the project.

T-code - ZENGMSTR

In case of creation – Excel upload is mandatory and in case of change only Revision # is
mandatory.

Page 3 of 5
4.3 Output definition

Following screen will appear for the user,

Header table fields

Header table should store following data fields,

1. Project ID
2. Revision Number
3. Date created
4. Date changed
Revision number should be auto-incremented, whenever the engineering master data is
updated for the project.

Date creation should be auto populated, based on the system date and should not be editable.

Changes in the engineering Master should be stored as a revision and date of change should
be stored for reference.

Line items table fields

The line item data entered by the user will be saved in this table. During the data entry, user will
get the following screen with input help (wherever indicated)

Following values will be stored in separate custom table (Search help) and will be available for
the F4 search help.

The output format of the custom report will be as follows,

4.4 User interface

The saved data can be viewed by the user from the table (Z_PS_ENGMST) via ‘display’
transaction.
Please provide upload facility for the user, to upload the engineering master data, from the
excel sheet in the custom table Z_PS_ENGMST.

4.5 Device to be used for accessing the program

Laptops, Desktop

4.6 Assumptions
User will enter/maintain the project wise engineering master data.

4.7 Preconditions
Check survey is initiated
Engineering details are available

Page 4 of 5
 4.8 Authorizations
Authorisation object (PROJ_PRCTR) is required for creating/changing the Engineering
master data and viewing the table data.

4.9 Transaction code definition

Z_ENGMST_CHG (Create/Change Engineering master data)
Z_ENGMST_DSP (Viewing the Engineering master data from the table)

5 OPEN POINTS IN BUSINESS/USER SPECIFICATION

Business to share the engineering master format for Substation, Solar, Civil, Cable. It will be
covered in a separate functional specification document.

6 APPENDIX

Page 5 of 5