Pricing
SAP SD VOFM Routines
1. What is requirement routine in pricing?
2. What is alternate condition ba value?
3. What is condition ba value?
4. In which ca we u alternate condition ba value.
5. What is alternative condition type in which ca we u alternate condition type? What is the purpo of using this?
6. Can any body tell me any difficult pricing procedure?
VOFM ROUTINES IN SALES & DISTRIBUTION
Table of Contents
1. Introduction
2. Creating a New VOFM Formula
3. Scale Ba
4. Condition Ba Value
5. Condition Value
6. Structure of Group Key
7. Rounding Rule
8. Calculation Rule – Free Goods
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 ud in the system during various business process. VOFM routines are ABAP code written in Forms. VOFM provides the ur with the benefit of choosing from one of the standard delivered R/3 routines or writing their own. VOFM is int
ended for the implementation team when configuring the system. It is not intended for the end ur.
VOFM is divided up into four main areas. The 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 ur 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 ur to adjust the way in which the system determines certain values. They can also be ud to t 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 ur needs. In the remaining ctions, the SAP standard delivered VOFM routines related to Sales & Distribution and Logistics Execution are documented. Starting with Relea 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.
Eddie Mogilevsky, SAP SD Certified Consultant, ilevsky@yahoo.ca, +11-972-5478056491\15
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 the steps:
1. First check to e whether you can u 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 u 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 Ba
A scale ba formula can be ud to alter the value that the system us 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 cas
$50 per ca
From 100 cas
$45 per ca
From 500 cas
生活大爆炸第四季百度影音$40 per ca
If the customer orders 100 cas of Product A, the system will read the pricing scale using 100 cas and determines the appropriate price, $45 per ca. Using a scale ba formula, it is possible to alter the value, in our example 100, prior to the scale being read. Scale ba formulas are assigned to pricing condition types in R/3 configuration.
When looking at the code for the standard delivered scale ba formulas or when writing your own, XKWERT is the field name that the scale ba value should be assigned to.
Following is a description of the scale ba formulas delivered in the standard system.
SCALE BASE FORMULA 1: FREE
This is an example of a scale basis formula. It is not currently ud.
SCALE BASE FORMULA 23: PARTIAL QUANTITY
The formula '23' ts 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.
Example:
A company lls their products in cas. Each of their materials has a conversion factor to pallets. When an order is placed by a customer, the ur would like the system to add up the quantities across items and compute the number of full pallets. If the customer does not order in full pallets, the ur would like to charge
Eddie Mogilevsky, SAP SD Certified Consultant, ilevsky@yahoo.ca, +11-972-5478056492\15
a fixed surcharge of 20 USD. The ur ts up condition type KP03 in the pricing procedure. In customizing for the condition type KP03, the scale ba formula '23' is assigned as well as the group condition flag so that the quantities across order items can be considered. Within the condition records for condition type KP03, the ur maintains a rate of "from 0.001 PAL" a fixed charge of 20 USD. If an order is placed, for example, that is equal to 10.35 pallets; the formula '23' will alter the va
lue to 0.35 and then read the condition record scale. A surcharge of 20 USD would then be applied to the overall sales order.
SCALE BASE FORMULA 43: TAX LICENSE FRANCE
wear是什么意思Formula '43' was delivered to support tax exemption licens in France (R/3 delivered condition type LCFR) where the tax exemption is granted up to a certain invoiced amount. For additional information on tax exemption licens, plea refer to Note 72040.
SCALE BASE FORMULA 202: PRICE-BOOK SCALE
surrenderedThis requirement is ud together with the feature 'Data determination in the access' (delivered with Relea 4.5). In the R/3 delivered system, condition type PBUD can be ud to determine a special scale basis in the pricing procedure. If scale basis formula '202' has been assigned to subquent condition types that appear in the pricing procedure, the system us the special scale basis versus the normal scale basis from the sales document line item. Further information about 'Data determination in the access' can be found in the R/3 Sales & Distribution documentation under the ction titled 'Special pricing functions'.
Example:
A company wishes to define a pricing agreement that specifies that all customers in a certain customer group receive the price associated with ordering 100 cas of product regardless of how many cas are ordered. This involves fixing the scale basis for the customer group for a certain period of time. This can be accomplished by using the ‘Data determination in the access”. A condition type, such as PBUD can be ud to define the fixed scale value of 100 cas. Subquent condition types that should u this fixed value are then assigned scale ba formula ‘202’.
4. Condition Ba Value
Condition ba value formulas can be ud to influence the condition basis to which the pricing condition rate will be applied. In standard pricing, the system will apply the condition rate to the quantity in the sales document. For example, the price determined by the system is $45 per ca for Product A. 100 cas of Product A have been ordered. The system would then multiply $45 times the number of cas of Product A ordered. Using a condition ba value formula, it is possible to alter the condition ba, in our example 100, prior to the calculation taking place. A condition ba value formula is commonly ud to determine the ba for distributing header discounts / surcharges to the sales document line items. A condition ba value formula is assigned to a condition type in the pricing procedure.
When looking at the code for the standard delivered condition ba value formulas or when writing your own, XKWERT is the field name that the condition ba value should be assigned to.
Following is a description of the condition ba value formulas delivered in the standard system.
pins
CONDITION BASE VALUE FORMULA 1: VOLUME
Formula '1' us the volume of the sales document line item as the condition ba value.
Example:
A company regularly applies fixed amount header discounts to a sales order. For example, the ur may apply a fixed discount of 500 USD to the header of the sales order. Fixed header conditions are always distributed across the line items in the document. In this ca, the company would like to distribute the fixed amount
Eddie Mogilevsky, SAP SD Certified Consultant, ilevsky@yahoo.ca, +11-972-5478056493\15
shurebad on the volume of the line items. To accomplish this, the ur would assign condition ba value formula '1' to the header discount condition type in the pricing procedure.
CONDITION BASE VALUE FORMULA 2: NET VALUE
Formula '2' us the net value of the sales document line item as the condition ba value.
Example:
Reference example for formula 1
CONDITION BASE VALUE FORMULA 3: NET PRICE
Formula '3' was delivered to support net price processing. For additional information on the u of this formula along with examples, plea refer to Note 80183.
CONDITION BASE VALUE FORMULA 4: NET VALUE PLUS TAX
Formula '4' us the net value plus tax of the sales document line item as the condition ba value. Example:
Reference example for formula 1
CONDITION BASE VALUE FORMULA 5: KZWI1
Formula '5' us the value determined for subtotal '1' in the pricing procedure as the condition ba value. Example:
A company regularly applies fixed amount header discounts to a sales order. For example, the ur may apply a fixed discount of 500 USD to the header of the sales order. Fixed header conditions are always distributed across the line items in the document. In this ca, the company would like to distribute the fixed amount bad on a subtotal derived bad on certain values in the pricing procedure. The ur has assigned subtotal '1' to the relevant pricing procedure value(s). In addition, the ur would assign condition ba value formula '5' to the header discount condition type in the pricing procedure.
CONDITION BASE VALUE FORMULA 6: KZWI2
Formula '5' us the value determined for subtotal '2' in the pricing procedure as the condition ba value. Example:
Reference example for formula 5
CONDITION BASE VALUE FORMULA 7: KZWI3
Formula '5' us the value determined for subtotal '3' in the pricing procedure as the condition ba value.
Example:
cy
Reference example for formula 5
CONDITION BASE VALUE FORMULA 11: CASH DISCOUNT BASE
杭州翻译公司Formula '11' can be ud with the cash discount condition type. This formula reads the indicator for the company code to determine if the cash discount is bad on the net value of the item. If it is not, then the system bas it off of the net value plus the tax.
CONDITION BASE VALUE FORMULA 12: GROSS WEIGHT
Formula '12' us the gross weight of the sales document line item as the condition ba value. Example:
Reference example for formula 1
Eddie Mogilevsky, SAP SD Certified Consultant, ilevsky@yahoo.ca, +11-972-5478056494\15
CONDITION BASE VALUE FORMULA 13: NET WEIGHT
Formula '13' us the net weight of the sales document line item as the condition ba value.
Example:
Reference example for formula 1
CONDITION BASE VALUE FORMULA 14: SET EXCLUSION INDICATOR
Formula '14' is an example of how a programmer can dynamically t the condition exclusion indicator bad on certain values. This condition exclusion indicator can then be checked in subquent condition ba value formulas (reference formula '15') to exclude certain condition types.
CONDITION BASE VALUE FORMULA 15: CHECK EXCLUSION INDICATOR
Formula '15' is an example of how a programmer can check the value of the condition exclusion indicator and then influence certain values. In this example, if the exclusion field is t to '$', the condition ba value is t to zero and the condition is marked inactive. This example is provided in combination with formula '14' which shows how to dynamically t the condition exclusion indicator.
CONDITION BASE VALUE FORMULA 16: NET VALUE MINUS CASH DISCOUNT
Formula '16' us the net value minus the cash discount value as the ba value. This can, for example, be applied to a tax condition type that should u this value as a basis.
CONDITION BASE VALUE FORMULA 17: NET PRICE
Formula '17' was delivered to support net price processing. For additional information on the u of this formula along with examples, plea refer to Note 80183.
CONDITION BASE VALUE FORMULA 18: NO QUANTITY CONVERSION
Formula '18' is ud to avoid rounding errors that can occur for quantity dependent condition types where the sales unit and the pricing unit are one unit of measure and the ba unit of measure is another. Using formula '18', no conversion is done to ba unit of measure when the sales unit of me
asure and pricing unit of measure are identical.
poor的反义词NOTE: As of Relea 4.0, this formula is no longer necessary. The ur can achieve the same result by tting the "quantity conversion" indicator in condition type configuration.
Example:
A company us KG as their ba unit of measure, but choos to quote prices and ll products in pieces (PC). A quantity conversion has been maintained to indicate that 3 PC correspond to 1 KG. A pricing record has been created to price 1 PC of product at 1 USD. If a customer orders, for example, 1 PC of product, it is possible that the system returns back an item value of 0.999 USD. To avoid this, the ur assigns condition ba value formula '18' to the price condition type as well as other quantity dependent condition types in the pricing procedure.
CONDITION BASE VALUE FORMULA 19: KZWI4
Formula '19' us the value determined for subtotal '4' in the pricing procedure as the condition ba value. Example:
Reference example for formula 5
CONDITION BASE VALUE FORMULA 20: KZWI5
Formula '20' us the value determined for subtotal '5' in the pricing procedure as the condition ba value.
Eddie Mogilevsky, SAP SD Certified Consultant, ilevsky@yahoo.ca, +11-972-5478056495\15
