Interface docking access method based on e-commerce SaaS ERP system

Abstract

The invention discloses an interface docking access method based on an e-commerce SaaS ERP system, and relates to the technical field of e-commerce, and the method comprises the following steps: obtaining interface authorization codes of different ERP systems, and generating corresponding target authorization codes according to platform rules; configuring a connector based on the target authorization code; the connector is used for connecting an information tool for a server specially configured by a user; generating a corresponding integration scheme based on the configured connector; each integration scheme corresponds to an interface docking demand of one service; aiming at the integration scheme, constructing a source platform configuration scheme; aiming at the integration scheme, constructing a target platform configuration scheme; and starting an integration scheme and setting a timing strategy based on the configured source platform and target platform. Through the unified API management and low-code integration scheme, e-commerce enterprises can efficiently and automatically obtain and process various business data, and low efficiency and high error rate caused by traditional manual operation and data export are avoided.

Description

Technical Field

[0001] The present invention relates to the technical field of e-commerce, and in particular to an interface docking and data acquisition method based on an e-commerce SaaS ERP system. Background Art

[0002] E-commerce SaaS ERP system refers to a service platform that provides software applications through the Internet through the SaaS system, i.e., software as a service technology. The e-commerce ERP system is a comprehensive enterprise resource planning (ERP) software designed and developed specifically for e-commerce enterprises. It integrates various key business functions and modules, including order management, inventory control, procurement management, financial management, report analysis, customer relationship management, etc., aiming to improve the operational efficiency and management capabilities of e-commerce enterprises. The advantages of the e-commerce ERP system lie in its integration and data consistency. By integrating various business functions and modules, information can flow automatically within the system, avoiding the problems of data redundancy and information islands. Such an integrated management system improves work efficiency, reduces human errors, and provides enterprises with an accurate and reliable data foundation.

[0003] With the booming development of e-commerce, enterprises have a growing demand for online sales platforms. SaaS website building, as a convenient way to build a website online, is favored by many enterprises because of its rapid deployment and easy management. As the core tool for internal resource management and process automation, the ERP system has become the focus of enterprise attention for its integration with SaaS website building. When e-commerce companies increase sales and platforms, sales data, product data, promotion data, after-sales data, financial data and other data need to be obtained from the ERP system to their own financial and taxation systems. The traditional way is to manually export and process data using Excel, which is inefficient, has a high error rate, and is highly dependent on manpower. Summary of the invention

[0004] The purpose of the present invention is to solve the problems in the prior art and to propose an interface docking and data acquisition method based on an e-commerce SaaS ERP system.

[0005] In order to achieve the above object, the present invention adopts the following technical solutions:

[0006] A method for obtaining data through interface connection based on an e-commerce SaaS ERP system comprises the following steps:

[0007] Obtain the interface authorization codes of different ERP systems and generate corresponding target authorization codes according to platform rules;

[0008] Based on the target authorization code, a connector is configured; the connector is a server connection information tool configured exclusively for the user;

[0009] Generate a corresponding integration solution based on the configured connector; each integration solution corresponds to an interface connection requirement of a business;

[0010] Constructing a source platform configuration plan for the integration plan;

[0011] Construct a target platform configuration solution for the integration solution;

[0012] Based on the source platform configuration scheme and the source platform configuration scheme, the integration scheme is started and a timing strategy is set.

[0013] According to an interface connection and data acquisition method based on an e-commerce SaaS ERP system provided by the present invention, interface authorization codes of different ERP systems are obtained, and corresponding target authorization codes are generated according to platform rules, and then the following is further included:

[0014] Check in to the open platform and obtain the application key and secret key assigned by the development platform;

[0015] Apply for API interface permissions from the development platform based on the application key and secret key, and obtain corresponding API interface permissions;

[0016] Based on the API interface permissions, a standard OAuth2.0 process is used to perform third-party business authorization and generate a business authorization code;

[0017] The business authorization code is exchanged for an authorization token, and based on the authorization token, an API request is used to obtain merchant data.

[0018] According to an interface docking and data retrieval method based on an e-commerce SaaS ERP system provided by the present invention, in the process of exchanging authorization tokens, a dynamic weighted average token generation algorithm is adopted to dynamically generate an optimal token through the weight distribution of historical requests, including:

[0019] Normalize the weight values ​​of historical requests;

[0020] Generate a new token based on the weight value of each request;

[0021] Correspondingly, the formula for generating a new token is:

[0022]

[0023] ; Among them, ω_i represents the weight corresponding to the i-th historical request, ω_j represents the weight corresponding to the j-th non-historical request; request_i represents the feature vector corresponding to each historical request; n represents the number of requests.

[0024] According to an interface docking and data acquisition method based on an e-commerce SaaS ERP system provided by the present invention, the process of configuring the connector is as follows:

[0025] Determine a connector environment, and configure a server based on the connector environment; the connector environment includes production, test, and development;

