SAP Implementation at PIL

SAP Script - Functional Specification

Note: As this is a case study that simulates a real life development object, some fields will be marked as
TBD and highlighted in Blue. These fields should be having real values, in customer development
specifications.

Functional Specification - Forms

Picking List

Document Reference:
Version:
Document Status:

TBD
1.0
Signed off

Author:

Gautam

Last Revision Date:

Date Created:
Date Printed:

22.01.2007
22.01.2007
22.01.2007

Picking List

3/16/2015

<Page 1 of 13>

SAP Implementation at PIL

Picking List - Functional Specification

Document Control
Business Area

Material Management

GAP ID

TBD

FS Definition Form ID

TBD

SAP R/3 Version

ECC 5.0

Location / Site

TBD

Approval and Distribution

Approved by
Process Team
Lead
Development
Team Lead

Name
TBD

Role
TBD

Signature
TBD

Date
TBD

TBD

TBD

TBD

TBD

Document History
Version
1.0
1.1
1.2
1.3

<File name>

Reason for change

Initial Version

Date
22-Jan-2006

3/16/2015

<Page 2 of 13 >

SAP Implementation at PIL

Picking List - Functional Specification

Table of Contents
1. GENERAL INFORMATION.................................................................................................4
2. BUSINESS NEEDS & REQUIREMENTS.............................................................................5
3. ISSUES......................................................................................................................... 6
4. SAP SCRIPT/FORMS.....................................................................................................7
4.1 CURRENT FUNCTIONALITY.............................................................................................7
4.2 PRINTING EXISTING SOLUTION.......................................................................................7
4.3 DESIRED FUNCTIONALITY.............................................................................................. 7
4.4 CUSTOMIZING REQUIREMENTS.......................................................................................7
5. FORM LAYOUT.............................................................................................................. 8
6. TECHNICAL DETAILS......................................................................................................9
LAYOUT WINDOWS.........................................................................................................9
FIELD MAPPING............................................................................................................ 9
7. STANDARDS TEXTS/TEXT MODULES.............................................................................10
8. TRANSLATION..............................................................................................................10
9. LAYOUT DETAIL...........................................................................................................10
10. CUSTOM TABLES/STRUCTURE IN SAP..........................................................................11
11. ASSUMPTIONS.............................................................................................................12
12. ERROR HANDLING.......................................................................................................12
13. LANGUAGE OF TEXTS.................................................................................................. 12
14. TESTING SCENARIOS...................................................................................................12

<File name>

3/16/2015

<Page 3 of 13 >

SAP Implementation at PIL

Picking List - Functional Specification

1. General Information
AREA (SAP SYSTEM
COMPONENTS):
Short description:

SD

REQUESTED BY:
AUTHOR:
Program Transaction code:
Task ID/Demand Number:
Project Name:

Date:

22-JAN-2007

TBD

Tel no:

TBD

Gautam

Tel no:

TBD

Picking List

YPLIST
TBD
SAP Implementation at PIL

Complexity:

High/mandatory
Low/optional
High

Volume of data:

Medium

Priority:

Mode:
Frequency:
Technical information:
1. Layout created using:

General information:
1. Results if no conversions
are created:
DURATION OF
WORK

Medium

Low

DATE AVAILABLE
TBD
FROM:
Online
Background
Daily
Weekly
Monthly
Biweekly
Others (Specify) :

Sapcript
Smartform
Subroutine pool
Text Elements
Standard Texts
Text Id
Print Program
Legal requirements not fulfilled
Lack of essential business information
Lack of functions compared to legacy system
Others (Specify):

DEVELOPMENT

(IN MAN-DAYS):
Is there an alternative in the
standard system?
Description of alternative:
Reasons why alternative is
not acceptable:

<File name>

Medium/recommended

5 days (Coding+Testing)

Yes

No

Performance problems
Others (Specify) :

3/16/2015

Complexity

<Page 4 of 13 >

SAP Implementation at PIL

Picking List - Functional Specification

2. Business Needs & Requirements

