Flexible Data Hierarchy for ERP Organizational Changes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Implementing organizational changes in ERP systems is time-consuming and complex due to the need to analyze and update numerous organizational units within databases, which often use different naming conventions for data, leading to increased complexity.

Innovation Solution

A computer-implemented method for providing a flexible data hierarchy that allows users to define and modify hierarchical structures by assigning sequence placements to attributes, enabling the automatic generation of hierarchical structures and reports, and allowing for user-defined and system-defined attributes to be organized and updated efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional database reorganization methods are used to implement organizational changes, then data accuracy and completeness are improved, but implementation time and system complexity increase significantly

Engineering Contradiction:
Improvedata accuracyVSAvoidimplementation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the hierarchical structure into multiple levels (e.g., country, region, city, department) that can be independently defined and configured. This allows organizational changes to be implemented by modifying individual segments rather than reorganizing the entire database, significantly reducing implementation time while maintaining data accuracy through structured segmentation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-defining hierarchical templates and data structures that can be reused across different organizational contexts. This allows rapid deployment of new organizational structures without starting from scratch, reducing implementation time while ensuring data completeness through pre-established frameworks.

Inventive Principle:
Principle #10Preliminary action

2Stability of the object's composition

If comprehensive database updates are performed to reflect organizational changes, then data consistency across all units is improved, but computational resources and processing time are consumed

Engineering Contradiction:
Improvedata consistencyVSAvoidcomputational resources
Core Design Contradiction:
Stability of the object's compositionVSUse of energy by moving object

Solution Approach 1:

The patent applies local quality by allowing different hierarchical levels and units to have customized attributes and data structures tailored to their specific needs. This enables data consistency to be maintained at each local level independently, avoiding the need for comprehensive global database updates while ensuring consistency within each organizational unit through localized data management.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system performs partial actions by updating only the specific hierarchical segments that require changes rather than performing comprehensive database updates. This selective approach maintains data consistency in affected areas while conserving computational resources by avoiding unnecessary processing of unchanged data.

Inventive Principle:
Principle #16Partial or excessive action

3Stability of the object's composition

If fixed hierarchical structures are used in ERP systems, then system stability and predictability are improved, but flexibility and adaptability to organizational changes are reduced

Engineering Contradiction:
Improvesystem stabilityVSAvoidflexibility
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamics by creating a hierarchical structure that can be dynamically configured and modified at multiple levels. The system maintains stability through a structured framework while enabling flexibility through customizable attributes, dynamic level creation, and the ability to reconfigure hierarchical relationships without system reinstallation, thus adapting to organizational changes while preserving system stability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system applies universality by designing a hierarchical structure that can serve multiple organizational purposes and configurations. The same framework can accommodate different organizational models (functional, divisional, matrix), various hierarchical levels, and customized attributes, providing both stability through a universal framework and flexibility through multi-functional adaptability to different organizational needs.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Measurement precision

If detailed attributes are collected for all organizational units, then reporting accuracy and detail are improved, but data collection complexity and storage requirements increase

Engineering Contradiction:
Improvereporting accuracyVSAvoiddata collection complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies local quality by allowing each organizational unit and hierarchical level to have customized attributes relevant to its specific reporting needs. This enables detailed and accurate reporting at each local level without requiring comprehensive data collection across the entire organization, reducing data collection complexity while maintaining reporting accuracy through localized attribute definition.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11036763B2Flexible organizational hierarchy
Publication Date: 2021.06.15 SAP SE
  • US11036763B2 patent drawing
  • US11036763B2 patent drawing
  • US11036763B2 patent drawing

AI summary

In one general aspect, a method and system are described for providing a flexible data hierarchy. The method may include obtaining a plurality of data sets, the plurality of data sets including system-defined attributes and user-defined attributes, generating, for each attribute in each data set, a field for receiving input, providing, in a user interface display, at least one data set of the plurality of data sets and the generated field for each attribute in the at least one data set, receiving, in two or more of the generated fields, a value indicating a sequence placement for a respective attribute associated with a respective field of the two or more generated fields, and automatically generating, for the attributes associated with the two or more fields having a value, at least one hierarchical structure according to the sequence placement.