[0026] Set the basic parameters of the connector;

[0027] Based on the connector environment, perform corresponding environment configuration;

[0028] After completing the development and test configuration, switch the connector to the production environment and check the production environment parameters.

[0029] According to an interface docking and data acquisition method based on an e-commerce SaaS ERP system provided by the present invention, the detailed process of the integration solution includes:

[0030] According to the actual business scenario, clarify the data types and operation targets that need to be synchronized;

[0031] Configure specific rules for each integration solution based on different business requirements;

[0032] Before configuring the integration solution, you need to obtain authorization for the data interface;

[0033] Select the operating environment according to business needs and create an integration solution;

[0034] Configure the corresponding data source for each integration solution;

[0035] After completing the configuration of the integration solution, execute the solution in the test environment to verify whether the data synchronization process meets expectations;

[0036] After the test is passed, the integrated solution will be deployed to the production environment for formal operation;

[0037] According to an interface docking and data acquisition method based on an e-commerce SaaS ERP system provided by the present invention, the source platform configuration includes a header area and a sub-tab area, wherein the header area displays substrate information and startup plan; the sub-tab area displays details of each function.

[0038] According to an interface docking and data acquisition method based on an e-commerce SaaS ERP system provided by the present invention, the target platform configuration includes request parameter settings, startup data mapping, and support function expressions;

[0039] Wherein, the request parameter configuration is used to transfer the data field of the target platform;

[0040] The startup data hard mapping is a static mapping, which is used to configure the mapping relationship between the source platform and the target platform data fields after clicking the static mapping;

[0041] The supported function expressions are used to process more complex business logic in complex business scenarios.

[0042] An interface docking and data acquisition system based on an e-commerce SaaS ERP system, comprising:

[0043] Acquisition unit: used to obtain the interface authorization codes of different ERP systems and generate corresponding target authorization codes according to platform rules;

[0044] A first configuration unit: configured to configure a connector based on the target authorization code; the connector is a server connection information tool configured exclusively for a user;

[0045] Generating unit: used to generate corresponding integration solutions based on the configured connectors; each integration solution corresponds to the interface connection requirements of a business;

[0046] A second configuration unit: used for constructing a source platform configuration solution for the integration solution;

[0047] The third configuration unit is used to construct a target platform configuration solution for the integration solution;

[0048] Timing and starting unit: used to start the integration solution and set the timing strategy based on the configured source platform and the target platform.

[0049] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the steps of the above-mentioned method for interface docking and data acquisition based on an e-commerce SaaS ERP system are implemented.

[0050] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the above-mentioned interface docking and data acquisition method based on the e-commerce SaaS ERP system are implemented.

[0051] Compared with the prior art, the present invention has the following advantages:

[0052] The present invention provides an interface docking and data acquisition method based on the e-commerce SaaS ERP system. By obtaining the interface authorization codes of different ERP systems and generating corresponding target authorization codes, the API interface docking of the e-commerce SaaS ERP system is realized, which solves the problems of low efficiency and high dependence on manual operation of data acquisition between multiple systems in e-commerce enterprises, and generates corresponding integration solutions in conjunction with connectors to realize unified API interface management and low-code integration solutions. E-commerce enterprises can efficiently and automatically acquire and process various types of business data, avoiding the inefficiency and high error rate caused by traditional manual operations and data export. In addition, in the process of configuring the integration solution, the source platform configuration solution and the target platform configuration solution are adopted. , realizing loosely coupled integration, making data flow between different systems smoother, breaking the problem of internal data islands in the enterprise in the past, improving the efficiency of information circulation, and helping enterprises to better utilize their data assets. In addition, the non-invasive integration solution and loosely coupled design allow enterprises to quickly adjust the integration solution according to business needs without large-scale modification of existing business systems, reducing the workload of development and maintenance; finally, for the configured source platform and target platform, start the integration solution and set the timing strategy, so that the combination of asynchronous API architecture and timing task scheduling mechanism ensures that data synchronization can remain efficient and stable even in high-traffic scenarios, meeting the high requirements of e-commerce companies for real-time and stability. In summary, through automated integration and synchronization solutions, the need for manual operation and data input is reduced, thereby reducing the risk of data errors, effectively saving labor costs, and improving overall operational efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0054] Figure 1 A flow chart of a method for interfacing and retrieving data based on an e-commerce SaaS ERP system provided by an embodiment of the present invention;

[0055] Figure 2 A schematic diagram of the structure of an interface docking and data acquisition system based on an e-commerce SaaS ERP system provided by an embodiment of the present invention;

[0056] Figure 3 This is a schematic diagram of the structure of the electronic device proposed by the present invention. DETAILED DESCRIPTION

[0057] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0058] Combine the following Figure 1 - Figure 3 The present invention describes an interface docking and data acquisition method based on an e-commerce SaaS ERP system.

