How To Fix IHC395 - Payment Order &1 is blocked

SAP Error Message - Details

• Message type: E = Error

• Message class: IHC - IHC Messages

• Message number: 395

• Message text: Payment Order &1 is blocked

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 IHC395 - Payment Order &1 is blocked ?

  The SAP error message IHC395, which states "Payment Order &1 is blocked," typically occurs in the context of the SAP Intercompany Financial Management (IHC) module. This error indicates that a specific payment order has been blocked for processing, which can happen for various reasons.
  Causes of the Error:
  
  
  Blocking Reasons: The payment order may be blocked due to specific criteria set in the system, such as:
  
  Missing or incorrect data in the payment order.
  Compliance checks that have not been met.
  Manual blocking by a user or system administrator.
  Issues with the payment method or bank details.
  
  
  
  Configuration Issues: There may be configuration settings in the IHC module that are causing the payment order to be blocked.
  
  
  Authorization Issues: The user attempting to process the payment order may not have the necessary authorizations to do so.
  
  
  Technical Issues: There could be underlying technical issues, such as system errors or inconsistencies in the database.
  
  
  Solutions:
  
  
  Check Payment Order Details: Review the payment order details for any missing or incorrect information. Ensure that all required fields are filled out correctly.
  
  
  Review Blocking Reasons: Use transaction codes like IHC1 or IHC2 to check the blocking reasons for the payment order. This can provide insights into why the order is blocked.
  
  
  Authorization Check: Ensure that the user has the necessary authorizations to process the payment order. This may involve checking user roles and permissions.
  
  
  Configuration Review: If the issue is related to configuration, consult with your SAP Basis or IHC configuration team to review the settings related to payment processing.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the IHC module for any specific guidance on handling blocked payment orders.
  
  
  Contact Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP support for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FBZP (Payment Program Configuration) and F110 (Automatic Payment Transactions) for managing payment processes.
  SAP Notes: Check for any SAP Notes related to IHC and payment processing that may provide additional insights or patches.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the IHC395 error and take appropriate action to resolve it.