How To Fix EDI_SD100 - Business system ID &1 not mntnd with type 'ARIBA' in config step 102450.

SAP Error Message - Details

• Message type: E = Error

• Message class: EDI_SD - Messages for EDI SD Integration

• Message number: 100

• Message text: Business system ID &1 not mntnd with type 'ARIBA' in config step 102450.

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 EDI_SD100 - Business system ID &1 not mntnd with type 'ARIBA' in config step 102450. ?

  The SAP error message EDI_SD100 indicates that there is an issue with the configuration of the business system ID in the context of EDI (Electronic Data Interchange) integration, specifically with Ariba. This error typically arises when the system is unable to find a corresponding business system ID that is configured for the type 'ARIBA' in the specified configuration step.
  Cause:
  
  Missing Configuration: The business system ID specified in the error message is not maintained in the relevant configuration settings for EDI with Ariba.
  Incorrect Business System ID: The business system ID may be incorrectly entered or does not exist in the system.
  Type Mismatch: The business system ID may be maintained, but it is not set up with the correct type ('ARIBA').
  Transport Issues: If the configuration was recently transported from another system, the transport may not have included the necessary settings.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the relevant configuration transaction (usually in SPRO) and navigate to the EDI settings for Ariba.
  Verify that the business system ID mentioned in the error message is correctly maintained in the configuration.
  
  
  
  Maintain Business System ID:
  
  If the business system ID is missing, you will need to create or maintain it in the configuration.
  Ensure that it is set with the correct type 'ARIBA'.
  
  
  
  Verify Type:
  
  Ensure that the business system ID is assigned the correct type. If it is not, you will need to change it to 'ARIBA'.
  
  
  
  Check Transport Requests:
  
  If the configuration was recently transported, check the transport requests to ensure that all necessary configurations were included.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to EDI and Ariba integration for any specific requirements or additional steps that may be necessary.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test to ensure that the error is resolved and that EDI transactions can be processed successfully.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as WE20 (Partner Profiles), WE21 (Port Definition), and SPRO (Customizing) for EDI configuration.
  Integration with Ariba: Understand the specific requirements and configurations needed for integrating SAP with Ariba, as this can vary based on the version and setup.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or EDI team for further assistance.