How To Fix WGDS_CONFIRMATION120 - ***** AUTHORIZATION FAILED (121-129) ************************************

SAP Error Message - Details

• Message type: E = Error

• Message class: WGDS_CONFIRMATION - Confirmation messages

• Message number: 120

• Message text: ***** AUTHORIZATION FAILED (121-129) ************************************

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message WGDS_CONFIRMATION120 - ***** AUTHORIZATION FAILED (121-129) ************************************ ?

  The SAP error message:
  **WGDS_CONFIRMATION120 * AUTHORIZATION FAILED (121-129) **
  typically occurs in the context of Warehouse Management (WM) or Extended Warehouse Management (EWM) during confirmation or posting processes.
  
  Cause
  
  Authorization Issue: The user performing the confirmation or posting does not have the required authorizations to execute the transaction or function.
  The error code range (121-129) indicates specific authorization objects or fields that are missing or insufficient.
  This can happen if the user lacks permissions for:
  
  Posting goods movements in WM/EWM
  Confirming warehouse tasks
  Accessing specific warehouse numbers or storage types
  Executing certain transaction codes related to warehouse confirmation
  
  
  
  
  Solution
  
  
  Check User Authorizations:
  
  Identify the user who encountered the error.
  Use transaction SU53 immediately after the error occurs to display the last failed authorization check.
  Analyze the missing authorization objects and fields.
  
  
  
  Review Authorization Objects:
  
  Common authorization objects related to WM/EWM confirmations include:
  
  L_TCODE (Transaction Codes)
  L_WARE (Warehouse Number)
  L_EWMW (EWM Warehouse)
  L_EWMT (EWM Task)
  M_MSEG_WM (Material Document WM)
  S_TCODE (Transaction Code)
  
  
  Ensure the user has the necessary values assigned for these objects.
  
  
  
  Adjust Roles and Profiles:
  
  Update the user’s roles in PFCG to include the required authorizations.
  If necessary, create or modify roles to grant access to the relevant warehouse numbers, storage types, and transactions.
  
  
  
  Test After Changes:
  
  After updating authorizations, have the user retry the confirmation process.
  Use SU53 again if the error persists to verify if any other authorizations are missing.
  
  
  
  
  Related Information
  
  Transaction Codes:
  
  WM confirmation transactions like /SCWM/CONF (EWM confirmation)
  Warehouse task processing transactions
  
  
  SAP Notes:
  
  Check SAP Notes related to authorization errors in WM/EWM confirmation.
  
  
  SAP Help Portal:
  
  Documentation on Warehouse Management authorization objects and roles.
  
  
  Common Authorization Objects in WM/EWM:
  
  L_WARE – Warehouse Number
  L_EWMW – EWM Warehouse Number
  L_EWMT – EWM Warehouse Task
  M_MSEG_WM – Material Document for WM
  S_TCODE – Transaction Code
  
  
  
  
  Summary
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  User lacks required authorizations for warehouse confirmation/posting (authorization failure).
  
  
  Solution
  Use SU53 to identify missing authorizations, then update user roles in PFCG accordingly.
  
  
  Related
  Authorization objects: L_WARE, L_EWMW, L_EWMT, M_MSEG_WM, S_TCODE; WM/EWM confirmation transactions.
  
  
  
  
  If you provide the exact transaction or process step where the error occurs, I can help identify the precise authorization objects to check.