ALV-Material Master Report

SAP Implementation at PIL ALV Report - 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 - ReportMaterial Master Data - Fields Summary

Document Reference: TBD Version: 1.0 Document Status: Signed Off

Author: Sangram Chowdhury

Last Revision Date: 17-Nov-2006Date Created: 17-Nov-2006Date Printed: 17-Nov-2006

ALV-Material Master Report.doc 17-Nov-2006 <Page 1 of 13>


Document Control

Business Area Material Management

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 17-Nov-20061.11.21.3

ALV-Material Master Report.doc 17-Nov-2006 <Page 2 of 13 >


Table of Contents

1. GENERAL INFORMATION.............................................................................................................32. BUSINESS NEEDS & REQUIREMENTS..........................................................................................43. ISSUES......................................................................................................................................54. SELECTION SCREEN DETAILS.....................................................................................................55. CURRENT FUNCTIONALITY..........................................................................................................66. DESIRED FUNCTIONALITY...........................................................................................................67. TECHNICAL DETAILS...................................................................................................................67.1.EXTRACT DATA RELATIONSHIP DIAGRAM....................................................................................68. STARTING CONDITIONS..............................................................................................................79. SECURITY REQUIREMENTS/ AUTHORIZATION DETAILS..................................................................810. DATA MAPPING TABLES.............................................................................................................8

10.1. DESIRED REPORT DESIGN/LAYOUT:.................................................................................1010.2. REPORT EXAMPLE:..........................................................................................................10

11. CUSTOM TABLES/STRUCTURE IN SAP......................................................................................1212. RECOVERY AND RESTART........................................................................................................1213. LANGUAGE OF TEXTS...............................................................................................................1214. CURRENCY AND UNITS OF MEASURE........................................................................................1215. ASSUMPTIONS..........................................................................................................................1216. ERROR HANDLING....................................................................................................................1317. Testing Scenarios..................................................................................................................13



1. General Information

Area (SAP System components): MM Date: 17-Nov-2006

Short description: Material Master Data - Field details

Requested by: TBD Tel no: TBD

Author: Sangram Chowdhury Tel no: TBD

Program Transaction code: YMMDETLREP

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

Frequency: Daily Weekly Monthly Biweekly Others (Specify) :

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



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 process2. Establishing an Integrated information repository3. Improvement in the area of Planning4. Complete visibility of stock

The material master settings establish, in large part, how SAP operates. The settings must be established according to company policy and should be set consistently from site to site. To support an effective and efficient review of these settings among materials and across sites a summary report is required.

This report will allow, via simple excel pivot tables, and audit of thousands of materials quickly to ensure all settings are appropriate. The use of this report will lead to downstream efficiencies because master data accuracy can be routinely assured.

3. Issues

None

Issue #

Issue owner

Date Raised

Issue Description Issue Resolution Resolved By & Date

4. Selection Screen Details

Name Table-Field / Check Box /

Radio Button – with group

Parameter (P) / Select-option (S)

Comments (Range, Single/Multiple

selection, Patterns, Mandatory etc.)

Default Value

Plant Table Field S Single/Multiple Selection



Name Table-Field / Check Box /

Radio Button – with group

Parameter (P) / Select-option (S)

Comments (Range, Single/Multiple

selection, Patterns, Mandatory etc.)

Default Value

Material Type Table Field S Single/Multiple Selection

Material Group Table Field S Single/Multiple Selection

Material Number

Table Field S Single/Multiple Selection

Desired screen design (selection possibilities):(use attachment if necessary):

5. Current Functionality Currently the Material master settings are viewed manually, and all the required fields are not available in a single view. Hence, effective and efficient review of settings among materials and across sites is not possible currently.

6. Desired Functionality

The material master data summary report will simply extract in a user friendly format the key elements from the material master tables. The report will be downloadable into excel. The user will be able to apply either data filters or pivot tables to the data to quickly identify data errors or inconsistencies.

This report is simply an extract of key fields from the material master. Any testing should involve ensuring that the selection criteria are working correctly and that the appropriate fields are being extracted.

7. Technical Details

The Report will be a ALV Grid Report.

The processing logic should be as follows:

Validate selection screen input parameters and issue error message in invalid entries are found.

Select data from MARA, MAKT and MARC and use inner join to make the select efficient. Display information message and exit list processing in case no material data is found as per the selection criteria, specified by the user.

Display output in ALV Grid format, as per details given in Data mapping table.



7.1.Extract Data Relationship Diagram



8. Starting Conditions

To run this report, there are no dependencies, as it directly extracts data from material master tables.

This report will be run on demand and once per week.

9. Security Requirements/ Authorization DetailsNone

10. Data Mapping Tables

Field Name Field Desc. Output Length

Output Type

Format Position SAP screen No./ field name

MARC-WERKS Plant 4 Char Left-Justified

<1>

MARA-MTART Material Type

4 Char Left-Justified

<2>

MARA-MATKL Material Group


<3>

MARA-MATNR Material Number


<4>

MAKT-MAKTX Material Description


<5>

MARC-PRCTR Profit Center 6 Char Left-Justified

<6>

MARC-DISLS Lot Size 8 Char Left-Justified

<7>

MARC-FIXLS Fixed Lot Size

8 Quan Right-Justified

<8> Use Reference field MARA-MEINS

MARC-LOSGR Costing Lot Size



MARC-BESKZ Procurement Type


<10>

MARC-SOBSL Special Procurement


<11>

MARC-DISMM MRP Type 3 Char Left-Justified

<12>

MARC-MINBE Reorder Point



MARC-DISPO MRP Controller


<14>

MARC-FXHOR Plan Time Fence

3 Numc Left-Justified

<15>



Field Name Field Desc. Output Length

Output Type

Format Position SAP screen No./ field name

MARC-PLIFZ Plan Delv. Time

3 Dec Right-Justified

<16>

MARC-AUSS Assembly scrap in percent

3 Dec Right-Justified

<17>

MARC-EISBE Safety Stock 8 Quan Right-Justified


MARC-RWPRO Coverage Profile


<19>

MARC-LVORM Flagged For Deletion


<20>



10.1. Desired Report Design/Layout: The default sequence of output fields should be as per data mapping table. The output list should be SORTED by default first by Plant, then by Material Type, then by Material Group and

then by Material Number. The Quantity fields should be having reference to MARA-MEINS to display the output is correct format for those

fields.

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

ALV-Material Master Report.doc 17-Nov-2006 <Page 10 of 13>


12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123

Program:ZCSRR_009_BACKORDER_COMPLETION_REPORT User : SY_UNAME ABC Plc Backorder Completion Report Date From: 01/10/01Date To: 31/10/01Sales Organisation: 3010 Distribution Channel: 01 Division: 01

Complete Order Customer Sales Document Item Material---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 9900000001 1000000002 10 C2C Pepsi Cola 20 C2C Seven Up 9900000026 1000000015 20 C2C Dr Pepper 9900000128 1000000218 10 C2C Dairy Milk 20 C2C Whole Nut 30 C2C Pepsi Cola 9900000220 1000000056 10 C2C Dr Pepper

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

***End of Report***



11. Custom Tables/Structure in SAPNone

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

The Quantity fields should be having reference to MARA-MEINS to display the output is correct format for those fields.

15. Assumptions



Material Master Data is accurately maintained 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 material 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 material master. 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 should 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 material data could be found according to the selection criteria.


Documents

ALV-Material Master Report