How To Fix /ISDFPS/PM_CP135 - EDI partner profiles for &1/&2 do not have to be adjusted

SAP Error Message - Details

• Message type: E = Error

• Message class: /ISDFPS/PM_CP -

• Message number: 135

• Message text: EDI partner profiles for &1/&2 do not have to be adjusted

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_CP135 - EDI partner profiles for &1/&2 do not have to be adjusted ?

  The SAP error message /ISDFPS/PM_CP135 indicates that there is an issue with the EDI partner profiles for the specified partners (represented by &1 and &2). This error typically arises in the context of Electronic Data Interchange (EDI) when the system is unable to find the necessary configuration or settings for the specified partner profiles.
  Cause:
  
  Missing Partner Profiles: The EDI partner profiles for the specified partners may not be set up correctly in the system.
  Incorrect Configuration: There may be incorrect or incomplete configuration settings for the EDI communication.
  Inconsistent Data: The data related to the partners may be inconsistent or not aligned with the expected format.
  System Settings: The system settings for EDI processing may not be properly configured.
  
  Solution:
  
  
  Check Partner Profiles: 
  
  Go to the transaction code WE20 in SAP to check the partner profiles for the specified partners. Ensure that the profiles are correctly defined and activated.
  Verify that the necessary message types and process codes are included in the partner profiles.
  
  
  
  Review EDI Configuration:
  
  Ensure that the EDI configuration settings are complete and correct. This includes checking the logical systems, ports, and other related settings in transaction WE21.
  Make sure that the communication method (e.g., IDoc, FTP, etc.) is properly configured.
  
  
  
  Validate Data:
  
  Check the data being sent or received for any inconsistencies or errors. Ensure that the data format matches the expected structure for the EDI messages.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on EDI configuration and troubleshooting.
  
  
  
  Testing:
  
  After making any changes, perform tests to ensure that the EDI communication works as expected. Use transaction WE19 to simulate the sending of IDocs for testing purposes.
  
  
  
  Contact Support:
  
  If the issue persists after checking the configurations and data, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  WE20: Partner Profiles
  WE21: Ports
  WE19: Test Tool for IDocs
  
  
  Documentation: SAP Help Portal and community forums can provide additional insights and troubleshooting steps.
  Logs: Check the EDI logs (transaction WE02 or WE05) for more detailed error messages that can help identify the root cause.
  
  By following these steps, you should be able to resolve the error message and ensure that the EDI partner profiles are correctly configured.