SAP Implementation at PIL

Smartforms - 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

Purchase Order - Summary

Document Reference: TBD

Version: 1.0
Document Status: Signed off

Author: Gautam

Last Revision Date: 04.12.2006

Date Created: 04.12.2006
Date Printed: 04.12.2006

Smart form PO summary 6/12/2018 <Page 1 of 14>

SAP Implementation at PIL
Smartforms - 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 Name Role Signature Date

Process Team TBD TBD TBD TBD
Lead
Development TBD TBD TBD TBD
Team Lead

Document History

Version Reason for change Date

1.0 Initial Version 30-Nov-2006
1.1
1.2
1.3

Smart form PO summary 6/12/2018 <Page 2 of 14 >

SAP Implementation at PIL
Smartforms - 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..........................................................................................11
8. TRANSLATION...........................................................................................................................11
9. LAYOUT DETAIL........................................................................................................................11
10. CUSTOM TABLES/STRUCTURE IN SAP......................................................................................12
11. ASSUMPTIONS..........................................................................................................................13
12. ERROR HANDLING....................................................................................................................13
13. LANGUAGE OF TEXTS...............................................................................................................13
14. TESTING SCENARIOS................................................................................................................13

Smart form PO summary 6/12/2018 <Page 3 of 14 >

SAP Implementation at PIL
Smartforms - Functional Specification

1. General Information
AREA (SAP SYSTEM MM Date: 30-Nov-2006
COMPONENTS):
Short description: Purchase Order Summary
REQUESTED BY: TBD Tel no: TBD

AUTHOR: Gautam Tel no: TBD

Program Transaction code: YPOSUMM
Task ID/Demand Number: TBD
Project Name: SAP Implementation at PIL
High/mandatory Medium/recommended
Priority:
Low/optional
Complexity: High Medium Low

Volume of data: Medium DATE AVAILABLE TBD

FROM:
Mode: Online Background
Daily Weekly Monthly Biweekly
Frequency:
Others (Specify) :      

Technical information:
Sapcript Smartform Subroutine pool
1. Layout created using:
Text Elements Standard Texts
Text Id Print Program
Legal requirements not fulfilled
General information:
Lack of essential business information
1. Results if no conversions
Lack of functions compared to legacy system
are created:
Others (Specify):      
DURATION OF DEVELOPMENT
WORK 5 days (Coding+Testing)
(IN MAN-DAYS):
Is there an alternative in the
Yes No
standard system?
Description of alternative:      
Reasons why alternative is Performance problems Complexity
not acceptable: Others (Specify) :      

Smart form PO summary 6/12/2018 <Page 4 of 14 >

SAP Implementation at PIL
Smartforms - 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

PIL needs to issue the PO to the appropriate vendor and to hand it over to their representative.
The MM clerk takes the print out of the PO and hands it over to the representative, the process
happens in presence of the representative so as to make minor adjustment in order to make the
process fast and effective. Assuming that the MM clerk knows the PO number whose printout is to be
taken.

Smart form PO summary 6/12/2018 <Page 5 of 14 >

SAP Implementation at PIL
Smartforms - Functional Specification

3. Issues
None

Issue Issue Date Issue Description Issue Resolution Resolved

# owner Raised By & Date

Smart form PO summary 6/12/2018 <Page 6 of 14 >

SAP Implementation at PIL
Smartforms - Functional Specification

4. 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

Smart form PO summary 6/12/2018 <Page 7 of 14 >

SAP Implementation at PIL
Smartforms - Functional Specification

5. Form Layout

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

Layout.xls

Logic for the driver program.

Selection Screen:

Name Table-Field / Parameter (P) / Comments (Range, Default Value

Check Box / Select-option (S) Single/Multiple
Radio Button selection, Patterns,
– with group Mandatory etc.)

Smart form PO summary 6/12/2018 <Page 8 of 14 >

SAP Implementation at PIL
Smartforms - Functional Specification

Purchase Table field P Mandatory None

Order (EKKO-
Number EBELN)

Selection Logic:

Get all fields (*) of DB table EKKO based on the selection screen Purchase Order number
(EBELN), it becomes the interface structure “it_ekko” for the smartform(refered later in the
specification).

Similarly get all the item data from the DB table EKPO based on PO number (EBELN), it
becomes the interface table “it_ekpo” for the smartform(refered later in the specification).

Steps for creating the Object.

1. Create the smart form layout

2. Create the driver program
3. Create a transaction code (YPOSUMM) for the driver program. Please note that if this transaction
code already exists you can create transaction code with any other name.

Flow logic for printing the purchase order summary

1. Execute the transaction created by you.

2. Select the required Purchase Order number.
3. Execute the program,
4. If there is data available for the give selection criteria, then the program will call your smartform.
5. This will bring a popup window asking the printer/output device type ‘LOCL’ and click on print preview
to view the output of your script.

Smart form PO summary 6/12/2018 <Page 9 of 14 >