Power India Limited started its operation in the year 1965. From its humble beginning in a small
town of Maharashtra called Ranjangaon PIL has achieved several milestones and today it is one
of the largest manufactures of storage batteries in India. Currently the company is having seven
production facilities in India namely Ranjangaon, Pune, Nashik, Chennai, Hosur, Gurgaon and
Durgapur respectively.
Power India Limited, the flagship company of the Oscar group is the market leader in the
storage battery industry. It manufactures wide range of batteries from 2 Ah capacities to 10500
Ah to cover the broadest spectrum of applications.
The SAP Implementation at Power India Limited (PIL) will achieve the following:
1. Standardize and streamline the business process
2. Establishing an Integrated information repository
3. Improvement in the area of Planning
4. Complete visibility of stock
Picking Lists are internal documents used to assist the picker with details of the order
requirements. They contain information such as delivery address, storage bin, material
reference and quantity and are printed when the picking operation is performed in delivery
notes, which have previously been created with reference to a sales order.
This process has a requirement to create a form for Picking List outputs that can be used by all
the business units. The SD clerk will enter the Warehouse number and the Transfer Order
Number and then the program will trigger the output.

<File name>

3/16/2015

<Page 5 of 13 >

SAP Implementation at PIL

Picking List - Functional Specification

Issues
None
Issue
#

Issue
owner

<File name>

Date
Raised

Issue Description

3/16/2015

Issue Resolution

Resolved
By & Date

<Page 6 of 13 >

SAP Implementation at PIL

Picking List - Functional Specification

3. SAP Script/Forms
4.1

Current Functionality

Output type
Program Name
Layout Form Name
IMG path to access output type
and layout set assignment
Type of solution (Standard R/3,
custom ABAP)

4.2

Printing Existing Solution

Menu Path for transaction:

Values to be used and output
type:
Actions to be taken:

4.3

Desired Functionality

Output type(s):
Form Types:
Transmission medium:
Legal requirements:
Type of printer:
Paper Size:
Orientation: Portrait/Landscape:
Special stationary to be used:

4.4

Customizing requirements

The functional consultant will customize the following output types:

Output type
Program Name
Layout Form Names
Development system

<File name>

3/16/2015

<Page 7 of 13 >

SAP Implementation at PIL

Picking List - Functional Specification

4. Form Layout
Refer to the following for an output samples for Window mapping, Label Description and Field
mapping.

Layout_Trans ferOrd
er.xls

Selection Screen:
Name

Warehouse

Table-Field /
Check Box /
Radio Button
with group
Table field

Parameter (P) /
Select-option (S)

Default Value

Comments (Range,
Single/Multiple
selection, Patterns,
Mandatory etc.)
Mandatory

Mandatory

None

None

(LTAK-LGNUM)
Transfer
Order
Number

Table field
(LTAK-TANUM)

Selection Logic:
The data extraction logic is maintained under the Section 5, Field-Mapping, also.
1. Get Transfer Order(TO) header data, from DB table LTAK based on Warehouse and Transfer Order
Number as entered on the selection screen.
2. Get Transfer Order(TO) item data, from DB table LTAP based on Warehouse and Transfer Order
Number as entered on the selection screen.
3. Get the Sales Order Number from VBFA, and address detail of the Ship-To Party from ADRC.
4. Start the Form and write the header info detail, main window header data, and then loop at item data
and to write the corresponding element. Finally close the script.

5. Technical Details
Layout windows

<File name>

3/16/2015

<Page 8 of 13 >

SAP Implementation at PIL

Window
W1
W2
W3
W4
W5
W6

Print On Pages
All Pages
All Pages
All Pages
All Pages
All Pages
All Pages

Picking List - Functional Specification

Meaning
Company Logo
Header Info Window
Title Window
Deliver To Window
Main Window
Footer Window

Left Margin
0,50 CM
12,50 CM
7,00 CM
0,50 CM
1,50 CM
1,00 CM

Upper Margin
1,50 CM
1,50 CM
1,50 CM
5,50 CM
9,50 CM
27,00 CM

Width
Height
5,50 CM 3,00 CM
7,50 CM 4,00 CM
5,00 CM 1,50 CM
9,00 CM 3,50 CM
18,00 CM 16,00 CM
19,00 CM 1,50 CM

Field Mapping
The SD clerk enters the Warehouse number and Transfer Order Number in transaction YPLIST and the
Print Out is generated.

Label

Field

Field
Description

Functionality

Logic

Print
on
page

Font

Font
Format

Window

Label 1

Title

Title

Title

All
Pages

Helve
20

Bold

W3

l Label 2

& LTAKTANUM &

Transfer
Order

Transfer Order

Print PICKING
LIST as
Heading title.
Get from LTAK.

