alv - customer purchase order change

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

CUSTOMER PURCHASE ORDER CHANGE

Document Reference: Version: 1.0 Document Status: Signed Off

Author: Nilesh Bhoyar & Vinay Golchha

Last Revision Date: 10 May 2007Date Created: 10 May 2007Date Printed: 10 May 2007

ALV-Material Master Report.doc 17-Nov-2006 < of 11>


Document Control

Business Area Sales and Distribution

GAP ID

FS Definition Form ID

SAP R/3 Version ECC 5.0

Global / Market

Approval and Distribution

Approved by Name Role Signature DateProcess Team Lead

Vinay GolchhaNilesh Bhoyar

10 May 2007

Development Team Lead

Document History

Version Reason for change Date1.0 Initial Version 10 May 20071.11.21.3

ALV-Material Master Report.doc 17-Nov-2006 < of 11 >


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: 10 May 2007

Short description:Customer Purchase Order Change

Requested by: Tel no:

Author:Vinay GolchhaNilesh Bhoyar

Tel no:93719341629881077934

Program Transaction code: ZMMPOCHANGE

Task ID/Demand Number:

Project Name: FAST TRACK

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

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.

Power India Ltd receives Customer POs for multiple Stores. These orders are broken down into sales orders by Store numbers. Power India Ltd has requirement of a screen through which changes can be made to sales order at PO level.- change done in this screen updates all the sales orders belonging to one PO. Functions done thru' this screen are:

a) Remove/set delivery block (change 'problem' flag)b) Change Guarantee (cancel date)c) Change delivery priority (change priority)d) Reject (delete) all open sales orders in a POe) Undelete (remove rejection) deleted orders in a PO

3. Issues

None

Issue #

Issue owner

Date Raised

Issue Description Issue Resolution Resolved By & Date

4. Selection Screen Details



Selection Screen :

A new Custom screen with following fields will be created:

a) Customer (Sold-to) Number (VBAK-KUNNR) single valueb) Customer PO Number (VBAK-BSTNK) single value

Option : Group the following options in radio button

1. Remove/set delivery block (change 'problem' flag)2. Change Guarantee (cancel date)3. Change delivery priority (change priority)4. Reject (delete) all open sales orders in a PO5. Undelete (remove rejection) deleted orders in a PO

Based on the selected radio button , the ALV report will be displayed

5. Current Functionality



6. Desired Functionality

To make changes to sales order at PO level.

Incorporating following functionalities :

a) Remove/set delivery block (change 'problem' flag)b) Change Guarantee (cancel date)c) Change delivery priority (change priority)d) Reject (delete) all open sales orders in a POe) Undelete (remove rejection) deleted orders in a PO

7. Technical Details

The Report will be a ALV Grid Report.

The processing logic should be as follows:

In the selection screen, user will be forced to input at-least one of the selection fields – Customer number or the PO number. User will also be forced to choose one of the 5 options (only one option could be chosen at a time).

Program will select all open sales orders (VBUK-LFGSK ne ‘C’) for a given Customer (Sold-to) and PO number (please note that PO number can be blank also). If no PO number was given in the selection screen, program will group all the sales orders by PO number and Requested Delivery date and will display by PO number and Requested Delivery date. Use the function module for grouping sales orders by Customer PO

Based on the option selected in the initial screen, program will display the field to be changed against the PO. There will be another field (same as the field to be changed) where user can make modification.

User will then make changes to the modifiable field and hit ‘execute’. Program will now show the original value and the modified value for that field. User will now click the save button. This will update the values in all the sales orders (and line

items if applicable). Fields that can be changed are:

o Remove/set delivery block (change 'problem' flag) VBAK-LIFSKo Change Guarantee (cancel date) VBAK-GWLDTo Change delivery priority (change priority) VBAP-LPRIOo Reject (delete) all open sales orders in a PO VBAP-ABGRUo Undelete (remove rejection) deleted orders in a PO VBAP-ABGRU



7.1.Extract Data Relationship Diagram

8. Starting Conditions

9. Security Requirements/ Authorization Details

10. Data Mapping Tables



10.1. Desired Report Design/Layout:

10.2. Report Example:

ALV-Material Master Report.doc 17-Nov-2006 < of 11>


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

13. Language of texts

14. Currency and Units of Measure

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


alv - customer purchase order change

Documents