Notes on Copying Groups

To copy groups, you have the following options:

To copy the group, you enter a supplementary key as a suffix. The copy receives a new name through the attachment of the suffix to the original name of the group node. If a suffix already exists, this will be replaced by the new suffix.
Copy and original are two separate, independent structures.
Example:
CO area 0001, group HIER
-> CO area 0001, group HIER.1997
In this case, you create a new group based on a reference group from another controlling area or chart of accounts.
The complete structure and name are copied from the current controlling area/chart of accounts.
Copy and original are two separate, independent structures.
Example:
CO area 0001, group HIER
-> CO area 9999, group HIER
This does not apply to order groups because they are not assigned to a controlling area or chart of accounts.
In this case, you create a new group based on a reference group from the same controlling area or chart of accounts.
The highest node holds the given group name, and the existing structure attaches to the highest node. All changes in the original automatically affect the copy as well.
Example:
CO area 0001, group HIER --> CO area 0001, group NEW_HIER
| |
+-> Node 1 +-> Node 1
+-> Node 2 +-> Node 2

When copying groups, the R/3 System checks whether group nodes with the copy name exist in the system. If at least one exists, the R/3 System asks whether it should overwrite all existing group nodes or whether it should not carry out copying. The standard hierarchy is exempt from this overwriting function.

Copying groups is especially useful when you want to freeze the characteristics of a group with time-based dependencies for objects at a given time in order to make changes affecting the following fiscal year.

Example: Copying Groups