Process Flow
This example is based on a production plan in which 100 pieces are planned for <reqdat1>, <reqdat2>, and <reqdat1>.
The BOM structure for this example has a parent material SZ-52 and a component ROH52A. The BOM has an item quantity of 1.
Stage 1: Demand Management
The system finds requirements type VSE because the strategy group has been set to 52.
See the
Date |
MRP element |
MRP element data |
Received/ |
Available quantity |
<today> |
Stock |
0 | ||
<today> |
® Planning w/o assembly |
|||
<reqdat1> |
IndReq |
VSE |
100 - |
100 - |
<reqdat2> |
IndReq |
VSE |
100 - |
200 - |
<reqdat3> |
IndReq |
VSE |
100 - |
300 - |
Stage 2: Procurement Before Sales
Date |
MRP element |
MRP element data |
Received/ |
Available quantity |
<today> |
Stock |
0 | ||
<today> |
® Planning w/o assembly |
|||
<reqdat1> |
PlOrd. |
1234/IndR |
100 |
100 |
<reqdat1> |
IndReq |
VSE |
100 - |
0 |
<reqdat2> |
PlOrd. |
1235/IndR |
100 |
100 |
<reqdat2> |
IndReq |
VSE |
100 - |
0 |
<reqdat3> |
PlOrd. |
1236/IndR |
100 |
100 |
<reqdat3> |
IndReq |
VSE |
100 - |
0 |
These procurement requisitions are the starting point for production or external procurement. Various possibilities exist for handling the procurement process in the R/3 System. The following factors, however, are important for this strategy:
· Stock at finished product level is not taken into account for production.
· The planned orders are not yet "real" because production of the finished product must be executed after receipt of the sales orders. The planned orders have order type (VP). It is impossible to convert these (VP) planned orders into production orders, or to use them in a repetitive manufacturing environment. The Conversion field in the display of the planned order is not set, which indicates that it is not possible to produce this planned order.
Date |
MRP element |
MRP element data |
Received/ |
Available quantity |
<today> |
Stock |
0 | ||
<reqdat1> |
PlOrd. |
1237/Stck |
100 |
100 |
<reqdat1> |
DepReq |
SZ-52 |
100 - |
0 |
<reqdat2> |
PlOrd. |
1238/Stck |
100 |
100 |
<reqdat2> |
DepReq |
SZ-52 |
100 - |
0 |
<reqdat3> |
PlOrd. |
1239/Stck |
100 |
100 |
<reqdat3> |
DepReq |
SZ-52 |
100 - |
0 |
Date |
MRP element |
MRP element data |
Received/ |
Available quantity |
<today> |
Stock |
300 | ||
<reqdat1> |
DepReq |
SZ-52 |
100 - |
200 |
<reqdat2> |
DepReq |
SZ-52 |
100 - |
100 |
<reqdat3> |
DepReq |
SZ-52 |
100 - |
0 |
Stage 3: Sales Order and Allocation
· The system will find the requirement type KSVS because the strategy group has been set to 52. See the
· It is possible to confirm a quantity that has been previously planned (100 pieces for each schedule line, in this example) . The header text that says Assignment of Planned Independent Requirements indicates that this is not a check according to ATP logic but rather an availability check based on planned independent requirements.
· The system finds the schedule line category CP and the item category TAN because the item category group was set to NORM.
Suppose that for this example an order with a quantity of 90 pieces is entered with a required delivery date of today. This order can be confirmed after the first planned independent requirement date <reqdat1> if the consumption parameters have been defined accordingly and this date can be found. For more information, see
Consumption Strategies and Logic.
Date |
MRP element |
MRP element data |
Received/ |
Available quantity |
<today> |
Stock |
0 | ||
<today> |
Order |
000333/0010/001 |
90 - |
|
<today> |
® Planning w/o assembly |
90 - | ||
<reqdat1> |
PlOrd. |
1234/IndR |
100 |
100 |
<reqdat1> |
IndReq |
VSE |
10 - |
90 |
<reqdat2> |
PlOrd. |
1235/IndR |
100 |
190 |
<reqdat2> |
IndReq |
VSE |
100 - |
90 |
<reqdat3> |
PlOrd. |
1236/IndR |
100 |
190 |
<reqdat3> |
IndReq |
VSE |
100 - |
90 |
Stage 4: Procurement After Sales
Date |
MRP element |
MRP element data |
Received/ |
Available quantity |
<today> |
Stock |
0 | ||
<today> |
Order |
000333/0010/001 |
90 - |
90 - |
<t+rlt> |
PlOrd. |
1237/Stck |
90 |
0 |
<today> |
® Planning w/o assembly |
0 | ||
<reqdat1> |
PlOrd. |
1234/IndR |
10 |
10 |
<reqdat1> |
IndReq |
VSE |
10 - |
0 |
<reqdat2> |
PlOrd. |
1235/IndR |
100 |
100 |
<reqdat2> |
IndReq |
VSE |
100 - |
0 |
<reqdat3> |
PlOrd. |
1236/IndR |
100 |
100 |
<reqdat3> |
IndReq |
VSE |
100 - |
0 |
The planned order ("Stck") for the parent material can now be converted to either a production order, a process order, or allow backflushing in the repetitive manufacturing process. This triggers the production after sales order stage. Production of this material can be performed quickly because all the necessary components are already available.

Working with production orders is only one option for production. This process is also possible in the area of repetitive manufacturing.
At component level (ROH52x), the dependent requirements ("DepReq" in the planned order) are replaced by an order reservation ("OrdRes" in a production order).
Stage 5: Goods Issue for Delivery and Reduction of Planned Independent Requirements
After goods issue for the delivery (choose Logistics ® Sales and distribution ® Shipping ® Delivery ® Create) for the parent material, the stock/requirements list of the parent material is reset back to empty again. In other words, it only shows the planned independent requirements and the corresponding planned orders. The planned independent requirements are, of course, reduced.