Copying 

Procedure

Wählen Sie vom Bild SAP Easy Access aus Logistik  Warenwirtschaft -> Stammdaten -> Artikelhierarchiedaten  Kopieren

In der Eingabemaske der Kopierfunktionalität ist die ID der Hierarchie, aus der kopiert wird (Quellhierarchie), die ID des zu kopierenden Knotens der Quellhierarchie und die ID der Hierarchie und der Vaterknoten ID der Zielhierarchie, unter den der Knoten kopiert werden soll einzugeben. Falls der zu kopierende Knoten bereits in der Zielhierarchie existiert, wird der User darauf hingewiesen, das die Zielhierarchiedaten überschrieben werden. Der User hat die Option die Aktion abzubrechen....

       1.      On the SAP Easy Access screen, choose Logistics ® Retailing ® Master Data ® Article Hierarchy Data ® Copy.

       2.      You can enter the following on the entry screen for the copy function:

¡        ID of the hierarchy from which you are copying (source hierarchy)

¡        ID of the node of the source hierarchy to be copied

¡        ID of the hierarchy and the parent node ID of the target hierarchy to which the node is to be copied

If the node to be copied already exists in the target hierarchy, the system will inform you that the target hierarchy data will be overwritten. You can cancel the action at this point.

The following statements apply for cross-hierarchy copying:

¡        You can only copy structure and article changes into a target hierarchy within the same level. The parent node of the target hierarchy must therefore be assigned to the same hierarchy level as the parent node of the node to be copied.

¡        The node that is to be copied must not exist in the target hierarchy. If a substructure is to be copied to the target hierarchy, the node that contains all other nodes in the substructure as subordinate nodes has to be copied. When copying, all subordinate nodes and articles for the node to be copied are also copied.

¡        If the substructure to be copied already exists in the target hierarchy, the substructure of the target hierarchy is overwritten by the structure to be copied. The system will inform you that existing data in the target hierarchy will be overwritten. You can cancel the action at this point.

As every article hierarchy can be characterized by characteristics, such as, status, scheduling, multiple article assignments, and number assignment, rules (conditions) for when cross-hierarchy copying is permitted are required:

¡        Hierarchy status

You can copy from a planned to an active article hierarchy and vice versa. Cross-hierarchy copying of hierarchies with the same status is also permitted.

¡        Distribution chain

A simulation is permitted in every conceivable constellation.

¡        Internal/external number assignment

With both external and internal number assignment, the nodes to be copied are created with the identical node ID in the target hierarchy to ensure a consistent copy logic. Every node ID to be copied is checked to make sure it is unique in the target hierarchy. The nodes are only copied to the target hierarchy if the node IDs do not yet exist in the target hierarchy.

To plan changes to the active article hierarchy, the activated article hierarchy can be chosen as a template (creation with template) for a new planned hierarchy. The external or internal node IDs in the template hierarchy are copied 1:1 into the planned hierarchy, so that enhancements can be entered in the planned article hierarchy and then copied to the active article hierarchy.

¡        Scheduling

Cross-hierarchy copying is permitted if schedules either can or cannot be defined for both the source and the target hierarchy.

The following logic applies for cross-hierarchy copying of scheduled node and article assignments to a target hierarchy:

§         Expired assignments in the substructure to be copied are not copied to the target hierarchy. If the assignment to be copied exists in the target hierarchy, and the valid-to date is later than the current date, the assignment is ended with the current date (logically deleted).

§         Valid assignments of the substructure to be copied are created in the target hierarchy with the current date.

§         Future assignments in the substructure to be copied are to the target hierarchy exactly as they are.

§         In the case of deletion, assignments that are scheduled in the future or are not scheduled and that are deleted in the source hierarchy, are deleted in the target hierarchy during copying.

The system issues a message that assignments will not be copied or will be copied with the current date.

¡        Multiple article assignment

Cross-hierarchy copying is permitted if multiple article assignment is either activated or deactivated in both the source and target hierarchy.

¡        BW Extraction

If BW extraction is active, the (scheduled) changes are to be updated in the extract structures when node and article assignments are copied to an activated article hierarchy.

The following checks, which run in article hierarchy maintenance, are also available for cross-hierarchy copying:

¡        Check whether all articles are attached to end nodes (this check can be switched off for value-only articles in Customizing):

Articles that are copied to an activated article hierarchy must be assigned to end nodes (nodes without subordinate nodes) in the structure to be copied.

¡        Check for attribute required entry field:

When copying changes to an activated article hierarchy, a check can be run to see whether an attribute assignment is mandatory for the node assignments to be copied.

¡        Check whether the node IDs of the nodes to be copied are unique in the target hierarchy.

¡        Check that articles to be copied are uniquely assigned within a category if the Multiple Article Assignment indicator is set in the target hierarchy.

¡        Check whether the validity of the node assignment to be copied is within the validity period of the parent node assignment of the target hierarchy.

¡        Check for authorization to process the hierarchy objects (article, structure).

The following checks are also available within cross-hierarchy copying:

¡        When copying non-scheduled changes, node and article assignments that are deleted in the source hierarchy are also deleted in the target hierarchy. A check is run to see whether the structure to be copied already exists in the target hierarchy and whether it has assignments that are missing in the structure to be copied.

¡        Assignments scheduled for the future that are deleted in the source hierarchy are deleted in the target hierarchy during copying.

You can perform the following checks in a customer enhancement without modifications:

¡        The variants of a generic article can be assigned to different nodes in the article hierarchy. These nodes must only belong to one node in a hierarchy level, however, (for example, subcategory).

¡        The mapping of validity periods with gaps can be stopped by a customer enhancement without modifications.

The OTB-relevant checks (change of assignment for future delivery periods only) are part of article hierarchy maintenance and run for both the planned and the activated article hierarchies. If the substructure to be copied exists in the target hierarchy and if the target hierarchy is active, the changes must be checked with regard to OTB and logged.

If the check for the copy of changes to structures and articles fails, the copying process is cancelled. An error message is issued and the data is not updated.