Scripting Engine for SaaS ERP Business Logic Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern Enterprise Resource Planning (ERP) applications face challenges in efficiently updating and modifying business logic without disrupting existing software functionality, as they often rely on processor-compiled languages that consume significant developer and processing resources.

Innovation Solution

The system converts business logic architecture from native languages to scripting languages, using a scripting engine to generate and execute business logic scripts, embedding a scripting language runtime that limits memory consumption and allows for non-disruptive updates and modifications by leveraging existing architecture and resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If processor-compiled languages are used for business logic, then software functionality and reliability are maintained, but updating and modifying business logic becomes slow and resource-intensive

Engineering Contradiction:
Improvespeed of updating business logicVSAvoiddeveloper time and processing resources required for updates
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments business logic into modular components that can be independently updated. Business logic is divided into discrete units that can be modified, tested, and deployed separately from the core processor-compiled architecture, enabling faster updates without recompiling the entire system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (scripting engine or abstraction layer) between the processor-compiled core and business logic. This intermediary allows business logic to be updated through scripts or configurations without directly modifying or recompiling the core processor code, reducing developer time and processing resources.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If scripting language runtime is embedded for fast business logic updates, then adaptability and ease of modification improve, but memory consumption increases

Engineering Contradiction:
Improveability to modify business logicVSAvoidmemory resources consumed
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent applies scripting language runtime selectively only in the portions of the system where business logic updates are needed, rather than embedding it throughout the entire application. This localized approach provides adaptability where required while minimizing overall memory consumption in the processor-compiled architecture.

Inventive Principle:
Principle #3Local quality

3Ease of operation

If business logic is converted from processor-compiled to scripting language, then ease of operation and update speed improve, but software complexity increases

Engineering Contradiction:
Improveease of modifying business logicVSAvoidsystem architecture complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer that mediates between the simple scripting language interface and the complex processor-compiled backend. This intermediary handles the complexity of integration, translation, and coordination, allowing users to operate with simple scripts while the system manages the underlying architectural complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a simplified copy or representation of business logic in scripting language that mirrors the functionality of the processor-compiled version. This copy allows easy modification and operation, while the original processor-compiled code remains intact to handle complex operations, thus managing overall system complexity.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9753701B2Generating logic with scripting language in software as a service enterprise resource planning
Publication Date: 2017.09.05 SAP SE
  • US9753701B2 patent drawing
  • US9753701B2 patent drawing
  • US9753701B2 patent drawing

AI summary

Systems and methods are described for converting business logic architecture from a native language (e.g., processor compiled code) into a scripting language (e.g., scripted code) for software as a service (SaaS) delivery methods for enterprise resource planning. The systems and methods may include generating a plurality of business process patterns representing business logic associated with one or more of a plurality of business objects, obtaining a plurality of code portions that correspond to one or more of the plurality of business process patterns, the plurality of code portions being coded in a scripting language and stored in a script repository, defining at least one extension point for each business process pattern. Each extension point may represent an interface, within the business logic, in which to insert one or more of the plurality of code portions into processor-compiled architecture in a software application.