SAP SD Pricing VOFM Routines

Transaction VOFM is a tool that was developed in R/3 to facilitate the definition of both SAP delivered as well as customer defined routines/rules used in the system during various business processes. VOFM routines are ABAP code written in Forms. 

VOFM provides the user with the benefit of choosing from one of the standard delivered R/3 routines or writing their own. VOFM is intended for the implementation team when configuring the system. It is not intended for the end user.

VOFM is divided up into four main areas. These include copying requirements, data transfer, requirements, and formulas. This paper will focus on formulas that were delivered by SAP to support the Sales & Distribution (SD) and Logistics Execution (LES) applications. At a high level, formulas are routines that define how a value should be calculated or determined in the R/3 system.

For example, a pricing condition value formula allows the user to define how a specific pricing value should be calculated. Similarly, a rounding rule formula defines how rounding should take place when pricing mass maintenance is performed. Formulas are a powerful tool allowing the user to adjust the way in which the system determines certain values. They can also be used to set certain variables in the coding, or even to call other programs.

Creating a New VOFM Formula

In each area of VOFM, with the exception of Structure of Group Key Formulas, SAP delivers routines using the name space from 1 to 599. SAP customers can create their own VOFM routines using the name space from 600 to 999. With Structure of Group Key Formulas, the SAP name space is 1 to 49, and the customer name space is 50 to 99. To create a new routine, follow these steps:

1. First check to see whether you can use one of the formulas delivered in the standard system.
2. Either overwrite an existing formula or enter a new number on a new line from the customer name space 600 to 999. Also enter a short description of your formula.
3. Program your formula in the ABAP editor.
4. Activate the program.
5. Enter the application if you want to use the formula in a specific application area.
6. Enter your new formula in the appropriate area in customizing. For example, a new pricing condition value formula would be assigned to a condition type or value line in a pricing procedure. As another example, a free goods calculation rule would be assigned to a free goods condition record. New VOFM routines created at a customer site are not overwritten by a software upgrade.

Determination rule in SD

Sales document based on following

Sales area + document type

 Item category determination for Sales document  based on following

Document type+ Item category grp + Usage+Highlevel

Schedule line category determination  based on following

 Item category group Material master + MRP type

Delivery  document determination  based on following

 Delivery document default type attached to  Sales document type

Item category determination for  Delivery document  based on following

Copy form  Sales document or  Delivery document+ Item category grp

Shipping Determination  based on following

Deliver Plant +shipping condition (Customer Master) + Loading group(Matrial Master)

Route determination  based on following

Deliver Plant +shipping condition(CM) + Transport group(MM)+ Transport condition(CM)

Storage location determination  based on following

Shipping point + Delivery plant+ storage  condition

Picking determination  based on following

Shipping point + storage condition(MM)+ Storage rule(MALA)  ( storage rule also assignment to Delivery type)

Packing determination based on following

Package usage

POD  based on following                          

This object use for confirmation of delivery, based on which billing document can create

Billing document determination based on following

 Sales document type is maintained as default type

Account determination based on following 

Sales area + Account grp (CM-Payer)+Account grp(MM)+Account key+ Condition procedure

Business area determination based on following

Plant + item div  / Sales area / Sales org + div + item div

Company code determination based on following

Sales organization uniquely attached to Company code

 Partner determination  based on following

At -Account group level, sales document header level, item level,  sales document delivery level, Shipment level   Billing document level and item level

Plant determination  based on following        

Customer -Plant info record, From customer master SH party, Delivery Plant  from MM

Out put determination  based on following            

Output determination at Sales document level, Delivery level, Billing level

Price determination  based on following

Pricing procedure + Document indicator from Sale document + Pricing indicator from CM

Text determination based on following         

Customer master ( General text, Accounting text, Sales text) 2) Material master text( Sales text or PO text) 3)Inforecord -Material and customer

Ware house determination based on following   

Ware house number + Plant + Storage location

Lean ware house determination  based on following

Lean ware house activate, Plant + storage location + Ware house number

Tax determination  based on following          

Material master tax condition + Ship to party tax condition

Routing determination based on following

Shipping point + Delivery plant + Loading condition+ Shipping condition

Shipping point determination based on following

Delivery plant + loading group shipping condition

Picking determination based on following

Shipping point +loading condition Delivery plant.

Credit check  based on following                                 

Credit check at Sales document level OR  at  Delivery   OR  at Good issue   Risk group at Sales document level and Risk category from CM, Item category  credit check should be activate

Incomplete log based on following 

Incomplete log assign to Status group, which is assign to Sales document, Item category or Schedule line level

Rebate condition setup based on following

customer master billing info checked, Sales organization activate, Billing document activate

Success factor for sap implementing

There are several factor depending upon successful sap implementation .

Most five most important things one should consider before embarking on an implementation.

My top five factors to consider would be:

•  Set up a Project Board
•  Secure the resources
•  Complete the GAP Analysis
•  Cut Over Plans
•  Train the users.

The Project Board

The correct set up and operation of the Project Board in my view is major factor in the Success failure of the project. The Project Board will consist of the stakeholders, key users and the vendor. The Project Board is part of the governance of the project. The Project Board will meet regularly to ensure that the project plans are created and being Executed as planned, moves from stage to stage with all the deliverables being signed off is resourced properly.

The Resources

Three types of resources are absolutely necessary -- end users, change team and technicians.Early involvement by the end users is absolutely necessary, as they will be the ones living with the system for hopefully many years to come. They will want to feel involved in its implementation. Buy in from the end users of the system is absolutely essential if the system is to have a long and stable life in any organisation. The Change Team will identify the gaps between the package and the business requirements, re-engineer some of the businesses process to cope with the package, train the users to ensure implementat ion is smooth as possible into the business.The Technical Team will prepare the systems environment for the package, apply any software fixes from the vendor, implement the  software in the best way possible for the organisation set up and tune the software for the particular technical environment.

GAP Analysis

A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed. In simple terms: Gap means small crack s. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.Actual gap analysis is time consuming and it plays vital role in blue print stage.

Cut Over Plans

Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data,convert and watch for a period after wards to ensure nothing unexpected happens.

Train Users

Well trained users will support and defend the system on site. Unsupported users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the user s master the system early the better.