Business Object Release Status Codes for Platform Evolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems fail to efficiently facilitate the adaptation of business applications to changes in business objects within an evolving application platform, such as additions, modifications, or deletions, which can disrupt the functionality of business applications.

Innovation Solution

The implementation of a business object release status code system that provides metadata to indicate the support status of business object entities, allowing for predefined transitions and notifications to developers, enabling them to plan and prepare for upcoming changes, including the use of an Enterprise Services Framework (ESF) and metadata repository to manage and communicate these changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the application platform evolves by adding, modifying, or removing business objects, then the platform's functionality and adaptability improve, but the stability and functionality of existing business applications are disrupted

Engineering Contradiction:
Improveplatform evolution capabilityVSAvoidapplication functionality stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by notifying application developers of planned business object changes before they are implemented. This advance notification allows developers to prepare and adapt their applications proactively, preventing functionality disruptions when changes are deployed to the live platform.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system establishes a feedback mechanism where the application platform communicates change information back to application developers through notifications. This feedback loop enables developers to understand upcoming changes and take appropriate actions to maintain application functionality across platform evolutions.

Inventive Principle:
Principle #23Feedback

2Reliability

If business applications are modified to adapt to changing business objects, then the applications remain functional, but the development time and complexity increase

Engineering Contradiction:
Improveapplication functionalityVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

By providing advance notification of planned changes, the system enables developers to schedule and perform adaptations during planned maintenance windows or development cycles, rather than dealing with unexpected disruptions that would require immediate, rushed modifications.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The notification system acts as an intermediary that bridges the application platform and application developers. It translates platform evolution plans into actionable information for developers, enabling systematic adaptation planning without requiring constant direct communication or manual tracking of platform changes.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If developers are notified of every business object change, then application adaptability improves, but the information overload and complexity for developers increase

Engineering Contradiction:
Improveapplication adaptation capabilityVSAvoidnotification system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The notification system provides localized, targeted information to developers based on their specific applications and the business objects they use. Rather than notifying developers of all platform changes universally, the system filters and delivers only relevant change information to each developer, reducing information overload while maintaining comprehensive adaptability.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8555248B2Business object change management using release status codes
Publication Date: 2013.10.08 SAP SE
  • US8555248B2 patent drawing
  • US8555248B2 patent drawing
  • US8555248B2 patent drawing

AI summary

A computer-implemented system may include a data store to store business data, an application platform, and a business application. The application platform may include a repository to store metadata defining a plurality of business objects, each of the business objects comprising a respective model of data and associated logic, each business object associated with respective business object entities, and a framework in communication with the repository to provide access to the business data. The business application is to access the data via the framework and based on the metadata, wherein the metadata associates a first plurality of the business object entities with a RELEASED release status code, and wherein the metadata associates a second plurality of the business object entities with a DEPRECATED release status code.