How To Fix MILL_PC_OB022 - Production order &1 already has a reference to original batch &2 &3 &4

SAP Error Message - Details

• Message type: E = Error

• Message class: MILL_PC_OB - Original Batch

• Message number: 022

• Message text: Production order &1 already has a reference to original batch &2 &3 &4

copied from HM6

What causes this issue?

A production order has more than one order item. The original batch
plant &V2& material &V3& batch &V4& has already been created for one
order item.

System Response

The system issues a message that enables the user to cancel creation of
the original batch.

How to fix this error?

Decide whether several original batches are to be created per order.

Procedure for System Administrators

Table T160M can be used to set whether the message is an information
message or an error message (Customizing transaction OMILL_T160M). ->
<AB><NP><SE> <DS:TRAN.OMILL_T160M>Message control</></></></> <AB><NP>
<SE> </></></>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MILL_PC_OB022 - Production order &1 already has a reference to original batch &2 &3 &4 ?

  The SAP error message MILL_PC_OB022 indicates that a production order is attempting to reference a batch that is already linked to another production order. This typically occurs in the context of batch management within the production planning and execution processes in SAP.
  
  Cause:
  
  Batch Already Assigned: The batch specified in the production order is already assigned to another production order. In SAP, a batch can only be assigned to one production order at a time.
  Incorrect Batch Selection: The user may have selected a batch that is not available for the current production order due to its current assignment.
  System Configuration: There may be configuration settings in the batch management or production order processing that restrict the use of certain batches.
  
  
  Solution:
  
  Check Batch Assignment: Verify if the batch is indeed assigned to another production order. You can do this by checking the batch status in the batch management transaction (e.g., MSC3N).
  Use a Different Batch: If