Document1 Page 1 of 16 Functional Specification

Pangaea Global Phase I

Functional Specification
RP50130__RTC_475_FS_RP_Production_Tracking_Report
 Document1 Page 2 of 16 Functional Specification

Functional Specification

Table of Contents
Objective 3
General Instructions Error! Bookmark not defined.
1. Overview Section 3
2. Change History 3
3. Initial Development Approval 4
4. Business Justification Section 4
5. Definition Section 5
5.1. Definitions, Acronyms, Abbreviations (optional) ......................................................................... 5
5.2. Assumptions .................................................................................................................................. 5
5.3. Business Drivers (Purpose) .......................................................................................................... 5
5.4. Process Description & Scope ........................................................................................................ 5
5.5. LS&CO Print sub processes related to this development (if applicable) ...................................... 5
5.6. Special Requirements.................................................................................................................... 6
5.7. Error Handling .............................................................................................................................. 6
5.8. Dependencies/Prerequisites .......................................................................................................... 6
5.9. Workflow Specifications............................................................................................................... 6
5.10. Other information KPIs (Key Performance Indicators) ................................................................ 7
5.11. Configuration Options................................................................................................................... 7
5.12. Conversions Specifications ........................................................................................................... 7
5.13. Size & perf. specifications ............................................................................................................ 7
5.14. Security specifications .................................................................................................................. 7
5.15. SODs ............................................................................................................................................. 8
6. Report / Form Section 8
6.1. Type of Development.................................................................................................................... 8
6.2. Language support requirements for Forms ................................................................................... 8
6.3. Description .................................................................................................................................... 8
6.4. Selection Screen Reports only ................................................................................................. 10
6.5. Data Selection Reports only (What data should the report select?) ...................................... 10
6.6. Output Layout ............................................................................................................................. 15
6.7. Printing Requirements................................................................................................................. 15
7. Data Mapping 15
8. Unit Testing Requirements 16
Document1 Page 3 of 16 Functional Specification

OBJECTIVE
To design a report that can be used to track the status of all open, cartonized, shipped, close and blocked
purchase orders for direct procurement.

1. OVERVIEW SECTION
Work Stream RTC
RICEFW ID & Description RP50130__RTC_475_FS_RP_Production_Tracking_Report
Functional Team Member Babu Venugopal Extension 1-6803
BSO / Process Team Member Jeannie Young / Simone Demaeyer Extension 1-3890
RIT Team Member
CCF Team Member Extension
Project Manager Jerry Rivera Extension 1-4279
Development Type ( X ) Report ( ) Workflow ( ) Conversion ( ) Enhancement ( ) Form
Priority ( ) High ( X ) Medium ( ) Low
Complexity ( ) Small ( X ) Medium ( ) Large ( ) Extensive

Brief Description To be used for tracking the status of all Direct purchase orders
for Direct procurement.

SAP System(s) R/3

List of Existing Legacy Systems N/A
Involved in this Development Effort

CHANGE HISTORY (To track changes to specification after it has been approved)
Version # Date
Modified
1 10/22/10
2 01/27/2011
3 10/07/2011
4 11/22/2011
Modified By Brief Description of Change
Babu Venugopal Initial Verison
Babu Venugopal Add Stock category field to the selection
and output screen
Mahesh Patil CO15200,
Enhancing the ZPTR to add below,
Delay reason code description, Header text,
Transportation mode on selection screen,
original po qty of all lines of the ouput
layout, Qtyis in number format.
Mahesh Patil CO17522
CO created to fix bug as original po qty on
size level was showing decimals.
On11/30 new change of Shipped untis logic
added, details in the FS.
On12/6 new change of Actual GR untis
logic added, details in the FS
 Document1 Page 4 of 16 Functional Specification

2. INITIAL DEVELOPMENT APPROVAL

Signature Date
Track Lead Neeraj Gupta

Business Lead Ann Tang

Note that all sections must be completed before the Specification will be approved, except those marked as
optional.

3. BUSINESS JUSTIFICATION SECTION

Impact of not creating the program Multiple transactions would need to be used to get the same
information.
Describe the alternatives if applicable: : User would need to look at individual purchase orders, inbound
deliveries, vendor and material masters to access the detailed information contained in the report.

Reason why this alternative was not It is too labor intensive.

acceptable
Document1 Page 5 of 16 Functional Specification

4. DEFINITION SECTION
4.1. Definitions, Acronyms, Abbreviations (optional)
CCI: Cut Complete Indicator
SCI: Ship Complete Indicator
DCI: Delivery Complete Indicator
EXF: Exit Factory

