cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Strategy Group 52 in SAP IBP (Planning w/o Final Assembly; ± Hybrid MTO)

vincentverheyen
Active Participant
0 Kudos
204

In SAP IBP standard, we can execute a process such as Strategy Group 40 (MTS; Make-to-Stock), which takes us from Forecast to Demand Plan to Supply Run. This results in Planned Orders in IBP, which are then sent to S/4 and converted into Production and Procurement Orders without requiring a Sales Order. The stock is therefore not customer-specific, and when a Sales Order arrives, it is allocated from this general inventory.

Similarly, Strategy Group 81 (MTO; Make-to-Order) in S/4 is triggered only after a Sales Order with account assignment, creating a Planned Order that is linked to the Sales Order. This process creates customer-specific stock only, without shared stock.

Some customers, however, would like to anticipate component planning even before a Sales Order arrives. In S/4, we could use Strategy Group 52 (Planning w/o Final Assembly; ± Hybrid MTO), where the forecast creates non-convertible planned orders as anonymous stock (not tied to a specific customer). Once a Sales Order arrives, MRP replaces the forecast with sales-specific planned orders, functioning like pseudo-MTO, but without customer-specific stock. This allows for early component and capacity planning while maintaining flexibility before the sales order is confirmed.

The question is: how would we implement Strategy Group 52 when planning the Finished Product in SAP IBP? Would it make sense to use Strategy Group 81 with a workaround—by creating non-convertible Planned Orders (using the Conversion Indicator flag)—so that no Production Orders are created before a Sales Order arrives, while still enabling early material (component) requirements planning and capacity planning? Or are there alternative approaches, experiences, or customizations in SAP IBP that simulate the behavior of Strategy Group 52?

Accepted Solutions (1)

Accepted Solutions (1)

vincentverheyen
Active Participant
0 Kudos

Custom development:

  • Use the new oDATA feature of OBP to download pegging results.
  • Write a custom SE38 report that sets the conversion indicator for planned orders based on your oDATA extraction of planned order pegging.
  • Use periodic RTI Outbound integration for planned orders.
  • Use an external scheduler and make sure that the jobs for:
  1. the OBP run,
  2. the oData Download
  3. Job Based RTI Outbound of planned orders
  4. and the custom S/4 report

are scheduled one after the other without a time gap in between.

Answers (1)

Answers (1)

vincentverheyen
Active Participant
0 Kudos

....