SAP Implementation at PIL
Smartforms - Functional Specification

6. Technical Details
Layout windows

Reference Print on page Label Position

W1 All Pages Left = 0.5 CM
Top = 0.5 CM
Width = 4.5 CM
Height = 4.5 CM
W2(Address Node) All Pages Left = 15 CM
Top = 0.5 CM
Width = 6 CM
Height = 4.5 CM
W3 First Page Left = 7.5 CM
Top = 1 CM
Width = 6.25 CM
Height = 2 CM
W4(Address Node) All Pages Left = 0.5 CM
Top = 5.5 CM
Width = 6 CM
Height = 2 CM
W5 All Pages Left = 15.2 CM
Top = 5.33 CM
Width = 5.5 CM
Height = 2 CM
W6 All Pages Left = 3.5 CM
Top = 8 CM
Width = 14 CM
Height = 16 CM
W7 All Pages Left = 0.5 CM
Top = 26 CM
Width = 17.2 CM
Height = 3 CM
W8 Last Page Left = 9.5 CM
Top = 24 CM
Width = 8 CM
Height = 1 CM

Field Mapping
The MM Clerk enters the PO number in transaction ‘YPOSUMM’ and the Print Out is generated.

Smart form PO summary 6/12/2018 <Page 10 of 14 >

 SAP Implementation at PIL
Smartforms - Functional Specification

Label Field Field Functionality Logic Print on Font Font Window

Description page Format
Label1 Title Title Title Print All Helv Bold W3 under
‘Purchase Pages e 18 Label1
Order’ as
Heading title.
label2 EKPO- Created by PO creater name Get from All Helv Normal W5 under
ERNAM it_ekpo. Pages e 10 label2
label3 EKPO- Created on Creation Date Get from All Helv Normal W5 under
ERDAT it_ekpo. Pages e 10 label3
label4 EKPO- Material Material No. Get from All Helv Normal W6 under
MATNR Number Displayed it_ekpo. Pages e 10 label4
label4 EKPO- Material Material Grp. Get from All Helv Normal W6 under
MATKL Group Displayed it_ekpo. Pages e 10 label4
label4 MAKT- Material Material Desc. Get from All Helv Normal W6 under
MAKTX Description Displayed Makt table Pages e 10 label4
label5 EKPO- Order Order Quantity Get from All Helv Normal W6 under
MENGE Quantity it_ekpo. Pages e 10 label5
label6 EKPO- Net Price Net Price Get from All Helv Normal W6 under
NETPR it_ekpo. Pages e 10 label6
Label7 Total Total Total Price Add the net Last Helv Normal W8 under
prices to get Page e 10 Label7
total price.
Label8 Page Page No. Page No. Print the All Helv Normal W7 under
No. Page no. in Pages e 10 Label8
format “ 1 of
10”.
Label9 T001- Address Address No. to Get bukrs All W2
ADRNR retrieve the from it_ekpo, Pages (Address
Business then get Node)
Address of the adrnr from
Comp. code T001
Database
Table.
Label10 Compan Company Company Logo Print All W1
y Logo Logo Company Pages
Logo
Label11 LFA1- Address Address No. to Get lifnr from All W4
ADRNR retrieve the it_ekko, then Pages (Address
Business get adrnr Node)
Address of the from LFA1
Vendor Database
Table.

Smart form PO summary 6/12/2018 <Page 11 of 14 >

SAP Implementation at PIL
Smartforms - Functional Specification

7. Standards Texts/Text Modules

Reference Text Print on Label Position Font Output Font

page Format Format

8. Translation

Reference Description of use Description of use Description of use Text Notes

(in Language1) (in Language2) (in Language3) module
Name

9. Layout Detail

Position of Left Margin 0.5 cm

(Specify Unit)
Position of Right Margin 0.5 cm
(Specify Unit)
Position of Logo Given in Layout windows
(Specify Unit)
Logo EnjoySAP
(Specify Logo)
Position of Main Given in Layout windows
Window
(Specify Unit)

Smart form PO summary 6/12/2018 <Page 12 of 14 >

SAP Implementation at PIL
Smartforms - Functional Specification

10. 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 Domain Type Length Check Key Foreign Description
Name Element Table- Field Key
Field

Comments

Smart form PO summary 6/12/2018 <Page 13 of 14 >

SAP Implementation at PIL
Smartforms - Functional Specification

11. Assumptions

The Purchase order is already created in the system and the MM clerk knows the PO number.

12. Error Handling

No Error Handling.

13. Language of texts

English

14. Testing Scenarios

Normal Functionality - test cases that ensure the report functions as it should.
ID Description
1 PO number given then we get the PO summary output in the spool request.
2
3
4
Exception - special logic or exceptions (e.g. report shold exclude certain specific condition)

5
6
Error Handling - functionality in case of errors (e.g. Error Message or Error Log )

7 If the purchase order number is wrong, there should not be any printout.
8

Smart form PO summary 6/12/2018 <Page 14 of 14 >