The Data Management copy process enforces global uniqueness of WBS template IDs, even across legal entities, and does not regenerate WBS hierarchy IDs during copy, even when “auto‑generate” options are

enabled.

The WBS ID conflict during “Copy into legal entity” is expected behavior by design.

When copying WBS templates between legal entities using Data Management → Copy into legal entity, the system:

• Treats WBS template IDs and hierarchy IDs as business keys
• Reuses the same hierarchy structure and IDs from the source legal entity
• Enforces ID uniqueness at the application level, not just per legal entity

As a result:

• If the same WBS template ID already exists (or previously existed) in the destination legal entity, the copy fails with a key already exists error.
• This behavior applies even though:
• You are copying templates, not transactions
• The ID hierarchy is mandatory
• “Auto‑generate” is enabled

Auto‑generate does not apply during Copy into legal entity for WBS templates. It only applies during manual creation of new WBS structures.

The reason why the ID hierarchy cannot be removed or ignored is that

• The WBS hierarchy is part of the primary key definition for the template
• Data Management does not support key transformation or remapping during legal entity copy

I suggest that the business key for WBS template entities should be based only on WBS ID and not on the ID hierarchy to allow the template copy between legal entities.