alv + badi + bdc - master invoice report

SAP Implementation at PIL ALV+BADI+BDC 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: Harshal Gajare

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

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

SAP Implementation at PIL ALV Report - Functional Specification

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-Master Invoice Report.doc 17-Nov-2006 < of 12 >


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): SD-Billing Date: 03/06/2007

Short description: Master invoicing Report

REQUESTED BY: Tel no:

AUTHOR: Tel no:

Program Transaction code: VF04

Task ID/Demand Number:

Project Name: Power India Limited

Priority: High/mandatory Medium/recommended

Low/optional

Complexity: High Medium Low

Volume of data: DATE AVAILABLE FROM:

Mode: Online Background

Frequency: Daily Weekly Monthly Biweekly Others (Specify) :

Technical information:

1. Type of Enhancement

2.Module /Submodule Information

3.Data Object (Purchase order/sales order etc.)

4. Dependancy on any object

UserExit BADI Requirement routine Custom transaction Business transaction

event Substitution & Validation Others Sap Std program modification

Module SD sub-module Billing

Billing document Creation

Sales orders and Delivery documents

General information:

1. Results if no conversions are created:

Legal requirements not fulfilled Lack of essential business information Lack of functions compared to legacy system Others (Specify):

APPROX. DURATION OF DEVELOPMENT WORK (IN MAN-DAYS):

20 Days

Is there an alternative in the standard system?

Yes No

Description of alternative: None

Reasons why alternative is not acceptable:

Performance problems Complexity Others (Specify) :

Reference Document N/A



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.

In the current NOPS system the users have the ability to create a master invoice for a customer. There are several ways to create this invoice (billing document). One of the ways not supported by SAP is by customer purchase order. This reqirment is in place because orders from Wal-Mart are split durring the EDI process. WalMart sends in an order that is for 100 difrent stores under one purchase order. These orders are split up by the individual ship–to location. They must be combined at the time of billing after they have all shipped.

Within SAP R/3 there is functionality to allow a order to be shipped to multiple locations, however if a sales order comes in with 300-400 line items, each ship-to must have a line item for the qty to be shipped to that location. So if 300 items are to ship to 100 stores the number of line items in the sales order whould be 30,000 lines on one sales order. This is a system issue for the number of items per sales order, and a FI issue for the number of conditions passed to FI. This is also not managable from a customer service point of view. There are also system performace issues with procesing a order of this size as well.

The required business process that needs to be supported is outline in the following flow chart and table:



Processing Steps ( this just spells out the processing steps a user would go through)

Task Description

EDI 850 is received from customer

The EDI 850 transmissions are received from the customer they are processed through the EDI translator.

Split of Orders

When the translator reviews the orders if the 50 is for more then one ship-to locations the orders are split in to individual sales orders. All of these order will be assigned the same customer Purchase order number. These orders are passed to SAP via an IDOC.

IDOCs Created

IDOCs are created for the individual sales orders by ship-to location. These are processed into SAP via the IDOC processing function modules The sales orders also need a flag that they are split orders this will carry through to the WMS systems

Sales Order Processing

Sales orders for the individual ship-to’s will be processed as P1 shipments ( shipments to a customer DC) Standard order processing applies with regard to ATP and Credit processing.

Create Deliveries

ZVL10 (modified VL10I) transaction will be used to create the deliveries. The deliveries will be processed based on the business rules for line fill and dollar fill. Note: there is also a requirement to view deliveries to be created by customer PO this as a selection option in ZVL10.

Create Shipments Shipments will be created with the standard shipment processing

Orders Dropped to the Floor

The shipments created will be dropped to the via the WMS interface programs.

Pick ,Pack, load truck The WMS systems at the sites will responsible for picking, packing and loading the trucks for shipment. This information will be passed back to SAP so the deliveries and shipments can be processed.

When truck leaves

When the driver picks up the load, the shipment start button will be selected and a Post Goods Issue transaction processed. This will allow billing to take place for goods that have been shipped but are not POD (Prof of Delivery) relevant.

Have all deliveries been picked and shipped

Decision is to use current SDO1 transaction to view delivery stat

A selection process is needed that will show the users all deliveries and their statuses so that they can then decide based on that list which deliveries are complete and ready to be master invoiced. The decision has been made to use the standard SDO1 functionality, and to change the associated screen (create a new screen variant) that will show only that information pertinent to the orders and deliveries’ statuses being reviewed.

Orders/deliveries billed

New SAP Transaction

The orders/deliveries that have like Customer Pos will be bill together on one billing document. Note: if there are invoice splits that need to take place for inco terms, payment terms, or others, The invoices will not be combined and will be invoiced separately. There is also the need for orders for these customers will not always be master invoice



customers. Some of the orders will flow though with out master invoicing. This new transaction will prompt only for customer and po.

EDI 810 A EDI 810 will be sent to the customer will all of the Like customer PO numbers on it.

3. Issues

None

Issue #

Issue owner

Date Raised

Issue Description Issue Resolution Resolved By & Date

4. Selection Screen Details

NOTE: Sold-to party and Customer purchase order number should be mandatory fields.

5. Current Functionality In the NOPS systems invoices can be processed and grouped by customer PO number.

6. Desired Functionality

Within SAPR/3 the customers PO number is held on the Sales order (VBKD-BSTKD), this information is changeable and a text field for all practical purposes. This field is NOT passed to a delivery document in field for reference therefore you have nothing to reference the creation of a billing document from the delivery without it.

In order to reference the customers PO number for Delivery related billing the communication structure of the delivery line items must be changed. The change would be to add a field to contain the customers PO number. (VBKD-BSTKD) We also need to add the customer PO number to the additional data tab of the deliveries Item data. Appropriate BADI needs to be found out and implemented here for outbound delivery



Once this field is included with the delivery then the we will select the deliveries for billing that are to be master invoiced.

7. Technical Details

With this selection the program select all ZMI orders for those sold-to customers and purchase orders. Error messages should be displayed if no ZMI order type records are found or if no ZMI order type records are found with deliveries.

After the records have been retrieved, a screen with the below fields needs to be displayed:

<selection/check box>Customer NumberCustomer NamePurchase order numberDelivery NumberShipment NumberDelivery PGI Date

Sort should be by Customer Number, then by Purchase Order Number. This is so that all documents that are to be combined will be grouped together on the display screen.

If a delivery DOES NOT have a PGI date, this line should show in RED so as to catch the user’s attention.

The user will then click on the selection box to the left of the Customer Number field and click on Save. Before the collective billing document is created, you need to first ensure that every line the user has clicked on has a Delivery PGI Date. Display an error if any of the lines the user has selected has not been PGI’d.

At this point, the collective billing document needs to be created for each purchase order/delivery created through VF04 as a BDC . All deliveries selected that share the same purchase order number should be collectively billed.

If the system encounters any errors while creating the billing document it should notify the user attempting to do the collective billing.

7.1.Extract Data Relationship Diagram



8. Starting ConditionsThis report will be run on demand and once Daily

9. Security Requirements/ Authorization DetailsNone

10. Data Mapping Tables



10.1. Desired Report Design/Layout:

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

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


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. AssumptionsSales Data is accurately maintained in the system.



16. Error HandlingCheck for Proper validations and Error conditons.

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.


alv + badi + bdc - master invoice report

Documents