Skip to end of metadata
Go to start of metadata

 

General Information

 

Trade Spend Exceptions provide a function to plan on products and trade spends in a more flexibel way. Trade Spend Exceptions can be created for different periods, and for different spend values. TS exceptions are considered for discout generation.

 

TS Exceptions are created for product / trade spend combination. The starting point is the product in the TP.

From the produce an Exception can be be created for each trade spend in the TP.

The 'exception exists' flag is then set on the product and trade spend.

 

TS Exception Validation

 

On entering TS exceptions the exceptional dates are validated against the TP dates - the TS exception dates need to fall within the TP dates.

 

When having more TS exceptions maintained for the same product and trade spend the validaty must not overlap.

 

Date Shift Scenario

 

On shifting the TP dates the TS exception dates are supposed to be shifted as well. The date shift works based on the design documented in the following SAP notes:

 

2331507 - Trade Spend Exception dates not updated when changing Trade Spend dates on a Released Promotion

2238850 - Copying Trade activities and shifting the dates doesn't shift the Trade Spend Exception dates

2076772 - In Trade Promotion, when changing the plan dates, the trade spend exception dates may be changed to an undesirable date

 

TS exception dates are shifted on manually changing the TP dates, in the mass change and mass copy scenario.

 

In released TPs there is the following design:

 

Usually the TS exception dates are not shifted in released TPs. If the TS exception dates however are similar to the TP dates, the TP exception dates are shifted together with the TP dates - even if the TP is released.

If the TS exception dates differ from the TP dates, the TS exception dates are not shifted.

If due to the TP date change the TS exception dates fall outside the TP dates the TS exception validation triggers an error.

In not yet released TPs and in the mass copy scenario with date shift the TS exception dates are shifted proportionally to the TP dates.

 

The TS exception dates are either extended or shortened.

 

The same is valid for the end date as well.

 

The proportional date shift works based on the following design, both for start and end date:

 

First the proportion is calculated based on the number of days in the TP dates divided by the number of days of the TS exception days.

proportion = (TP end date - TP start date) / (TS Exp end date - TS Exp start date)

Then the number of shifted days in the TP dates are calculated.

shift d = TP start date shifted - TP start date before

The no of shifted days is divided by the proportion to get the number of shifted days for the TS exception.

shift TS Exp d = shift d / proportion

Finally the new TS exception date is calculated based on the rounded value of the shifted days for the TS exception.

TS Exp start date new = TS Exp start date old + shift TS Exp d

 

When taking the following example:

TP date: start date 01.07.  end date 10.07.

TP Exp date: start date 04.07. end date 10.07.

 

The TP start date gets shifted from 01.07. to 04.07.

 

proportion = (TP end date - TP start date) / (TS Exp end date - TS Exp start date)
proportion = (10.07. - 01.07.) / (10.07. - 04.07.)
proportion = 1,5

 

shift d = TP start date shifted - TP start date before
shift d = 04.07. - 01.07.
shift d = 3

 

shift TS Exp d = shift d / proportion
shift TS Exp d = 3 / 1,5
shift TS Exp d = 2

 

TS Exp start date new = TS Exp start date old + shift TS Exp d

TS Exp start date new = 04.07. + 2

TS Exp start date new = 06.07.

 

The new TS exception start date is 06.07.

 

Known Issues

 

Daylight Saving Time

 

There is an issue related to the daylight saving time - this is solved with the following SAP note:

 

2292783 TPM: Trade Spend Exception Dates are getting copied wrongly while creating Product Exception

 

 

  • No labels