CN115481612A - Table arrangement system and method thereof - Google Patents

Abstract

A table deployment system and method thereof, the table deployment system includes a deployment manager, a plurality of deployment executors and a deployment monitor. The arrangement manager receives a plurality of working tables and divides the working tables into a plurality of table work packages for distribution in sequence, wherein the table work packages all have a specific number of working tables. The deployment executor is used for receiving the table work packages in sequence, correspondingly unpacking the received table work packages to obtain a specific number of work tables, and respectively executing an updating transaction program on the work tables. The deployment monitor captures and displays the results of the deployment executors executing the update transaction program. The table arrangement system can process a large amount of complicated table transaction programs, and reduces the time for additional manual judgment and processing.

Description

Table arrangement system and method thereof

Technical Field

The present invention relates to a form deployment system and method thereof, and more particularly, to a form deployment system and method using production scheduling.

Background

An Enterprise Resource Planning (ERP) ERP system can effectively integrate operation information required by operation processes such as finance, accounting, human resources, manufacturing and selling and the like in an Enterprise through organization and process Planning and application of information technology, and reflect the use condition of resources in the Enterprise in real time to provide a reference for Enterprise decision making, thereby increasing the competitive advantage of the Enterprise.

Because the ERP system can integrate the workflows of various departments, the ERP system must use many worksheets to effectively manage material characteristics and resource changes, such as inventory production, order production or order assembly, etc. with the worksheets. However, the ERP system frequently needs to change the format of the working table according to the requirement during the operation process. Once the modifications are accumulated over a period of time, the number of the work tables to be updated is large, and the updates often require the intervention and supervision of professionals, which results in a large amount of time and labor consumption. And the work form is easy to update failure due to manual careless or no proper supervision interface, and more manpower is required to carry out the fine work.

Disclosure of Invention

In one aspect, a table deployment system is provided, which includes: the system comprises a deployment manager, a management module and a management module, wherein the deployment manager is used for receiving a plurality of working forms, dividing the working forms into a plurality of form working packages and dispatching the form working packages in sequence, and the form working packages are provided with a specific number of working forms; a plurality of deployment executors coupled to the deployment manager, the deployment executors being configured to receive the table work packages assigned by the deployment manager in sequence, wherein each of the deployment executors correspondingly de-packages the received table work packages to obtain the specific number of work tables, and respectively execute an update transaction procedure on the specific number of work tables; and a deployment monitor coupled to the deployment actuators for capturing and displaying results of the deployment actuators executing the update transaction.

In another aspect, a method for deploying a table is provided, which includes: receiving a plurality of worksheets by using a deployment manager, and dividing the worksheets into a plurality of worksheet packages and performing an assigning process to assign the worksheet packages, wherein each worksheet package has a specific number of worksheets; using a plurality of deployment executors to sequentially receive the form work packages assigned by the deployment manager, wherein each deployment executor correspondingly unpacks the received form work packages to obtain a specific number of work forms, and respectively executing an updating transaction program on the specific number of work forms; and using a deployment monitor to capture and display the results of the deployment executors executing the update transaction program.

In one embodiment, the form deployment method further comprises determining whether the form work packages are all assigned for completion using the deployment manager.

In one embodiment, when the deployment manager determines that the dispatching of the form work packages is completed, the method further comprises determining whether an abnormal form work package exists in the form work packages; when the abnormal table work packages do not exist in the table work packages, the deployment manager completes the dispatching program, and when the abnormal table work packages exist in the table work packages, the deployment manager marks an update record state of the abnormal table work packages as update transaction failure.

In one embodiment, when the deployment manager determines that the dispatching of the table workflows is not completed, the deployment manager further determines whether a system resource utilization upper limit has been reached; when the system resource use upper limit is reached, the deployment manager suspends the dispatching program, and when the system resource use upper limit is not reached, the deployment manager continues the dispatching program and dispatches a table work package which does not execute the update to the deployment executor.

In one embodiment, the table deployment method further includes using the deployment executors to determine whether an exception occurs when the update transaction is executed on each of the specific number of working tables.

In one embodiment, when the exception procedure is executed, the deployment executor marks an update record status of a corresponding working table as an update exception failure, and when the exception procedure is not executed, the deployment executor further determines whether there are working tables for which the update exception procedure is not executed.