[0059] Figure 1 This is a flow chart of a method for obtaining data through an interface connection based on an e-commerce SaaS ERP system provided by the present invention. Figure 1 As shown, the method comprises the following steps:

[0060] Step 101, obtain the interface authorization codes of different ERP systems, and generate corresponding target authorization codes according to platform rules; the target authorization code mainly opens the door to obtain merchant data.

[0061] Specifically, it also includes:

[0062] Check in to the open platform and obtain the application key and secret key assigned by the development platform;

[0063] Apply for API interface permissions from the development platform based on the application key and secret key to obtain the corresponding API interface permissions; when applying for API interface permissions from the development platform, it is mainly based on the ISV / developer's approval to the platform. Only after approval can the corresponding API permissions be obtained.

[0064] Based on API interface permissions, the standard OAuth2.0 process is used to authorize third-party services and generate service authorization codes. When performing OAuth2.0 authorization, in order to ensure the security and integrity of the authorization chain, a multi-layer recursive authorization verification algorithm is used. This algorithm recursively decomposes the requested authorization code into multiple sub-nodes, and verifies each layer of sub-nodes one by one through a multi-layer authorization verification model. The core principle is to build a permission-dependent directed acyclic graph (DAG), and use depth-first search (DFS) to recursively traverse each node in the authorization chain to ensure the permission inheritance relationship of each authorization node.

[0065] Exchange the business authorization code for an authorization token, and use the API to request merchant data based on the authorization token.

[0066] Specifically, through third-party business authorization, ISV / developers can obtain merchant data within the authorized scope to complete related business processing or application development (such as merchant store order data to achieve financial accounting, etc.) after obtaining merchant authorization, and ISV / developers need to initiate, or ISV / developers add corresponding functions in their own applications and the merchant completes the authorization behavior; after the authorization is agreed, ISV / developers can use API to request merchant-related data. When authorizing third-party business, ISV / developers need to assemble the authorization URL. After each successful authorization, ISV / developers will obtain a business authorization code in exchange for the authorization token access_token (equivalent to the access_token in the public request parameter).

[0067] In summary, the API interface connection of the e-commerce SaaS ERP system solves the problems of low data acquisition efficiency and high dependence on manual operations among multiple systems in e-commerce companies.

[0068] Step 102, configure the connector based on the target authorization code; the connector is a server connection information tool configured exclusively for the user; the data sources of the development environment and the production environment can be added and isolated separately to protect data security. According to the specific situation, the user can choose three different environments, namely production env_production, test env_test, and development env_development. After completing development and testing, be sure to switch the connector environment to the production environment before formal operation.

[0069] Specifically, the process of configuring the connector is as follows:

[0070] Determine the connector environment and configure the server based on the connector environment to ensure data transmission security. In addition, the connector environment includes production, testing, and development; and the connector environment needs to ensure that the authorization code has been obtained on the ERP open platform, and the connector will use the authorization code for configuration. At the same time, the server supports switching between multiple environments (i.e. production, testing, and development).

[0071] Set the basic parameters of the connector; the basic parameters include the authorization code and the application key and secret key. The authorization code obtained on the ERP platform is filled in the connector configuration file to ensure that the connector can correctly access the API interface. Fill in the application app_key and app_secret assigned by the ERP open platform to facilitate subsequent API verification and data requests.

[0072] Based on the connector environment, perform the corresponding environment configuration; since the connector supports three different environment configurations, namely production, test, and development environments, the configuration steps are as follows:

[0073] Production environment (env_test): used for data acquisition and processing during the official run, ensuring that all data flows are run under strict authorization control. Set the env parameter in the connector to env_production. Configure the data source information of the production environment, including the server's IP address, port, database link and other details. Configure encryption protocols such as SSL / TLS for the production environment to ensure the security of data transmission.

[0074] Test environment (env_development): used by developers to debug and develop features. Set the env parameter in the connector to env_development. Configure the data source for the development environment, usually using mock data or low-sensitivity data. Set detailed logging for the development environment so that developers can track the interface call process.

[0075] Development environment (env_development): used by developers to debug and develop features. Set the env parameter in the connector to env_development. Configure the data source for the development environment, usually using mock data or low-sensitivity data. Set detailed logging for the development environment so that developers can track the interface call process.

[0076] After completing the development and test configuration, switch the connector to the production environment and check the production environment parameters. To switch to the production environment, you need to switch the env parameter from env_test or env_development to env_production in the connector configuration file before preparing to enter the formal operation and when checking the environment parameters.

[0077] In addition, when verifying the authorization code and key, ensure that the authorization code and key filled in the configuration file are the authorization credentials used for the production environment.

[0078] When restarting the connector, after modifying the configuration file, restart the connector for the changes to take effect.

[0079] When running the test, before the official operation, a complete interface debugging process is performed to ensure that the connector in the production environment works normally and meets the security requirements.

