Message type: E = Error
Message class: AA - Messages for Asset Accounting
Message number: 593
Message text: No authorization for company code &
You have <ZH>no</> authorization for the function <ZH>Post Depreciation
</> in company code &V1&.
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 AA593: No authorization for company code & typically indicates that the user attempting to perform an action does not have the necessary authorization to access or perform transactions related to the specified company code. This is a common issue in SAP systems where authorization checks are in place to ensure that users can only access data and perform actions for which they have been granted permission.
Cause:
- Missing Authorization Roles: The user may not have been assigned the appropriate roles that include authorization for the specified company code.
- Authorization Object Restrictions: The authorization objects related to company codes (e.g.,
F_BKPF_BES
,F_LFA1_BES
, etc.) may not include the company code in question for the user.- User Profile Issues: The user profile may not be correctly configured, or the user may be using a different profile that lacks the necessary permissions.
- Changes in Authorization: Recent changes in roles or authorizations may have inadvertently removed access to the company code.
Solution:
Check User Authorizations:
- Use transaction code SU53 immediately after encountering the error to see the last authorization check and identify which authorization is missing.
- Alternatively, use transaction code SU01 to view the user’s roles and authorizations.
Assign Appropriate Roles:
- If the user lacks the necessary roles, work with your SAP security team to assign the appropriate roles that include access to the required company code.
Modify Authorization Objects:
- If the user has the correct roles but still encounters the error, check the relevant authorization objects to ensure that the company code is included in the user’s authorizations.
Consult with Security Team:
- If you are not authorized to make changes, contact your SAP security team or administrator to review and adjust the user’s authorizations as needed.
Testing:
- After making changes, have the user log out and log back in to ensure that the new authorizations take effect. Test the transaction again to confirm that the issue is resolved.
Related Information:
Transaction Codes:
Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to company codes, such as:
F_BKPF_BES
: Authorization for Document ManagementF_LFA1_BES
: Vendor Master DataF_KNA1_BES
: Customer Master DataDocumentation: Review SAP documentation or internal guidelines on user roles and authorizations to understand how to manage and troubleshoot authorization issues effectively.
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Sign up takes 1 minute. 7-day free trial.
AA592 Depreciation key has fewer depreciation types than previously valid key
The system issues an error message and will not allow you to continue with this...
AA591 Depreciation key has more depreciation types than previous deprec. key
Self-Explanatory Message Since SAP believes that this specific error message is ...
AA594 Errors occurred for asset & in fiscal year &
Self-Explanatory Message Since SAP believes that this specific error message is ...
AA595 Company code &1 locked against changes
What causes this issue? Company code &V1& is locked against changes in ...
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.