FS

Document Control Information

Document Information

Document Identification

Document Name

Project Name

Global TYPE

Company

Document Author

Document Version

Document Status

Date Released

Document Edit History

Version Date Additions/Modifications Prepared/Revised by

1.0 Click here to enter a Initial Version

date.

Document Review/Approval History

Date Name Organization/Title Comments

Distribution of Final Document

The following people are designated recipients of the last version of this document:

Name Organization/Title

<Name> <Organization/Title>
 Functional Specifications IT PARTNER

Table of Contents

1.1 Overview....................................................................................................................................................... 3
1.2 Business Requirements.............................................................................................................................. 3
1.2.1 Type of RICEF.................................................................................................................................. 3
1.2.2 Comments........................................................................................................................................... 3
1.2.3 Related Documents.......................................................................................................................... 3
1.2.4 User section...................................................................................................................................... 3

2 Functional Specification Details...................................................................4

2.1 Functional Design........................................................................................................................................ 4
2.2 Requirements............................................................................................................................................... 4
2.3 Customizing.................................................................................................................................................. 4
2.4 Impacted Subprocess (es)....................................................................................................................... 4
2.5 Assumptions................................................................................................................................................. 4
2.6 Risks............................................................................................................................................................... 4
2.7 Test Scenario.............................................................................................................................................. 4
2.7.1 Test Scenario / Test data............................................................................................................. 4
3 Operational Considerations.........................................................................6
3.1 Data Source................................................................................................................................................. 6
3.2 Trigger.......................................................................................................................................................... 6
3.3 Dependencies............................................................................................................................................... 6
3.3.1 Environment / Configuration......................................................................................................... 6
3.3.2 Development Dependencies........................................................................................................... 6
3.3.3 Run / Execution Dependencies...................................................................................................... 6
3.3.4 Expected System Load................................................................................................................... 6
4 Detail Specification.................................................................................7
4.1 Detail Design............................................................................................................................................... 7
4.1.1 Existing SAP related details......................................................................................................... 7
4.1.1.1 Similar process.....................................................................................................................................7
4.1.1.2 Data Verification.................................................................................................................................7
4.1.1.3 Selection Screen..................................................................................................................................7
4.1.2 Interface detail............................................................................................................................... 7
4.1.2.1 Source System – Layout...................................................................................................................11
4.1.2.2 Target System – Layout...................................................................................................................11

5 Design Considerations.............................................................................14
5.1 Design Details............................................................................................................................................ 14
5.1.1 Detailed Description...................................................................................................................... 14
5.1.2 Access Method or Path................................................................................................................. 14
5.1.3 Required Custom Table................................................................................................................. 14
5.2 Data Flow.................................................................................................................................................... 14
5.3 Input Parameters...................................................................................................................................... 14
5.3.1 Screen Flow..................................................................................................................................... 14
5.3.2 Screen Layout and Field List....................................................................................................... 14
5.3.2.1 Screen Layout.....................................................................................................................................14

Attachments and Documentation Page 2 of 16

20-Nov-15
 Functional Specifications IT PARTNER

5.3.2.2 Field List...............................................................................................................................................14

5.4 Output Parameter..................................................................................................................................... 14
5.5 Error Handling, Correction and Recovery........................................................................................... 14

6 Security and Controls.............................................................................15

6.1 Security Requirements............................................................................................................................ 15
6.2 Auditing and Control Requirements...................................................................................................... 15
7 Attachments and Documentation.................................................................16

Overview
1.1 Overview

The purpose of this program is to print the WMS pick List for Finish Goods outbound delivery. This
program will display list of Materials of selected deliveries. Printing of Outbound Delivery pick list
can be at Delivery item level.
The pick list quantity will be based on delivery item. A summary sheet of all materials of selected
deliveries will be displayed in the 1st page of Pick List

1.2 Business Requirements

As per the business requirement, Pick List form needs be developed which will capture the list of
Materials and the source bin of each Pick List ID. Respective Outbound Delivery also should be
shown along with Truck details

Business requires a customized Picking list form with enhanced layout and additional information.

Process flow diagram:

Create Sales Create Outbound Print Pick List from

Order delivery Order Outbound Deliveries in
Custom Report

1.2.1 Type of RICEF

