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............................................................ Error! Bookmark not defined.
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 Authorizations ..........................................................................................................3
4.9 Transaction code definition ........................................................................................3
5 Open points in business/user specification ............................... Error! Bookmark not defined.
6 Appendix ............................................................................ Error! Bookmark not defined.

Page 1 of 3
1 GENERAL

In EPC, execution oriented project structures are used for project management. The project
structures are mainly divided in three heads, Supply, Bough out & Construction. During the project
execution, work is executed based on BOQ quantity, against these heads. The project invoicing is
done based on executed quantity. Executed quantity is used for generating unbilled revenue,
which eventually gets invoiced & revenue is realised. Hence, it is important to monitor the
unbilled revenue and its conversion to billed revenue.

In case of EPC, based on project structure, the unbilled revenue is generated from three heads,
Supply, Bought outs and Construction. The unbilled revenue for Supply and Bough out is handled
in SD, as a part of custom development. This functional specification deals with unbilled revenue
generated out of Construction head.

In Construction, the executed quantity is entered in a custom development, namely, Service

register. Input for invoicing for the work executed under Construction head, is generated from
Service register. The unbilled revenue for the work executed under Construction head shall be
based on Service register.

Note

Unbilled Revenue Functional Specification is split into two sections

1. Unbilled Revenue for Construction services: FS by PS module, data source from Service
Register. (Refer PS FS No: FS_PS-006_Unbilled Revenue Construction)

2. Unbilled Revenue for Supplies & Bought Out: Attached FS, data source is Sales Transactions.
(Refer FS No: FS_SD-021_Unbilled Revenue BOI & FGS)

# Unbilled revenue custom development should have a single custom transaction code for both
of above mentioned sections
# Report layout is common for both the functional specification documents.

2 BLUEPRINT REFERENCE

MRP 07.07

3 MASTER DATA REQUIRED

Service register custom table (ZPS005_T_ITEMDET)

4 FUNCTIONAL SPECIFICATION

4.1 Functional Development Description

Unbilled revenue custom program will calculate and display the unbilled revenue details (read,
construction) for the project, against the WBS elements. The custom report output will be
generated in the form of prescribed format and will be available to the users, based on
authorisation.
Page 2 of 3
4.2 Input Definition

The unbilled revenue report will be generated on run time, based on service register data. The
report will have following selection criteria,

1. Project Number (Multiple selection – From – To)

2. Sales organisation (Multiple selection – From – To)
3. Distribution channel (Multiple selection – From – To)
4. Division (Multiple selection – From – To)
5. Plant (Single entry)

Either the “Project Number” or “Sales organization” field should be mandatory.

For “Project” field, wild card search (example, TL*) should be permitted by the program.
Also, all the projects having system status “CLSD” (JEST_STAT= I0046) should be excluded
from the selection.

Logic – Pass the PROJ_PSPID as OBJNR in JEST table, to get the STAT value. It should not be
equal to I0046 & I0001.
(The above selection criteria are also mentioned in the report output file, attached in the output
section 4.3)

Submit button will be available for confirming the selection screen data, entered by the user.
Once confirmed, user will get an access to the report.

Common custom transaction will be available for displaying the data for Unbilled revenue for
the project.

4.3 User interface

The saved data can be viewed by the user from the report (ZUBRC) via ‘display’ transaction.

4.4 Device to be used for accessing the program

Laptops, Desktop

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

4.6 Preconditions
Service register is updated with data

4.7 Authorizations
Authorisation object (PROJ_PRCTR) is required for displaying the unbilled revenue report
data

4.8 Transaction code definition

ZUBRC (Display unbilled revenue report)

Page 3 of 3