Cutting and Pasting Allows WBS Levels to Be Created With the Same WBS Name
Last updated on JULY 25, 2017
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 6.1 and later
Update baseline error "Errors located: WBS Name: Unique constraint (Parent WBS,Project ID,WBS Name) violated. The value XXXX of the field WBS Name already exists."
When cutting a WBS and pasting to another Project on the same level as another WBS with the same WBS Name, it allows the WBS Name to stay the same, resulting in an error when Updating Baselines.
Cutting from Proj A and pasting to Proj B should not allow a duplicate WBS Name in Project B:
But pasting into Proj B does allow for duplicate WBS Name:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms