VOFM Scale Base

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:

Scale Price something like this 

if you buy 0 quantity XYZ product - $50 per product 

if you buy 100 quantity XYZ product - $45 per product 

if you buy 500 quantity XYZ product -$40 per product 

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.

Example:

A company sells their products in cases. Each of their materials has a conversion factor to pallets. When an order is placed by a customer, the user 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 user would like to charge a fixed surcharge of 20 USD. The user sets up condition type KP03 in the pricing procedure. In customizing for the condition type KP03, the scale base 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 user 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 value 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

Formula '43' was delivered to support tax exemption licenses in France (R/3 delivered condition type LCFR) where the tax exemption is granted up to a certain invoiced amount.

SCALE BASE FORMULA 202: PRICE-BOOK SCALE

This requirement is used together with the feature 'Data determination in the access' (delivered with Release4.5). In the R/3 delivered system, condition type PBUD can be used to determine a special scale basis in the pricing procedure. If scale basis formula '202' has been assigned to subsequent condition types that appear in the pricing procedure, the system uses the special scale basis versus the normal scale basis from the salesdocument line item. Further information about 'Data determination in the access' can be found in the R/3 Sales& Distribution documentation under the section 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 cases of product regardless of how many cases 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 used todefine the fixed scale value of 100 cases. Subsequent condition types that should use this fixed value are then

assigned scale base formula ‘202’.

Define Rule for Date Determination

This configuration setting enables creation or modification of rules for determining dates in Billing plan. Various Rules are preconfigured in system and can be used for various scenarios. There are three options for configuring new rules: 􀂃 Change existing rule 􀂃 Copy existing rule and change it to new requirements 􀂃 Create a new rule.

You define the rules for date determination on the basis of the following dates: 􀂃 The possible baseline date is predefined by a fixed value range (for example current date, beginning of the contract) and cannot be changed. 􀂃 You can define the period in any way by specifying a number with a corresponding time unit. 􀂃 If you use a calendar ID to define a rule, the system determines the next possible workday starting from the baseline date. If you use a calendar ID, you may NOT specify a period. We will study the configuration of SAP provided rule ’50 – Monthly at end of each month’.

Instructions Follow Menu Path: IMG → Sales and Distribution → Billing → Billing Plan → Define Rules for Determining Dates 1. Click

Here the three options explained in background are applicable. m. If existing Rule is to be modified, choose the Rule from list and click on to get into details n. For copying existing Rule to new one select the Rule to be copied and click on or F6. o. For creating a new Rule click on Here we will follow option ‘a’ and select Rule ‘50’ and click on. To search for Rule click on and enter the key. Following screen is displayed

Maintain the fields as explained below: Field Name Field Description and Value Date Det.rule 2 character code for Indirect rule determination of dates in Billing plan. Here ‘50’ exists in system, for new any two characters can be entered. Description Text description of rule for identification Baseline date This is baseline date from which further dates are calculated. This is predefined in system and following entries exist:

Here ‘07’ is selected Time Period Time Period, which is to be added or subtracted from baseline date, is added here. Time Unit Time Unit of time period defined above Last of Month Last of month switch for date determination Calendar ID If Calendar is to be used to influence date determination, example actual dates in month it has to be entered here. Contract data Used for Contract items where item date has not to be selected from baseline date, but from Header date. Click and back.

Effect of Configuration Rule for date determination are defined to be used in Billing plans.