In one embodiment, when the deployment executor determines that there is no working table that has not yet executed the update transaction process, the deployment executor further marks an update record status of a corresponding table working packet of the working table with the update transaction failure flag as update transaction failure.

In one embodiment, retrieving, using the deployment monitor, results of the execution of the update transaction by the deployment executors further comprises: an update record status of each of the table workflows is periodically retrieved using the deployment monitor.

In one embodiment, the table deployment method further includes receiving a re-execution instruction by using the deployment monitor, and calling a corresponding deployment executor to re-execute the update transaction program for the corresponding table work package according to the re-execution instruction.

Therefore, according to the technical content of the present disclosure, when executing the update transaction of the working form, the deployment manager first divides a large number of working forms into a plurality of form working packages containing a certain number of working forms, then sequentially assigns the form working packages to the deployment executor to perform the update transaction of the working forms, and further uses the deployment monitor to perform the real-time monitoring and debugging processing procedure of the update transaction.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the embodiments.

FIG. 1 is a schematic diagram of a table deployment system utilizing production scheduling in accordance with a preferred embodiment of the present invention;

FIG. 2 is a flowchart illustrating a method performed by the deployment manager according to a preferred embodiment of the present invention;

FIG. 3 is a flow chart of a method for deploying actuators according to a preferred embodiment of the present invention;

fig. 4 is a flowchart illustrating a method performed by the deployment monitor according to a preferred embodiment of the present invention.

[ description of symbols ]

100 form deployment system

110 deployment manager

112 deployment actuator

114 deployment monitor

200 deployment manager execution method

202-218 step

300 executing method for deploying actuator

302-318 step

400 deployment monitor execution method

402-414 steps

Detailed Description

The spirit of the present disclosure will be described in detail with reference to the drawings, and it should be understood that the embodiments of the present disclosure can be changed and modified by the technology taught in the present disclosure without departing from the spirit and scope of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The singular forms "a", "an", "the" and "the", as used herein, also include the plural forms.

As used herein, the term "couple" or "connect" refers to two or more elements or devices being in direct or indirect physical contact with each other, and may refer to two or more elements or devices operating or acting together.

As used herein, the terms "comprising," "including," "having," "containing," and the like are open-ended terms that mean including, but not limited to.

As used herein, "and/or" is inclusive of any and all combinations of the recited thing.

With respect to the term (terms) used herein, it is generally understood that each term has its ordinary meaning in the art, in the context of this document, and in the context of particular contexts, unless otherwise indicated. Certain words used to describe the disclosure are discussed below or elsewhere in this specification to provide additional guidance to those skilled in the art in describing the disclosure.

FIG. 1 is a schematic diagram of a table deployment system using production schedules in accordance with a preferred embodiment of the present invention. The form deployment system 100 adopts a scheduling method to schedule a plurality of work forms to be updated in the ERP system in advance, so as to smoothly complete the updating of the plurality of work forms under the condition of meeting the limitation of system resources. In one embodiment, the table deployment system 100 includes a deployment manager 110, a plurality of deployment executors 112, and a deployment monitor 114. The deployment manager 110 is configured to split a table package containing a plurality of work tables to be updated in the ERP system into a plurality of table work packages, and sequentially assign the table work packages to the deployment executors 112 for execution. Wherein, each table work package has the same number of work tables to be updated. In one embodiment, assuming that an ERP system includes 1000 bundles of worksheets to be updated, deployment manager 110 may split the bundles of worksheets, for example, split the bundles of worksheets into 250 bundles of worksheets, each of which includes 5 worksheets to be updated. The deployment manager 110 sequentially assigns the 250 table work packages to the deployment executors 112 according to the system processable resources, for example, only five deployment executors 112 are allowed to execute the update procedure of the work table at the same time according to the system processable resources, so that the deployment manager 110 assigns the table work packages to the five deployment executors 112 for execution in advance, and performs the subsequent table work package assignment after the deployment executors 112 perform the update. It should be noted that the number of splits of the table packet is not limited to the above, and may be changed according to the processing resources of the system.

