cancel
Showing results for 
Search instead for 
Did you mean: 

Pricing analysis details are wrong

Former Member
0 Kudos

Hi,

When I check the pricing analys in the sales order , the details captured there is wrong.

I have a sales order created in sales area xxxx 01 01 & when I check the pricing analysis shows yyyy 01 01.

While the order is created the condition type ZPR0 is determined, but if I reprice is it, ZPR0 because of wrong sales area captured in the pricing analyis.

Could any one seen or faced this kind of problem, please let me know what may be the problem.

Best regards,

Sharan

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

hi sharan

check in OVKK and assign correct pricing procedure come back to sales order and click on determine pricing

regards

raghu

Former Member
0 Kudos

solved.

former_member204513
Active Contributor
0 Kudos

Dear Sharan,

The pricing procedure will get determine based on these combination

Sales areaDocument pricing procedureCustomer pricing procedure--->Pricing procedure.

When you create sales order with sales area xxxx 01 01, system will check the availability of pricing procedure with combination Sales area(i.e xxxx 01 01)Document pricing procedure(From document type)Customer pricing procedure(From customer master).

If the pricing procedure avaialable for this combination system will consider that pricing procedure if not available system will give error Pricing determination is not available.

But system will not consider the pricing procedure which is assigned to the other sales area(i.esales order sales area and Pricing determination sales area will be same).

I have a sales order created in sales area xxxx 01 01 & when I check the pricing analysis shows yyyy 01 01

This is not possible please check one more time under which sales area you have created the saes order.

Do the pricing procedure determination properly through OVKK transaction.

Before that you check all these settings

Document pricing procedure assignment to your sales document type through VOV8 transaction.

Customer pricing procedure assignment in your customer master through XD02 transaction.

I hope this will help you,

Regards,

Murali.

Former Member
0 Kudos

Hi Murali,

Thanks for your reply.

All the setting you had mentioned is already checked. Everything is ok.

Since this was strange problem, I had put this question in the forum.

Somehow in the pricing analysis the sales area (sales org) is taken wrongly.

If I need to look at the other areas , please let me know.

Best regards,

Sharan

former_member217082
Active Contributor
0 Kudos

Hi sharan

First of all go to OVKK and check what pricing procedure you have assigned to the sales area, Cupp & Dupp

Check in VD02 wheather the Customer pricing procedure is maintained or not ,if maintained check the 2nd option if not maintained check the 1st option

1) Check in OVKK the combination you maintained -- sales area(YYYY/01/01) + Cupp --> ZRVAA01

2) check in OVKK the combination you maintained --sales area(YYYY/01/01) + Cupp+Dupp --> RVAA01

May be in ZRVAA01 you might have maintained the ZPRO conditon type

Secondly check wheather the customer is available in both sales areas or not

Now in OVKK check the following combination :

1) Check in OVKK the combination you maintained -- sales area(XXXX/01/01) + Cupp --> ZRVAA01

2) check in OVKK the combination you maintained --sales area(XXXX/01/01) + Cupp+Dupp --> ZRVAA01

Regards

Srinath

Former Member
0 Kudos

Hi Srinath,

Thanks for your reply.

All the setting you had mentioned is already checked. Everything is ok.

Since this was strange problem, I had put this question in the forum.

Somehow in the pricing analysis the sales area (sales org) is taken wrongly.

If I need to look at the other areas , please let me know.

Best regards,

Sharan

Former Member
0 Kudos

Debug the pricing in the sale order and see which values are passing to the structure KOMK for these org units. It might be that there is some user exit that is working in include *FZZ or *FZB that is making these values flow to the internal pricing commuinication structure.