classical report-storage location extract
DESCRIPTION
Classical Report-Storage Location ExtractTRANSCRIPT
SAP Implementation at PIL Report Functional Specification
Functional Specification - Report Storage Location Extract
Document Reference: TBDVersion: 1.0 Document Status: Signed off
Author: Aviroop Deb
Last Revision Date: 22-11-2006Date Created: 22-11-2006Date 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 DateProcess Team Lead
TBD TBD TBD TBD
Development team Lead
TBD TBD TBD TBD
Document History
Version Reason for change Date1.0 Initial Version 22-11-20061.11.21.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........................................................................................................................... 42. BUSINESS NEEDS & REQUIREMENTS........................................................................................................53. ISSUES.................................................................................................................................................... 54. SELECTION SCREEN DETAILS................................................................................................................... 55. CURRENT FUNCTIONALITY........................................................................................................................ 67. TECHNICAL DETAILS................................................................................................................................ 67.1.EXTRACT DATA RELATIONSHIP DIAGRAM..................................................................................................78. STARTING CONDITIONS............................................................................................................................ 79. SECURITY REQUIREMENTS/ AUTHORIZATION DETAILS................................................................................810. DATA MAPPING TABLES........................................................................................................................... 8
10.1. DESIRED REPORT DESIGN/LAYOUT:................................................................................................810.2. REPORT EXAMPLE:........................................................................................................................ 8
11. CUSTOM TABLES/STRUCTURE IN SAP......................................................................................................812. RECOVERY AND RESTART........................................................................................................................ 913. LANGUAGE OF TEXTS............................................................................................................................... 914. CURRENCY AND UNITS OF MEASURE........................................................................................................915. ASSUMPTIONS......................................................................................................................................... 916. ERROR HANDLING................................................................................................................................... 917. Testing Scenarios.................................................................................................................................. 9
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-2006Short description: Storage Location ExtractRequested by: TBD Tel no: TBDAuthor: Aviroop Deb Tel no: TBDProgram Transaction code: ZPPISTORLOCTask ID/Demand Number: TBDProject Name: SAP Implementation at PIL
Priority: High/mandatory Medium/recommended Low/optional
Complexity: High Medium LowVolume of data: Medium DATE AVAILABLE FROM: TBDMode: Online Background
Frequency: Daily Weekly Monthly Biweekly Others (Specify) : On Demand
Technical information:1. Report created using:
2. Characteristics required:
Report Painter Report Writer SAP Query ABAP program Info system R/3 BW Crystal Reports
Drilldown Buttons Sort ALV Grid ALV List Entry file Others: Call Transaction
General information:1. Results if no Reports are
created:
Legal requirements not fulfilled Lack of essential business information Lack of functions compared to legacy system Others (Specify):
DURATION OF DEVELOPMENT WORK (IN MAN-DAYS):
5 days (Coding+Documentation+Testing)
Is there an alternative in the standard system? Yes No
Description of alternative: Reasons why alternative is not acceptable:
Performance problems Complexity 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 & RequirementsPower 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 process2) Establishing an Integrated information repository3) Improvement in the area of Planning4) 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. IssuesNone
Issue #
Issue owner
Date Raised
Issue Description Issue Resolution Resolved By & Date
4. Selection Screen DetailsName Table-Field /
Check Box / Radio Button –
with group
Parameter (P) / Select-option (S)
Comments (Range, Single/Multiple
selection, Patterns, Mandatory etc.)
Default Value
MARC-WERKS
S_WERKS S Range/Optional
Classical Report-Storage Location Extract.doc 22-11-2006 Page 5 of 10
SAP Implementation at PIL Report Functional Specification
Desired screen design (selection possibilities):(Use attachment if necessary):
5. Current Functionality NA
6. Desired FunctionalityThe 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
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
SELECTION SCREEN
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.
SAP Implementation at PIL Report Functional Specification
9. Security Requirements/ Authorization DetailsNone
10. Data Mapping TablesField Name Field Desc Outpu
t Length
Output Type
Format Position SAP screen No./ field name
MARD-LGORT Storage Location
4 Char
MARD-MATNR Material Number
18 Char
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 NameShort textSize categoryTable maintenance allowedData classBufferingTable maintenance generatorAuthorization GroupField Name
Data Element Domain Type Length Check Table-Field
Key Field
Foreign Key
Description
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 textsThe 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 HandlingCheck 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 Description1 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.234Exception - special logic or exceptions (e.g. report shold exclude certain specific condition)
56Error 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