How To Fix GPD2036 - Pegging and distribution for grouping WBS &1 locked by user &2

GPD2036 - Overview

• Message type: E = Error

• Message class: GPD2 - GPD for DIMP4.71 uses message class GPD & GPD2

• Message number: 036

• Message text: Pegging and distribution for grouping WBS &1 locked by user &2

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 GPD2036 - Pegging and distribution for grouping WBS &1 locked by user &2 ?

  The SAP error message GPD2036 indicates that there is an issue with pegging and distribution for a specific Work Breakdown Structure (WBS) element, which is currently locked by another user. This typically occurs in the context of project management and resource planning within SAP.
  
  Cause:
  
  User Lock: The WBS element is being accessed or modified by another user, which prevents your transaction from proceeding.
  Transaction in Progress: Another transaction that involves the same WBS element is currently being processed, leading to a lock.
  System Configuration: There may be specific configurations or settings in the system that enforce locking mechanisms for certain operations.
  
  
  Solution:
  
  Identify the Locking User: Check who is currently using the WBS element. You can do this by using transaction code SM12 to view the locks in the system. Look for the user ID mentioned in the error message.
  Wait for Release: If the locking user is performing a legitimate operation, you may need to