Click on the applicable RICEF radio button

Form Report Conversion Interface Enhancement

Attachments and Documentation Page 3 of 16

20-Nov-15
 Functional Specifications IT PARTNER

1.2.2 Comments

NA
1.2.3 Related Documents

NA
1.2.4 User section

NA

Attachments and Documentation Page 4 of 16

20-Nov-15
 Functional Specifications IT PARTNER

2 Functional Specification Details

2.1 Functional Design

A customized Picking List form and print program is required to be created to issue to the
warehouse team for picking the goods. Same pick list form will be used to reprint the Pick List also.
During re print, details like Shipment Number and Truck details will be visible in the form which
won’t be available during first time printing of Pick List.

Initial Pick List form will be generated between TO creation from Outbound Delivery and picking
process.

Re print pick list layout is also similar form which can be generated after Picking process.

The layout of the Pick List form is given in below attachment

Logic for the fields are provided below

1. Delivery Address:

Ship to Party:

Step 1: Pass Delivery Number-VBELN in table LIKP and get the Ship to Party -KUNNR

Step 2: KUNNR (Customer Number) pass it to KNA1 and get the name NAME1 – KNA1

Address Line 1 & Line 2:

Step 1: Pass Delivery Number-VBELN in table LIKP and get the Ship to Party -KUNNR

Step 2: Pass Customer Number- KUNNR in KNA1 table and get address number -ADRNR

Step 3: Pass ADRNR and NATION (V) in ADRC table and get below fields

Street: STREET
Street 1: STR SUPPL1
Street 2: STR SUPPL2
City: CITY1
District: CITY2
Postal Code: POST CODE1
Country: COUNTRY

Attachments and Documentation Page 5 of 16

20-Nov-15
 Functional Specifications IT PARTNER

3. Sold to Party

Step 1: Pass Delivery Number-VBELN in table LIKP and get the Ship to Party - KUNAG

Step 2: Pass above number as KUNNAR in table KNA1 and get the name NAME1 – KNA1

4. Shipment Number

Go to LTAP (Transfer order Item) and pass the TO Number to get the field VBELN – LTAP
(Delivery Number). Pass the Delivery Number VBELN to VTTP (Shipment item table) to get
Shipment Number TKNUM - VTTP.

5. Plant:

Pass TANUM (TO Number) in LTAP table to get Plant- WERKS

6. Storage Location:

Pass TANUM (TO Number) in LTAP table to get Storage Location- LGORT

7. Warehouse Number:

Pass TANUM (TO Number) in LTAP table to get Warehouse Number- LGNUM

8. Picking Date:

Go to LIKP (Delivery Header) and pass VBELN – LIKP and get the Picking date KODAT –
LIKP

(Date format will be based on User profile format)

9. Delivery Date:

Go to LIKP (Delivery Header) and pass VBELN – LIKP and get the Delivery date LFDAT –
LIKP

(Date format will be based on User profile format)

10. Truck No:

Attachments and Documentation Page 6 of 16

20-Nov-15
 Functional Specifications IT PARTNER

Case 1: VBELN has value: Pass TANUM in LTAP and get VBELN. If VBELN is having
value, proceed with below logic

Truck Number will be updated in one of the text ids of Outbound Delivery Header. Use
Function module READ_TEXT to fetch the Truck Number details. Use FM – READ_TEXT to
get the Truck Number from the outbound Delivery header. Text ID for Truck Number is
ZP02

Case 2: VBELN is blank

Step 1: Pass Warehouse Number LGNUM and Transfer Order Number TANUM in table
LTAK and get Material Document number MBLNR and Material document year MJAHR
Step 2: Pass Material Document number MBLNR and Material document year MJAHR in
table MKPF to get Material slip (Vehicle Number) XBLNR

If XBLNR is blank in any of the cases, field must be shown as blank

11. Truck Capacity:

Get the Truck Number as per above logic (10) and pass the field TRUCK_NO in table
ZTAB_T0005 and get the Truck Capacity - TRUCK_CAPACITY

12. Transporter Name:

Get the Truck Number as per above logic and pass the field TRUCK_NO in table
ZTAB_T0005 and get the Transporter Name - TRANSPORTER_NAME

13. Summary Sheet

