Kontakt

Ansicht
Dokumentation

WLF_SD_PRICE_PRO - Define Pricing Procedures

WLF_SD_PRICE_PRO - Define Pricing Procedures

Vendor Master (General Section)   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Set the calculation schema for purchasing.

In this step, you define the calculation schemas.

In the MM area, a calculation schema - a framework of steps used to calculate or determine something - is used among other things to calculate costs, prices, period-end rebates, and taxes.

Note
This concept is referred to in the Sales and Distribution (SD) area as a pricing procedure.

In the calculation schema (pricing procedure), you specify which condition types are to be taken into account in which sequence.
In the price (or cost) determination process, the SAP System automatically determines which calculation schema is valid for a business transaction and takes into account, one after another, the condition types it contains.

The determination of the procedure depends on how you configure the following:

Set Pricing Procedures

You create new pricing procedures, for example, by copying a similar pricing procedure. In addition, you can change or delete your own pricing procedure. You can change a pricing procedure to a main procedure or a subprocedure by using condition types that have been defined as inclusion points:

  • If you add an inclusion point to a pricing procedure, the pricing procedure becomes a main procedure.

  • If you assign an inclusion point to a pricing procedure, the pricing procedure becomes a subprocedure.

Set Customer Pricing Procedures

You specify the customer pricing procedure in the customer master record for each sales area.

Note: You can delete your own customer pricing procedure only, if it is not allocated in the Set Pricing Procedure Determination step.

Set Document Pricing Procedure

You specify the document pricing procedure for each sales document type and billing type.

Assign Document Pricing Procedure to Order Types

Assign Document Pricing Procedure to Billing Types

Set Pricing Procedure Determination

You specify how the system determines pricing procedures for sales documents every time you create a new pricing procedure.

To determine the procedure, you allocate the customer pricing procedure and the document pricing procedure to a pricing procedure within a sales area.

Recommendation

·,,Define your own pricing procedures that contain only those condition types that you actually use. Otherwise, the system makes unnecessary accesses to conditions.

·,,Do not change the pricing procedures contained in the standard system.

·,,If you want to determine condition types for a sales rebate or a sales commission in the order-to-cash process, you must add the condition types for rebate accruals and commission accruals (for example, REA1, RCA1) to your pricing procedure used in sales documents. To ensure the posting of the accrual amounts to accounting, you must also maintain the corresponding accounting key for that condition type as well.

Warning: Do not add the condition types for rebates and commissions (for example, RES1, RCS1) to your pricing procedure used in sales documents. This can influence the pricing results and can lead to incorrect accounting data.

The following calculation schemas are predefined in the standard system. You should not change these schemas.

RM0000 and RM1000
Control the price determination process in POs, quotations, and scheduling agreements.
Both calculation schemas require 2 condition types for the gross price: one for automatic price determination (standard: PB00) and one for manual maintenance (standard: PBXX).
RM0001 and RM1001
Determine which condition types you can enter in purchasing document headers with time-dependent conditions (e.g. contracts).
RM0002, RM1002
Determine which additional condition types you can enter in purchasing document items with time-dependent conditions or in the purchasing info record.
RMMP00
Defines the condition type for determining the market price which can be entered for each material.
RM2000
Controls the delivery cost determination process in stock transport orders and stock transport scheduling agreements.

Note
In the calculation schemas RM0000, RM1000, RM0001, and RM1001, the field "Subtotal" must contain the following values in the following lines:

Gross value: 9
Effective value: S

If the interim total 'S' is not set, the PO values cannot be updated in the Purchasing Information System (PURCHIS).

A few calculation schemas are predefined in the standard system. You are not allowed to change these schemas.

  • Define your own pricing procedures that contain only those condition types that you actually use. Otherwise, the system makes unnecessary accesses to conditions.
  • Do not change the pricing procedures contained in the standard system.
  • In pricing procedures that are delivered by SAP, you can change the value of certain fields, for example, Manual, but you can neither add nor delete steps.
Note:
  • If you want to change the values of these fields, you should carefully consider that these changes could affect existing business documents and therefore change their pricing result.

  • If you want to add or delete steps in a delivered pricing procedure, you must copy the pricing procedure and adapt it in your custom pricing procedure.

  • If you want to determine condition types for a purchasing rebate in the procure-to-pay process, you must add the condition types for rebate accruals (for example, REA1) to your calculation schema used in purchasing documents. To ensure the posting of the accrual amounts to accounting during goods receipt, you must also maintain the corresponding accounting key for that condition type as well.
Warning: Do not add the condition types for rebates (for example, RES1) to your calculation schema used in purchasing documents. This can influence the pricing results and can lead to incorrect account data.
  1. Check to what extent you can use the calculation schemas provided in the standard SAP System.
  2. Create new calculation schemas by copying similar existing ones and changing them.

  • Enter a key (length max. six characters) for the schema you wish to create, and a descriptive text.

  • Enter a key (length max. six characters) starting with the character Z for the schema you wish to create, and a descriptive text.

  • For each schema, specify the condition types in the order of their usage, and maintain the relevant data.






ROGBILLS - Synchronize billing plans   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 8316 Date: 20240523 Time: 194556     sap01-206 ( 128 ms )