How To Fix /PF1/MSG_CONV223 - IDOC import of payment run &1 completed; Object list &2/&3

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/MSG_CONV -

• Message number: 223

• Message text: IDOC import of payment run &1 completed; Object list &2/&3

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 /PF1/MSG_CONV223 - IDOC import of payment run &1 completed; Object list &2/&3 ?

  The SAP error message /PF1/MSG_CONV223 typically occurs during the import of an IDoc related to a payment run. This message indicates that the IDoc processing has completed, but there may be issues with the object list specified in the message.
  Cause:
  
  Data Inconsistencies: The IDoc may contain data that does not match the expected format or values in the target system.
  Missing Objects: The objects referenced in the IDoc (like payment documents, vendors, etc.) may not exist in the target system.
  Configuration Issues: There may be configuration settings in the payment run process that are not correctly set up.
  Authorization Issues: The user or process executing the IDoc may not have the necessary authorizations to create or modify the objects referenced in the IDoc.
  
  Solution:
  
  Check IDoc Data: Review the IDoc data for any inconsistencies or errors. Use transaction WE02 or WE05 to analyze the IDoc and check for any error messages or warnings.
  Verify Object Existence: Ensure that all objects referenced in the IDoc (like payment documents, vendors, etc.) exist in the target system. If they do not, you may need to create them or adjust the IDoc data.
  Review Configuration: Check the configuration settings related to the payment run process. Ensure that all necessary settings are correctly configured.
  Authorization Check: Verify that the user or process executing the IDoc has the necessary authorizations to perform the actions required by the IDoc.
  Reprocess IDoc: If the issues are resolved, you can reprocess the IDoc using transaction BD87 or WE19 to test the IDoc processing.
  
  Related Information:
  
  IDoc Types: Familiarize yourself with the specific IDoc type being used for the payment run, as different IDoc types may have different structures and requirements.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance related to this error message.
  Transaction Codes: Use transaction codes like WE02, WE05, BD87, and WE19 for monitoring and troubleshooting IDocs.
  Logs and Traces: Review application logs and traces for additional context on the error, which can provide insights into what went wrong during the IDoc processing.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.