You are on page 1of 13

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:
Version:
Document Status:

TBD
1.0
Signed off

Author:

Gautam

Last Revision Date:


Date Created:
Date Printed:

04.12.2006
04.12.2006
04.12.2006

Smart form PO summary

11/8/2014

<Page 1 of 13>

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

Reason for change


Initial Version

Smart form PO summary

Date
30-Nov-2006

11/8/2014

<Page 2 of 13 >

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

11/8/2014

<Page 3 of 13 >

SAP Implementation at PIL

1.

Smartforms - Functional Specification

General Information

AREA (SAP SYSTEM


COMPONENTS):
Short description:

MM

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

Date:

30-Nov-2006

TBD

Tel no:

TBD

Gautam

Tel no:

TBD

Purchase Order Summary

YPOSUMM
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/recommended
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:

Smart form PO summary

5 days (Coding+Testing)

Yes

No

Performance problems
Others (Specify) :

11/8/2014

Complexity

<Page 4 of 13 >

SAP Implementation at PIL

2.

Smartforms - Functional Specification

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

11/8/2014

<Page 5 of 13 >

SAP Implementation at PIL

3.

Smartforms - Functional Specification

Issues

None
Issue
#

Issue
owner

Date
Raised

Smart form PO summary

Issue Description

11/8/2014

Issue Resolution

Resolved
By & Date

<Page 6 of 13 >

SAP Implementation at PIL

4.

Smartforms - Functional Specification

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

11/8/2014

<Page 7 of 13 >

SAP Implementation at PIL

5.

Smartforms - Functional Specification

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

Purchase
Order
Number

Table-Field /
Check Box /
Radio Button
with group
Table field
(EKKOEBELN)

Parameter (P) /
Select-option (S)
P

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

Default Value

None

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

11/8/2014

<Page 8 of 13 >

SAP Implementation at PIL

6.

Smartforms - Functional Specification

Technical Details

Layout windows
Reference

Print on page

Label Position

W1

All Pages

W2(Address Node)

All Pages

W3

First Page

W4(Address Node)

All Pages

W5

All Pages

W6

All Pages

W7

All Pages

W8

Last Page

Left = 0.5 CM
Top = 0.5 CM
Width = 4.5 CM
Height = 4.5 CM
Left = 15 CM
Top = 0.5 CM
Width = 6 CM
Height = 4.5 CM
Left = 7.5 CM
Top = 1 CM
Width = 6.25 CM
Height = 2 CM
Left = 0.5 CM
Top = 5.5 CM
Width = 6 CM
Height = 2 CM
Left = 15.2 CM
Top = 5.33 CM
Width = 5.5 CM
Height = 2 CM
Left = 3.5 CM
Top = 8 CM
Width = 14 CM
Height = 16 CM
Left = 0.5 CM
Top = 26 CM
Width = 17.2 CM
Height = 3 CM
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

11/8/2014

<Page 9 of 13 >

SAP Implementation at PIL

Smartforms - Functional Specification

Label
Refere
nces

Field

Field
Description

Functionality

Logic

Print on
page

Font

Font
Format

Window

Label1

Title

Title

Title

All
Pages

Helv
e 18

Bold

W3 under
Label1

label2

EKPOERNAM

Created by

PO creater name

Print
Purchase
Order as
Heading title.
Get from
it_ekpo.

All
Pages

Helv
e 10

Normal

W5 under
label2

label3

EKPOERDAT

Created on

Creation Date

Get from
it_ekpo.

All
Pages

Helv
e 10

Normal

W5 under
label3

label4

EKPOMATNR

Material
Number

Material No.
Displayed

Get from
it_ekpo.

All
Pages

Helv
e 10

Normal

W6 under
label4

label4

EKPOMATKL

Material
Group

Material Grp.
Displayed

Get from
it_ekpo.

All
Pages

Helv
e 10

Normal

W6 under
label4

label4

MAKTMAKTX

Material
Description

Material Desc.
Displayed

Get from
Makt table

All
Pages

Helv
e 10

Normal

W6 under
label4

label5

EKPOMENGE

Order
Quantity

Order Quantity

Get from
it_ekpo.

All
Pages

Helv
e 10

Normal

W6 under
label5

label6

EKPONETPR

Net Price

Net Price

Get from
it_ekpo.

All
Pages

Helv
e 10

Normal

W6 under
label6

Label7

Total

Total

Total Price

Last
Page

Helv
e 10

Normal

W8 under
Label7

Label8

Page
No.

Page No.

Page No.

All
Pages

Helv
e 10

Normal

W7 under
Label8

Label9

T001ADRNR

Address

Address No. to
retrieve the
Business
Address of the
Comp. code

Label10

Compan
y Logo

Company
Logo

Company Logo

Label11

LFA1ADRNR

Address

Address No. to
retrieve the
Business
Address of the
Vendor

Add the net


prices to get
total price.
Print the
Page no. in
format 1 of
10.
Get bukrs
from it_ekpo,
then get
adrnr from
T001
Database
Table.
Print
Company
Logo
Get lifnr from
it_ekko, then
get adrnr
from LFA1
Database
Table.

Smart form PO summary

11/8/2014

All
Pages

W2
(Address
Node)

All
Pages

W1

All
Pages

W4
(Address
Node)

<Page 10 of 13 >

SAP Implementation at PIL

7.

Standards Texts/Text Modules

Reference

8.

Text

Print on
page

Label Position

Font

Output
Format

Font
Format

Translation

Reference

9.

Smartforms - Functional Specification

Description of use
(in Language1)

Description of use
(in Language2)

Description of use
(in Language3)

Text
module
Name

Notes

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)

Smart form PO summary

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

11/8/2014

<Page 11 of 13 >

SAP Implementation at PIL

10. Custom

Smartforms - Functional Specification

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

Smart form PO summary

11/8/2014

<Page 12 of 13 >

SAP Implementation at PIL

11.

Smartforms - Functional Specification

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.

Smart form PO summary

11/8/2014

<Page 13 of 13 >