On-Demand SAP Data Ingestion via OData for Multi-Cloud Provisioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional business data handling architectures are inflexible and require custom configuration and programming to provide SAP data to specific cloud storage environments, workforce accessible applications, and machine learning services, limiting real-time and batch data access.
Innovation Solution
An on-demand data ingestion system using the OData API on REST protocol provides no-code access to SAP data, enabling real-time and batch mode provisioning to any cloud storage, workforce applications, and machine learning services without custom software, via a service module and service agent communicating through industry-standard protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional business data handling architectures are used, then data can be accessed by specific applications through custom configuration, but the system lacks flexibility and requires custom coding for each cloud environment and application
Solution Approach 1:
The patent implements a universal data provisioning system that can serve multiple cloud environments (AWS, Azure, Google Cloud) and various application types (workforce applications, machine learning services, business processes) through a single standardized interface. The service module uses industry-standard protocols (OData, REST, JSON) to provide uniform data access across diverse targets, eliminating the need for custom integration code for each destination.
Solution Approach 2:
The patent introduces a service module as an intermediary layer between the SAP system and various cloud environments/applications. This mediator translates internal SAP data formats into standardized external formats (JSON, XML) using industry-standard protocols, thereby simplifying the integration process and eliminating the need for custom configuration code for each target system.
2Reliability
If custom programming is required for each cloud environment, then specific data access requirements can be met, but the implementation time and cost increase significantly
Solution Approach 1:
The patent establishes pre-configured service modules that are ready to connect to multiple cloud environments (AWS, Azure, Google Cloud) and application types before actual data provisioning is needed. These service modules come with built-in support for industry-standard protocols and data formats, so when data provisioning is required, the system can immediately begin operation without time-consuming custom development.
Solution Approach 2:
The patent enables dynamic configuration of data provisioning parameters through standardized interfaces. Instead of hardcoding connections for each target, the system allows parameters such as target environment, data format, and protocol to be changed through configuration files or API calls, thereby reducing implementation time while maintaining reliable data access.
3Reliability
If traditional architectures are used, then on-premise systems can be secured, but real-time and batch data access to cloud environments is limited
Solution Approach 1:
The patent segments the data provisioning system into distinct functional layers: an on-premise SAP system, a service module that handles protocol translation and data formatting, and cloud-based service agents that receive and process data requests. This segmentation allows the on-premise system to remain secure while enabling fast real-time and batch data access to cloud environments through the intermediary service module.
Solution Approach 2:
The service module acts as a secure intermediary that maintains the security boundary between on-premise SAP systems and cloud environments while enabling fast data access. It uses standardized protocols (OData, REST) to communicate with cloud service agents, allowing real-time and batch data provisioning without compromising the security of the on-premise system.
4Stability of the object's composition
If proprietary protocols are used for data access, then SAP system integrity is maintained, but compatibility with diverse cloud environments and applications is reduced
Solution Approach 1:
The service module serves as a protocol translation intermediary that receives data from the SAP system in proprietary formats, converts it to standardized formats (JSON, XML) using industry-standard protocols (OData, REST), and transmits it to cloud service agents. This maintains SAP data integrity while ensuring compatibility with diverse cloud environments and applications.
Solution Approach 2:
The service module dynamically changes data format parameters based on the target destination. It transforms SAP-internal data structures into standardized formats suitable for cloud environments, thereby maintaining source system integrity while achieving broad compatibility with diverse targets through parameter transformation.
Data Source
AI summary
Disclosed herein is novel system and method for business data handling technology that provides on-demand access to business data and provisioning the business data flexibly for use by multiple applications, and for storage to multiple cloud environments. In exemplary embodiments, the system comprises an on-demand data ingestion service module and a service agent existing independently from the remaining entrenched architectural elements of a business information system architecture.