Ansicht
Dokumentation

V_USMD0028 - Define Scope for Changes

Fill RESBD Structure from EBP Component Structure   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

In this Customizing activity, you can determine the level of freedom with which users can make parallel changes to a hierarchy that belongs to a particular hierarchy type. A change to a hierarchy can comprise adding a node, moving a node, removing a node, changing the attributes of a node, or creating a hierarchy.

After a change to a hierarchy is saved to a change request, changes to interlocked nodes must be saved to the same change request. The system determines which nodes are interlocked by referring to the Interlocking setting for the relevant hierarchy type.

For a full description of the interlocking settings with graphical examples, see Scope for Hierarchy-Specific Changes.

To minimize business disruption, we recommend that you define the scope for changes to a hierarchy type when you define the hierarchy type within a data model. You can only change the scope for changes to a hierarchy type when no pending change requests exist for any hierarchy of this type. If you must change the scope after you have already defined the hierarchy type and then transport your changes, ensure no pending changes exist for the affected hierarchies in the target.

General Data in Customer Master   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 1526 Date: 20240523 Time: 185229     sap01-206 ( 41 ms )