Dynamic Web Service Server for ERP Interface Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing custom interfaces for interacting with Enterprise Resource Planning (ERP) systems via native APIs is difficult and expensive, requiring extensive IT departments or external consultants.
Innovation Solution
A Dynamic Web Service (DWS) server dynamically creates web services by recording and mapping transactions between ERP clients and servers, allowing for custom interface development with minimal developer input, using a transaction map to generate a web service description and automatically creating forms for user input.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If developers create custom interfaces for ERP systems using native APIs, then custom functionality is achieved, but development cost and complexity increase significantly
Solution Approach 1:
The system enables self-service interface generation where the ERP system automatically creates web service interfaces based on recorded user transactions. The system serves itself by observing its own operations and generating appropriate web service definitions without requiring external developers to manually create custom interfaces.
Solution Approach 2:
The system performs preliminary actions by recording user transactions and analyzing operation sequences before generating web service interfaces. This advance preparation allows the system to pre-generate interface definitions based on actual usage patterns, eliminating the need for subsequent manual interface development.
2Adaptability or versatility
If developers create custom interfaces for ERP systems, then specific transactions are enabled, but IT resource requirements increase
Solution Approach 1:
The ERP system performs self-service by automatically generating web service interfaces based on recorded transactions. This eliminates the need for expensive IT departments or external consultants to manually develop custom interfaces, as the system creates its own interface definitions autonomously.
Solution Approach 2:
The system changes parameters by transforming recorded transaction data into web service interface definitions. By analyzing operation sequences and extracting parameters from actual user interactions, the system dynamically generates interface specifications that match real business requirements.
3Adaptability or versatility
If manual interface development is used for ERP systems, then custom forms are created, but development time and cost increase
Solution Approach 1:
The system performs preliminary actions by recording user transactions and analyzing operation sequences before generating web service interfaces. This advance preparation allows the system to pre-generate interface definitions based on actual usage patterns, eliminating the need for subsequent manual interface development.
Solution Approach 2:
The system creates copies of actual user transactions and operation sequences to generate web service interface definitions. By copying and analyzing real usage patterns, the system produces accurate interface specifications that reflect actual business processes without requiring manual recreation.
Data Source
AI summary
A Dynamic Web Service server may facilitate custom Enterprise Application interface development with little or no developer input by dynamically creating a web service for performing a particular transaction according to a transaction map. An Enterprise Application client device may create a transaction map by “recording” a transaction between an Enterprise Application client and an Enterprise Application server and mapping transaction fields to a custom interface generated to collect data for re-performing the recorded transaction. The Enterprise Application client device may call the dynamic web service, and the Dynamic Web Service server may then perform the recorded transaction using input data collected in the custom interface.