How To Fix 1Q356 - No authorization for payment order &1

1Q356 - Overview

• Message type: E = Error

• Message class: 1Q - Messages In-House Banking

• Message number: 356

• Message text: No authorization for payment order &1

What causes this issue?

During a posting update run, the system checks if the user is
authorized to post the payment order. The user has no authorization for
this payment order.

System Response

Processing is terminated.

How to fix this error?

CHeck:
1) if the user has the relevant authorization to post payment orders;
2) if the amount-dependent posting of payment orders is set correctly
in the IMG. Please also consider the documentation on the FX netting
report.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 1Q356 - No authorization for payment order &1 ?

  The SAP error message 1Q356: No authorization for payment order &1 typically indicates that the user attempting to process a payment order does not have the necessary authorizations to perform that action. This can occur in various SAP modules, particularly in Financial Accounting (FI) or Treasury and Risk Management (TRM).
  
  Cause:
  
  Missing Authorization Roles: The user may not have the required roles or authorizations assigned in their user profile to execute payment orders.
  Authorization Object Restrictions: The authorization objects related to payment processing (e.g., F_BKPF_BES, F_BKPF_AKT) may not be properly configured for the user.
  Payment Order Status: The payment order may be in a status that requires additional authorizations (e.g., if it is pending approval).
  Company Code Restrictions: The user may not have access to the specific company code associated with the payment order.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to analyze the missing authorizations.
  Review the user’s roles and profiles in