How To Fix /ISDFPS/PM_CP138 - Cannot determine recipient port for EDI partner &1/&2

SAP Error Message - Details

• Message type: E = Error

• Message class: /ISDFPS/PM_CP -

• Message number: 138

• Message text: Cannot determine recipient port for EDI partner &1/&2

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 /ISDFPS/PM_CP138 - Cannot determine recipient port for EDI partner &1/&2 ?

  The SAP error message /ISDFPS/PM_CP138 Cannot determine recipient port for EDI partner &1/&2 typically occurs in the context of Electronic Data Interchange (EDI) when the system is unable to find the appropriate communication port for a specified EDI partner. This can happen for various reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Missing Configuration: The communication port for the specified EDI partner is not configured in the system.
  Incorrect Partner Profile: The partner profile for the EDI partner may not be set up correctly or is missing.
  Incorrect Partner Type: The partner type (e.g., vendor, customer) may not be correctly defined in the system.
  Inactive Port: The port that is supposed to be used for communication may be inactive or not properly set up.
  Transport Layer Issues: There may be issues with the transport layer settings that prevent the system from determining the correct port.
  
  Solutions:
  
  
  Check Partner Profile:
  
  Go to transaction code WE20 and check the partner profile for the EDI partner. Ensure that the correct port is assigned to the partner.
  Verify that the partner type is correctly defined.
  
  
  
  Configure Communication Port:
  
  Go to transaction code WE21 to check the configuration of the communication ports.
  Ensure that the port is defined and active. If it is missing, create a new port and assign it to the partner profile.
  
  
  
  Verify Port Settings:
  
  Ensure that the port settings (e.g., IDoc, RFC, file) are correctly configured based on the communication method being used.
  
  
  
  Check for Inactive Ports:
  
  If the port is inactive, activate it or create a new one as needed.
  
  
  
  Review EDI Settings:
  
  Check the overall EDI settings in your SAP system to ensure that everything is configured correctly for EDI communication.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to EDI configuration for any specific requirements or updates.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  WE20: Partner Profiles
  WE21: Ports
  WE30: IDoc Types
  WE02: IDoc Display
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to EDI partner configuration or the error message in question.
  
  
  Testing: After making changes, test the EDI communication to ensure that the issue is resolved.
  
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis or EDI team for further investigation, as they may have additional insights or access to logs that can help diagnose the issue.