SAP SD VOFM Routines
1. What is requirement routine in pricing?
2. What is alternate condition base value?
3. What is condition base value?
4. In which case we use alternate condition base value.
5. What is alternative condition type in which case we use alternate condition type? What is the purpose of using this?
6. Can any body tell me any difficult pricing procedure?
2. What is alternate condition base value?
3. What is condition base value?
4. In which case we use alternate condition base value.
5. What is alternative condition type in which case we use alternate condition type? What is the purpose of using this?
6. Can any body tell me any difficult pricing procedure?
VOFM ROUTINES IN SALES & DISTRIBUTION
1. Introduction
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.
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.
Section 2 defines how to create a new VOFM routine, in the event that the standard routines do not match the user needs. In the remaining sections, the SAP standard delivered VOFM routines related to Sales & Distribution and Logistics Execution are documented. Starting with Release 4.6A, this documentation is part of the standard product. This paper assumes that the reader has a general understanding of the SD and LES modules in R/3 as well as a working understanding of the condition technique.
2. 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.
3. Scale Base
A scale base formula can be used to alter the value that the system uses to read the scales in a condition record during pricing. In standard pricing, the system will read the scale in a pricing condition record using the quantity, value, weight, etc. of the document depending on the type of scale that has been defined.
Example:
Price Product A
From 0 cases
$50 per case
From 100 cases
$45 per case
From 500 cases
$40 per case
If the customer orders 100 cases of Product A, the system will read the pricing scale using 100 cases and determines the appropriate price, $45 per case. Using a scale base formula, it is possible to alter the value, in our example 100, prior to the scale being read. Scale base formulas are assigned to pricing condition types in R/3 configuration.
When looking at the code for the standard delivered scale base formulas or when writing your own,
XKWERT is the field name that the scale base value should be assigned to.
Following is a description of the scale base formulas delivered in the standard system.
SCALE BASE FORMULA 1: FREE
This is an example of a scale basis formula. It is not currently used.
SCALE BASE FORMULA 23: PARTIAL QUANTITY
The formula '23' sets the whole number part of the value to zero. For example, the value 203.559 would be changed to 0.559. Formula '23' was delivered to support the R/3 delivered condition type KP03 to support mixed pallet surcharges.
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.
3. Scale Base
A scale base formula can be used to alter the value that the system uses to read the scales in a condition record during pricing. In standard pricing, the system will read the scale in a pricing condition record using the quantity, value, weight, etc. of the document depending on the type of scale that has been defined.
Example:
Price Product A
From 0 cases
$50 per case
From 100 cases
$45 per case
From 500 cases
$40 per case
If the customer orders 100 cases of Product A, the system will read the pricing scale using 100 cases and determines the appropriate price, $45 per case. Using a scale base formula, it is possible to alter the value, in our example 100, prior to the scale being read. Scale base formulas are assigned to pricing condition types in R/3 configuration.
When looking at the code for the standard delivered scale base formulas or when writing your own,
XKWERT is the field name that the scale base value should be assigned to.
Following is a description of the scale base formulas delivered in the standard system.
SCALE BASE FORMULA 1: FREE
This is an example of a scale basis formula. It is not currently used.
SCALE BASE FORMULA 23: PARTIAL QUANTITY
The formula '23' sets the whole number part of the value to zero. For example, the value 203.559 would be changed to 0.559. Formula '23' was delivered to support the R/3 delivered condition type KP03 to support mixed pallet surcharges.
No comments:
Post a Comment