4.2. Assumptions
ZPTR report will execute efficiently and quickly. Report should not time out for normal users, who would request status
reports for up to 1000 purchase orders. Global ZPTR should run faster than LSA version of current report.

4.3. Business Drivers (Purpose)

Users need easy access to the current status of finished goods that have been ordered from suppliers. This
includes planned and actual cut, cartonization, exit factory, shipment and goods receipt data.

4.4. Process Description & Scope

PO Lifecycle:
PO created
PO changed
Inbound delivery created
Inbound delivery changed
Financial ownership
Goods receipt
Invoice received,, do 3 way match, then pay.

4.5. LS&CO Print sub processes related to this development (if applicable)
Document1 Page 6 of 16 Functional Specification

4.6. Special Requirements

System and Security Users that can access this report must be able to display purchase
Authorization orders, deliveries, vendor and material masters.

Control / Audit Processing NA

Archiving NA

4.7. Error Handling

Error Handling

No errors will be generated from an online report. However, it may occur where no data will be generated due to
the selection criteria or data may not exist in the system. The following message should be generated in this
case:

1) selection criteria returned zero results

4.8. Dependencies/Prerequisites
Description Related Document(s)
n/a

4.9. Workflow Specifications

Seq. ID Workflow Name Description
1 n/a
2
3
4
Document1 Page 7 of 16 Functional Specification

4.10. Other information KPIs (Key Performance Indicators)

Processing Mode: ( ) Batch ( X) Real-time
Frequency (if applicable): ( ) Monthly ( ) Weekly ( ) Daily Mo-Fr ( ) Daily Mo-Su
(X ) Other: daily, multiple times ( ) Ad Hoc

Frequency Justification:
Approx. Expected Data
Volume
Estimate 300 users will need to run ZPTR report multiple times a
day to manage 50,000 active POs on any given day.
Estimate globally, there will be 50,000 POs will be checked by
LS&Co staff and Vendors throughout the day. Each report could
range from 1 to 5000 rows of data.

4.11. Configuration Options

Seq. ID Configuration Area IMG Path needs to be specified
1 n/a
2
3
4

4.12. Conversions Specifications

Seq. ID Conversion Name Source Destination Description
1 n/a
2
3
4

4.13. Size & perf. specifications

Seq. ID SAP Benchmark Forecasted Expected records to Peak Volume on
expected # of be converted Black Friday
records
1 1000 adhoc reports 50,000 active
per day POs on any
day.
2
3
4

4.14. Security specifications

User Group Data Approve View Create Maintain Comments
Vendors with POs view no yes no In SNC Cut date, ExFty
Date
Document1 Page 8 of 16 Functional Specification

Product create yes yes yes yes

Management
Man Ops view no yes no no
LS&Co staff view no yes no no

4.15. SODs
Seq. ID SOD
1 Each Vendor will see only see PO data issued to them and will not be able to see
other vendors POs. Vendor will see ZPTR via SNC.
2
3
4

5. REPORT / FORM SECTION

Name of Report/Form: RP50130 Production Tracking Report
Type: (X ) Report ( ) Form

5.1. Type of Development

( ) Modification of Standard SAP Report/Form Name of Standard Report/Form:

( X) Custom Report/Form Are there some similar standard Reports/Form?

5.2. FCLanguage support requirements for Forms

Languages required for Form:
5.3. Description
Explain the following:
The report will use a custom Z transaction code
The report should be in an ALV Grid Display (Including sort orders, sums, subtotals, totals, specifics on
how it differs from SAP report)
The report should be able to display corresponding purchase order (ME23N) when clicked on a
particular row.
The report has the archiving functionality where we would be able to select the archive check box and
see the past records/transactions.
The report displays the Vendor Part number if it is maintained in the purchase info record.
The report can also run if you know the IBD and Shipment Number.

Note:
The ship units in the report should be taken from LIPS-LFIMG instead of LIPS-ORMNG
Ship To Country Field Logic: Req1: For all Third Party POs the content of the above fields will be as
per the present functionality (ie., taken from Sales Oder)
Document1 Page 9 of 16 Functional Specification

Req2: For all Non-Third Party - Samples POs" created for Plant 2001 (LSUS HQ),
( The Ship - To fields will show Address data from the Delivery Address Tab of the PO Line as per
the Data Mapping. The Sold - To fields will show Address data of the Plant of the PO Line.)
Req 3: For all "Non-Third Party - Samples POs" created for Plants OTHER THAN 2001, the content of
the above fields will be blanks.
Business Driver for the above requirements: This data needs to be visible to help Finance manage
accruals for samples shipped to any Plant 2001 locations and to help PM insure they can validate they
have created Samples PO's for each relevant location.

