SAP_PP_004 | Planning of Standard Lots in 3 Horizons | Using Max Lot Sizes

[former_member594046]

We want to use SAP_PP_004 [

Planning of Standard Lots in 3 Horizons] with the following settings:

[Short Term] Lot Sizing Procedure from Product Master (Daily/Lot for Lot)

[Medium Term] Periodic Lot Sizing (Weekly)

[Long Term] Periodic Lot Sizing (Monthly)

The issue we have is we are using max lot sizes on the product master (example 100 EA) and the demand is for example 100 EA every day.

Short term we get 1 order a day for 100EA which is great.

Medium Term we want periodic lot sizing of weekly resulting in one order for 700 to cover the full weekly requirement.

However because we are using max lot sizing we still get 7 planned orders at a single point in the week.

There's a BADI [Change Data for PP Heuristics] does anyone know if it's possible to use this BADI to change the lot sizing behaviour so it ignores max lot sizing in the medium and long term horizon?

Alternative any other suggestions would be welcome.

[former_member183665]

Hello,

Do we have any solution for this requirement?

Thanks,

[former_member594046]

We decided on creating a new heuristic with lot sizing driven from the heuristic itself, which means it ignores any lot sizing in the product master. It increases complexity but gives us the desired results and we perform the following steps in the planning run...

1) Run a standard planning run (with order constrained by the product lot sizes)

2) Use the firming objects function with a Time Profile [4 Weeks] to firm up the orders in the short term horizon.

3) Run the new heuristic with a Weekly Lot Size - the system them leaves in the firmed orders but deletes and recreates the orders unfirmed in the medium/long term horizon.

4) Use the unfirm objects function in the same Time Profile [4 Weeks] to unfirm the product lot size constrained orders.

NOTE: This method is not suitable if the business are already manually firming orders as the orders will become unfirmed by step 4.

Hope this helps 🙂

[former_member183665]

Hi,

Thanks for sharing your experience on the approach, but in our Business case this approach is not suitable.

I went with code change in PPDS Algorithm.

At this line we applied a small code change which helped me to solve this requirement.

If sy-index <> 1.

GS_MATLOTSZ-BSTMA = 0

ENDIF.

Thank you,