Reg:condition type in OVKK

[former_member1249468]

Hi Gurus ,

What is the importance of assigning condition type in pricing procedure determination ? What happens if we don't assign condition type in determination and what happens if we assign the same.

Kindly through me some light on this point.

Thanking you all in advance.

With Regards,

SASH.

[Former Member · Accepted solution]

If we maintain condition type in OVKK it will be determined at sales order level.If we don't maintain ,we need to enter manually at order level.

Regards,

Pasapula.

[Former Member]

Hi,

We maintain condition type in pricing procedure determination so that it will appear in line item of order.This we do to have fast entry e.g basic price of material.This is just for our convineince or making simpler in entering price without going to condition tab and entering there.

[Former Member]

Hi there,

This is already answered many times earlier.

Pricing procedure determination OVKK: Sales area + doc pricing procedure + customer pricing procedure.

For eg 1000 / XX / 00 / 01 / A ---> RVAA01.

Doc pricing procedure comes from VOV8 --> transaction flow settings.

Cust pricing procedure comes from customer master.

When a sales order is entered, system will call the pricing procedure condition technique. Accordingly, it will 1st check under what sales area (sales org / dist channel / division) the sales order is raised. Then from the order type OR it will check for the doc pricing procedure. Then from the sold-to in the sales order, it will check for the cust pricing procudure. Then it will check what pricing procedure is assigned in OVKK.

In the above eg it will pick up RVAA01 from OVKK. Then it will go into the relevant pricing procedure RVAA01 & check the condition types that are maintained in sequence. Along with it, system will also read the other characters (like statistical, requirement. Alt cal type etc) maintained in the procedure. Then it will go to each line & read the access sequence that is assigned to each condition type (pls note that manual condition types will not have any access sequnece). It will read the values in the condition tables as maintained in the access sequence. Then it will apply the value accordingly in the sales order. If condition records are not maintained in the table combination in the access sequence system will not defauly any value.

This is called condition technique. This is used to propose the values of condition types in the sales order. If the condition types are not maintained in the pricing procedure & OVKK entries are not maintained, pricing is not done for the sales order. To make pricing possible, you will maintain the condition types in the pricing procedure RVAA01 for eg & assign it to the sales area in OVKK.

Regards,

Sivanand

[former_member217082]

Hi sash

In pricing procedure determination OVKK, we give a condition type. so if you enter that condition type , that condition type appears in the line item .in the sales order. and if you have not maintained condition record for that condition type PR00 , it gives an error message telling " pricing error missing" when you create a sales order. so instead of going to item -> conditions tab and maintaining price manually, directly you can enter the value in the line item itself

Example:

PRICING PROCEDURE DETERMINATION - OVKK

sales orgn + dist channel + divn + cuPP + duPP RVAA01 PR00

So if you have not maintained condition record for PR00 for any material and if you have entered that material in the sales order it will give a message "pricing error missing" , so instead of going to

item data - > conditions - > entering the PR00 value manually, directly you can enter the PR00 value at the line item itself

Regards

Srinath

[Lakshmipathi]

Check this thread

[ovkk -price determination|]

thanks

G. Lakshmipathi