[0080] After the environment is switched, a comprehensive security check is required before the connector is officially run, including:

[0081] Authorization verification: Ensure that the authorization code is valid and has data access permissions for the production environment.

[0082] Network security: Confirm that the data connection of the production environment has security measures (such as firewall and VPN configuration).

[0083] Log management: Make sure error logging is turned on to facilitate subsequent troubleshooting of potential issues.

[0084] The above are the detailed connector configuration steps. By configuring the connector through this process, you can ensure that data is securely isolated in different environments, and at the same time, data can be exchanged efficiently and securely in the production environment.

[0085] Step 103: Generate a corresponding integration solution based on the configured connector; each integration solution corresponds to an interface connection requirement of a business.

[0086] Specifically, users can create multiple integration solutions with different rules according to different businesses. For example, in one embodiment, purchase order synchronization, online sales delivery synchronization, offline sales delivery synchronization, online sales order synchronization, online after-sales return and refund order synchronization, online product information synchronization, online inventory information synchronization, etc.

[0087] In addition, the detailed process of the integrated solution includes:

[0088] Step 10301, based on the actual business scenario, clearly define the data types and operation targets that need to be synchronized; such as purchase order synchronization, online sales delivery synchronization, etc.

[0089] Step 10302, configure specific rules for each integration solution according to different business requirements; these rules define how to obtain data from the source system, how to process data, and how to push data to the target system. When configuring rules, you can set data screening conditions, field mapping rules, data conversion logic, etc. to ensure that the data meets the requirements of the target system.

[0090] Step 10303, before configuring the integration solution, it is necessary to obtain authorization for the data interface; that is, the target authorization code in step 101.

[0091] Step 10304, select the operating environment according to business needs and create an integration solution; to ensure the accuracy and security of data operations, as shown in step 102.

[0092] Step 10305, configure the corresponding data source for each integration solution to obtain data from the source system. For example, the purchase order integration solution needs to configure the purchase order data source, while the inventory information synchronization solution needs to configure the inventory data source.

[0093] Step 10306, after completing the configuration of the integration solution, execute the solution in the test environment to verify whether the data synchronization process meets expectations; and check the accuracy and completeness of data transmission to ensure that data can be correctly transmitted from the source system to the target system.

[0094] Step 10307, ​​after the test is passed, the integration solution is deployed to the production environment for formal operation; in the production environment, the integration solution will be executed periodically or in real time to ensure that data synchronization can meet business needs.

[0095] After the integration solution is deployed, users need to continuously monitor it to ensure the stability of the data synchronization process. Check logs regularly, handle errors or abnormal situations, and optimize the solution configuration when necessary to improve synchronization efficiency and accuracy.

[0096] The execution of the integration solution requires an authorized API interface. The target authorization code and access_token obtained in step 101 are the credentials for the integration solution to access the data interface. Therefore, before configuring the integration solution, you must ensure that you have obtained authorization for the relevant API.

[0097] The environment (production, testing, development) in which the integration solution runs depends on the connector environment configured previously. The environment configuration has been completed in step 102, and the integration solution needs to synchronize data based on these environments. Integration solutions in different environments can be used for development, testing, and formal business operations to ensure data isolation and operational security.

[0098] In summary, a unified API management platform is provided to support real-time data integration and low-code configuration. Users can easily configure integration solutions through visual tools. In this way, e-commerce companies can customize various data docking processes according to business needs, reducing development difficulty and improving business flexibility.

[0099] Step 104: construct a source platform configuration solution for the integration solution.

[0100] The source platform configuration includes a header area and a sub-tab area. The header area displays substrate information and startup scheme; the sub-tab area displays the details of each function.

[0101] Step 105: construct a target platform configuration solution for the integration solution.

[0102] Target platform configuration includes request parameter settings, startup data mapping, and support function expressions.

[0103] The request parameter configuration is used to pass the data fields of the target platform; the request parameters are fixed values ​​that can be directly entered into the target platform fields, which are used to ensure that certain fields have fixed values ​​each time they are written (such as identifiers, default categories, etc.). This part of the settings ensures that the basic information of the request can be received and processed on the target platform.

[0104] Start data hard mapping as static mapping, which is used to configure the mapping relationship between the source platform and the target platform data fields after clicking static mapping; for example, the "commodity code" field of the source platform can be mapped to the "product ID" field of the target platform, thereby realizing the docking of data fields. Data mapping can ensure that the data fields transmitted between the two systems correspond to each other, improving the accuracy of data transmission.

[0105] Supports function expressions to handle more complex business logic in complex business scenarios.

[0106] After the configuration is completed, the write task of the target platform defines how the data is transferred from the source platform to the target platform, and applies the above mapping and function operations to ensure that the field requirements of the target system are met. After the configuration is completed, the system will be able to write data to the target platform according to the set rules and logic.