Tables:
EKKO PO Header
EKPO PO Line Item
LIPS Outbound/Inbound Delivery Item Detail
LIKP Outbound/Inbound Delivery Header

Document Type:
Purchase Orders will have the following document types

Document types Description

Direct Purchase order

ZDIR
Includes 3rd Party PO; Purchase to Order PO; Subcontracting

ZQPO Quick PO
ZWRP Warp PO
ZEXR External Rework PO
ZITC Intercompany PO
ZGIC GTC Intercompany PO
ZITS Intercompany Stock Transport Order
ZRAW Fabrics/Sundries PO
ZDEV Developments & sample yardage
ZFOD Framework PO Direct FO for Bulk & Commitment Liabilities
UB Stock Transport Order
Document1 Page 10 of 16 Functional Specification

5.4. Selection Screen Reports only

(Specify fields for selection and what checks are needed after the user had entered his or her criteria)

Refer the attached spreadsheet for the selection screen details

Selection Screen
Layout for ZPTR_RP50130.xlsx

Version 3 CO15200 Enhancing the ZPTR

Selection screen sheet updated for addition of new field Transportation mode

5.5. Data Selection Reports only (What data should the report select?)
The report will give all the Purchase Orders based on the selection criteria above. The date range is mandatory
so the user does not forget to enter a range, in the future the report might take too long to execute if the user
forgets to enter the date.

The following selectiong fields are mandatory to run the ZPTR report, 1. Plant, 2. Purchasing Org, 3. Company
Code, and 4. Purchasing Group. Purchasing Org will be prepopulated globally but Company code should not be
prepopulated for global SAP.

Data:
Purchase orders have header and item details. The header table, EKKO, will supply information on creation date
of the PO. The item table, EKPO, will provide receiving plant information, material number, and the line item
number.

Using the header and line item detail will enable searches on delivery information.

The breakdown will be as follows:

EKKO Table:
Creation Date lookup
Purchasing group lookup
Vendor lookup

EKPO Table:
Material Number lookup
Receiving Plant lookup

LIKP Table:
CARTS Shipment number

LIPS Table
Inbound delivery number (PO reference is on this table)
Document1 Page 11 of 16 Functional Specification

Use the fields in the selection criteria to gather the basic list then use the PO numbers and get the inbound
deliveries from LIPS. The LIPS table has fields VGBEL and VGPOS that reference PO number (from EKKO)
and PO line item (from EKPO).

Status should be a the following status 1 Open, 2 Closed, 3 Cancelled or All.

1 Open - PO is created and no delivery has been issued (delivery could be created no GI posted)
2 Cartonized - this status from CARTS
3 Shipment this status from CARTS
4 Closed - PO has been received at the receiving plant (G/R posted)
5 Cancelled - PO has been cancelled
6 Blocked PO has been Blocked -pending Release by Approver/ s (NOTE: Displaying the Blocked

Status of a PO is to be provided only in SAP ZPTR and NOT in the SNC - Supplier Web ZPTR. The
business does NOT want the Vendors who will access the SAP POs via Supplier Web to see whether a
PO is Blocked OR not approved. So the Selection screen in Supplier Web will NOT have this check
Box)

The ZPTR output should show the Unit of Measure for Prepacks and its corresponding conversion
Units. i.e if qty in uom as CAR and the corresponding number of EAs for 1 CAR.
This conversion factor should come from the Purchase Order and NOT from the Material Master.
A column "Hot Shipment" should appear in the Production Tracking Report.

When the trailer closure comes from CARTs to SAP, the inbound delivery qty of an open size gets
changed to 0 and the confirmation line item goes away from the PO. Due to this the ZPTR shows
Shipment number and Shipped qty as blank. The requirement is that since shipment is already sent by
CARTS earlier, the Shipment number & Shipped units should still be shown. This can be done as
below, Map the Shipped units to LIPS-ORMNG (Original delivery qty) & the Shipment number to
LIKP-VERUR. For shipment number the logic needs to be changed as currently it looks for only
confirmed items and gives the Shipment number. By doing this change the existing functionality to
compute and display the report field-values for fields "Shipped Units", "Actual GR Units", "Due In
Qty", & "Missing GR Units" should not be affected. (Additional changes requested by business based
on a scenario where the Shipment record was getting removed from the Po line item detail as a result of
a trailer closure at WMS and subsequent GR posting when the inbound IT20 file was processed.)
.
Enhance the Original PO Quantity to only print on one line item (recommend line item 010) and do not show
original PO quantity on all other line items of same PO. There should only be one Original PO Quantity per overall
PO, should NOT show on other line items 020, 030, etc.

