Pricing error

[Former Member]

Hello,

I am getting a error in pricing for a one condition type, which is configured as header as well as item level.The condition value is getting calculated twice (which should calculate one time only)

The Issue is below,

The main criterion is simple in that if the total value of the order received is below a certain value then a surchage will be applied. The complexity is that the Refinish materials is split into 2 plants, This warehouse split should be irrelevant to the charge made to the customer but during various tests the following happens

1. If the total order value is above the charge threshhold regardless of the value in each plant then no charge is applied.---- This is CORRECT.

2. If the both plants are below the charge threshold, the system generates 2 charges, one on each plant. --- This is INCORRECT.

it should only ever be applied to the first order. Surcharge should apply one time for the customer, not two times for same order as material is available at two different plants.

Thanks and regards,

Abhijit Dixit

+91 9820935468

-

---

First Solution---

Hi

Look into the pricing procedure-steps

Arrange it in the way that it vl caluculate one time. it is relevant to steps and forming ur condition types in pricing procedure.

Look into the pricing procedure;shuffle and create a transaction and have a look

Thanks

Paresh Kolte

Dear Abhijit,

It looks like your problem can be solved by condition Supplement functionality.

1)

e.g if PR00 is determined then supplement conditions will be determined, you can maintain the condition requirment for the amount with the help of ABAPer , to trigger the supplement condition ( Surcharge ) only if order value is not met.

2) regarding the surcharge being calculated two times , this may be happening because , you must have maintained conditon access dependant on Plant,

Instead of plant try to maintain Customer and Material only. that should determine that condition once only in pricing.

Hope solves your problem

Regards,

Paresh

The Issue in not solved----

---

Kindly check the querry as below........................

Thanks for the reply Paresh,

I have informed the solution to business but they are asking me to pick the condition record at plant level only.

In which surcharge should apply for one time only. They want to apply this surcharge for only this two plants( WF-- and VX--).

If we maintain the condition record at header level then it will calculate for only once regardless whichever is the plant,but business don't want that.

Is there any routine or user exit is available which can we apply at pricing procedure.

Or is there any solution which solves my issue.

Kindly suggest the solution asap

Thanks and regards,

Abhijit

[former_member648947]

Dear Abhijit,

I think we need to get more clarity as to what exactly is the requirement.

Please let us know what do you see in pricing analysis screen in sales Order.

Just want to Clear that there cannot be any condition record maintainace at header level. and the header condition can only be entered manually to the header, anyway business has denied that so its irrelevant for your current problem at hand.

Please let me know the following:

1) I assume that you are creating a sales Order by entering material and quantity only once, and you could see Surcharge condition twice in the item level pricing. Here you want system to calculate the condition only once based on the plant.

2) Is there any split actually happening at sales order level.?

3) Can you please elaborate the following sentence "if the both plants are below the charge threshold"?

I think there is a custom requirment assigned in the pricing which is checking the order value correctly but fails to compare the delivering plant determined in the Order.

Please let me knwo your views on above 3 points.

Regards,

Paresh

[Lakshmipathi]

one condition type, which is configured as header 
    as well as item level

The condition value is getting calculated twice 
    (which should calculate one time only)

If you have maintained access sequence (you should have maintained) for a header condition, then system will populate the value wrongly which is a standard behaviour.

thanks

G. Lakshmipathi