How To Fix OIJ_ATL002 - ATL not granted

OIJ_ATL002 - Overview

• Message type: E = Error

• Message class: OIJ_ATL - Authority to Load related messages

• Message number: 002

• Message text: ATL not granted

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

OIJ_ATL002 - Details

• The SAP error message OIJ_ATL002, which states "ATL not granted," typically occurs in the context of the SAP Oil and Gas (OIJ) module, particularly when dealing with the Allocation process. This error indicates that the user does not have the necessary authorization to perform the allocation task.
  
  Cause:
  
  Authorization Issues: The most common cause of this error is that the user lacks the required authorization to execute the allocation transaction or process.
  Role Configuration: The user's role may not be properly configured to include the necessary permissions for the allocation tasks.
  Missing Authorization Objects: The relevant authorization objects that control access to allocation functions may not be assigned to the user's profile.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Verify the user's roles and authorizations in the SAP system.
  Use transaction code SU53 immediately after encountering the error to see which authorization check failed.
  
  
  
  Role Adjustment:
  
  If the user lacks the necessary authorizations, work with your SAP security team to adjust the user's