Can we have one Header Group Condition value for items with different pricing dates (essentially driven off differently dated condition records)?

[Former Member]

Hi All,

Need your expert opinion on an issue:

We have a scale based group surcharge condition type, ZSUR, that is based on the order volume.  ZSUR is Access Sequence driven with manually changes prevented.  Currently there is one condition record (say # 00958713) with three scales (valid from 1/1/2016 thru 12/31/9999):

From 1 gallon = 5.00

From 100 gallons = 100.00

From 500 gallons = 250.00

Now the Business wants to a new tier <From 1000 gallons = 320.00>, so the new tier would look like:

From 1 gallon = 5.00

From 100 gallons = 100.00

From 500 gallons = 250.00

From 1000 gallons = 320.00

The catch is that the Business wants the new tier to be effective for existing open orders ONLY if quantity or line items are added.

A couple of ways I think that this can be achieved are (limitations are below each):

1. Add the new scale <From 1000 gallons = 320.00> to the existing condition record # 00958713 (keeping the start date of 1/1/2016 and end date of 12/31/2016 intact)

Limitation: The pricing is called explicitly in change mode (in case of existing orders); meaning if there is an order created before the existing condition record was appended, and the order was for 600 gallons, then in display ZSUR = 250.00 but in change mode ZSUR = 320.00 per the appended condition record.

2. Invalidate condition record # 00958713, to end on 06/13/2016 and have a new condition record # 00999719 as given below:

From 1 gallon = 5.00

From 100 gallons = 100.00

From 500 gallons = 250.00

From 1000 gallons = 320.00

Limitation: In case of an existing order, when items are added, the system adds another ZSUR at the header.  Let's take the example # 1, wherein the order was for 600 gallons.  We get one ZSUR at the header for 250.00, and let's say that now we add items so that the volume becomes 800 gallons.  This generates another ZSUR for 320.00 in the order.  So we have two ZSURs, we need just one (the second one) for 320.00 when items are added alone.

Has anyone faced this?  Any suggestions, recommendations would be greatly appreciated.  Thank you!

Regards,

Yet Another SAPAddict!

[Jelena]

Technically the order would have to be re-priced to get the new conditions. If the old order records are just sitting there, no changes are made and you have copy control that preserves original pricing then wouldn't these orders still have the old pricing regardless of changes made in the conditions?

To be honest, I feel you should rather go with the option 2 and the customers should get whatever pricing is applicable by the pricing date of their order. Seems like the most decent solution from the customer service standpoint.

I'm quite curious though what kind of business this is? Everyone wants to sell more and you are charging your customers extra? Whaaat...

[Former Member]

Hi Jelena,

Thank you for your reply.

To your question: Everyone wants to sell more and you are charging your customers extra?

This is a surcharge based on order value.  If the order is open and customers add more items, then obviously one would want the header surcharge condition to go up in value.  I guess I am missing something.

On another note: I purchased your IDoc book and am reading it.  So far I am enjoying it!  Well written!

Regards,

SAPAddict

[Jelena]

SAP Addict wrote:

This is a surcharge based on order value.  If the order is open and customers add more items, then obviously one would want the header surcharge condition to go up in value.  I guess I am missing something.

But why there is a surcharge in the first place? It's rather unusual in free market society to go to a grocery store and get charged extra for buying 10 tomatoes instead of 5 tomatoes. Such store would be out of business in a week. Usually you'd get a volume discount, not a volume surcharge.

What is the business scenario that does not encourage more spending by the customers? Is there some kind of rationing? That's the confusing part.

[Former Member]

Hi Jelena,

I guess the terminology 'surcharge' is the cause of confusion,  It is actually freight charge.  So in the case of tomoatoes, if you buy 1000 lbs of tomoatoes, you can expect to pay a higher freight than if you had bought 100 lbs of tomatoes.  In both case, they are being delivered to you.

Hope this clarifies.

Thanks,

SAPAddict

[Jelena]

OK, the freight charge makes sense, thanks for an explanation.

Back to the original question - I still feel your option 2 is a better and cleaner solution. Don't know why you'd get two condition records with it (maybe because it's a surcharge type?), might want to check with an ABAPer. There are also plenty of posts on SCN on the duplicate condition problems, make sure to search.

[jignesh_mehta3]

Hello,

I would suggest to go for option one.

Incase of option 2 since you are planning to end date exiting condition record on 13.06.2016, there would be open orders with Pricing date in past (for example 01.06.2013) and the end dated condition would be valid, thus you see two condition records.

With option 1, since the pricing scales have changed, you will have to reprice the existing open orders (after adding additional scale in condition record) and system will determine the correct applicable surcharge.

Just one question, do you have cases where Orders are partially delivered and you need to apply additional scale to these orders too?

Thanks,

Jignesh Mehta

[Former Member]

Hi Jignesh,

Thank you for your reply,  There is a typo in my initial email in regards to the limitation of Option # 1; my bad!

Paragraph with the typo As-Is:

Limitation: The pricing is called explicitly in change mode (in case of existing orders); meaning if there is an order created before the existing condition record was appended, and the order was for 600 gallons, then in display ZSUR = 250.00 but in change mode ZSUR = 320.00 per the appended condition record.

Paragraph corrected:

Limitation: The pricing is called explicitly in change mode (in case of existing orders); meaning if there is an order created before the existing condition record was appended, and the order was for 1100 gallons, then in display ZSUR = 250.00 but in change mode ZSUR = 320.00 per the appended condition record.

So, the problem with option 1 is that without making any change to the order the system triggers pricing when in TCode VA02.  This would happen if the new tier is applicable for that order.  In other words, if the order was created on 1 Feb, 2016, and the order value is 1100 gallons, then the ZSUR would have been 250.00; however when opened in VA02 on 14 June, 2016, the order invokes pricing for ZSUR to 320.00 (without making any change to the order).

Now the answer to your question:

Just one question, do you have cases where Orders are partially delivered and you need to apply additional scale to these orders too?

Answer: Yes, we do have orders that are partially delivered, and new items can be added.  The requirement is to price the existing ordes only if relevant items/quantity have been added/increased.

Hope this clarifies,

Regards,

SAPAddict

[Former Member]

Hi,

In the case mentioned above, Option 2 is suitable and you can have requirement routine written in ABAP to restrict the ZSUP condition type such that, if it's already existing:

1. Update it

2. Make it inactive and insert ZSUP again with new value.

[Former Member]

Hi Bheem,

Thank you for your reply.  I went with option 1 with a calculation type in the pricing procedure that suits our requirement.

Best regards,

SAPAddict