SAP Implementation at PIL

Report Functional Specification

Functional Specification - Report

Storage Location Extract

Document Reference: TBD

Version: 1.0
Document Status: Signed off

Author: Aviroop Deb

Last Revision Date: 22-11-2006

Date Created: 22-11-2006
Date Printed: 22-11-2006

Classical Report-Storage Location Extract.doc 22-11-2006 Page 1 of 10

 SAP Implementation at PIL
Report Functional Specification

Document Control
Business Area Production Planning

GAP ID TBD

FS Definition Form ID TBD

SAP R/3 Version ECC 5.0

Global / Market 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 22-11-2006
1.1
1.2
1.3

Classical Report-Storage Location Extract.doc 22-11-2006 Page 2 of 10

 SAP Implementation at PIL
Report Functional Specification

Table of Contents

1.GENERAL INFORMATION.............................................................................................................................................................................4
2.BUSINESS NEEDS & REQUIREMENTS............................................................................................................................................................5
3.ISSUES..................................................................................................................................................................................................5
4.SELECTION SCREEN DETAILS......................................................................................................................................................................5
5.CURRENT FUNCTIONALITY .........................................................................................................................................................................6
6.DESIRED FUNCTIONALITY...........................................................................................................................................................................6
7.TECHNICAL DETAILS.................................................................................................................................................................................6
EXTRACT DATA RELATIONSHIP DIAGRAM...........................................................................................................................................................7
8.STARTING CONDITIONS..............................................................................................................................................................................7
9.SECURITY REQUIREMENTS/ AUTHORIZATION DETAILS........................................................................................................................................8
10.DATA MAPPING TABLES..........................................................................................................................................................................8
10.1. DESIRED REPORT DESIGN/LAYOUT: ............................................................................................................................................8
10.2.REPORT EXAMPLE: ..................................................................................................................................................................8
11.CUSTOM TABLES/STRUCTURE IN SAP........................................................................................................................................................9
12.RECOVERY AND RESTART........................................................................................................................................................................9
13.LANGUAGE OF TEXTS..............................................................................................................................................................................9
14.CURRENCY AND UNITS OF MEASURE..........................................................................................................................................................9
15.ASSUMPTIONS.....................................................................................................................................................................................10
16.ERROR HANDLING...............................................................................................................................................................................10
17.TESTING SCENARIOS............................................................................................................................................................................10

Classical Report-Storage Location Extract.doc 22-11-2006 Page 3 of 10

 SAP Implementation at PIL
Report Functional Specification

1. General Information

Area (SAP System components): PP Date: 22-11-2006

Short description: Storage Location Extract
Requested by: TBD Tel no: TBD
Author: Aviroop Deb Tel no: TBD
Program Transaction code: ZPPISTORLOC
Task ID/Demand Number: TBD
Project Name: SAP Implementation at PIL
Priority: High/mandatory ✘ Medium/recommended Low/optional
Complexity: High ✘ Medium Low
Volume of data: Medium DATE AVAILABLE FROM: TBD
Mode: ✘ Online Background
Daily Weekly Monthly Biweekly
Frequency: ✘ Others (Specify) : On Demand

Technical information:
Report Painter Report Writer SAP Query
1. Report created using: ✘ ABAP program Info system
R/3 BW Crystal Reports

Drilldown Buttons Sort

2. Characteristics required:
ALV Grid ALV List
Entry file Others: Call Transaction
Legal requirements not fulfilled
General information: ✘ Lack of essential business information
1. Results if no Reports are
Lack of functions compared to legacy system
created:
Others (Specify):
DURATION OF DEVELOPMENT WORK
5 days (Coding+Documentation+Testing)
(IN MAN-DAYS):
Is there an alternative in the
Yes ✘ No
standard system?
Description of alternative:
Reasons why alternative is not Performance problems Complexity
acceptable: Others (Specify) :

Classical Report-Storage Location Extract.doc 22-11-2006 Page 4 of 10

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

This report should be able to get the required Storage location stock for the concerned plants
and report out the type of stock accordingly as Unrestricted and/or Restricted and/or Quality
inspection and/or Blocked stock. We need to extract only the material stock for which the
quantity is always greater than zero. And in case the Storage location MRP indicator for
Storage locations is set, write it out as Unavailable.

3. Issues
None

Issue Issue Date Issue Description Issue Resolution Resolved

# owner Raised By & Date

4. Selection Screen Details

