Page 1 of 7

Document Control information

1. Document reference
ERP-SCM-DES-REP014 KPI Report 100519 v1.0.doc

2. Document type
Functional Specifications

3. Security classification
Restricted – Document Recipients Only

4. Synopsis
This document has been written following functional specifications given by
respective key users and process owners.

5. Document control
Author Change Controller Distribution
Controller

6. Authorisation
Issuing authority Approval authority

Signature Date: Signature Date:

7. Modification history
Version Date Comments
Version 1.0

8. Document distribution list

Authorised Recipients Role / Position

9. References

10. Acknowledgements

Page 2 of 7
Table of Contents

1. OBJECT DOCUMENTATION .........................................................................................................4

2. BUSINESS NEED AND REQUIREMENT........................................................................................4

3. SOLUTION.......................................................................................................................................4
3.1 Tables Access .............................................................................................................................4

Page 3 of 7
 Development Specification - Reports

1. Object Documentation

General Information

Object Identifier
Clear Quest Object Type
Heading (Program ID, Layout
Request (Program, Transaction, Layout Set)
Set ID, etc)

2. Business Need and Requirement

The requirement is to create a query to list a KPI Report.

3. Solution

The query has been created on the 220 client. This query and infoset names are both called ZKPI.

3.1 Tables Access

Currently when running the query, there will be no output as the query done is trying to enter the
same value into two different tables.

The Table that we require are the following:

• QMEL
• QMMA
• AFIH
• ADRC
• ZADRC (Alias if table ADRC)
• AFRU
• ILOA
• ZEAM_WSCEMPLOYEE

The joining of tables table is shown on the next page.

Filename: 43092359.doc
Author: IBM QA
Page 4 of 7
Security Classification: IUBS confidential
Last Updated: 12/10/2010
 Development Specification - Reports

As can be seen above, the tables are joined via their respective fields.

Filename: 43092359.doc
Author: IBM QA
Page 5 of 7
Security Classification: IUBS confidential
Last Updated: 12/10/2010
 Development Specification - Reports

The query should initially start from the table QMEL and the AFRU table. The user may start the search
from one of the following fields:

• QMEL-QMNUM
• QMEL-AUFNR
• AFRU-ISDD
• AFRU-IEDD

The report should first check that when a search input is entered that entries exist in the AFRU table. If no
entries exist for a given order/notification then their respective data should not be displayed in the result of
the report.

The field QMEL-QMCOD is required to be retrieved.

The following fields need to be retrieved from the AFRU table:

• ISDD
• IEDD
• ISMNW

The fields AFRU-GRUND and AFRU-PERNR must then be utilised in the table ZWSC_EMPLOYEE with
fields ZWSC_EMPLOYEE-ZEMPLOYEE= AFRU-PERNR and ZWSC_EMPLOYEE-GRUND= AFRU-
GRUND.

The field ZWSC_EMPLOYEE-NAME is required to be retrieved.

To get the address one of the follow should be done depending on the QMEL-ADRNR field:

1) If the QMEL-ADRNR is fulfilled then the query must get that value and enter the ADRC table
directly with field ZADRC- ADRNR.

The following fields need to be retrieved from the ADRC table:

• CITY1
• POST_CODE1
• STREET
• HOUSE_NUM1
• STR_SUPPL3

2) If QMEL-ADRNR is empty, then the query must grab the value found in QMEL-QMNUM and do
the following
a. Enter the AFIH with field AFIH-QMNUM = QMEL-QMNUM and retrieve the value of the
field AFIH- ILOAN.
b. The query must then enter table ILOA with ILOA-ILOAN=AFIH-ILOAN and retrieve the
value of the field ILOAN- ADRNR
c. Finally the query must enter the table ZADRC with ZADRC- ADRNR = ILOAN- ADRNR.

The following fields need to be retrieved from the ADRC table:

• CITY1
• POST_CODE1
• STREET
• HOUSE_NUM1
• STR_SUPPL3

The field AFIH-ILART is required to be retrieved from the AFIH table.

Next would be to get the information from the tab QMMA. We must enter the table with the following
QMMA-QMNUM = QMEL-QMNUM. The query should only return one value of the field QMMA-MATXT
where QMMA-MNCOD = ‘VAN’.

The following fields need to be retrieved from the ADRC table:

• MNCOD
• MATXT

Filename: 43092359.doc
Author: IBM QA
Page 6 of 7
Security Classification: IUBS confidential
Last Updated: 12/10/2010
 Development Specification - Reports

Below is how the layout of the report should be displayed:

AUFN QMNU ISD IED 1)Total QMCO HOUSE_NUM STR_SUPPL CITY STREE POST_CODE ILAR MNCOD MATX 2)NAME1
R M D D ISMN D 1 3 1 T 1 T T
W

NAME2 NAME3 NAME4 NAME5 NAME6

1) This field should come from summation of the AFRU-ISMNW field. For every entry of that field that is found the addition should be done and the total shown
in the report.
2) This field should come from the ZEAM_WSCEMPLOYEE-NAME field. For every unique record found, an entry must be shown in the report (i.e. first unique
name -> NAME1, second -> NAME2, third -> NAME3, ......, n -> NAMEn

Filename: 43092359.doc
Author: IBM QA
Page 7 of 7
Security Classification: IUBS confidential
Last Updated: 12/10/2010