The deployment executor 112 is coupled to the deployment manager 110. The deployment executor 112 unpacks the form bundle dispatched by the deployment manager 110 into a plurality of work forms to perform an update procedure on the plurality of work forms in the form bundle, and in one embodiment, the deployment executor 112 performs a form transaction handler on the work forms to perform a form update. The deployment executor 112 further marks failure of update transaction when the table update transaction is abnormal. The deployment monitor 114 is coupled to the deployment executors 112 for monitoring the execution results of the deployment executors 112. In one embodiment, the deployment monitor 114 periodically retrieves the execution results of the deployment executor 112 and reports back to the logists, so that the deployment monitor 114 can check the records and handle the results when there is an abnormal condition.

Specifically, the form deployment system 100 disclosed herein may be implemented in a variety of different ways, including software, hardware, or any combination thereof. In one embodiment, the table deployment system 100 may be, but is not limited to, a microprocessor, a microcontroller, a complex instruction set computing microprocessor, a reduced instruction set computing microprocessor, a Very Long Instruction Word (VLIW) microprocessor, a hyper-parallel instruction set computing microprocessor, a graphics processor, a digital signal processor, or any other type of processor. In another embodiment, the table deployment system 100 may include a processor and a memory storing a computer program code that is accessible and executable by the processor. The deployment manager 110, deployment executors 112 and deployment monitor 114 functions may be implemented when computer program code in memory is executed by a processor, the memory may comprise elements suitable for storing data and machine-readable instructions, such as, but not limited to, read Only Memory (ROM), random Access Memory (RAM), erasable Programmable Read Only Memory (EPROM), electrically Erasable Programmable Read Only Memory (EEPROM). The account database 140 may be any type of fixed or removable Random Access Memory (RAM), read-Only Memory (ROM), flash Memory (flash Memory), hard Disk Drive (HDD), solid State Drive (SSD), or the like or any combination thereof. The computer program Code may be combinatorial language instructions, instruction set architecture instructions, machine related instructions, microinstructions, solid state instructions, or Object Code written in any combination of one or more programming languages, including Object oriented programming languages, such as: common Lisp, python, C + +, objective-C, smalltalk, delphi, java, swift, C #, perl, ruby, and PHP, etc., as well as conventional Procedural (Procedural) programming languages, such as: c or a similar programming language.

Fig. 2 is a flow chart illustrating a method executed by the deployment manager according to a preferred embodiment of the present invention. The deployment manager executes the method 200 by first receiving the spreadsheet package at step 202, including determining if there is an abnormal outstanding dispatched worksheet package. And establishing a working directory to copy the form package file into the working directory. In one embodiment, assuming that an ERP system contains 1000 form packages of the working forms to be updated, the deployment manager 110 in the form deployment system 100 receives the file path of the form package and creates a working directory in the ERP system to be subjected to form update so as to copy the file of the form package into the working directory.

At step 204, the form package is unpacked, and in one embodiment, the deployment manager 110 unpacks the form package to restore 1000 working forms to be updated.

In step 206, all the worksheets are divided into a plurality of worksheet packages according to a set number, and the worksheet packages are distributed. In one embodiment, the deployment manager 110 may split 1000 sheets of the work table to be updated according to a certain number, for example, split 1000 sheets of the work table to be updated into 250 sheet work packages according to a certain number of 5 sheets, so that each sheet work package includes 5 sheets of the work table to be updated. In other embodiments, the splitting of the work table to be updated may be performed according to other numbers, which are not limited to the above embodiments.

In step 208, it is determined whether all form work packages have been allocated. In one embodiment, after the deployment manager 110 splits all the worksheets into a plurality of sheet worksheets according to a predetermined number, the sheet worksheets are sequentially distributed to the following deployment executors 112 according to the system processing resources, and it is determined whether all the sheet worksheets have been distributed. If there is no table work package allocated yet, go to step 210 to determine whether the upper limit of available system resources has been reached. In one embodiment, since the system resources have to perform other daily tasks, only a certain number of deployment executors 112 are allowed to execute the worksheet update procedure at the same time, so in step 210, the deployment manager 110 first determines whether the upper system resource limit available for executing the worksheet update has been reached, and if not, the deployment manager 110 continues the dispatching procedure in step 212, in one embodiment, the deployment manager 110 calls a deployment executor 112 to dispatch a worksheet that has not yet executed the update to the deployment executor 112, executes the unpacking of the worksheet and the worksheet transaction procedure, and sets initial records, such as the initial update record, for subsequent checking, and again executes step 208 to determine whether all worksheets have been allocated. On the other hand, if it is determined in step 210 that the upper limit of available system resources has been reached, the deployment manager 110 suspends the dispatch execution and proceeds to step 208 again to determine whether all the table work packages have been allocated.