[0107] Step 106: Based on the source platform configuration scheme and the target platform configuration scheme, start the integration scheme and set the timing strategy.

[0108] Specifically, when an integration solution is started, its header information (such as solution name, creation time, etc.) cannot be modified, but the specific platform configuration information in the table body (such as data mapping, field configuration) can still be modified. After the solution is started, it will automatically run according to the configured timing strategy and start synchronizing data from the source system to the target system. A solution that has not been started will not execute any tasks, and tasks in the queue will not actually enter the queue state.

[0109] In requeue, when the timing strategy is configured, the steps are as follows: After starting the plan, the task will automatically enter the queue. If you need to start running immediately, you can click [Requeue] in the queue pool, so that the task will be activated and executed immediately.

[0110] Linux Crontab scheduled tasks; Linux crontab is a tool for periodically executing tasks. The system checks every minute by default whether there are tasks to be executed. If there are tasks, they are automatically executed. Crontab tasks are divided into two categories: system tasks (such as system backup, cache cleaning, etc.) and user tasks (such as checking the mail server every 10 minutes).

[0111] Common Crontab commands: crontab-e: Enter edit mode, set task time and task content; the default editor is VI. crontab-r: Delete all current scheduled tasks; crontab-l: List currently set scheduled tasks.

[0112] The present invention relates to the field of e-commerce, and proposes an interface docking and data retrieval method based on an e-commerce SaaS ERP system. In the present invention, the proposed interface docking and data retrieval method realizes the API interface docking of the e-commerce SaaS ERP system by obtaining the interface authorization codes of different ERP systems and generating corresponding target authorization codes, thereby solving the problems of low efficiency and high reliance on manual operation of data acquisition between multiple systems in e-commerce enterprises, and generating corresponding integration solutions in conjunction with connectors to realize unified API interface management and low-code integration solutions, so that e-commerce enterprises can efficiently and automatically acquire and process various types of business data, avoiding the inefficiency and high error rate caused by traditional manual operations and data export; in addition, in the process of configuring the integration solution, the source platform configuration solution and the target platform configuration solution are adopted to realize loosely coupled integration. The integrated approach makes data flow between different systems smoother, breaks the problem of internal data silos in enterprises, improves the efficiency of information flow, and helps enterprises make better use of their data assets. The non-invasive integration solution and loosely coupled design allow enterprises to quickly adjust the integration solution according to business needs without large-scale modifications to existing business systems, reducing the workload of development and maintenance. Finally, for the configured source platform and target platform, the integration solution is started and the timing strategy is set, so that the combination of asynchronous API architecture and timing task scheduling mechanism ensures that data synchronization can remain efficient and stable even in high-traffic scenarios, meeting the high requirements of e-commerce companies for real-time and stability.

[0113] In step 101, in the process of exchanging authorization tokens, a dynamic weighted average token generation algorithm is used to dynamically generate the optimal token through the weight distribution of historical requests.

[0114] Specifically, it includes: normalizing the weight values ​​of historical requests;

[0115] A new token is generated based on the weight value of each request.

[0116] Correspondingly, the formula for generating a new token is:

[0117]

[0118] ; Among them, ω_i represents the weight corresponding to the i-th historical request, ω_j represents the weight corresponding to the j-th non-historical request; request_i represents the feature vector corresponding to each historical request; n represents the number of requests.

[0119] Furthermore, the following formula is used when assembling the authorization URL to ensure the consistency and security of the request. The formula is:

[0120] URL_auth=BaseURL+ClientID*exp(α*RedirectURL) / (1+ln1+Scope);

[0121] Here, α represents the key negotiation constant with the authorization server, which aims to improve the encryption strength of the URL in a high-concurrency environment by combining the exponential function with the logarithmic function.

[0122] When generating access_token, a symmetric encryption formula is used to ensure the security of the token during transmission. The symmetric encryption formula is:

[0123]

[0124] in, SHA256 represents a bitwise XOR operation, and SHA256 represents a hash encryption function. This encryption mechanism can prevent the token from being attacked by a man-in-the-middle during network transmission.

[0125] In step 103, in the configuration of the integration solution, the source system, the source system API, the target system, and the target system API need to be configured. Before adding a new integration solution, it is necessary to ensure that the connectors of the two systems have been configured.

[0126] Specifically, the configuration steps are as follows:

[0127] 1. Configure the plan information and fill in the basic information [Plan Name]; [Maximum Retries] indicates the number of times the system automatically retries when an error occurs in writing a document; [Strategy Mode] defaults to Scheduled Asynchronous-Scheduled Asynchronous. Scheduled Asynchronous is a programming mode that combines scheduled tasks and asynchronous processing. It allows the program to automatically perform certain operations at specified time intervals without waiting for these operations to complete before continuing to execute other codes.

[0128] Implementation method: 1. Use built-in functions of programming languages: The programming language provides support for timed asynchronous tasks. For example, the setTimeout and setInterval functions in JavaScript can be used to set timers, while the async / await keywords are used to handle asynchronous operations.

