Component management

• Additional information
• 1808922 - FAQ: Components in the production order and process order
• 125364 - Order component: Non-supported combinations

Additional information

125364 - Order component: Non-supported combinations

SAP R/3 supports various special processings in the area of the components in the production order, process order, network and maintenance order (but not in the sales order!):

• Batch split
• Discontinued parts
• Alternative control
• Phantom assemblies
• Directly manufactured components (collective orders).

For technical reasons you cannot use any combination of these processings.

1808922 - FAQ: Components in the production order and process order

This SAP Note contains answers to frequently asked questions (FAQ) about components in the production order. This information also applies accordingly to the material components in a process order.

Question: How is the storage location of the components defined in the production order?

Answer:

The following logic has applied since SAP Note 137225:

The system first transfers the production storage location of the material to be withdrawn (MARC-LGPRO) from the MRP data in the material master if this is populated.

The system overwrites this value with the production storage location from the bill of material (RC29P-LGORT, STPO-LGORT) if this is populated.

If the operation to which the component is assigned in the production order contains a work center with a production supply area (PSA), the system transfers the storage location from this production supply area (PVBE-LGORT). However, the transfer takes place only if storage location data (MARD) is maintained for this storage location for the material.

Question: Are there special cases in storage location determination?

Answer:

Yes. There are special cases.

For special stocks, you do not have to check whether the storage location exists for this material because it can be created for the goods movement. This logic was transferred to the standard system with SAP Note 623082.

The system transfers the issue storage location from the production version if no storage location is defined in the bill of material (BOM) and in the PSA of the operation. However, this applies only if strategy '2' or '4' is set for storage location determination in the MRP group of the material (transaction OSPK).

Question: How can the storage location determination be influenced?

Answer:

In principle, you can define your own logic in the user exit PPCO0005. SAP Note 651925 provides a modification that reverses the logic explained in question 1 and gives the storage location the highest priority in the material master.

Question: The reservation relevance is different in transactions CO40 and CO01. Why?

Answer:

Dependent requirements in the planned order are always MRP-relevant. Therefore, they retain this property in the planned order conversion as well. Therefore, Customizing for the order type-dependent parameters (transaction OPL8) is not evaluated either.

Since SAP Note 569984, you can use the customizing of system message C2 280 to decide whether customizing OPL8 should also be considered in the planned order conversion.

Question: There is only one common indicator for the MRP relevance of reservations and for PReq generation. Is separate control possible?

Answer:

In the customizing in the order type-dependent parameters (transaction OPL8), you can specify whether the reservation and the PReq are to be MRP-relevant and to be created "Immediately", "On Release", or "Never". At present, the standard system does not have a separate selection option only for the MRP relevance of reservations or only for PReq creation.

SAP Note 1696709 provides a modification that prevents automatic PReq creation. However, this modification is not possible for the planned order conversion. If you require this modification note, create a message under the component PP-SFC-PLN and reference the SAP Note or this FAQ note.

Question: When you create a production order or a process order, the "Bulk Material" indicator is not transferred from the bill of material (BOM) if the components in question are components with direct procurement. Why?

Answer:

The "Direct Procurement" indicator has priority over the "Bulk Material" indicator. This logic was implemented with SAP Note 131464. That is why the "Bulk Material" indicator was reset until now. Since SAP Note 1638442, you can use system message CO 140 to control whether the "Bulk Material" indicator can be combined with the direct procurement indicator.

Question: The availability check always returns the status MACM (Material committed) and the message "All the materials checked are available" for an open order without active reservations. Why?

Answer:

If the availability check is called without active reservations, a full availability is always returned. To receive a meaningful result of the availability check, this should be called if the reservations are active. If the reservation relevance is therefore defined from release (RESB-AUSDISP = 2), the availability check should takes place only after release.

Question: Which combinations are not supported in the standard system?

Answer:

Refer to SAP Note 125364.

Question: When the yield is changed in the production order, the system does not calculate the component quantities correctly; it does not read the BOM conversion here. Why?

Answer:

The system transfers the data from the BOM during order creation. If the order quantity is subsequently changed, the BOM is not automatically read. There is a proportion calculation for the previous quantity.

Example:

10 PC yield = 7.67 component quantity

If you change the yield to 11 PC, the system thus calculates 11 * 7 ,67 / 10 to calculate the new component quantity.

Question: If there are more than 99 assemblies (phantom or directly-produced assemblies) on one level, the system generates the runtime error MESSAGE_TYPE_X in FORM PLMZ_STPO_CHK when you create a collective order. How can this be prevented?

