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............................................................................................................3
4.7 Preconditions...........................................................................................................3
4.8 Authorisation ...........................................................................................................3
4.9 Transaction code definition ........................................................................................3
5 Open points in Business/User specification .........................................................................3
6 Appendix – template for dpr ..............................................................................................3

Page 1 of 3
1 GENERAL
This Activity Master provides the input for DPR
This will not have any input for Transmission Line SBU DPR

2 BLUEPRINT REFERENCE
N/A

3 MASTER DATA REQUIRED

Custom Master data table for Activity and Sub-Activity Master list. For WBS element and project
definition, SAP standard table PRPS & PROJ would be used

4 FUNCTIONAL SPECIFICATION

4.1 Functional Development Description

This activity master table would be given an upload option for user to upload the values into this
custom table. There would a maintenance table for mapping activity and sub activity, which in
turn fetch those activity and sub activity values into this custom transaction as drop down.

This custom transaction is project specific and all the values are stored in backend table for
future analysis on given activity.

Perquisites –
There needs to be a Maintenance table for capturing activity and sub activity
This Maintenance table “ZPS_ACTVTY_NTL” to be created with 2 column Activity and Sub
activity.

Under Sub-Activity (ZSBACTVY), the user will enter the values for activity specific like one
activity would be having many sub-activities
New Fields in table - ZPS_ACTVTY_NTL

Add field SBU & Activity Type

4.2 Input definition

Custom transaction: ZPS_ENG_NTL and database table name: ZPS_ENGNTL

Entry Screen / Selection Screen–

Project Definition – User would search all the available projects for their SBU specific, so the F4
selection should be having the search option by Description, Project number (This project
number search can be of through project coding search eg: SL* or RL*)
The search help for project can be used through table V_PRSMP with field POSTU for description
and table V_PRSMP with field PSPID for project definition search

Validation –

If the user enters project number along with WBS element, there needs to be a validation check
if this WBS element belongs to the same project definition else system should allow.

Once the user enters the project definition through selection screen or entry screen, below given
are the column
Page 2 of 3
 4.3 Output definition

The values entered in this screen would be saved in the background tables for future reference.
This values from this transaction would be fetched as inputs to DPR for NON-TL SBUs

4.4 User interface

-

4.5 Device to be used for accessing the program

4.6 Assumptions
This custom transaction would be used only for EPC project for the purpose of DPR SBU which
are NON_TL

4.7 Preconditions
Activity master should be defined

4.8 Authorisation
Authorization would be created based on the custom transaction to add or delete values

4.9 Transaction code definition

N/A

5 OPEN POINTS IN BUSINESS/USER SPECIFICATION

6 APPENDIX – TEMPLATE FOR DPR

Page 3 of 3