How To Fix /SRMSMC/ROS_EXT006 - Supplier & has been informed about rejection

SAP Error Message - Details

• Message type: E = Error

• Message class: /SRMSMC/ROS_EXT -

• Message number: 006

• Message text: Supplier & has been informed about rejection

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SRMSMC/ROS_EXT006 - Supplier & has been informed about rejection ?

  The SAP error message /SRMSMC/ROS_EXT006 typically indicates that a supplier has been informed about a rejection related to a specific transaction or process in the Supplier Relationship Management (SRM) module. This error can occur in various contexts, such as during the processing of purchase orders, contracts, or other procurement-related activities.
  Cause:
  The error message usually arises due to one of the following reasons:
  
  
  Rejection Notification: The supplier has been notified about a rejection of a document (e.g., a purchase order or a request for quotation) that they submitted. This could be due to various reasons such as incorrect data, compliance issues, or failure to meet certain criteria.
  
  
  System Configuration: There may be issues with the configuration of the SRM system, particularly in how notifications and rejections are handled.
  
  
  Data Issues: There could be inconsistencies or errors in the data related to the supplier or the transaction that led to the rejection.
  
  
  Workflow Issues: If there are workflow processes in place for handling supplier communications, any issues in these workflows could lead to this error.
  
  
  Solution:
  To resolve the /SRMSMC/ROS_EXT006 error, consider the following steps:
  
  
  Review the Rejection Reason: Check the specific rejection reason provided in the system. This will give you insights into why the supplier was informed about the rejection.
  
  
  Communicate with the Supplier: If necessary, reach out to the supplier to clarify the rejection and discuss any required actions or corrections.
  
  
  Check System Configuration: Review the configuration settings in the SRM system to ensure that they are set up correctly for handling supplier notifications and rejections.
  
  
  Data Validation: Validate the data associated with the transaction to ensure that all required fields are correctly filled and that there are no inconsistencies.
  
  
  Workflow Monitoring: If workflows are involved, monitor them for any errors or issues that may have caused the rejection notification to be sent incorrectly.
  
  
  Consult Documentation: Refer to SAP documentation or support resources for more detailed information on the error message and potential fixes.
  
  
  SAP Support: If the issue persists, consider reaching out to SAP support for assistance, especially if it appears to be a system-related issue.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP SRM that may help in troubleshooting, such as BBP_PD for processing purchase orders or BBP_CTR for managing contracts.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific fixes or patches.
  User Forums: Engage with SAP user communities or forums where similar issues may have been discussed, providing insights or solutions from other users' experiences.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.