Business Object Service Simulation via Pseudo-Functional Entities

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current enterprise systems face challenges in determining which functional entities are triggered during business object service execution and calculating the maximum number of executed entities, making it difficult to predict and optimize the behavior of business objects.

Innovation Solution

A simulation runtime model is generated with pseudo-structural and pseudo-functional entities, allowing for the execution of business object services without actual functional entities, enabling the prediction of behavior and optimization of business object service execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If a business object service is executed with actual functional entities, then the service functionality is realized, but it becomes difficult to predict which functional entities are triggered and calculate the maximum number of executed entities

Engineering Contradiction:
Improveprediction precision of functional entity executionVSAvoidcomplexity of determining triggered entities
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent creates a simulation runtime model that copies the structure and behavior of the actual runtime model but uses pseudo-functional entities instead of real functional entities. This copy allows prediction of triggered entities without executing the actual complex functionality, resolving the contradiction between prediction precision and complexity analysis.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The simulation runtime model performs preliminary analysis by executing business object services with pseudo-functional entities before actual runtime execution. This preliminary action determines which functional entities would be triggered and calculates maximum execution counts in advance, avoiding the complexity of analyzing actual runtime behavior during execution.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If the actual business object service is executed to determine triggered functional entities, then the service runs with real functionality, but the calculation of worst case scenario is time-consuming

Engineering Contradiction:
Improvespeed of determining triggered entitiesVSAvoidtime for worst case scenario calculation
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

By copying the runtime model to create a simulation version with pseudo-functional entities, the system can perform worst-case scenario calculations without executing actual functional entities. This copy executes faster and consumes less time while providing the same analytical insights about triggered entities and execution paths.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The simulation runtime model performs preliminary determination of triggered functional entities and worst-case scenario calculations before actual service execution. This preliminary action completes quickly using pseudo-functional entities, providing advance knowledge that avoids time-consuming real-time analysis during actual runtime execution.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If functional entities are replaced with pseudo-functional entities in simulation mode, then prediction capability is enabled, but the actual service execution cannot be performed

Engineering Contradiction:
Improveaccuracy of behavior predictionVSAvoidability to execute actual service
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The system dynamically switches between simulation mode (using pseudo-functional entities for prediction) and execution mode (using actual functional entities for service execution). The same runtime model structure supports both modes, allowing accurate prediction during simulation and actual functionality during execution without requiring separate systems.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8640110B2Business object service simulation
Publication Date: 2014.01.28 SAP SE
  • US8640110B2 patent drawing
  • US8640110B2 patent drawing
  • US8640110B2 patent drawing

AI summary

Systems, methods, computer program products, and the like for performing business object service simulation are disclosed. A runtime model of a business object can be generated. The runtime model can include a plurality of structural and functional entities. A simulation runtime model of the business object can be instantiated. The simulation runtime model can include a plurality of pseudo-structural and pseudo-functional entities. During the simulation runtime model, a predetermined business object service of the business object can be selected and at least one parameter of the predetermined business object service can be determined. Functional entities of the runtime model can be replaced with pseudo-functional entities of the simulation runtime model. The simulation runtime model can be executed using pseudo-functional entities.