Sd pragathi template masters

Process code

GFCL-SD-001 Business BlueprintSales & Distribution

Project - Pragathi

Process Owner : D. DAVID GEORGEConsultant (EID) RAJASEKHAR Consultant (CFL) ANANDAN Coreteam Member : KVS CHITTI A. SRINIVASA RAO

Title : Masters Version : 1.0 Date : 29.06.2006

1. BUSINESS PROCESS SCOPE............................................................................................................................................. 10

MAINTENANCE OF MASTERS................................................................................................................................................. 10

2. DESCRIPTION OF BUSINESS PROCESS FLOW............................................................................................................10

1. CUSTOMER MASTER................................................................................................................................................................. 10

3. CLIENT REQUIREMENTS................................................................................................................................................ 18

3.1 PROCESS REQUIREMENTS................................................................................................................................................. 183.2 PRINTING REQUIREMENTS................................................................................................................................................ 183.3 AUTHORIZATION REQUIREMENTS...................................................................................................................................... 183.4 LEGAL REQUIREMENTS.................................................................................................................................................... 183.5 DEVELOPMENT................................................................................................................................................................ 183.6 REPORTING REQUIREMENTS............................................................................................................................................. 183.7 INTERFACE REQUIREMENTS.............................................................................................................................................. 18

4. SPECIFICATION FOR IMPLEMENTATION IN SAP.....................................................................................................19

4.1 DEFINITION OF SAP CONCEPTS........................................................................................................................................ 194.2 MODELING OF CLIENT REQUIREMENTS IN SAP...............................................................................................................19

4.2.1 Organizational elements used..................................................................................................................................... 194.2.2 To-Be process flow description................................................................................................................................... 194.2.3 To-Be process flow chart............................................................................................................................................ 194.2.4 Change management issues........................................................................................................................................ 194.2.5 Requirements mapping............................................................................................................................................... 194.2.5.1 Process.................................................................................................................................................................. 204.2.5.2 Printing.................................................................................................................................................................. 204.2.5.3 Authorization......................................................................................................................................................... 204.2.5.4 Legal...................................................................................................................................................................... 204.2.5.5 Development.......................................................................................................................................................... 204.2.5.6 Reporting............................................................................................................................................................... 204.2.5.7 Interface................................................................................................................................................................. 20

5. REFERENCE........................................................................................................................................................................ 20

6. GAP ANALYSIS................................................................................................................................................................... 20

7. BUSINESS PROCESS APPROVAL.................................................................................................................................... 20

of 14

Process code


Project - Pragathi



1. Business Process Scope

Maintenance of Masters Create > Change > Display

of 14

Process code


Project - Pragathi



2. Description of Business Process Flow

ORGANISATION STRUCTURE

1) Customer Master (V-09)2) Destination Master (VORF)3) Distance Master (Z1DM)4) Freight Master (ZFM)5) Incoterms (FOL/Ex) (SPRO)6) Sales District (SPRO)7) Sales Office (SPRO)8) Sales Group (SPRO)9) Material Master (MM01)10) ADA Master (ZDAT)11) Route Master 12) Plant Master (SPRO)13) Pricing Conditions (VK11)14) WRO Numbers maintenance (ZV06)15) Vendor Master (XK01) 16) Service Master (AC01)

of 14

Process code


Project - Pragathi



1. Customer MasterSold to Party (1400170001)

He is an authorized customer - Legal & Mandatory. A sold to party is responsible for payment of the sale transaction and also

required for effecting Sale and for creation of Sale Order and checking credit limits.

Customer, Sales Officer, RM, Chief Manager (Sales & Mktg) & Vice President (Mktg) are involved.

When the customer approaches the Sales Officer for Dealer Ship, the concerned Sales Officer visits the Customer's Shop and after ascertaining the credentials, recommends for Dealership after fulfilling all the legal formalities and stipulating our terms & conditions as per the agreement. Duly filled in application in all respects, along with the necessary enclosures and Security Deposit is forwarded to VP (Mktg) through RM, after his recommendations. VP (Mktg) then forwards the application to Dy. Manager (Mktg) for further processing to FI Department. On creation of this Customer, exists in the Master.

Number ranges are maintained Sales Organization wise basing on the accounting group. The width is restricted to 10 characters, 1st 4 will be representing Sales Orgn. Next 2 digits will represent District and last 4 digits represent the Customer serial number.

