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

FI339 - Overview

• 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.

FI339 - Details

• 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