Tuesday, April 14, 2009

SAP Pricing

Configuration of Pricing Procedure is as follows:

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.In SD, the steps to configure Pricing procedure are as under:Step 1:Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG –> Sales & Distribution –> Basic Function –> Pricing Control –> Condition Table (select the required fields combination, which will store condition record).Step 2:Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG –> Sales & Distribution –> Basic Function –> Pricing Control –> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.Step 3:Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG –> Sales & Distribution –> Basic Function –> Pricing Control –> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.Step 4:a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG -> Sales & Distribution –> Basic Function –> Pricing Control –> Pricing Procedure -> Maintain Pricing Procedure.b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG -> Sales & Distribution –> Basic Function –> Pricing Control –> Pricing Procedure -> Determine Pricing Procedure.Step 5:Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

There are 16 fields in pricing procedure which can surely be termed as back bone when configuring pricing in SAPSD. These are:
1. STEP
2 CTRSTEP
3. CTYP
4. DESCRIPTION
5. FROM
6. TO 7. MAN
8. Mand
9. STAT
10. PRINT
11. REQUIREMENT
12. ALCTYP
13. ALBCTYP
14. ACKEYS
15. ACCRUALS
A. STEP: This indicates the number of step-in the procedure.

B. COUNTER: This is used to show a second ministep

C. CONDITION TYPE: This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.

D. DESCRIPTION: This forms the description of the condition type.

E. FROM: This is used to define the progression of the calculation and range of subtotals

F. TO: This is used to define the progression of the calculation and range of subtotals

G. MANUAL: This function enables to allow the condition type to be entered manually also apart from automatic pickup.

H. MANDATORY: This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.

I. STATISTICS: This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price

J. PRINT: The activation of this function will enable the printing of the values and conditions to the document.

K. SUBTOTAL: A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also

L. REQUIRMENT KEY: This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.

M. ALTERNATE CALCULATION TYPE: This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.

N. ALTERNATE CONDITION BASE VALUE: The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.

O. ACCOUNTS KEY: The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.
PR00- ERL K007/KA00- ERS. KF00- ERF………….& so On.

P. ACCRUAL KEY: The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.Few Related links:SAP Help - Pricing ProcedurePricing ProcedureSD Pricing Procedure




Pricing and Conditions




The system determines the price according to information stored in the condition record. If a pricing scale exists, the system calculates the appropriate price. In the example, the sales order item is for 120 pieces of the material. Using the scale price that applies to quantities from 100 pieces and more, the system determines a price of USD 99 per piece. Introduction to the Condition Technique

The term pricing is used broadly to describe the calculation of prices (for external use by customers or vendors) and costs (for internal purposes, such as cost accounting). Conditions represent a set of circumstances that apply when a price is calculated. For example, a particular customer orders a certain quantity of a particular product on a certain day. The variable factors here - the customer, the product, the order quantity, the date - determine the final price the customer gets. The information about each of these factors can be stored in the system as master data. This master data is stored in the form of condition records.
The Condition Technique in Pricing
The condition technique refers to the method by which the system determines prices from information stored in condition records. In Sales and Distribution, the various elements used in the condition technique are set up and controlled in Customizing. During sales order processing, the system uses the condition technique to determine a variety of important pricing information. For example, the system automatically determines which gross price the customer should be charged and which discounts and surcharges are relevant given the conditions that apply.

Example of Pricing in the Sales Order
The following figure shows how the condition technique works in the background to produce the pricing information. The diagram shows how the various elements in the condition technique work together.

The system repeats this process for each condition type in the pricing procedure determines a final price.
For further information on the condition technique, see


The system determines the pricing procedure according to information defined in the sales document type and the customer master record.
The pricing procedure defines the valid condition types and the sequence in which they appear in the sales order. In the example, the system takes the first condition type (PR00) in the pricing procedure and begins the search for a valid condition record.
Each condition type in the pricing procedure can have an access sequence assigned to it. In this case, the system uses access sequence PR00. The system checks the accesses until it finds a valid condition record. (Although you cannot see this in the diagram, each access specifies a particular condition table. The table provides the key with which the system searches for records).
In the example, the first access (searching for a customer-specific material price) is unsuccessful. The system moves on to the next access and finds a valid record.



Introduction to the Condition Technique
Use
This section describes the elements within the condition technique. It is organized to reflect the likely sequence of events that you go through when you implement pricing in Customizing. The standard R/3 System includes predefined elements for routine pricing activities. For example, the standard system includes condition types for basic pricing elements, such as material prices, customer and material discounts, and surcharges such as freight and sales taxes. In the case of each element, you can use the standard version, modify the standard version, or create entirely new definitions to suit your own business needs. The sequence of activities is generally as follows:
Define condition types for each of the price elements (prices, discounts, and surcharges) that occur in your daily business transactions.
Define the condition tables that enable you to store and retrieve condition records for each of the different condition types.
Define the access sequences that enable the system to find valid condition records.
Group condition types and establish their sequence in pricing procedures.
For more information about implementing and customizing pricing in sales order processing, see Customizing for Sales and Distribution.
For a more technical description of how the condition technique works, see the Business Workflow documentation for Message Control.
Elements Used in the Condition Technique








How Condition Technique Elements Work Together

The following figure illustrates the relationships between elements of the condition technique.

Pricing Elements in Sales Order Processing Working with Condition Records.
The task of actually defining condition types is part of system configuration and maintenance. For further information on condition types, seeIntroduction to the Condition Technique.
Pricing Elements in the Standard Version
Pricing elements are divided into four categories:




When entering sales orders, the system can carry out an automatic check. During sales order entry, the system can calculate prices automatically by finding a gross price, deducting all the relevant discounts and adding any surcharges such as freight and sales tax. The following figure illustrates how the system represents various pricing elements of everyday business.

In the figure, you can see that the price of a material is represented by one condition type (PR00). However, the price of a material can be based on different kinds of pricing records. The price can come from a price list; it can be specific to a particular customer, or it may be a simple material price. On the other hand, each discount, surcharge, freight charge, and tax is defined by its own condition type.
Sales TaxesFreight CostsSurcharges and DiscountsPrices

Use

All of the pricing elements that you use in your day-to-day pricing procedures - the prices, surcharges, discounts, freight charges, and taxes - are defined in the R/3 system as condition types. This section gives you an overview of the pricing elements and their corresponding condition types that appear in Sales & Distribution (SD). When you create or maintain pricing information for a particular pricing element in the system, you create condition records. For more information about the tasks of creating and maintaining conditions, see
Further InformationPricing proceduresAccess SequencesCondition TablesCondition Types

Purpose

No comments:

Post a Comment