How To Fix SLS_LO_GAF_EWB009 - No authorization for package &1: Activity &2 (&3)

SLS_LO_GAF_EWB009 - Overview

• Message type: E = Error

• Message class: SLS_LO_GAF_EWB - GAF Enh WB Msg for LO based FPM config sales UI

• Message number: 009

• Message text: No authorization for package &1: Activity &2 (&3)

What causes this issue?

Your user has no development authorization for package &V1&, activity
&V2& (&V3&).

System Response

This is just a warning. This check becomes effective if you later want
to append customer-defined fields to an SAP standard structure and
activate the append structure.
This authorization might not be necessary, for example, if the
customer-defined fields have already been appended to the SAP standard
structure in a previous session.

How to fix this error?

If you want to append customer-defined fields to the SAP standard
structures, contact your system administrator for additional
authorizations for authorization object S_DEVELOP.

Procedure for System Administrators

Grant authorizations for the authorization object S_DEVELOP as follows:
Parameter,,Value
DEVCLASS,,&V1&
OBJTYPE,,Dummy or STRU
OBJNAME,,Dummy or name of append structure to be defined in a later step
P_GROUP,,dummy
ACTVT,,&V2&

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SLS_LO_GAF_EWB009 - No authorization for package &1: Activity &2 (&3) ?

  The SAP error message SLS_LO_GAF_EWB009 indicates that a user does not have the necessary authorization to access a specific package or perform a certain activity within that package. This error typically arises in the context of SAP's logistics or supply chain modules, particularly when dealing with Extended Warehouse Management (EWM) or similar functionalities.
  
  Cause:
  The error message is triggered when:
  
  The user attempts to execute a transaction or access a package for which they lack the required authorization.
  The authorization object associated with the package or activity is not assigned to the user's role.
  There may be a misconfiguration in the authorization profiles or roles assigned to the user.
  
  
  Solution:
  To resolve this issue, you can follow these steps:
  
  
  Check User Roles and Authorizations:
  
  Use transaction code SU01 to display the user profile.
  Check the roles assigned to the user and ensure that the necessary roles include the required authorizations for the package and activity in question.
  
  
  
  Identify Missing Authorizations:
  
  Use transaction