Metadata-Driven Business Object Template with Logic Hooks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems require manual creation and design of business logic for business objects, which is time-consuming and resource-intensive, especially since developers must manually identify locations for specific business logic within these objects.

Innovation Solution

The use of meta-data to create a business object template with hooks for calling generic business logic, allowing developers to modify and insert specific business logic efficiently, thereby reducing manual intervention and increasing productivity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual creation and design of business logic is used, then business objects can be created with custom business logic, but the process is time-consuming and resource-intensive

Engineering Contradiction:
Improvecustomization of business logicVSAvoiddevelopment speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system performs preliminary action by automatically generating business logic code and identifying insertion locations before the developer needs to customize it. The adapter pre-processes meta-data to create templates with placeholder code, so developers only need to modify pre-generated content rather than create everything from scratch.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by allowing meta-data to automatically generate the shell and business logic structure of business objects without manual intervention. The adapter autonomously processes meta-data definitions and produces ready-to-use code templates, reducing the need for manual programming work.

Inventive Principle:
Principle #25Self-service

2Manufacturing precision

If manual identification of business logic locations is required, then precise placement of business logic can be achieved, but developer time and effort increase significantly

Engineering Contradiction:
Improveprecision of business logic placementVSAvoidtime to identify insertion locations
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The adapter performs self-service by automatically analyzing meta-data and determining the precise locations where business logic should be inserted. The system autonomously identifies insertion points within the business object template without requiring manual code review or analysis by developers.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system replaces the mechanical process of manual code analysis with an automated computational process. The adapter uses algorithmic processing to scan meta-data definitions and automatically determine business logic insertion locations, substituting manual intellectual effort with automated software processing.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Ease of manufacture

If meta-data is used to create only the shell of business objects, then the structure can be defined efficiently, but the business objects lack real business logic

Engineering Contradiction:
Improveease of creating business object structureVSAvoidcompleteness of business object functionality
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The system performs preliminary action by pre-generating not just the shell but also the business logic code and identifying insertion locations. The adapter processes meta-data to create complete templates including placeholder business logic, so the business object is pre-prepared with both structure and functionality before developer intervention.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The adapter serves multiple functions: it creates the business object shell, generates business logic code, identifies insertion locations, and produces ready-to-use templates. This multi-functional approach consolidates what would otherwise require separate manual processes into a single automated operation.

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

Data Source

PatentUS8001521B2Meta-date driven implementation of business objects and their transactional behavior
Publication Date: 2011.08.16 SAP SE
  • US8001521B2 patent drawing
  • US8001521B2 patent drawing
  • US8001521B2 patent drawing

AI summary

Systems, methods and computer readable media are provided for the creation of a business object. In one exemplary embodiment, the method may include defining the shell of a business object utilizing meta-data stored within a repository. The method may also include storing the defined business object shell within the repository. Moreover, the method may include generating a business object template utilizing the business object shell, meta-data, and hooks for calling generic business logic, and modifying the hooks to insert the generic business logic.