while doing pricing determination procedure in ovvkk

[Former Member]

while doing pricing procedure process i.e., creating condition tables, accseques, types and finally assigning in ovkk, is there a necessary to declare the condition type or it directly takes it, another thing do we require a condition table for PR00 also.

[Former Member]

Hi Amar,

It is not mandatory to give a condition type in OVKK. If any condition type is given then this condition type along with its value would be displayed in the litem level of an order and can be viewed without going to the conditions tab.

Your second question is not clear?

Regards

Nadarajah Pratheb

[Former Member]

thanx, for ur reply ! and my second question is : while doing pricing procedure for pricing and discounts, pr00 and k004,k005 ,k007 respectively, the first step is to create condition tables, subsequently, asscess seq and so on...but,i want to know whether we need to create same procedure for PR00 as well, as we do with other ctypes for discount.

all i want to ask is whether or not we require condition table for pr00 pricing procedure or will it takes by default?

with regards

amar

[Former Member]

Hi Amar,

Just a correction to get your understanding in pricing better. We do not create pricing procedures for the condition types pr00, k004 etc. Instead a pricing procedure is a collection of condition types and its a formula to calculate the net price at which a product must be sold.

<b>Answering you question whether PR00 should have condition tables?</b>

Incase you want the system to determine the value of PR00 automatically then you need to assign an access sequence. The access sequence would further have the condition tables attached to it. If you decide to have the value entered by the user manually then no access sequence and condition tables are required.

What is recommended is to have the condition tables and access sequence for the condition type PR00 instead of asking the end user to enter these critical values.

Hope I have cleared your doubt. Do let me know if you have any futher query else do reward for the helpful answers.

Regards

Nadarajah Pratheb

[Former Member]

write-up on pricing procedure:

Check the Pricing Procedure:

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 (T.Code: V/04): 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 (T.Code: V/07): 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 (T.Code: V/06): 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 (T.Code: V/08): 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 (T.Code: VOK0): 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.

5. Condition record (T.Code: VK11 / VK12): 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. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.

Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.

Regards,

Rajesh Banka

Reward suitable points.

• How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).