Dynamic Node Extensions for Business Objects

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional techniques do not allow for the dynamic addition of fields with 1:n cardinality to existing business objects within a business process platform, requiring recompilation of the entire database system and affecting all tenants in a multi-tenant scenario, limiting flexibility and tenant-specific customizations.

Innovation Solution

A system that enables the creation and management of dynamic node extensions for business objects, allowing tenants to add extension nodes and fields without recompiling the application platform, using a user interface to define and associate new nodes and fields with existing business objects, and storing this information in metadata for tenant-specific views.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional techniques are used to add fields to business objects, then the field can be added to the business object structure, but the entire database system must be recompiled and all tenants are affected

Engineering Contradiction:

Improvefield addition capabilityVSAvoidsystem recompilation requirement

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the business object structure into core fields and extension fields. Extension fields are stored separately in extension tables rather than being part of the core business object table. This allows individual extension fields to be added or modified without requiring recompilation of the entire database system, as each extension is independent and can be added dynamically.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic extension fields that can be added, modified, or removed at runtime without requiring system recompilation. The extension mechanism allows the business object structure to evolve dynamically by adding new fields to extension tables while maintaining compatibility with existing core business object definitions.

Inventive Principle:

Principle #15Dynamics

2Adaptability or versatility

If conventional techniques are used to add fields to business objects, then the field structure is updated, but all tenants must adapt to the additional field globally

Engineering Contradiction:

Improvetenant-specific customizationVSAvoidimpact on other tenants

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies local quality by allowing different tenants to have different extension fields added to their business objects. Each tenant can customize their business objects with tenant-specific extension fields that do not affect other tenants. The extension mechanism supports tenant-specific views and data, enabling localized customization without global impact.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

By segmenting extensions into tenant-specific extension tables and fields, the system allows each tenant to have their own customized business object structure. Tenant A can add extension fields relevant to their business needs without forcing Tenant B to adapt to the same changes, as each tenant's extensions are isolated.

Inventive Principle:

Principle #1Segmentation

3Adaptability or versatility

If extension fields are added using conventional techniques, then the business object structure is modified, but the application platform cannot be reused by other tenants

Engineering Contradiction:

Improvebusiness object extensibilityVSAvoidplatform recompilation requirement

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the business object into core components and extension components. The core business object definition remains stable and can be reused across tenants, while extensions are added in separate extension tables. This segmentation allows the platform to serve multiple tenants with different customizations without requiring recompilation of the core application platform.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The extension mechanism provides universal functionality that allows any tenant to add extension fields to business objects without affecting the core platform or other tenants. The same extension mechanism serves all tenants, enabling multi-tenant customization while maintaining platform reusability and avoiding recompilation requirements.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS8108434B2Dynamic node extensions and extension fields for business objects

Publication Date: 2012.01.31 SAP SE

AI summary

A system may include generation of extension metadata defining an extension node associated with a core node of a business object and extension fields associated with the extension node, and generation of a runtime metadata buffer comprising enhanced metadata, the enhanced metadata based on core metadata of the business object and the extension metadata. In some aspects, a service request associated with the business object is received, it is determined whether the service request is associated with the extension node, an extension service associated with the extension node is provided if it is determined that the service request is associated with the extension node, and a core service associated with core data of the business object is provided if it is determined that the service request is not associated with the extension node.