Message type: E = Error
Message class: 1Q - Messages In-House Banking
Message number: 356
Message text: No authorization for payment order &1
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.
Processing is terminated.
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.
Error message extract from SAP system. Copyright SAP SE.
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 transaction SU01 or PFCG to ensure they have the necessary permissions.
Modify Authorization Roles:
- If the user lacks the required authorizations, work with your SAP security team to update the user’s roles or create new roles that include the necessary authorizations for payment processing.
Review Authorization Objects:
- Check the relevant authorization objects (e.g., F_BKPF_BES, F_BKPF_AKT) to ensure that the user has the correct values assigned for the fields (like activity, company code, etc.).
Payment Order Status:
- Verify the status of the payment order. If it requires approval, ensure that the user has the necessary rights to approve or process it.
Consult Documentation:
- Refer to SAP documentation or your organization’s internal guidelines for specific authorization requirements related to payment processing.
Related Information:
If the issue persists after checking the above points, it may be necessary to engage with your SAP Basis or Security team for further investigation and resolution.
1Q355 Warning: Posted payment order found, run in display mode
What causes this issue? The selection contains at least one posted payment orde...
1Q354 No payment item found, payment order &1 is skipped
What causes this issue? No payment items exist for the payment order selected.S...
1Q357 No payment note found
What causes this issue? None of the payment items selected have a payment note....
1Q358 Error in posting payment order &1
What causes this issue? An error occurs during the posting update run. The data...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.