Dynamic Business Object Property Management via Configuration Tables

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional business object management systems lack the ability to centrally manage and maintain properties effectively, leading to inefficiencies in property determination and reuse, as properties are typically fixed and determined by service providers without clear data requirements or calculation methods.

Innovation Solution

A computer system and method that includes an access manager to determine, display, and configure business object properties in a user interface, using a context handler to define input parameters, a rule handler to define rules, and a model handler to generate metadata models, allowing properties to be locked and mapped to UI fields, thereby enabling dynamic property calculation and management without relying on service providers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If properties are determined by instantiating a service provider with fixed conditions, then property determination is achieved, but central improvements, maintenance, and reuse are not possible

Engineering Contradiction:
Improveproperty management flexibilityVSAvoidservice provider instantiation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts property determination logic from the service provider instantiation process and places it in a separate configuration table. This allows properties to be defined and managed independently from the service provider code, enabling central improvements and maintenance without modifying the service provider itself.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments property determination into distinct components: input parameters defined by a context handler, rules defined by a rule handler, and metadata models generated by a model handler. This segmentation allows each component to be independently configured and maintained in the configuration table.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If properties are fixed and determined by service providers, then property determination is achieved, but it is not known which data is required for property determination and how properties are calculated

Engineering Contradiction:
Improveproperty calculation transparencyVSAvoidproperty configuration simplicity
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent introduces a configuration table as an intermediary between the service provider and property determination. This intermediary explicitly defines input parameters, their data sources, and calculation rules, making the property determination process transparent and configurable without complicating the service provider code.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If central improvements and maintenance of properties are enabled, then property management flexibility is improved, but system complexity increases

Engineering Contradiction:
Improveproperty management flexibilityVSAvoidconfiguration table complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal configuration table structure that handles multiple aspects of property management (input parameters, rules, metadata models) in a single standardized format. This universal approach enables central improvements and maintenance while avoiding the need for separate configuration mechanisms for each property aspect.

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

Data Source

PatentUS9053445B2Managing business objects
Publication Date: 2015.06.09 SAP SE
  • US9053445B2 patent drawing
  • US9053445B2 patent drawing
  • US9053445B2 patent drawing

AI summary

In accordance with aspects of the disclosure, a system and methods are provided for managing business objects in memory. The system and methods may be provided for defining a context of one or more input parameters of data used to determine one or more properties of one or more business objects, defining one or more rules associated with the one or more properties of each business object, and generating a metadata model for each business object based on the context of the one or more input parameters of each business object and the one or more rules associated with the one or more properties of each business object.