Aligned Purpose Disassociation in Multi-System Landscapes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In a multi-system landscape, distributed end of purpose checks and purpose disassociations can lead to inconsistencies and errors due to lack of alignment, causing one system to disassociate a purpose from an object only to have another system replicate it back with the purpose attached, and new transactional data referencing master data objects can result in unexpected errors.

Innovation Solution

An aligned purpose disassociation approach where each system performs a local 'can disassociate purpose' decision without actual disassociation, and a central component evaluates these decisions to provide disassociation instructions to systems, ensuring synchronized disassociation across the landscape.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If distributed end of purpose checks are performed independently by each system, then each system can make local disassociation decisions autonomously, but inconsistencies and errors occur when one system disassociates a purpose from an object only to have another system replicate it back with the purpose attached

Engineering Contradiction:
Improveautonomous decision-makingVSAvoiddata consistency
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

A central component is introduced as an intermediary to coordinate purpose disassociation decisions across multiple systems. Each system sends its local can-disassociate status to the central component, which evaluates all statuses and determines a central disassociate purpose decision. This mediator ensures that all systems remain synchronized and prevents the inconsistency problem where one system disassociates a purpose only to have another system replicate it back.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If synchronous calls are used to ensure alignment across systems, then data consistency is maintained, but the process becomes time-consuming

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

Solution Approach 1:

Each system performs a preliminary local evaluation and determines its can-disassociate status in advance, without waiting for other systems. These preliminary decisions are then submitted to the central component for coordinated final determination. This preliminary action reduces the need for time-consuming synchronous calls while maintaining consistency through the central coordination mechanism.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If systems perform local can-disassociate decisions independently, then processing speed increases, but regulatory compliance may be compromised due to lack of alignment

Engineering Contradiction:
Improveprocessing speedVSAvoidregulatory compliance
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The central component collects feedback from all systems in the form of can-disassociate statuses, evaluates this feedback comprehensively, and generates a central disassociate purpose decision that ensures regulatory compliance. This feedback mechanism allows systems to operate independently at high speed while the central component maintains alignment and compliance by considering all system perspectives before making the final decision.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11714828B2Aligned purpose disassociation in a multi-system landscape
Publication Date: 2023.08.01 SAP SE
  • US11714828B2 patent drawing
  • US11714828B2 patent drawing
  • US11714828B2 patent drawing

AI summary

The present disclosure involves systems, software, and computer implemented methods for aligned purpose disassociation in a multi-system landscape. One example method includes receiving, from multiple systems, a can-disassociate status for a purpose for an object instance. The status from a respective system can be an affirmative status that indicates that the system can disassociate the purpose from the instance or a negative status that indicates that the system cannot disassociate the purpose from the instance. The received statuses are evaluated to determine a central disassociate purpose decision for the purpose for the instance. The central disassociate purpose decision can be to disassociate the purpose from the instance when no system has the negative status and to not disassociate the purpose from the instance when at least one system has the negative status. The central disassociate purpose decision is provided to at least some of the multiple systems.