[0129] 2. Use third-party libraries or frameworks: For more complex scheduled asynchronous tasks, you can use third-party libraries or frameworks to simplify the development process. For example, the node-cron library in Node.js can be used to create scheduled tasks, and the axios library supports asynchronous HTTP requests.

[0130] 3. Operating system level support: In some cases, you can use the functions provided by the operating system to implement scheduled asynchronous tasks. For example, in Unix / Linux systems, you can use the cron job scheduler to execute scripts or commands regularly.

[0131] 2. Configure the access system information, select [Source Platform] [Connector] [API Asset] in sequence. Source Platform: Select the source system of the data. Connector: Select the configured connector to connect to the source system to ensure that the data can be accessed. API Asset: Select the corresponding API interface asset. This interface should be a query interface because the access system obtains data from the source system and does not perform modification operations.

[0132] 3. Configure the information of the write system. For the write system configuration, select [Target Platform] [Connector] [API Asset] in sequence. Target Platform: Select the target system of the data, that is, the system where the data will be written. Connector: Select the configured connector to connect to the target system. API Asset: Select the corresponding API interface asset. This interface should be an operation interface because the write system will write data to the target system. After completing the above configuration, the newly added integration solution will appear in the list page.

[0133] 4. After the addition is successful, start configuring the detailed information. After the addition is successful, the newly added integration plan will be the first one to be found on the list page. Click the plan name to start configuring the detailed information.

[0134] In step 104, the sub-tabs are detailed functions: Log management: used to output various log records during the operation of the integration solution; Data management: can manage the original data of mongoDB; Request queue pool: view and maintain the query tasks of the request source system; Write queue pool: view and maintain the write tasks of the target system; Request scheduler: used to configure how to generate the query tasks of the source system; Write scheduler: used to configure how to generate the write tasks of the target system; Debugger: Operation and maintenance, developers can activate various instruction sets of the integration solution through the debugger; Exception monitoring: view the exception errors that occur during the operation of the solution; Event processing factory: custom script codes can be embedded in some special solutions for special processing. Among them, the request parameter - requestParams, the request parameters of the source platform are usually some business parameters used for query, such as the date, department, material code and other field information in the query conditions; other request parameters - otherRequestParams, other request parameters of the source platform are usually some non-business parameters, used for paging, document identifiers and other field information; the definition of the two is not necessary, and it varies according to the adaptation of each platform. But in the end, these two parameters will form the final request parameter data; response parameter - responseParams, response parameter refers to the field information that will be returned after the source platform query is successful. These field information usually does not contain non-business parameters, such as response success status code, message and other system-level parameters. These system-level fields will be filtered out by the adapter in the handleResponse method of the adapter. Other response parameters - otherResponseParams, other response parameters do not play any role at present, and may be used to configure system-level parameters to automatically process the handleResponse method in the future; further, when configuring the source platform, when configuring the access system and writing system information, you need to access the API interface, which depends on the authorization code and access_token obtained in step 101 to ensure that the integration solution can legally access the data of the source system and the target system. The selected connector needs to be based on the environment configured in step 102 to ensure the isolation and security of the data source and the target data source. Therefore, the steps of adding the integration solution are based on the previous authorization and environment configuration. Only after completing the authorization and environment configuration can the data synchronization process in the solution be guaranteed to be legal and secure.

[0135] In step 105, several common function expression configuration methods are as follows:

[0136] Time conversion: For example,

[0137] FROM_UNIXTIME({{LAST_SYNC_TIME}}-600,'%Y-%m-%d %H:%i:%s') is used to calculate and format the time field to ensure that the time data received by the target platform conforms to the standard.

[0138] Tax rate calculation: You can use an expression like function({fdetails_list.tax}*108) to convert the source platform tax rate value into the tax rate value that meets the target platform.

[0139] Logical judgment expression: supports writing logical judgment expressions similar to CASEWHENTHEN, which is equivalent to the conditional syntax in SQL and is suitable for passing different field values ​​under different conditions.

[0140] Basic function operations: You can use basic functions such as SUM, AVG, MAX, MIN, etc. to perform aggregation or statistical operations. For example, functionSUM({fdetails_list.gty}) is used to accumulate quantities.

[0141] In addition, the process of configuring the target platform also depends on the system authorization and connector environment configuration. Only after the authorization and connector configuration are completed can the system access the target platform and write data. At the same time, the target platform can be configured only after the integration solution is successfully added and the access configuration of the source system is completed.

[0142] At the same time, the source platform configuration is used to obtain data, while the target platform configuration is used to write the obtained data to the target platform. These two configurations together complete the flow of data between the two systems. The query parameters and request queues for data acquisition have been defined in the source platform configuration, and the target platform configuration completes the mapping and business logic of data writing.

