PPDS Product Heuristics to consider First Date in Sales Order as Requirement Date

[former_member640818]

Hello,

We are using S/4 1709 with ePPDS.

Is it possible to consider the first date on Sales Order Line item as the Requirement date for PPDS Product Heuristics?

As per standard functionality, in MTO scenario the confirmation date on the schedule line is considered as requirement date. The confirmed date is based on Total Replenishment Lead Time, which could be later than what customer is requesting for.

For e.g. Lets say today is 11/07 and TRLT = 21 days (default)

CSR takes an order with Customer Requested Delivery Date = First Date on SO Line item = 11/15

Based on TRLT of 21 days, the confirmed date on schedule line = 11/28

Hence PPDS Requirement Date for creation of planned order = 11/28, which is late by 13 days based on RDD.

But if look into RRP3, everything appears to be okay...no delay.

Pl provide any insights if the consideration of requirement date for PPDS Heuristics can be influenced by BADI to consider the First Date on the Sales Order Line Item.

Appreciate your feedback.

Thanks,

Mangesh

[former_member640818]

Hello R Brahmankar,

Yes MAD is used for Production Planning, but the MAD is calculated based on Confirmed Date on Schedule Line and not based on First Date. We want to use First Date to be used as a starting point to calculate MAD.

Is this possible? Have anyone experienced this requirement before?

Thanks,

Mangesh

[rupesh_brahmankar]

Hello Mayur,

Customer requested material availability date use for planning in ECC or PPDS. Not the confirmation date. Even if you don't have a confirmation system will plan it. Also check if you are using fix date quantity in sales order.

First Date in planning make no sense, as if you plan based on first date and you have 3 weeks of transit time to customer, then you will produce it too early. Which could result in pileup inventory and inventory cost. Also customer would need a material on his requested date, why customer will buy it 3 weeks early and built his inventory and inventory cost.

Customer calls and confirms an order and indicates delivery date as 20th Jan 2020.

Now system does backward scheduling from requested delivery date 20th Jan 2020.

Let us take an easy example transit time as 3 days; loading time as 1 day; pick pack time as 1 day; transportation lead time as 1 day. Requested delivery date - transit time 2 days = Goods issue date (18th JAN) Goods issue date - load time of 1 day = Loading date (17th JAN) Loading date - transportation lead time of 1 day = 16th JAN Loading date - pick/pack time of 1 day = 16 JAN. As per example above, material should be available on 16th JAN so that delivery can be confirmed to customer on time.

So that production/purchase should be available on 16 Jan 2020 to delivery it on time. Producing/purchasing it before that also make no sense to me.

Best Regards,

R.Brahmankar

[rupesh_brahmankar]

Hello,

The system uses the material availability date to generate automatic production and purchasing requirements. Material avail.date of requested schedule line first schedule line not the confirm schedule line.

The system calculates the material availability date by working backwards from the customer's requested delivery date, taking into account how much time is needed for delivery-related procedures, such as picking, packing, loading, and transportation but not the lead time to produce or procure the goods.

Sales Order MBDAT (Material avail.date) use in Heuristic for planning in standard SAP.

Best Regards,

R.Brahmankar