SAP MDG · MDG FINANCE

What upload modes are available for hierarchy maintenance in SAP MDG, and how do they behave for synchronized and non-synchronized hierarchies?

SAP MDG hierarchy maintenance supports five upload modes: Delete All, Overwrite or Add, Move Children, Replace Nodes, and Remove Edges. The safest choice depends on whether you need to delete everything, add missing edges only, re-parent children, replace a parent’s direct children, or delete only explicit edges; synchronized hierarchies can impact multiple hierarchies because technical edges are shared.

SAP MDG hierarchy maintenance supports five upload modes: Delete All, Overwrite or Add, Move Children, Replace Nodes, and Remove Edges. The safest choice depends on whether you need to delete everything, add missing edges only, re-parent children, replace a parent’s direct children, or delete only explicit edges; synchronized hierarchies can impact multiple hierarchies because technical edges are shared.

SAP MDG hierarchy upload offers five modes, each with a different impact on existing edges and child assignments. The most important distinction is whether the hierarchy is synchronized or non-synchronized, because synchronized hierarchies can share technical edges across multiple hierarchies. The guide also shows that Delete All is broad, Overwrite or Add is non-destructive, Move Children re-parents nodes, Replace Nodes rebuilds direct children, and Remove Edges deletes only the explicit edges.

Process flow

  1. Identify the hierarchy that needs to be maintained.
  2. Determine whether it is synchronized or non-synchronized.
  3. Determine whether it is version-dependent or version-independent.
  4. Select the upload mode according to the required operation.
  5. Define the file structure with the correct header, higher-level node, and lower-level node entity types.
  6. Include the hierarchy name where required by the selected mode and hierarchy type.
  7. Upload the file.
  8. Review the effect carefully, especially for synchronized hierarchies where one technical edge may occur in multiple hierarchies.

Master Data Governance > General Settings > Process Modeling > Hierarchies > Create Hierarchy Versions

Define required hierarchy versions for version-dependent hierarchies.

Master Data Governance > Classic Mode in SAP MDG > Central Governance > Central Governance for Financials > Control of Validation Messages > Change Message Type for Validations

Demonstration-only path used in the guide to change validation message severity from Error to Warning in a playground system.

The remaining configuration, implementation details, and testing guidance continue from this answer more…

Related questions and keywords

Alternative questions

  • Which hierarchy upload mode should I choose in SAP MDG?
  • How do Delete All, Overwrite or Add, Move Children, Replace Nodes, and Remove Edges differ?
  • How can I upload or change hierarchies in MDG?

Possible questions

  • What does Delete All do in MDG hierarchy upload?
  • When should I use Overwrite or Add?
  • How does Move Children behave in synchronized hierarchies?
  • What is the effect of Replace Nodes on child order?
  • When should I use Remove Edges instead of Delete All?

Keywords

SAP MDGhierarchy maintenancefile uploadDelete AllOverwrite or AddMove ChildrenReplace NodesRemove Edgessynchronized hierarchynon-synchronized hierarchyMDG 9.2S/4HANA 1809USMD_HRYCOAFRSFRSIACCOUNT