Do you have any question about this error?
Message type: E = Error
Message class: GPD2 - GPD for DIMP4.71 uses message class GPD & GPD2
Message number: 013
Message text: &2 cannot be assigned without an exception WBS on Group &1
Exception handling in pegging refers to the way in which scrap,
surplus, and stock difference ( lost / found ) replenishments are
handled.
Pegging Customizing is defined to have all the exceptions pegged to
exception WBS elements (for each group).
Thus, these exception WBS elements must be defined for each group.
However, such a definition has not been made for each group.
Pegging will not execute until you fix this problem.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
You can take one of the following two steps to fix this problem:
1. Go to Pegging Customizing transaction ( 0PEG01 ) and change the way
exceptions are handled.
2. Go to transaction PEG04 and define exception WBS elements for each
group.
Error message extract from SAP system. Copyright SAP SE.
GPD2013
- &2 cannot be assigned without an exception WBS on Group &1 ?The SAP error message GPD2013 indicates that there is an issue with assigning a project or a cost element to a Work Breakdown Structure (WBS) element in the context of project management. Specifically, the error states that the assignment cannot be made without an exception WBS on the specified group.
Cause:
The error typically arises due to one of the following reasons:
- Missing WBS Element: The system is trying to assign a cost or project element to a WBS element that does not exist or is not properly defined.
- Group Assignment Issues: The group specified in the error message may not have a valid WBS element associated with it, or the WBS element may not be set up to allow the assignment.
- Configuration Issues: There may be configuration settings in the project system that prevent the assignment of certain elements without a valid WBS.
Solution:
To resolve the GPD2013 error, you can take the following steps:
Check WBS Element:
- Verify that the WBS element you are trying to assign to exists and is active.
- Ensure that the WBS element is correctly defined in the system.
Review Group Settings:
- Check the group specified in the error message to ensure it has a valid WBS element associated with it.
- If necessary, create or modify the WBS element to ensure it meets the requirements for the assignment.
Configuration Review:
- Review the configuration settings in the project system to ensure that they allow for the assignment of elements without requiring an exception WBS.
- Consult with your SAP configuration team to ensure that the project management settings are correctly set up.
Consult Documentation:
- Refer to SAP documentation or help resources for additional context on the error message and its implications.
Testing:
- After making the necessary changes, test the assignment again to ensure that the error has been resolved.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant who specializes in SAP Project System (PS) for further assistance.
Get instant SAP help. Start your 7-day free trial now.
GPD2012
&2 cannot be assigned without an exception WBS on Plant &1
What causes this issue? Exception handling in pegging refers to the way in which scrap, surplus, and stock difference (lost / found ) replenishments ...
GPD2011
Please maintain the exception handling WBS elements
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
GPD2014
&3 cannot be assigned without an exception WBS on Plant &1 and Group &2
What causes this issue? Exception handling in pegging refers to the way in which scrap, surplus, and stock difference ( lost / found ) replenishment...
GPD2016
Run pegging for all group involved in group-to-group transfers first.
What causes this issue? The possible causes for this message are: 1. You may not have run pegging for any of the account assignment groups that are ...
Click on this link to search all SAP messages.