[0143] In step 106, when the integration mode is started, in one embodiment, it is assumed that a new "purchase order synchronization" plan is created. Before starting, even if the task and time strategy have been set in the plan, data synchronization will not start. Only after the plan is started, the task will enter the queue and the system will start to run data synchronization according to the timing strategy.

[0144] During the requeuing process, in one embodiment, if the timing strategy of the plan is modified and the effect is expected to be seen immediately, the [Requeue] button can be clicked to start executing the task immediately without waiting for the next scheduled time to arrive.

[0145] When configuring the timing strategy, in one embodiment, a system task can be set to allow the server to automatically clean up the cache every hour, which can ensure efficient operation of the system.

[0146] At the same time, in the time format description, Crontab time format:

[0147] f1f2f3f4f5program; f1: minute, f2: hour, f3: date, f4: month, f5: day of the week, program: the task to be executed.

[0148] * means it is executed at every time point, ab means the time interval from a to b, and * / n means it is executed once every n time interval.

[0149] In one embodiment: The following are several Crontab time format examples:

[0150] ***** / path / to / script.sh: executes the script.sh script once every minute.

[0151] 00*** / path / to / backup.sh: Executes the backup.sh script at 0:00 a.m. every day. It is suitable for daily backup tasks.

[0152] * / 10**** / path / to / check_mail.sh: executes the check_mail.sh script every 10 minutes, which is suitable for periodically checking new emails.

[0153] In summary, the startup plan is the switch for the operation of the entire integrated plan. Only after it is started will the plan execute tasks according to the timing strategy.

[0154] Timing strategy configuration is the core of controlling the frequency of task execution. It can define when a task is executed and how long it takes for the task to be executed.

[0155] Requeueing is a manual triggering method. After starting the plan, you can click Requeue to activate the task immediately, eliminating the need to wait for the scheduled time.

[0156] Each step is interrelated: first create and start the plan, then configure the timing strategy, and finally execute the task by requeuing or waiting for the system timing.

[0157] Figure 2 This is a structural diagram of an interface docking data acquisition system based on an e-commerce SaaS ERP system provided by the present invention, such as Figure 2As shown, the system includes: an acquisition unit 10: used to obtain interface authorization codes of different ERP systems, and generate corresponding target authorization codes according to platform rules; a first configuration unit 20: used to configure a connector based on the target authorization code; the connector is a server connection information tool configured exclusively for the user; a generation unit 30: used to generate a corresponding integration plan based on the configured connector; each integration plan corresponds to the interface docking requirements of a business; a second configuration unit 40: used to construct a source platform configuration plan for the integration plan; a third configuration unit 50: used to construct a target platform configuration plan for the integration plan; a timing and start unit 60: used to start the integration plan and set the timing strategy based on the configured source platform and target platform.

[0158] Figure 3 is a schematic diagram of the structure of the electronic device provided by the present invention, such as Figure 3 As shown, the electronic device may include: a processor 310, a communication interface 320, a memory 330 and a communication bus 340, wherein the processor 33, the communication interface 320 and the memory 330 complete mutual communication through the communication bus 340. The processor 33 may call the logic instructions in the memory 330 to execute an interface docking and data acquisition method based on an e-commerce SaaS ERP system, the method comprising: obtaining interface authorization codes of different ERP systems, and generating corresponding target authorization codes according to platform rules; configuring a connector based on the target authorization code; the connector is a server connection information tool configured exclusively for the user; generating a corresponding integration plan based on the configured connector; each integration plan corresponds to an interface docking requirement of a business; constructing a source platform configuration plan for the integration plan; constructing a target platform configuration plan for the integration plan; starting the integration plan and setting a timing strategy based on the source platform configuration plan and the target platform configuration plan.

[0159] In addition, the logic instructions in the above-mentioned memory 330 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0160] On the other hand, the present invention also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the computer can execute an interface docking and data acquisition method based on an e-commerce SaaS ERP system provided by the above methods, and the method includes: obtaining interface authorization codes of different ERP systems, and generating corresponding target authorization codes according to platform rules; configuring a connector based on the target authorization code; the connector is a server connection information tool configured exclusively for the user; generating a corresponding integration plan based on the configured connector; each integration plan corresponds to an interface docking requirement of a business; for the integration plan, constructing a source platform configuration plan; for the integration plan, constructing a target platform configuration plan; based on the source platform configuration plan and the target platform configuration plan, starting the integration plan and setting a timing strategy.

[0161] On the other hand, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to execute the above-mentioned interface docking and data acquisition method based on an e-commerce SaaS ERP system, the method comprising: obtaining interface authorization codes of different ERP systems, and generating corresponding target authorization codes according to platform rules; configuring a connector based on the target authorization code; the connector is a server connection information tool configured exclusively for the user; generating a corresponding integration plan based on the configured connector; each integration plan corresponds to an interface docking requirement of a business; constructing a source platform configuration plan for the integration plan; constructing a target platform configuration plan for the integration plan; starting the integration plan and setting a timing strategy based on the source platform configuration plan and the target platform configuration plan.

