Pricing Condition record Determination Error

[Former Member]

Dear SD Pricing Experts,

I have an serious issue on pricing, while creating a sales order system determined the different condition record rather than the original condition record.

1. We have created a new table 901 with combination of Sales organization and Material., and uploded all the pricing for the same combination,around 60000 records.

2.But while createing the sales order we are enter Sales organization as 1000, and material as "A" , but system is picking up the price of "Z" . this problem is happending in rare case, 99% of cases system determined the correct condition record, in 1% cases system is determined the different condition record Material price.

3. We analyzed through techincal and functional side ther is no issue, can anyone give some idea or solution, to rectify the issue.

Regards,

Rajesh T

[Former Member]

Hi,

I have check the condition records for the particualr article there is only one condition record is maintained and validity period also falling on the order creation date.

and also we check the given transaction code VCHECKT683, there is no errors are inconsistency is there for using the pricing procedure.

is there any alternative way to test the process flow how system is determining the condition record in technical leve. function level there is no issue.

Regards,

Rajesh T

[Former Member]

Hi,

Inform you that this issue is related to sap retail project, in this MM43 transaction we don't have option for Sales tab 2 and i also checked in the sales order level, there is no reference priciging material is maintained in sales order or in article master.

I am using condition table as combination of Sales organization and Material. its an basic pricie condition type. ZPRO, for this am using the same accesss sequence ZPRO.

is the below sequence is correct, which we are using, and i marked as exclusive indicator "X' for each condition table.

30 902 Sales org./Distr. Chl/Customer Hierarachy/Article 0

35 720 Sales org./Distr. Chl/Customer/Brand ID/Art.pr.grp 0

41 908 Sales org./Distr. Chl/Customer/Article 0

42 914 Sales org./Distr. Chl/Customer/Article/Batch 0

43 900 Sales org./Distr. Chl/Price grp/Article 0

44 913 Sales org./Customer/Article 0

46 912 Sales org./Distr. Chl/Article/Batch 0

48 907 Sales org./Distr. Chl/Article 0

56 909 Sales org./Article/Batch 0

60 901 Sales org./Article 0 -

---

>> this level we are facing an issue.

Regards,

Rajesh T

[Former Member]

Hi,

Is not so straightforward. You need to check all possibilities why the correct pricing condition is not determined.

Go to the Sales Order where the wrong condition type is triggered.

Then go to the Conditions tab and click on "Analysis" and check on which Condition record is determined. From there you should drilldown on the issue why other conditions are determined instead of the created records or why is the condition record you created is not determined.

Then, check through the records created, and check the validity of the condition records.

Then, check in OVKK if the determination for the right DPP and CPP exist for a particular Sales Area.

Also, go to tcode VCHECKT683 and key in your Pricing procedure to check for consistency / errors (if any).

Hope this helps.

Thanks.

[Former Member]

You will need to analyse one of the "incorrect" conditions in a sales document to see exactly what is going on.

As a first step though, for the materials which are giving unsatisfactory results, have you checked whether there is a Pricing Ref Material maintained in the Sales Org 2 tab?

This could give the results which you described, e.g. if your material A has material Z as the pricing reference material.

[Lakshmipathi]

99% of cases system determined the correct condition record

In all documents if you face this issue, then you can straightaway check the field assignments in access sequence V/07. But since it is not the case, you have to analyse in depth by comparing the one which was flowing correctly with the problematic one.

thanks

G. Lakshmipathi

[Former Member]

Hi Laxmipathi,

This error we are facing on rare caes, but buy seeing the volume it gets effecting monthly 50-60 sales and invoice docuiments, we analyzed all the ways but we could not get any solution, we check the contion types ,access sequences, condition record, and techinically we analyzed but 99% cases it picking up correct record.

can you give me some idea which area to be analyed further, give me some techinal help also.

Regards,

Rajesh T