Answer:

In the SAP standard system, there is a limit of 99 [phantom] assemblies on one level in the order. This is technically limited by the field length.

If more than 99 assemblies are required, there is a modification that extends the maximum limit to 9999 assemblies. However, some database tables must be converted for this. Since you should not implement these changes without serious consideration, the modification note (SAP Note 129226) is not released generally for customers; instead it is sent by request only. If you require this SAP Note, create a message under the component PP-SFC-PLN and reference SAP Note 129226.

Question: In the collective conversion or in the partial conversion of planned orders (for production orders, this means transactions CO41, CO48, and CO40 with the "Partial Conv." indicator; for process orders, this means COR8, COR7_PC and COR7 with the "Partial Conv." indicator), the system does not display a dialog box if the material status does not allow usage in the production. Why?

Answer:

Since SAP Note 578341, you can use the customizing for message C2 257 to decide whether or not you want to receive a dialog box. Via the message type P in the OPJB customizing, the system issues the dialog box in the transactions mentioned. In the batch input processing, the system issues a status notification instead of a dialog box.

Question: When a planned order is converted, the system writes the short text of the PReq (EBAN-TXZ01) to the short text of the item (RESBD-POTX1) for components with direct procurement. However, when you create the order manually, for example, in transaction CO01 or COR1, the first line of the long text is used as the item text. Can you change the behavior when converting the planned order?

Answer:

SAP Note 513900 provides a modification that you can use to prevent the system from overwriting the item text (RESBD-POTX1) with the short text of the PReq when a planned order is converted for the component with direct procurement.

Question: If an error occurs during WM staging when a planned order is converted, the system displays a dialog box in the dialog of transaction CO40 or COR7 and enables the user to decide whether or not the order should be saved despite this. If you use the report PPBICO40 or PPBICOR8 to execute the planned order conversion, the order is not saved when an error occurs in WM staging. Can this be changed?

Answer:

Yes. You can use the customizing for message CO 727 (transaction OPJB or O04C) to decide whether the order should still be created in the background.

Question: When you create the order or use another transaction that executes a BOM explosion (such as CK51N, CK11N), this triggers the runtime error MESSAGE_TYPE_X in the program SAPLCOBT in the function module CO_BT_ZAEHL_MK_ADD_MULTIPLE. How can this be prevented?

Answer:

The runtime error is caused by a field overflow. The system creates a reservation number during the BOM explosion and it creates a reservation item for this reservation number for each material component. The field for the reservation item is four-digit in the standard system; this means that 9999 materials can be entered. The dump is triggered if there are more components. The respective BOM must be checked. There are usually many phantom assemblies that are exploded and therefore result in a component number > 9999.

At this point, we recommend that you use phantom assemblies sparingly and that you work with directly produced components (that is to say, collective orders) if possible.

Question: You delete a component in a released production order or process order. This component remains in the order and receives only the deletion indicator (DLT). Why is the component not deleted completely?

Answer:

The component is deleted completely only if the order has not yet been released. Once the order is released, deleted components are not removed completely, rather they remain in the order with the deletion indicator for documentation purposes.

When you use the OCM process, however, this does not apply. Refer to the FAQ 1887717 for OCM for further details.

Question: A user who has no authorization to display the BOM can display the component list in the order processing. Why?

Answer:

The material list of the order is not the BOM. You call the BOM by navigating to the master data tab and then double-clicking the BOM. The BOM is only a default value that can be changed automatically and that therefore need not be identical to the material list. Therefore, there is no authorization check for the BOM authorization at this point.

Question: The system does not allow the change of the special stock indicator to the value "5" (Customer Stock) for production orders and process orders. Why?

Answer:

This behavior corresponds to the SAP standard design. Currently, the special stock (RESB-SOBKZ) 5 is not supported in the production order and process order.

Question: The "Movement allowed" indicator is not set. As a consequence, the system does not carry out any goods movements for the order. How can the indicator be set?

Answer:

Refer to SAP Note 2191464.

Question: The indicator "Routing Text" (T399X-ROUT_TEXT) was set in Customizing for the order type-dependent parameters. During order creation, the system then transfers the long text from the routing. However, if only a short text is maintained, the system does not transfer any data. Why?

Answer:

The system behavior is correct. The "Routing Text" indicator (T399X-ROUT_TEXT) refers only to the long text of the routing.