This example is based on a production plan in which 100 pieces are planned for <reqdat1>,
<reqdat2>, and <reqdat1>.
Stage 1: Demand Management
1. Planned independent requirements are created for the production plan. For information on how to create planned independent requirements, see Creating Planned Independent Requirements with Reference [Page 201] or Creating Planned Independent
Requirements Without a Reference [Page 202].
The system finds requirements type VSEB because the strategy group has been set to 59. See the table of planning strategy assignments [Page 147].
2. The requirement is passed on to MRP. The stock/requirements list (Logistics ® Production ® MRP ® Evaluations ® Stock/reqmts list) for the phantom displays the following information:
Date MRP element MRP element
data Received/
<today> ® Planning w/o assembly
<reqdat1> IndReq VSEB 100 - 100
-<reqdat2> IndReq VSEB 100 - 200
-<reqdat3> IndReq VSEB 100 - 300
-Stage 2: Procurement Before Use in Production
1. Procurement requisitions are created in the MRP run (Logistics ® Production ® MRP ® Total planning). The stock/requirements list for the phantom displays the following information:
Date MRP element MRP element
data Received/
<today> --> Planning without assembly
<reqdat1> PlOrd. 1234/IndR 100 100
<reqdat1> IndReq VSEB 100 - 0
<reqdat2> PlOrd. 1235/IndR 100 100
<reqdat2> IndReq VSEB 100 - 0
<reqdat3> PlOrd. 1236/IndR 100 100
<reqdat3> IndReq VSEB 100 - 0
This procurement requisition is the starting point for production or external procurement.
You have a variety of options for handling the procurement process. The following factors, however, are most important in this strategy:
· At phantom assembly level, stock is not taken into account.
· The planned orders are not yet “real” because production of the phantom assembly must be executed after receipt of the production order (or the schedule line in repetitive manufacturing). The planned orders are independent requirements with order type VP. This order type cannot be converted (note the Conversion field in the display of the planned order). This ensures that it is not possible to produce yet. It is impossible to convert these (VP) planned orders into production orders or to use them in a repetitive manufacturing environment.
2. The MRP run also creates procurement requisitions for the components of the phantom assembly (In this example, SZ-59 is the phantom assembly). The stock/requirements list for a component displays the following information:
Date MRP element MRP element data Received/
required quantity
Available quantity
<today> Stock 0
<reqdat1> PlOrd. 1237/Stck 100 100
<reqdat1> DepReq SZ-59 100 - 0
<reqdat2> PlOrd. 1238/Stck 100 100
<reqdat2> DepReq SZ-59 100 - 0
<reqdat3> PlOrd. 1239/Stck 100 100
<reqdat3> DepReq SZ-59 100 - 0
3. The main objective of this strategy (procurement for the components of the phantom assembly) has now been reached, even without an order. In this scenario, we assume that a goods receipt (for a purchase order, for example) takes place. The
stock/requirements list for all components of the final assembly displays the following information:
Date MRP element MRP element data Received/
required quantity
Available quantity
Sample Scenario: Strategy 59
<today> Stock 300
<reqdat1> DepReq SZ-59 100 - 200
<reqdat2> DepReq SZ-59 100 - 100
<reqdat3> DepReq SZ-59 100 0
Stage 3: Production Order and Allocation
1. A sales order is created for a finished product whose BOM uses the phantom assembly.
A planned order for the finished product is created that includes (at least) the phantom assembly and the components of the phantom assembly. The requirements type of the finished product is not important.
2. After a second MRP run, the stock/requirements list for the phantom assembly displays the following information:
Date MRP element MRP element
data
<today> ® Planning w/o assembly
<reqdat1> PlOrd. 1234/IndR 50 50
<reqdat1> IndReq VSEB 50 - 0
<reqdat2> PlOrd. 1235/IndR 100 100
<reqdat2> IndReq VSEB 100 - 0
<reqdat3> PlOrd. 1236/IndR 100 100
<reqdat3> IndReq VSEB 100 - 0
The independent requirements for the phantom assembly have been consumed, resulting in reduction of the planned independent requirements.
3. A reservation was therefore created one level lower, shifting the source of the requirement from the independent requirement to the sales order. The
stock/requirements list of the component of the phantom assembly displays the following information:
Date MRP element MRP element data Received/
required quantity
Available quantity
<today> Stock 300
<today> Ord.Res SZ-59 50 - 250
<reqdat1> DepReq SZ-59 50 200
<reqdat2> DepReq SZ-59 100 - 100
<reqdat3> DepReq SZ-59 100 - 0
Today’s dependent requirement was created by the planned order for the finished product (containing the phantom assembly and the component(s) of the phantom assembly). The other dependent requirements were created by the independent requirements.
4. Now a production order is created for the finished product (Logistics ® Production ® Production control ® Order ® Create).
· An availability check can be performed for all components of the order (Component
® Availability ® Check availability). For more information, refer to Availability Check [Page 157].
· The source of a requirement for a component of the phantom assembly is shifted from the planned order to a production order.
Stage 4: Procurement After Production This does not apply for this strategy.
Stage 5: Goods Issue for Production Order
After goods issue for the production order (choose Logistics ® Production ® Prod. Control ® Confirmation), the stock/requirements list for the phantom assembly looks the same as in Stage 3.
The stock/requirements list for the components of the phantom assembly displays the following information:
Date MRP element MRP element data Received/
required quantity
Available quantity
<today> Stock 250
<reqdat1> DepReq SZ-59 50 200
<reqdat2> DepReq SZ-59 100 - 100
<reqdat3> DepReq SZ-59 100 - 0
It is vital that you use backflushing when withdrawing the components.
Planning w/o Final Assembly at Assembly Level (74)