If in step 208, it is determined that all the form work packages have been dispatched, in step 214, it is determined whether there are any abnormal unfinished form work packages. If there are no exception outstanding form packages, then the deployment of the form packages is complete in step 218. On the contrary, if there is an abnormal incomplete table bundle, for example, the table bundle is abnormally incomplete when the table bundle is split into a plurality of table bundles, the update status of the table bundle whose assignment cannot be completed due to the abnormality is recorded as an update transaction failure in step 216.

FIG. 3 is a flowchart illustrating a method for executing a deployment executor according to a preferred embodiment of the present invention. The deployment executor performs the method 300 by first receiving a form work package at step 302. Including receiving a table work package path and creating a work directory to copy the table work package files into the work directory. In one embodiment, the deployment executor 112 in the table deployment system 100 receives the path of the table bundle file and creates a working directory in the ERP system to be subjected to the table update, so as to copy the table bundle file into the working directory.

At step 304, the form work package is unpacked, and in one embodiment, the deployment executor 110 unpacks the form work package to restore 5 work forms to be updated. At step 306, the job table execution order is sorted according to the list in the table bundle. In one embodiment, the deployment executor 110 orders the 5 worksheets according to a set executive to execute the worksheet update transaction in this order. In step 308, the call form transaction process proceeds to the worksheet update transaction process. In one embodiment, the deployment executor 110 calls a form transaction program to perform a worksheet update transaction program. In step 310, the deployment executor 110 determines whether an exception occurs in the worksheet update exception procedure. If the worksheet update transaction is abnormal, in step 312, a failure in updating the transaction is indicated. In one embodiment, when the deployment executor 110 performs a table update exception procedure, if an exception condition occurs, for example, the update procedure cannot be executed, the deployment executor 110 marks the update condition of the table as an exception, and then proceeds to step 314 to determine whether there are any tables that have not executed the table update exception procedure. On the other hand, if the deployment executor 110 determines that the exception condition does not occur in the table updating exception program in step 310, step 314 is also executed to determine whether there is a working table in the table working package that does not execute the table updating exception program.

If there are working tables without executing the table transaction program, go to step 308 again, call the table transaction program to update the working tables. Otherwise, if all the transaction procedures of the working tables in a table package have been executed, step 316 is executed, if there is a working table transaction exception, the record of the table package is marked as update transaction failure, and the transaction procedures of the table package are completed in step 318.

Fig. 4 is a flowchart illustrating a method performed by the deployment monitor according to a preferred embodiment of the present invention. The deployment monitor performs the method 400 by first retrieving and displaying records of each table bundle in step 402. In one embodiment, the deployment monitor 114 in the form deployment system 100 retrieves the records of each form job package and displays the retrieved records, and the end-user confirms the execution results of each form job package. In step 404, a period of time is waited for, and in step 406, the records of each table task package are retrieved again to update the execution results of each table task package. In one embodiment, since the deployment executor 110 continuously updates the worksheet, the deployment monitor 114 periodically, for example, every 3 seconds, retrieves the record of the deployment executor 110 executing the worksheet bundle to update the transaction result of the worksheet bundle. In other embodiments, the period is not limited to 3 seconds. In step 408, it is determined whether a person is designated to re-execute one of the form work packages. In one embodiment, a back-end worker may specify to re-execute the transaction of a form job package when the record of the form job package indicates an exception. In this way, deployment monitor 114 receives a re-execution instruction, and in step 410, deployment monitor 114 calls deployment executor 112 to re-execute the transaction of the table bundle. In one embodiment, the deployment executor re-executes the form work package after receiving the deployment monitor call, unpacks the form work package, and calls a form transaction program to update the work form. In another embodiment, if it is determined in step 408 that no one of the forms is designated to be re-executed, step 412 is executed to determine whether a leave button is pressed. If the away button is manually pressed, the monitoring procedure ends in step 414. Otherwise, if it is determined in step 412 that the leave button has not been pressed, step 404 is executed again, and after waiting for a period of time, the records of the respective table work packages are retrieved again to update the execution results of the respective table work packages.

