How To Fix FI339 - Checking old authorization objects is no longer supported

SAP Error Message - Details

• Message type: E = Error

• Message class: FI - TR-FM Funds Management

• Message number: 339

• Message text: Checking old authorization objects is no longer supported

What causes this issue?

Authorization checks for individual master data values using old
authorization objects are no longer supported.
Conversion to the new authorization objects is required.

System Response

The current transaction is terminated.

How to fix this error?

Inform your system administrator about the settings required.
The following steps are required:
Deactivation of the <DS:DE.FM_AUTH_CHECK_OLD>old authorization checks</>
using transaction <ZH>SM30</> and the maintenance view <ZH>VV_FMISPS_4
</>
Introduction of authorization groups for all master data values that
require an authorization check.
Conversion of authorization profiles for all system users to new
authorization objects in Funds Management.

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message FI339 - Checking old authorization objects is no longer supported ?

  The SAP error message FI339, which states "Checking old authorization objects is no longer supported," typically arises when there is an attempt to use outdated authorization checks in the SAP system. This error is often encountered in the context of financial transactions or when accessing certain functionalities that rely on authorization objects.
  Cause:
  
  Outdated Authorization Objects: The error indicates that the system is trying to check authorization against old or deprecated authorization objects that are no longer supported in the current version of SAP.
  Custom Code or Enhancements: Custom programs or enhancements may still reference these old authorization objects, leading to the error when they are executed.
  System Upgrade: If the SAP system has been upgraded, some older authorization checks may have been removed or replaced with new ones.
  
  Solution:
  
  Identify the Authorization Objects: Determine which specific authorization objects are causing the error. This can often be found in the detailed error log or by analyzing the transaction that triggered the error.
  Update Custom Code: If the error is due to custom code, update the code to use the current authorization objects that are supported in the version of SAP you are using.
  Review Authorization Profiles: Check the authorization profiles assigned to users to ensure they are using the correct and updated authorization objects.
  Consult SAP Notes: Look for relevant SAP Notes that may provide guidance on how to resolve issues related to deprecated authorization objects. SAP frequently releases notes that address such issues.
  Testing: After making changes, thoroughly test the affected transactions to ensure that the error is resolved and that users have the appropriate access.
  
  Related Information:
  
  SAP Documentation: Review the official SAP documentation for information on authorization objects and their usage.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have implemented.
  Authorization Management: Familiarize yourself with the authorization management tools in SAP, such as PFCG (Profile Generator), to manage and maintain authorization objects effectively.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or Security team for further assistance.