Generic Boxed Components for Business Object Extensibility

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional business process platforms face challenges in supporting multiple clients with client-specific extension fields, as they struggle to efficiently generate proxy objects and manage extension fields across different business objects, leading to complexities in data storage and access.

Innovation Solution

The implementation of a system that uses reference field bundles and metadata repositories to facilitate the addition of client-specific extension fields to business objects, allowing for dynamic extensibility and client-dependent metadata management, enabling seamless integration with user interfaces and data storage systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional application platforms support extension fields to nodes of existing business objects, then data associated with extension fields can be stored in primary persistency, but systems struggle to efficiently generate proxy objects and manage extension fields across different business objects in multi-client systems

Engineering Contradiction:

Improveextensibility of business objectsVSAvoidcomplexity of proxy object generation and extension field management

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments extension field management by introducing a metadata repository that separates extension field definitions from core business object structures. Extension fields are stored as distinct metadata entries with associations to specific business objects and clients, allowing independent management and retrieval without affecting core object integrity or other clients' extensions.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A metadata repository acts as an intermediary layer between the core business object system and extension field requirements. This repository stores extension field definitions, data types, and client associations, serving as a centralized mediation point that enables proxy objects to access extension fields without direct coupling to the core business object structures.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If a business process platform operates on proxy objects corresponding to supported business objects, then business logic can be executed, but generating proxy objects that incorporate client-specific extension fields creates management complexities

Engineering Contradiction:

Improveexecution of business logicVSAvoidcomplexity of proxy object generation

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by pre-storing extension field definitions, data types, and client associations in the metadata repository before proxy objects are generated. This advance preparation allows proxy objects to be constructed efficiently by retrieving pre-defined extension field metadata rather than creating extension field structures dynamically during proxy generation.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system uses copying by creating metadata representations of extension fields in the repository that can be replicated and associated with multiple business objects and clients. Extension field definitions are copied and adapted to different contexts without modifying the core business object structures, enabling efficient proxy object generation with client-specific extensions.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If multiple clients require different extension fields on the same business object, then client-specific requirements can be met, but data storage and access becomes complex

Engineering Contradiction:

Improveclient-specific extension field supportVSAvoidcomplexity of data storage and access

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system applies local quality by associating extension field metadata with specific client identifiers in the metadata repository. Each client's extension fields are stored with client-specific context, allowing the system to retrieve and apply only the relevant extension fields for each client's business objects, maintaining data organization without requiring separate storage systems for each client.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The metadata repository provides universality by serving as a single data storage and access mechanism for all clients' extension fields. The repository structure accommodates multiple clients, business objects, and extension field types within a unified system, eliminating the need for separate storage systems while maintaining client-specific data organization through metadata associations.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS8489640B2Field extensibility using generic boxed components

Publication Date: 2013.07.16 SAP SE

AI summary

A system may include reception of a definition of an extension field to be added to a business object node, generation of metadata for a data type enhancement object associated with the extension field, and generation of an ABAP dictionary proxy object based on the data type enhancement object, wherein the ABAP dictionary proxy object describes the extension field in a sub-structure of a first field of the ABAP dictionary proxy object.