It exists in SAP.

Ship to Party

of 14

Process code


Project - Pragathi



We are not maintaining any separate master for these 3 types of partner functions. Number ranges are also not maintained separately and the Sold to Party only gets reflected in all the 3 partner functions.

Bill to PartyWe are not maintaining any separate master for these 3 types of partner functions. Number ranges are also not maintained separately and the Sold to Party only gets reflected in all the 3 partner functions.

Pay to Party we are not maintaining any separate master for these 3 types of partner functions. Number ranges are also not maintained separately and the Sold to Party only gets reflected in all the 3 partner functions.

Customers pertaining to Sales Organization “9900” (Plant) is being created by Distribution Department.

2. Destination Master (VORF) Mandatory. Physical Location (14170020) Used in Customer, Distances Masters and Shipping Points Mktg. Corp. IT(SD) & Dist is creating destinations (Transport Zones).1st 2 digits denote Sales Orgn, next 2 digits represent district and last 4 digits serial number of the destination.

of 14

Process code


Project - Pragathi



3. Distance Master (Z1DM) Mandatory for FOL. Distance between 2 locations operated for calculation of Freight - FOL Sales / Stock Transfers Maintained by IT (SD) at Corporate Office and Distribution. 1 st 2 digits denote Sales Orgn, next 2 digits represent district and last 4 digits serial number of the destination.

4. Freight Master (ZFM) Mandatory for FOL Deliveries. Used for calculation of freight between 2 locations. After negotiations by Distribution Dept, Finance & RMO, Work Orders are issued to Vendors by Distribution with the approval of competent authority.

The Masters are updated with approved rates & validity period, by Distribution for AP Regions. The same process is adopted at RMOs for OAP Regions. Freight Rate is checked in the Master for a particular slab for a Plant.

5. Incoterms (OVSG) Mode of Sale. Used in Sale Orders. Mandatory. 2 types of Incoterms are operated. (1) Free On Lorry (FOL) from Mfg. Plant (2) Free On Lorry (FOL) & Ex from Rail Head /WH.

In case of FOL the transport contractor nominated will place the truck on behalf of the company, where as in case of EX the customer himself will place the lorry.

of 14

Process code


Project - Pragathi