These details must be fetched from the Pick List Quantities. This is manual calculation logic
which should be added in the logic.
This summary of Materials need to be fetched from the Transfer Orders belong to the
Deliveries which are selected by the user. For example, when user selects 4 outbound
deliveries and click on Print Pick List, system will generate 4 Outbound Deliveries as per the
Materials and quantities of each Outbound Delivery. The logic for the creation of TO will be
1Transfer Order for 1 Delivery Order when user clicks Print Pick List option.
In this summary, the logic should be provided to list out the list of Unique materials and the
quantities and Storage bin etc. details need to be fetched from the TO. There should be a
field with name Total Quantity and this will be the sum of all the quantities of respective
material. Storage Bin will be as per the Transfer Order.
User will select the Outbound Deliveries which are related to same customer. As the
customer shipping address and other customer details are being provided at the Header
level in the Pick List form, system should allow to create multiple TOs for multiple outbound
deliveries when the customer of all the outbound deliveries are same. If the Customer is

Attachments and Documentation Page 7 of 16

20-Nov-15
 Functional Specifications IT PARTNER

different from other Outbound Deliveries which are selected by the user, system should
throw an error messages as “Sold to Party is different for selected Deliveries” for
different Sold to Party and” Ship to Party is different for selected Deliveries” for
different Ship to Party.
The logic in Custom Outbound Delivery Report (WM-R101) is given to generate 1 TO for 1
DO for respective quantity at the time of clicking Print Pick List.
These summary details are only information purpose. Due to this form, picker collects the
materials which are required for respective customer belong to selected deliveries. This
process will simplify the Picking process as Picker brings all the materials to the loading bay.
Then checker will scan respective Delivery number and its model and serial numbers to
confirm the picking process. If the picker (Forklift operator) picks the materials from
different Storage Bins, he/she needs to mention the exact source bin so that Checker will
update the correct Storage Bin during confirmation process.

14. Picklist ID/ Transfer Order Number:

Key input field for the Form. TANUM-LTAP. Pick List ID must be visible as number and Bar
Code- Code 39
VBELN-LTAP = VBELN-LIPS

15. Delivery Number:

Go to LTAP (Transfer order item) and pass TO Number TANUM – LTAP and retrieve
delivery document number VBELN

16. Model or Material:

Pass TO number TANUM in LTAP table and get the Model Number MATNR

MATNR-LTAP = MATNR-VBLNR
Where VBLNR-LTAP = VBLNR-LIPS

17. Material Description:

Get Material Number as per above logic (16) and pass MATNR in MAKT to get the
description MAKTX

18. Quantity:

Pass TO Number-TANUM and Material -MATNR in LTAP table to get the Quantity VSOLA

19. Unit of Measure:

Pass TO Number-TANUM and Material -MATNR in LTAP table to get the UoM ALTME

Attachments and Documentation Page 8 of 16

20-Nov-15
 Functional Specifications IT PARTNER

20. Storage Type:

Pass TO Number-TANUM and Material -MATNR in LTAP table to get the Storage Type
VLTYP

21. Storage Bin:

Pass TO Number-TANUM and Material -MATNR in LTAP table to get the Storage Bin
VLPLA

22. Picked Quantity

This field will be filled manually by the checker so no logic is required

23. Remaining Quantity:

This field will be filled manually by the checker so no logic is required

24. As per the layout, respective boxes need to be hardcoded.

25. As per the layout, respective box needs to be hardcoded.

26. Date printed:

System date at the time of Print needs to be fetched. (Date format will be based on
User profile format)

2.2 Requirements
1) Create a customized Picking list form layout

2) A new print program is created in RICEF object WM-R101 to trigger this form as soon the
TO is created. In custom Outbound delivery report, user selects the list of deliveries
related to same customer and click on Print Pick List. This will trigger TO creation followed
by printing FG Pick List form

2.3 Customizing
No customization required for this interface

2.4 Impacted Sub process(es)

WM-R101_Create TO against Outbound Delivery from Custom Outbound Delivery Report

2.5 Assumptions

Attachments and Documentation Page 9 of 16

20-Nov-15
 Functional Specifications IT PARTNER

 User selects the list of deliveries which are related to same Ship to party as per the code