All
Pages

Helve
12

Normal

W2

l Label 3

& LIKPLFDAT &

Picking Date

Picking Date

To find the
relevant delivery in
table LIKP use the
delivery number
from LTAKVBELN.

All
Pages

Helve
12

Normal

W2

Label 4

& VBFAVBELV&

Sales Order

Sales Order

Get from VBFA

using VBELN =
LTAK-TANUM.

All
Pages

Helve
12

Normal

W2

Label 5

&LIKPKUNNR&

Ship-To Party

Ship-To Party

Get from LIKP

All
Pages

Helve
12

Normal

W2

Label 6

&LTAPVLPLA&

Storage Bin

Storage Bin

Get LTAP

data
using warehouse
number and
Transfer Order
number as entered
on the selection
screen.

All
Pages

Helve
10

W5

Label 7

&LTAPMATNR&

Material
Number

Material Number

Get LTAP

All
Pages

Helve 10

W5

<File name>

using
VBELN=LTAKVBELN.

data
using warehouse
number and
Transfer Order
number as entered
on the selection
screen..

3/16/2015

<Page 9 of 13 >

SAP Implementation at PIL

Label 8

Label 9

Label
10

Label
11

&LTAPMAKTX&

Material
Description

Material
Description

Get LTAP data

&LTAPVSOLM&

Quantity

Quantity

&LTAPMEINS&

Unit of issue

&PAGE&

Label 12

Label 13

Picking List - Functional Specification

&SAPSCR
IPTFORMPA
GES&
Delivery to
address

All
Pages

Helve
10

Normal

W5

Get LTAP

data
using warehouse
number and
Transfer Order
number as entered
on the selection
screen.

All
Pages

Helve
10

Normal

W5

UOI

Get LTAP

data
using warehouse
number and
Transfer Order
number as entered
on the selection
screen.

All
Pages

Helve
10

Normal

W5

Page no.

Page no.

Current Page
No.

All
Pages

Helve
12

Normal

W6

Total Pages.

Total Pages.

Total Form
pages.

All
Pages

Helve
12

Normal

W6

Delivery to
address

Ship-to-Party
Address

Get KUNNR
from VBFA,
then from
KNA1 get the
ADRNR to get
address details
from ADRC.
Print

All
Pages

Helve
12

Normal

W4

using warehouse
number and
Transfer Order
number as entered
on the selection
screen.

ADRC-NAME1
ADRC-STREET
ADRC-CITY1
ADRCPOST_CODE1

<File name>

3/16/2015

<Page 10 of 13 >

SAP Implementation at PIL

Picking List - Functional Specification

Standards Texts/Text Modules

Reference

Text

Print on
page

Label Position

Font

Output
Format

Font
Format

6. Translation
Reference

Description of use
(in Language1)

Description of use
(in Language2)

Description of use
(in Language3)

Text
module
Name

Notes

7. Layout Detail
Position of Left Margin
(Specify Unit)
Position of Right Margin
(Specify Unit)
Position of Logo
(Specify Unit)
Logo
(Specify Logo)
Position of Main
Window
(Specify Unit)

<File name>

0.5 cm
0.5 cm
Given in Layout windows
EnjoySAP
Given in Layout windows

3/16/2015

<Page 11 of 13 >

SAP Implementation at PIL

Picking List - Functional Specification

8. Custom Tables/Structure in SAP

Not Applicable

Table Name
Short text
Size category
Table maintenance
allowed
Data class
Buffering
Table maintenance
generator
Authorization Group
Field
Data
Name
Element

Domain Type

Length Check
TableField

Key
Field

Foreign Description
Key

Comments

<File name>

3/16/2015

<Page 12 of 13 >

SAP Implementation at PIL

Picking List - Functional Specification

9. Assumptions
The Transfer order exists in the system.

10. Error Handling

Check whether TO (Transfer Order) exists for the selection screen values from LTAK, if not found display
an error message.

11. Language of texts

English

12. Testing Scenarios

Normal Functionality - test cases that ensure the report functions, as it should.
ID Description
1
Transfer Order issued and then we get the output in spool request.
2
3
4
Exception - special logic or exceptions (e.g. report should exclude certain specific condition)
5
6
Error Handling - functionality in case of errors (e.g. Error Message or Error Log )
7

<File name>

3/16/2015

<Page 13 of 13 >