Therefore, when the working form updating transaction is executed, the deployment manager divides a large number of working forms into a plurality of form working packets containing a certain number of working forms, then the form working packets are sequentially distributed to the deployment executor to update the working forms, and the deployment monitor is used for performing real-time monitoring and debugging processing procedures of the updating transaction. In addition, the invention can be applied to the condition of updating a large amount of tables and can be applied to the condition of updating a small amount of tables, thereby meeting the requirement of updating a small amount of tables for multiple times.

Although the present disclosure has been described with reference to particular embodiments, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the disclosure, and therefore, the scope of the disclosure is to be determined by the appended claims.

Claims (10)

1. A form deployment system, comprising:

the system comprises a deployment manager, a management module and a management module, wherein the deployment manager is used for receiving a plurality of working forms, dividing the working forms into a plurality of form working packages and distributing the form working packages in sequence, and the form working packages are provided with a specific number of working forms;

a plurality of deployment executors coupled to the deployment manager, the deployment executors being configured to receive the table work packages assigned by the deployment manager in sequence, wherein each of the deployment executors correspondingly de-packages the received table work packages to obtain the specific number of work tables, and respectively execute an update transaction procedure on the specific number of work tables; and

and a deployment monitor coupled to the deployment actuators for capturing and displaying the results of the update transaction executed by the deployment actuators.

2. A method for deploying a table, comprising:

receiving a plurality of worksheets by using a deployment manager, and dividing the worksheets into a plurality of worksheet packages and performing a dispatching procedure to dispatch the worksheet packages, wherein the worksheets each have a specific number of worksheets;

using a plurality of deployment executors to sequentially receive the form work packages assigned by the deployment manager, wherein each deployment executor correspondingly unpacks the received form work packages to obtain a specific number of work forms, and respectively executing an updating transaction program on the specific number of work forms; and

and a deployment monitor is used for capturing and displaying the results of the deployment executors executing the updating transaction program.

3. The form deployment method of claim 2, further comprising using the deployment manager to determine whether the form work packages have all been dispatched.

4. The form deployment method of claim 3, wherein when the deployment manager determines that the form work packages have been assigned, further comprising determining whether there is an abnormal form work package in the form work packages;

wherein the deployment manager completes the dispatch procedure when there is no abnormal table work package in the table work packages, an

When the abnormal table work packages exist in the table work packages, the deployment manager marks an updating record state of the abnormal table work packages as updating transaction failure.

5. The form deployment method of claim 3, wherein when the deployment manager determines that the form work packages are not completely assigned, further comprising determining whether a system resource usage upper limit has been reached;

wherein the deployment manager suspends the dispatch procedure when the upper limit of system resource usage is reached, and

when the system resource use upper limit is not reached, the deployment manager continues the dispatching program and dispatches a table work package which is not updated to the deployment executor.

6. The form deployment method of claim 2, further comprising using the deployment executors to determine whether an exception occurs when the update transaction is executed separately for the specific number of working forms.

7. The form deployment method of claim 6, wherein the deployment executor marks an update record status of the corresponding working form as update transaction failure when the execution of the update transaction procedure is abnormal, and

when the abnormal updating program is executed, the deployment executor judges whether a working table which is not executed yet exists.

8. The form deployment method of claim 7, wherein when the deployment executor determines that there is no working form that has not executed the update transaction procedure, the deployment executor further marks an update record status of a corresponding form working package of the working form with the update transaction failure flag as update transaction failure.

9. The method of claim 2, wherein retrieving, using the deployment monitor, results of the executing of the update transaction by the deployment executors further comprises: an update record status of each of the table workflows is periodically retrieved using the deployment monitor.

10. The method of claim 9, further comprising receiving a re-execution instruction using the deployment monitor to call a corresponding deployment executor to re-execute the update transaction for the corresponding table bundle according to the re-execution instruction.

Images