When reporting in Excel format, the ZPTR needs to maintain consistent formatting. For example all quantities and
numbers should show as numbers, not as text and numbers.

On sample POs (ZSAM) will bring in the Bill of Lading data from the PO. This Bill of Lading data
should interface from CARTS into the SAP Sample POs, after Vendor ships samples.

To efficiently work with the Global Trading Company, we need the following related
purchase orders, STOs and purchase requisitions added to the ZPTR report For any PO if
there is a PR and STO exist it should list it in this format PR PO STO. Also we would
like to display ATP PR created in affiliate plant listed in the output screen.
Document1 Page 12 of 16 Functional Specification

Financial Ownership Date: Currently we get the value from table LIKP-ZZFO_DATE field.
This should be changed to table LIKP-XABLN (Format YYYYMMDD)

PO Grouping Number (Both in Selection and Output Screen)

Logic: Concatenate Original Ex factor date + Material Number ZZEXFDATE+MATNR

Shipment Event and Event Date: These two fields should be removed from the report.

Two new fields should be added in the Selection Screen

Field Name: ZZEXFDATE

Description: Original Ex-Factory Date
Table Name: EKKO

Field Name: J_3ADAT or EEIND

Description: Delivery Date (Actual Ex-Factory Date)
Table Name:EKPO or RMO6E

Version 2 Changes:
Add Stock category field both in selection and output screen.
Field Name: J_4KSCAT
Description: Stock category on item level
Table Name: EKPO
Selection Screen: Add it next to the document type (2nd filed from the top)
Output screen: Add it anywhere.

Make Sales organization and Distribution Channel Mandatory only for Third party PO Details
tab and move those two field down the screen as it was before.
Change the current logic of Actual ex-factory date in the output screen to get the
value(source) from the below field.
Field Name: DPREG
Description: Planned date of check in
Table Name: VTTK
Link: PO has Inbound delivery and Inbound delivery has shipment.
3 Scenarios:
a. If there is no shipment exist then the actual ex-factory date should come from the PO
b. If the shipment exists then it should come from the shipment.
c. If the shipment exist and no date appear then the value comes from the PO itself.

Version 3 CO15200 Enhancing the ZPTR

1. Adding Delay Reason code description on the report layout

Document1 Page 13 of 16 Functional Specification

Delay Reason Code description = ZTGLBRTC_DELAY_C-ZZDESCRI, data type = CHAR &

length = 25 needs to be added to the Report output layout only
Logic to extract the same:
For a particular PO from the selection screen, check if the Delay code (EKPO-ZZDEL_CODE) is
populated. If EKPO-ZZDEL_CODE has values then go to table ZTGLBRTC_DELAY_C and
pick the Delay Reason Code description (ZTGLBRTC_DELAY_C-ZZDESCRI) and output the
same on the report output. If the Delay code on the PO is blank then the Delay Reason Code
description on the Report output should also be blank.

2. Adding Header text on the report layout

Header Text Text id F01, data type = CHAR & length = 50, Add to the Report output layout
only
Logic to extract the same:
For a particular PO from the selection screen, check if the Header text is populated. Use funtion
module READ_TEXT, input id = F01, language = EN, name (PO number) = EKKO-EBELN,
Object = EKKO execute and the result TDLINE needs to be outputted on the report layout. If the
PO Header text field is blank then the Header text on report should also be blank.

3. Add transportation mode in the Production Tracking selection screen

Mode of transportation = EKPO-TSBED; Add to the selection screen layout only as this is
existing in report layout.
Logic to extract the same:
Find the POs based on the mode of transportation (EKPO-TSBED) as search criteria and report
out these POs only. If the search criteria has more than mode of transportation, then accordingly
the POs needs to be outputted for the slection criteria.

4. Displaying original qty field on all the lines with different statuses for a particular PO in the report
layout
Currently the original PO qty field (EKPO-ZZPO_QTY) is appearing only on the first line of the
PO report output which shows the different lines based on the statuses like Open, Cartonized,
Shipment, Closed etc..If there are multiple line for the different statuses, then the Original PO qty
field should be displayed from the EKPO-ZZPO_QTY on all the lines and not only on the first
line. This will result in duplication however this is a business requirement so that when the user
ouputs the report, he/she will do some macro formula in the Excel to extract the unique original po
qty.

5. Quantity /unit are in correct format.

