How To Fix ECCEDI135 - Error reading service provider &1 (external number &2)


SAP Error Message - Details

  • Message type: E = Error

  • Message class: ECCEDI - IS-U Deregulation: IDoc Processing

  • Message number: 135

  • Message text: Error reading service provider &1 (external number &2)

  • Show details Hide details


  • 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 ECCEDI135 - Error reading service provider &1 (external number &2) ?

    The SAP error message ECCEDI135, which states "Error reading service provider &1 (external number &2)," typically occurs in the context of Electronic Data Interchange (EDI) or when dealing with service providers in SAP systems. This error indicates that the system is unable to retrieve information about a specified service provider, which can be due to various reasons.

    Causes:

    1. Incorrect Service Provider Configuration: The service provider may not be correctly configured in the system, or the details may be incomplete or incorrect.
    2. Missing Master Data: The service provider might not exist in the master data tables, or the relevant data might be missing.
    3. Authorization Issues: The user may not have the necessary authorizations to access the service provider data.
    4. Data Consistency Issues: There may be inconsistencies in the data, such as missing entries or incorrect relationships between entities.
    5. Technical Issues: There could be underlying technical issues, such as database connectivity problems or issues with the EDI subsystem.

    Solutions:

    1. Check Service Provider Configuration:

      • Verify that the service provider is correctly configured in the system. Check the configuration settings in the relevant transaction codes (e.g., WE20 for partner profiles).
      • Ensure that the external number (e.g., EDI ID) is correctly assigned to the service provider.
    2. Verify Master Data:

      • Check the master data for the service provider in the relevant tables (e.g., LFA1 for vendors, KNA1 for customers).
      • Ensure that the service provider exists and that all required fields are populated.
    3. Review Authorizations:

      • Ensure that the user encountering the error has the necessary authorizations to access the service provider data.
      • Check the authorization roles assigned to the user and make adjustments if necessary.
    4. Data Consistency Check:

      • Perform a consistency check on the relevant data to identify any discrepancies or missing entries.
      • Use transaction codes like SE11 or SE16 to inspect the relevant database tables.
    5. Technical Troubleshooting:

      • Check for any technical issues that may be affecting the EDI subsystem or database connectivity.
      • Review system logs (transaction SM21) for any related error messages that could provide additional context.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as WE20 (Partner Profiles), WE21 (Port Definition), and WE02 (EDI Audit Log) for troubleshooting EDI-related issues.
    • SAP Notes: Search for SAP Notes related to ECCEDI135 for any known issues or patches that may address the error.
    • Documentation: Review SAP documentation on EDI and service provider configuration for best practices and troubleshooting steps.

    If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or EDI support team for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author