How To Fix /PF1/MSG_CP350 - Maximum number of payment items &1 pieces was reached

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/MSG_CP -

• Message number: 350

• Message text: Maximum number of payment items &1 pieces was reached

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_CP350 - Maximum number of payment items &1 pieces was reached ?

  The SAP error message /PF1/MSG_CP350 Maximum number of payment items &1 pieces was reached typically occurs in the context of payment processing, particularly when dealing with payment runs or payment proposals in the SAP system. This error indicates that the maximum limit for the number of payment items has been exceeded.
  Cause:
  
  Configuration Limits: The system has a predefined limit for the number of payment items that can be processed in a single payment run. This limit is set in the configuration and can vary based on the organization's requirements.
  Data Volume: If a payment run is attempting to process a large number of invoices or payment items, it may exceed the configured limit.
  Batch Processing: The error may also occur if the payment items are being processed in batches and the batch size exceeds the allowed limit.
  
  Solution:
  
  
  Check Configuration: Review the configuration settings in the SAP system to determine the maximum number of payment items allowed. This can typically be found in the payment program settings (Transaction code: OBPM1 or similar).
  
  Navigate to SPRO > Financial Accounting > Accounts Payable > Payment Transactions > Define Payment Program.
  Look for settings related to the maximum number of payment items.
  
  
  
  Adjust Limits: If necessary, adjust the configuration to increase the maximum number of payment items allowed. Ensure that this change aligns with your organization's processing capabilities and performance considerations.
  
  
  Split Payment Runs: If increasing the limit is not feasible or advisable, consider splitting the payment run into smaller batches that do not exceed the maximum limit. This can be done by selecting a smaller range of invoices or payment items for processing.
  
  
  Review Payment Proposal: Check the payment proposal to ensure that it is not including unnecessary items. You can filter or modify the selection criteria to reduce the number of items being processed.
  
  
  Consult Documentation: Refer to SAP documentation or support notes for any specific guidance related to this error message, as there may be additional context or updates provided by SAP.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F110 (Automatic Payment Transactions) and F111 (Manual Payment Transactions) for managing payment runs.
  Performance Considerations: Be aware that increasing the number of payment items may impact system performance, especially during peak processing times.
  Testing Changes: Always test configuration changes in a development or quality assurance environment before applying them to the production system to avoid unintended consequences.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or functional team for further investigation and support.