[0162] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, i.e., they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art may understand and implement it without creative effort.

[0163] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0164] The above description is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can make equivalent replacements or changes according to the technical scheme and inventive concept of the present invention within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.

Claims

1. A method for obtaining data through interface connection based on e-commerce SaaS ERP system, characterized in that: The following steps are involved: Obtain the interface authorization codes of different ERP systems and generate corresponding target authorization codes according to platform rules; Based on the target authorization code, a connector is configured; the connector is a server connection information tool configured exclusively for the user; Generate a corresponding integration solution based on the configured connector; each integration solution corresponds to an interface connection requirement of a business; Constructing a source platform configuration plan for the integration plan; Constructing a target platform configuration solution for the integration solution; Based on the source platform configuration scheme and the target platform configuration scheme, the integration scheme is started and a timing strategy is set.

2. The interface docking and data acquisition method based on the e-commerce SaaS ERP system according to claim 1 is characterized in that: Obtain the interface authorization code of different ERP systems and generate the corresponding target authorization code according to the platform rules, and then include: Check in to the open platform and obtain the application key and secret key assigned by the development platform; Apply for API interface permissions from the development platform based on the application key and secret key, and obtain corresponding API interface permissions; Based on the API interface permissions, a standard OAuth2.0 process is used to perform third-party business authorization and generate a business authorization code; The business authorization code is exchanged for an authorization token, and based on the authorization token, an API request is used to obtain merchant data.

3. The interface docking and data acquisition method based on the e-commerce SaaS ERP system according to claim 2 is characterized in that: In the process of exchanging authorization tokens, a dynamic weighted average token generation algorithm is used to dynamically generate the optimal token through the weight distribution of historical requests, including: Normalize the weight values ​​of historical requests; Generate a new token based on the weight value of each request; Correspondingly, the formula for generating a new token is: ； Among them, ω_i represents the weight corresponding to the i-th historical request, ω_j represents the weight corresponding to the j-th non-historical request; request_i represents the feature vector corresponding to each historical request; n represents the number of requests.

4. The interface docking and data acquisition method based on the e-commerce SaaS ERP system according to claim 1 is characterized in that: The process of configuring the connector is as follows: Determine a connector environment, and configure a server based on the connector environment; the connector environment includes production, test, and development; Set the basic parameters of the connector; Based on the connector environment, perform corresponding environment configuration; After completing the development and test configuration, switch the connector to the production environment and check the production environment parameters.

5. The interface docking and data acquisition method based on the e-commerce SaaS ERP system according to claim 1 is characterized in that: The detailed process of the integration solution includes: According to the actual business scenario, clarify the data types and operation targets that need to be synchronized; Configure specific rules for each integration solution based on different business requirements; Before configuring the integration solution, you need to obtain authorization for the data interface; Select the operating environment according to business needs and create an integration solution; Configure the corresponding data source for each integration solution; After completing the configuration of the integration solution, execute the solution in the test environment to verify whether the data synchronization process meets expectations; After the test is passed, the integrated solution will be deployed to the production environment for formal operation.

6. The interface docking and data acquisition method based on the e-commerce SaaS ERP system according to claim 1 is characterized in that: The source platform configuration includes a header area and a sub-tab area, wherein the header area displays substrate information and startup scheme; and the sub-tab area displays the details of various functions.

7. The interface docking and data acquisition method based on the e-commerce SaaS ERP system according to claim 1 is characterized in that: The target platform configuration includes request parameter settings, startup data mapping and support function expressions; Wherein, the request parameter configuration is used to transfer the data field of the target platform; The startup data hard mapping is a static mapping, which is used to configure the mapping relationship between the source platform and the target platform data fields after clicking the static mapping; The supported function expressions are used to process more complex business logic in complex business scenarios.

8. An interface docking and data acquisition system based on an e-commerce SaaS ERP system, characterized in that: include: Acquisition unit: used to obtain the interface authorization codes of different ERP systems and generate corresponding target authorization codes according to platform rules; A first configuration unit: configured to configure a connector based on the target authorization code; the connector is a server connection information tool configured exclusively for a user; Generating unit: used to generate corresponding integration solutions based on the configured connectors; each integration solution corresponds to the interface connection requirements of a business; A second configuration unit: used for constructing a source platform configuration solution for the integration solution; The third configuration unit is used to construct a target platform configuration solution for the integration solution; Timing and starting unit: used to start the integration solution and set the timing strategy based on the configured source platform and the target platform.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of an interface docking and data acquisition method based on an e-commerce SaaS ERP system as described in any one of claims 1 to 7 are implemented.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of an interface docking and data acquisition method based on an e-commerce SaaS ERP system as described in any one of claims 1 to 7 are implemented.

Images