cancel
Showing results for 
Search instead for 
Did you mean: 

How do I assign priority to CTM Aggregated Demand?

ruchi_das2
Active Participant
0 Kudos

Hello Experts,

I am setting up a model where is use Sales Order and Custom Category Forecast (ZM) as demands with no consumption set in the model. CTM plans daily and the time stream is in days.


Demand Prioritization:

1. LIFPRO

2. MBDAT

3. CTMQTY

Some of the sales order will be set with a priority and i would like this demand to be the 1st demand to propose supply for. The Sales Order and the custom category forecast are always on the same day. Instead of CTM creating multiple SNP Planned Orders for each demand, I would like it to aggregate these demands within each day and propose a single SNP Planned Order.

Aggregation Settings:

Check - Time Based Aggregation

Aggregate Demands and Receipts from different ATP Categories: "BM" and "ZM".

When I run Demand Prioritization with the above settings, the "BM" which has priority is combined with "ZM" on the same day and assigned a priority of 255 and this is not the 1st demand in the prioritization list.

How can I make CTM to attach a priority to the aggregated demand if a sales order within it has a priority set? I am ok with ZM getting priority as well in this process.

Regards

AK

Accepted Solutions (1)

Accepted Solutions (1)

RahulHanda
Active Contributor
0 Kudos

Hi Abhishek,

You can use prioritization ATPCAT for the same. In customizing assign categories accordingly under category tab. Example

1BRDeliv.
2BMSalesOrder
3BNSchAgr
4FAFC req.

Supply Chain Planning - Multilevel Supply & Demand Matching (SDM) - Demand Prioritization - Define Special Sorting

If you want to further influence then you can use USEREXIT prioritization. For the same check SAP note.

450794 - CTM: User Exit EXIT_/SAPAPO/SAPLBOP_SORT_020


Regards

Rahul

ruchi_das2
Active Participant
0 Kudos

Hi Rahul,

I initially had ATPCAT as 3rd line in demand prioritization with following sequence:

1. BM

2. ZM

Even with this, the results were no different when aggregation is used. I think USEREXIT would be the way to go.

Regards

AK

RahulHanda
Active Contributor
0 Kudos

Hi Abhishek,

Do share the result with USEREXIT approach (after implementing and testing).

Regards

Rahul

Answers (1)

Answers (1)

ruchi_das2
Active Participant
0 Kudos

Hi,

We have decided to let go the customization route and get around with this by changing the RDD of sales order item if required and dropped "LIFPRO" from the prioritization list.

Regards

AK