All the quantity fields (*MENGE) outppted on the report output layout like original po qty;
Shipped qty; Actual GRunits; Missing Receipt units & Due In should be displayed in number
format without any decimals and not as text to allow the data to be calculated in SAP or after
converted to excel spreadsheet.

Important Note:
Document1 Page 14 of 16 Functional Specification

All the above changes to the ZPTR vide this CO15200 would impact SNC since SNC does an RFC
call from SAP for this ZPTR report. So on the SNC side these changes needs to be incorporated and
thouroughly tested to ensure that SNC ZPTR report also shows the same output as the SAP.

Version 4 CO17522 Fix the Org qty at size bug, excel output & change logic of shipped units

This CO was initially created to fix incident 375775 where the zPTR showed decimals on the
original po qty field at size level.

On 11/30/2011 following changes added,

Shipped Units on the ZPTR output
When the report is run at item level Change logic of this field output to report value which is the sum
of ZTGLBRTC_HU_DATA (Shipment Reconcilliation - Additional HU Data) -VEMNG (Base
Quantity Packed in the Handling Unit Item) for combination of for EBELN & EBELP as provided on
the ZPTR selection
When the report is run at size level Change logic of this field output to report value which is the sum
of ZTGLBRTC_HU_DATA (Shipment Reconcilliation - Additional HU Data) -VEMNG (Base
Quantity Packed in the Handling Unit Item) for the respective sizes J_3ASIZE (Grid Value) under
combination of EBELN & EBELP as provided on the ZPTR selection

On12/06/2011, following changes added,

Actual GR units on the ZPTR output

The logic of this field should be same as that used in the shipment dashboard Actual Receipt quantity.
Please refer the enhancement ZGLBRTCEN50124_SHIPMENT_DB.
When the report is run at item level Change logic of this field output to report value is the sum of
VEPO-VEMNG (Base Quantity Packed in the Handling Unit Item)
For the PO number (EKES-EBELN), PO item number (EKES-EBELP) & Confirmation Category
(EKES-EBTYP) = LA get the inbound delivery number (EKES-VBELN) & inbound delivery item
number (EKES-EBELP). For item level this item number would be always < 900000. Then go to
VEPO table and for the VBELN Delivery & POSNR Delivery Item get the summation of the
quantities VEPO- VEMNG and report out as Actual GR units for the PO number in the selection.

When the report is run at size level Change logic of this field output to report value is the sum of
VEPO-VEMNG (Base Quantity Packed in the Handling Unit Item).
For the PO number (EKES-EBELN), PO item number (EKES-EBELP), Grid Value (J_3ASIZE) &
Confirmation Category (EKES-EBTYP) = LA get the inbound delivery number (EKES-VBELN) &
inboun delivery item number (EKES-EBELP). For Size level execution the size (grid value) would be
always > 900000. Then go to VEPO table and for the VBELN Delivery & POSNR Delivery Item get
the summation of the quantities VEPO- VEMNG and report out as Actual GR units for the PO number
in the selection.
When the report is run at size level Change logic of this field output to report value is the sum of
VEPO-VEMNG (Base Quantity Packed in the Handling Unit Item).
Document1 Page 15 of 16 Functional Specification

Alternatively the inbound delivery information can be extracted from LIPS table as well. The inbound
delivery number (LIPS- VBELN) & inbound delivery item number (LIPS- POSNR) for the Purchase
order number (LIPS-VGBEL) & Purchase order item (LIPS-VGPOS)

End of CO17522

5.6. Output Layout

Attach a mock up version of the output (MS Excel or MS Word format).

ZPTR_Output
Layout.xls

Indicate the SAP Layout Set, Output Type, and Print Program.
Indicate any special characteristics e.g. for reports the totals/subtotals, sorting

The Header should state:

Production Tracking Report

Layout
Standard R/3 ALV grid

Version 3 CO15200 Enhancing the ZPTR

Added Delay Reason Description & Header Text field on the report output layput

5.7. Printing Requirements

NA
Users will be able to setup variants of the report in SAP that can be exported to Excel.

6. DATA MAPPING

Use the attached Excel Data Mapping template to specify the following:
Table, Field, Field description
Any formatting requirements
Where on the form/report is this field used

Data Mapping
 Document1 Page 16 of 16 Functional Specification

Version 3 CO15200 Enhancing the ZPTR

Added Delay Reason Description & Header Text field in the data mapping

7. UNIT TESTING REQUIREMENTS

UTC

Version 3 CO15200 Enhancing the ZPTR

Unit test script updated for the CO15200

Note that the Actual results will not be tracked here, in the Functional spec.