Name Table-Field / Parameter (P) Comments (Range, Default Value
Check Box / / Select-option Single/Multiple
Radio Button – (S) selection, Patterns,
with group Mandatory etc.)
MARC- S_WERKS S Range/Optional
WERKS

Desired screen design (selection possibilities):

(Use attachment if necessary):

Classical Report-Storage Location Extract.doc 22-11-2006 Page 5 of 10

 SAP Implementation at PIL
Report Functional Specification

5. Current Functionality
NA

6. Desired Functionality
The report should display the storage location stock for the concerned plants and report out the
type of stock.

User should be able to take download in Excel file, Word Doc, HTML format, etc and should
also be able to print the output. Print to be taken in A4 page.

7. Technical Details

The report should be a Classical Report Display.

The processing logic should be as follows:

a) Retrieve the fields MATNR WERKS LGORT KVORM LABST INSME EINME SPEME
DISKZ from the database table MARD for plant = the value of plant provided in the
selection screen. Ensure that the rows retrieved have the value for LVORM = space.
Store the values in an internal table ITAB_MARD.
b) For each of the unique material numbers retrieved in the internal table ITAB_MARD
retrieve the fields MATNR LVORM and MEINS from the database table MARA. Ensure
that the rows retrieved have the value for LVORM = space.
c) For each of the unique material numbers retrieved in the internal table ITAB_MARD
retrieve the fields MATNR LVORM and MEINS from the database table MARC. Ensure
that the rows retrieved have the value for LVORM = space.
d) Get unique materials stored in the ITAB_MARD by plant and Storage Location (LGORT).
Ensure that the values for the fields LABST, INSME, EINME and SPEME are not equal
to Zero.
e) For all the rows in the internal table ITAB_MARD , extract the relevant data . (Refer to
the mapping table)

Classical Report-Storage Location Extract.doc 22-11-2006 Page 6 of 10

 SAP Implementation at PIL
Report Functional Specification

7.1.Extract Data Relationship Diagram

SELECTION

Get Storage Location Data from table MARD

Filter data such that at least one of the Stock

types should have a non-zero value and
Storage location deletion indicator is not set

Get data from table MARA to check Materials

deletion at Client level

Get data from table MARC to check Materials

deletion at Plant level

Pass data to Report.

8. Starting Conditions
To run this report, there are no dependencies, as it directly extracts data from Material
tables.
This report will be run on demand.

Classical Report-Storage Location Extract.doc 22-11-2006 Page 7 of 10

 SAP Implementation at PIL
Report Functional Specification

9. Security Requirements/ Authorization Details

None

10.Data Mapping Tables

Field Name Field Desc Output Output Format Position SAP screen No./ field name
Lengt Type
h
MARD-LGORT Storage 4 Char
Location
MARD-MATNR Material 18 Char
Number

MARD-WERKS Plant 4 Char

MARD-LABST Quantity 15 Quan

10.1. Desired Report Design/Layout:

(use attachment if necessary):

10.2.Report Example:
(use attachment if necessary):

Classical Report-Storage Location Extract.doc 22-11-2006 Page 8 of 10

 SAP Implementation at PIL
Report Functional Specification

11.Custom Tables/Structure in SAP

NONE

Table Name
Short text
Size category
Table maintenance
allowed
Data class
Buffering
Table maintenance
generator
Authorization Group
Field Data Element Domain Type Length Check Key Foreign Description
Name Table- Field Key
Field

Comments

12.Recovery and Restart

If the program fails half way it will not have any impact on any other processes or
programs. It should be simply re-started by the user.

13.Language of texts
The texts for the report should be displayed in User’s logon language. If translation is not
maintained in user’s logon language, he/she should be displayed with English texts.

14.Currency and Units of Measure

NA

Classical Report-Storage Location Extract.doc 22-11-2006 Page 9 of 10

 SAP Implementation at PIL
Report Functional Specification

15.Assumptions
All data are maintained correctly in the system.

16.Error Handling
Check validity of the parameters entered in the Selection Screen, and display error message if
invalid input are made.

Display Information message and leave processing the list, if no data could be found according
to the selection criteria.

17.Testing Scenarios

Normal Functionality - test cases that ensure the report functions as it should.
ID Description
1 This report is simply an extract of key fields from the system. Any testing should involve ensuring
that the selection criteria are working correctly and that the appropriate fields are being extracted.
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 Check validity of the parameters entered in the Selection Screen, and display error message if
invalid input are made
8 Display Information message and leave processing the list, if no data could be found according to
the selection criteria.

Classical Report-Storage Location Extract.doc 22-11-2006 Page 10 of 10