or delivering address
 Use generates Pick List for the deliveries which are planned for respective truck

2.6 Risks

Without this enhancement, Picking list cannot be printed which means the Picker can’t pick the
consolidated materials which are required for that truck or plan. And also checker uses this form to
complete the Picking process by scanning respective Pick List IDs

2.7 Test Scenario

2.7.1 Test Scenario / Test data

Business Test Conditions

No. Scenario
1 Generate Pick List for
Single Outbound Delivery
2 Generate Pick List for the
selection of Outbound
Deliveries
3 Generate Pick List for the
selection of Outbound
Deliveries
4 Checking Pick List layout
5 Checking Re Print Pick List
Execution Expected result Remarks
Open Custom Outbound System has to create TO in the
Delivery Report and backend and generate Pick List
click on Print Pick List form from the Print Program.
Correct details should be visible in
Pick List form for summary and
individual delivery details
Open Custom Outbound System has to create TO in the
Delivery Report and backend and generate Pick List
click on Print Pick List form from the Print Program.
by selecting Outbound Correct details should be visible in
Deliveries related to Pick List form for summary and
same Ship to Party individual delivery details
Open Custom Outbound System has to given an error
Delivery Report and messages as Ship to Parties are
click on Print Pick List different and it should not create
by selecting Outbound TO and also no Pick List form
Deliveries related to generation
different Ship to
Parties
Open Custom Outbound Correct data need to be visible in
Delivery Report and the Pick List form as per the TO
click on Print Pick List and Delivery
Open Custom Outbound Correct data need to be visible in
Delivery Report and the Pick List form as per the TO
click on Print Pick List and Delivery. Details like Shipment
Number and Truck Details need to
be visible

Attachments and Documentation Page 10 of 16

20-Nov-15
 Functional Specifications IT PARTNER

3 Operational Considerations
3.1 Data Source
Data from ACE System

3.2 Trigger

Tcode for customize report Y0NMM_xxxx

3.3 Dependencies

3.3.1 Environment / Configuration

No Environment or configuration is required.
3.3.2 Development Dependencies
N/A

3.3.3 Run / Execution Dependencies

N/A

3.3.4 Expected System Load

N/A

Attachments and Documentation Page 11 of 16

20-Nov-15
 Functional Specifications IT PARTNER

4 Detail Specification
4.1 Detail Design
4.1.1 Existing SAP related details

4.1.1.1 Similar process

Report Name N/A

Menu Path N/A

Transaction Code N/A

4.1.1.2 Data Verification

Report Name N/A

Menu Path N/A

Transaction Code N/A

4.1.1.3 Selection Screen

NA

4.1.2 Interface detail

Attachments and Documentation Page 12 of 16

20-Nov-15
 Functional Specifications IT PARTNER

5 Design Considerations
5.1 Design Details
5.1.1 Detailed Description

Ztable creation and update :

No Z table is created as the data will be fetched from SAP Standard tables and custom tables
which are created in other RICEF objects

A custom T Code needs to be created to print the form. Input parameters can be TO number
and Delivery Number. TO number is mandatory.

In this case, system can allow to enter only one TO number or delivery number but not multiple
documents

5.1.2 Access Method or Path

Execution:

☒Custom Transaction Code :

☐Menu Path : ________

☐ Standard Transaction Code :

☐Other : _________

5.1.3 Required Custom Table

NA

5.2 Data Flow

5.3 Input Parameters

NA
5.3.1 Screen Flow

NA
5.3.2 Screen Layout and Field List

NA

5.3.2.1 Screen Layout

NA

Attachments and Documentation Page 13 of 16

20-Nov-15
 Functional Specifications IT PARTNER

5.3.2.2 Field List

NA
5.4 Output Parameter

5.5 Error Handling, Correction and Recovery

Attachments and Documentation Page 14 of 16

20-Nov-15
 Functional Specifications IT PARTNER

6 Security and Controls

6.1 Security Requirements

Role Transaction Code(s) Level of Security

TBD TBD

6.2 Auditing and Control Requirements

Attachments and Documentation Page 15 of 16

20-Nov-15
 Functional Specifications IT PARTNER

7 Attachments and Documentation

Attachments and Documentation Page 16 of 16

20-Nov-15