Pricing Procedures

[Former Member]

I am trying to understand the concept of pricing procedures in SD. When I am looking in IMG - Maintain Pricing Procedures at a specific procedure is every step going to be applied? Can anyone simplify what will occur in price determination?

[Former Member · Accepted solution]

Hi James,

Let me put it in very simple words for you.

Firstly you have condition types ( V/06 ) maintained in your pricing procedure.

These condition types may or may not have access sequence ( V/07 ) assigned to them. If its a manual condition type - no access sequence attached, if its determined automatically you have to assign access sequence.

Access sequence is nothing but list of tables with field catalogues, that form the basis for your condition records

( VK11 ).

If in your access sequence against your table, if the exclusion column is ticked, the system would determine the condition record from there and exit from the access sequence.Otherwise it will keep looking for records that satisfy the condition based on the inputs given in the sales order. Its advisable for performance issues to have the exclusion column ticked against each table in the access sequence.

Hope this makes some sense to you.

If it does dont forget to reward suitable points for contribution.

Regards

Ravi

[Former Member · Accepted solution]

So if no access condition would this mean the condition type is optional for a specific pricing procedure? In same logic only the condition types in the pricing procedure are allowed to be used?

[Former Member · Accepted solution]

yes you are right. And also whether the condition type is optional or not u can set that up. If you want any particular condition type as Mandatory u mark the mandatory field against that condition type...similarly whether u want it to be statistical( only for reporting pruposes) or Manual (manually enter the value in the sales order) you can make those settings too in the pricing procedure.

When u select manual...make sure for that particular condition type you main the changes can me made as "c" in T.code v/06 for that particular condition type.

rgds

Sai

[Former Member · Accepted solution]

hi,

access sequence only contains the conditin tables ie key combinations used to maintain conditin records at VK11 for a particular conditno type. Having an access seq or not does not indicate if a condition type is optional or mandatory for a given pricing procedure, it only provides a way to store condition records in the databased so that you dont have to enter every time at sales order level. In the pricing procedure config if you tick the Mandatory check box for a conditin type then you must supply it with a value at sales order level to proceed for further processing. This value can be entered at sales order level or we fetch the values through conditin records as mentioned earlier.

Hope it answers your query.

regards

sadhu kishore

[Former Member]

Hi James,

The Sap System try to determine the valid condition record using the pricing procedure determination .The pricing procedure is automatically copied into the sales order for the combination of SALES AREA + CUST. PRICING PROCEDURE+ DOCU.PRI PRO. i will explain here clearly.

While creating sales order, first you need to enter Sales Document type. As soon as you enter the document type, the system will take the document pricing procedure from this document type.

Then you will enter sales area. The system uses this sales area to determine the pricing procedure.

The you need to enter the Customer. the system uses the customer pricing procedure from this.

Using the above three combinations, The sap system determine Pricing procedure into sales order.

The pricing procedure contain number of condition types. condition records may exist for some condition types and may not exist for some.

here the sap system determine a valid condition types to which condition records exist into the sales order using this pricing procedure.

[Former Member]

What do you mean when you say condition records may exist for some condition types and not for others? Is this an error or part of normal behaviour?

[Former Member]

when u create the condition records u will mention the validity periods...and make sure the Pricing date in Sales Order will be within this validity periods of the condition record for the system to pick up this.

[Shiva_Ram]

Hi,

That depends on whether the user maintains the condition records or not for each condition type (for example transaction code VK11).

It also depends on any requirements assigned in the pricing procedure.

Hope this helps.