How To Fix MPE_RTG_UI115 - SAS containing status scrap not allowed for OAs in simultaneous groups

SAP Error Message - Details

• Message type: E = Error

• Message class: MPE_RTG_UI - Messages for Routing Maintenance

• Message number: 115

• Message text: SAS containing status scrap not allowed for OAs in simultaneous groups

What causes this issue?

You want to create an operation activity in a simultaneous group.
However, the status and action schema (SAS) for serialized products
assigned to the operation activity contains the status <ZK>Scrap</>.
This is not allowed as this status could cause discrepancies in the
confirmation of work done.

System Response

The system issues an error message when saving the shop floor routing.

How to fix this error?

When creating the operation activity, select a different status and
action schema for serialized products that does not contain the status
<ZK>Scrap</>.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MPE_RTG_UI115 - SAS containing status scrap not allowed for OAs in simultaneous groups ?

  The SAP error message "MPE_RTG_UI115 SAS containing status scrap not allowed for OAs in simultaneous groups" typically occurs in the context of production or maintenance processes within SAP, particularly when dealing with operations (OAs) that are part of simultaneous groups. This error indicates that there is an issue with the status of certain operations that are marked as "scrap," which is not permitted in the context of simultaneous processing.
  Cause:
  
  
  Simultaneous Groups: The error arises when you attempt to process operations that are part of a simultaneous group, and one or more of those operations are marked as scrap. In SAP, operations in a simultaneous group are expected to be processed together, and having one marked as scrap can lead to inconsistencies.
  
  
  Status Configuration: The configuration of the operation statuses may not allow for scrap status when operations are grouped together. This is often a result of business rules or system settings that prevent scrap operations from being processed in conjunction with other operations.
  
  
  Data Integrity Issues: There may be data integrity issues where the status of operations is not correctly aligned with the expected workflow or process.
  
  
  Solution:
  
  
  Review Operation Status: Check the status of the operations in the simultaneous group. If any operation is marked as scrap, consider whether it should be removed from the group or if its status should be changed.
  
  
  Adjust Grouping: If the operations need to be processed together, ensure that none of them are marked as scrap. You may need to separate the scrap operation from the simultaneous group.
  
  
  Configuration Settings: Review the configuration settings in SAP related to operation statuses and simultaneous processing. Ensure that the settings align with your business processes and allow for the necessary flexibility.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling simultaneous groups and operation statuses. This may provide insights into best practices and configuration options.
  
  
  Contact Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert who can provide tailored assistance based on your specific system configuration and business processes.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide updates and patches that could resolve the issue.
  Transaction Codes: Familiarize yourself with relevant transaction codes (e.g., CO02 for order confirmation, COHV for mass processing) that may help in managing operations and statuses.
  User Forums: Engage with SAP user forums or communities where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.