6. Sales District (OVR0) Geographical Area (1st 2 digits denote Sales Orgn. & 2nd 2 digits denote District. (1418 Rangareddy District of Hyderabad Sales Orgn.) Used in Customer Master. Useful for getting District wise Reports. Mandatory. Maintained by IT(SD)

Dealer codes , destinations are maintained basing on sales district.

7. Sales Office (OVX1) Head Quarter of Marketing Officer. Used in Sale Order. Assigned to Sales Area. This is also 4 digit code 1st 2 digits representing Region. Mandatory. Maintained by IT(SD)

7.a Sales Group Sales group is represented by Sales Officer. Depending on the market requirement one or more sales groups can be attached to one sales office.

of 14

Process code


Project - Pragathi



8. Material Master (MM01) Maintained by Corporate IT (SD) for Traded Fertilizer products only (HAWA) and material assignments to Plant with the approval of Corporate Mktg. Mandatory.

While creating materials “Material pricing group” should be maintained for pricing purpose (Invoice) Screen shots below explain material pricing group.

Material assigned to Plant by Corporate IT (SD)

The “Acct assignment group” will also be maintained for GL a/c.

of 14

Process code


Project - Pragathi



Updation is done according to “account determination procedure” KOFI. Maintained by IT(SD)

9. ADA Master (ZADAT) 5 digit code (1st 2 digits denote Sales Orgn., 3rd Character denote District last 2 digits are Sl.Nos. Entered in Customer Master for GOI reports. Mandatory.

10. Route Master Not following the routes.

of 14

Process code


Project - Pragathi



11. Plant Master (SPRO) Unique Key identifying the Plant. Done by Corporate IT (SD) for RMO, through recommendation of Distribution. Plant used in Business process like creation of Sale Orders & Purchase Orders & SPRO etc., 4 Digit Code in which 1st 2 digits represent Sales Orgn. & Last 2 digits represent serial number upto 99 Nos. Each Plant is treated as a notional customer and attached in the customer field with same Code while creating a Plant Code. Each Plant is attached to respective Business Area.

If the serial no. is above, 99 alpha numeric code is followed.Eg. 31AA (Sales Orgn. (31) Nagpur AA: Nashik Plant

Legal & Mandatory

12. Price Master (VK11) Used for the creation of Orders and billing. Condition created by Corp. IT (SD) and maintained by Corporate Mktg. Mandatory.

Payment Terms(OBB8) Depending on the market situations the management

decides the price terms of the payments for calculation of due date particulars. The terms of payment as applicable from time to time will be intimated to corp IT(SD) for creation of new payment terms.

of 14

Process code


Project - Pragathi



13. WRO Numbers maintenance

Region wise preprinted WRO books with serial numbers starting with sales org. code, with 50 leaves in each book will be issue to Sales officer for raising manual WRO against order booking from. Customers. This will have control on Sale Order to avoid duplication entry in sale order with same WRO Number as system check the manual wro number in table which is maintained in SAP . Maintained by RMOs. Mandatory

The above information will be maintain in SAP, through the T.cods ZV06

In the above screen the numbers will maintain Sales org and sale group wise indicating wro start number and end number.

14. Vendor Master

Vendor Master is centrally maintained by Materials Department & Finance Department. However, the transport vendors related to Distribution Activity alone are created by Distribution Finance.

of 14

Process code


Project - Pragathi



15. Service MasterService Master creation is a one-time job and was done by Corporate Finance initially. However, now service conditions are maintained by Distribution Department and RMOs.

Note approval of Competent Authority is compulsory for creation and maintenance of all masters.

.

3. CLIENT Requirements

3.1 Process Requirements

3.2 Printing requirements No printing is required. Only view of Abap Reports on Screen/Printing.

3.3 Authorization requirements User specific. Eg Creation of Customer for branches: FI and for Sales Orgn.(Plant) by Dist .

3.4 Legal requirements Fertilizer License, Financial Status, Registration under VAT etc. (Dealt in Customer Master creation)

3.5 Development For maintenance of distance “Z1DM” and for maintenance of Freight “ZFM”

3.6 Reporting requirements

3.7 Interface requirements Destination, Distance, Freight, WRO Books, ADA & JDA reports.

of 14

Process code


Project - Pragathi



4. Specification for Implementation in SAPSAP Definitions if applicable

4.1 Definition of SAP conceptsA top level Conceptual Understanding of the relevant SAP Model that would influence the above mentioned Business Process

4.2 Modeling of CLIENT requirements in SAPHow will the CLIENT Requirements gets addressed in the above described SAP model

To be process mapping With reference to AS-IS process, how it will be mapped in SAP Whether all requirements are met in SAP If certain requirements are not met with standard SAP, identify this as GAP To-be Process chart if applicable

4.2.1 Organizational elements used (List the organizational elements proposed to be used during the process. E.g., whether separate company code will be needed for an EOU?)

4.2.2 To-Be process flow description (Describe process flow in To-Be scenario)

4.2.3 To-Be process flow chart

4.2.4 Change management issues(This is for ‘Organization Change Management’ – List the changes identified in the process mapping. E.g. with purchase order release strategy, the document will have to be released in R/3 by the Materials Manager. In AS-IS scenario, the manager used to sign the PO. Releasing the document in the system would be an additional activity)

4.2.5 Requirements mapping (Check whether the requirements listed by client can be mapped in standard SAP. If those are not available in standard SAP, then those are to be listed as ‘Gaps’)

4.2.5.1 Process 4.2.5.2 Printing4.2.5.3 Authorization4.2.5.4 Legal4.2.5.5 Development4.2.5.6 Reporting4.2.5.7 Interface

of 14

Process code


Project - Pragathi



Process No Process DescriptionLinks to CLIENT process If applicable (any external

reference process number, e.g. from ISO/ FDA etc.)

1. Gap Analysis

Gaps Approach**List the requirements which cannot be mapped with standard SAP

**Identify that there is a needed business function that cannot be accommodated by SAP. Mention System modification that needs to be done- at a higher level, any future enhancements which might address the requirement

2. Business Process Approval

By Date Comments

of 14

1. Reference

Sd pragathi template masters

Education

Transcript of Sd pragathi template masters