Table Deployment System and Its Method

Abstract

A form deployment system and its method. The form deployment system includes a deployment manager, multiple deployment executors, and a deployment monitor. The deployment manager receives multiple work forms and splits them into multiple form work packages for sequential dispatching, where each of these form work packages has a specific number of work forms. The deployment executors are used to sequentially receive these form work packages, unpack the received form work packages to obtain a specific number of work forms, and respectively execute an update and change procedure on the work forms. The deployment monitor captures and displays the results of these deployment executors executing the update and change procedure. Through the above form deployment system, a large number of complex form change procedures can be processed, reducing the time required for additional manual judgment and processing.

Description

Technical Field

[0001] The present invention relates to a form deployment system and method, and more particularly to a form deployment system and method using production scheduling. Background Art

[0002] Enterprise Resource Planning (ERP) system can integrate the operation information required by internal enterprise operation processes including finance, accounting, human resources, manufacturing, and sales, etc., through the planning of organization and processes and the application of information technology to achieve effective integration, and instantaneously reflect the usage status of internal enterprise resources to provide reference for enterprise decision-making, thereby being an integrated information system capable of increasing the competitive advantage of the enterprise.

[0003] Since the ERP system can integrate the work processes of various departments, the ERP system must use many work forms to effectively manage material characteristics and resource changes. For example, work forms are used to manage inventory production, order production, or order assembly, etc. However, during the operation of the ERP system, it is often necessary to change the format of work forms according to requirements. Once cumulative modifications have been made over a period of time, the number of work forms to be updated is numerous. Professional personnel often need to intervene and supervise during the update, resulting in a large consumption of time and manpower. It is also easy for the update of work forms to fail due to human negligence or lack of a proper supervision interface, and more manpower is required for follow-up work. Summary of the Invention

[0004] An embodiment of the present case provides a form deployment system, including: a deployment manager for receiving multiple work forms, and splitting the work forms into multiple form work packages and sequentially dispatching them, where each of the form work packages has a specific number of work forms; a plurality of deployment executors coupled to the deployment manager, the deployment executors being used to sequentially receive the form work packages dispatched by the deployment manager, where each of the deployment executors correspondingly unpacks the received form work package to obtain the specific number of work forms, and respectively executes an update and change program on the specific number of work forms; and a deployment monitor coupled to the deployment executors for capturing and displaying the results of the deployment executors executing the update and change program.

[0005] Another embodiment of this case is to provide a form deployment method, including: using a deployment manager to receive multiple work forms, splitting these work forms into multiple form work packages and performing a dispatching process to dispatch these form work packages, where each of these form work packages has a specific number of work forms; using multiple deployment executors to sequentially receive these form work packages dispatched by the deployment manager, where each of these deployment executors unpacks the received form work package to obtain the specific number of work forms, and respectively executes an update change process on the specific number of work forms; and using a deployment monitor to capture and display the results of these deployment executors executing the update change process.

[0006] In one embodiment, the form deployment method further includes using the deployment manager to determine whether all of these form work packages have been dispatched.

[0007] In one embodiment, when the deployment manager determines that all of these form work packages have been dispatched, it further includes determining whether there are abnormal form work packages among these form work packages; when there are no abnormal form work packages among these form work packages, the deployment manager completes the dispatching process, and when there are abnormal form work packages among these form work packages, the deployment manager marks the update record status of the abnormal form work package as update change failure.

[0008] In one embodiment, when the deployment manager determines that these form work packages have not been dispatched completely, it further includes determining whether a system resource usage limit has been reached; when the system resource usage limit is reached, the deployment manager suspends the dispatching process, and when the system resource usage limit is not reached, the deployment manager continues the dispatching process and dispatches a form work package that has not been updated to the deployment executor.

[0009] In one embodiment, the form deployment method further includes using these deployment executors to determine whether an abnormality occurs when respectively executing the update change process on the specific number of work forms.

[0010] In one embodiment, when an abnormality occurs during the execution of the update change process, the deployment executor marks the update record status of the corresponding work form as update change failure, and when no abnormality occurs during the execution of the update change process, the deployment executor further determines whether there are still work forms on which the update change process has not been executed.

[0011] In one embodiment, when the deployment executor determines that there are no work forms on which the update change process has not been executed, the deployment executor further marks the update record status of the corresponding form work package of the work form with the update change failure mark as update change failure.

[0012] In one embodiment, using the deployment monitor to capture the results of the deployment executors executing the update change program further includes: using the deployment monitor to periodically capture an update record status of each of the table work packages.

[0013] In one embodiment, the table deployment method further includes using the deployment monitor to receive a re-execution instruction, and calling a corresponding deployment executor to re-execute the update change program for the corresponding table work package according to the re-execution instruction.

[0014] Therefore, according to the technical content of this case, when performing the update change of the work table in this case, the deployment manager first splits a large number of work tables into multiple table work packages each containing a certain number of work tables, and then sequentially assigns these table work packages to the deployment executors for the update change of the work table. In addition, a deployment monitor is used for real-time monitoring and error handling of the update change. Therefore, through the above production scheduling mechanism, a large number of complex table change programs are processed, reducing the time required for additional manual judgment and processing, and relatively improving the system availability and reliability. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawings herein are incorporated into the specification and form a part of the specification. These drawings illustrate embodiments consistent with the present invention and, together with the specification, are used to explain the technical solutions of the embodiments of the present invention.

[0016] Figure 1 The schematic diagram of a table deployment system using production scheduling according to a preferred embodiment of the present invention is shown;

[0017] Figure 2 The flowchart of the execution method of the deployment manager according to a preferred embodiment of the present invention is shown;

[0018] Figure 3 The flowchart of the execution method of the deployment executor according to a preferred embodiment of the present invention is shown;

[0019] Figure 4 The flowchart of the execution method of the deployment monitor according to a preferred embodiment of the present invention is shown.

[0020]

Symbol Description

[0021] 100: Table deployment system

[0022] 110: Deployment manager

[0023] 112: Deployment executor

[0024] 114: Deployment monitor

[0025] 200: Execution method of the deployment manager

[0026] 202 - 218: Steps

[0027] 300: Method for Deploying and Executing Actuators

[0028] 302 - 318: Steps

[0029] 400: Method for Deploying and Monitoring Executions

[0030] 402 - 414: Steps Detailed Implementation Manner

[0031] The spirit of this case will be clearly explained below with the accompanying drawings and detailed descriptions. After understanding the embodiments of this case, any person with ordinary knowledge in the relevant technical field can make changes and modifications based on the techniques taught in this case without departing from the spirit and scope of this case.

[0032] The terms used in this article are only for describing specific embodiments and are not intended to limit this case. Singular forms such as "a", "this", "this", "the present", and "the" also include plural forms as used herein.

[0033] Regarding the use of "coupled" or "connected" in this article, it can refer to two or more elements or devices making direct physical contact with each other, or making indirect physical contact with each other, and can also refer to two or more elements or devices operating or acting on each other.

[0034] Regarding the use of "comprising", "including", "having", "containing", etc. in this article, they are all open - ended terms, meaning including but not limited to.

[0035] Regarding the use of "and / or" in this article, it includes any one or all combinations of the described things.

[0036] Regarding the terms used in this article, unless otherwise specified, they generally have their ordinary meanings in the relevant technical field, in the context of this case, and in the specific context. Some terms used to describe this case will be discussed below or elsewhere in this specification to provide additional guidance to those skilled in the art in the description of this case.

[0037] Please refer to Figure 1The following is a schematic diagram of a form deployment system using production scheduling according to a preferred embodiment of the present invention. The form deployment system 100 adopts a scheduling method to pre-schedule multiple work forms to be updated in the ERP system, so as to successfully complete the update of multiple work forms under the condition of meeting the system resource constraints. In one embodiment, the form deployment system 100 includes a deployment manager 110, a plurality of deployment executors 112, and a deployment monitor 114. The deployment manager 110 is used to split a form package containing multiple work forms to be updated in the ERP system into multiple form work packages, and sequentially assign them to the plurality of deployment executors 112 for execution. Among them, each form work package has the same number of work forms to be updated. In one embodiment, assuming that a form package in an ERP system contains 1000 work forms to be updated, the deployment manager 110 can split this form package. For example, the form package is split into 250 form work packages, and each form work package includes 5 work forms to be updated. Among them, the deployment manager 110 sequentially assigns these 250 form work packages to a plurality of deployment executors 112 according to the system's available resources. For example, according to the system's available resources, only five deployment executors 112 are allowed to execute the update program of work forms at the same time. Accordingly, the deployment manager 110 will first assign the form work packages to five deployment executors 112 for execution. After one of the deployment executors 112 finishes the update, subsequent form work packages will be assigned. It should be noted that the splitting quantity of the form package is not limited to the above, and can be changed according to the system's processing resources.

[0038] The deployment executor 112 is coupled to the deployment manager 110. The deployment executor 112 is used to unpack multiple work forms from the form work package assigned by the deployment manager 110, so as to perform an update program on the multiple work forms in this form work package. In one embodiment, the deployment executor 112 performs a form change processing program on the work form to perform form update. The deployment executor 112 further marks the update failure when the form update change processing is abnormal. The deployment monitor 114 is coupled to the plurality of deployment executors 112 and is used to monitor the execution results of the deployment executors 112. In one embodiment, the deployment monitor 114 will periodically retrieve the execution results of the deployment executors 112 and report them to the logistics personnel, so that the logistics personnel can immediately view the records of the deployment monitor 114 and handle them when there are abnormal conditions in the execution results.

[0039] It should be specifically noted that the form deployment system 100 disclosed in this case can be implemented in various different ways, including software, hardware, or any combination thereof. In one embodiment, the form deployment system 100 can 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 microprocessor, a super parallel instruction set computing microprocessor, a graphics processing unit, a digital signal processor, or any other type of processor. In another embodiment, the form deployment system 100 can include a processor and a memory. The memory stores a computer program code, which can be accessed and executed by the processor. When the computer program code in the memory is executed by the processor, the functions of the deployment manager 110, multiple deployment executors 112, and a deployment monitor 114 in this case can be realized. The memory can include components 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 can be any type of fixed or removable random access memory (RAM), read only memory (ROM), flash memory, hard disk drive (HDD), solid state drive (SSD), or similar components, or a combination of the above components. The computer program code can be assembly language instructions, instruction set architecture instructions, machine instructions, machine-related instructions, microinstructions, solid instructions, or source code or object code written in any combination of one or more programming languages. The programming languages include object-oriented programming languages, such as: Common Lisp, Python, C++, Objective-C, Smalltalk, Delphi, Java, Swift, C#, Perl, Ruby, and PHP, etc., and conventional procedural programming languages, such as: C language or similar programming languages.

[0040] Figure 2The flowchart of the execution method of the deployment manager according to a preferred embodiment of the present invention is shown. For the execution method 200 of the deployment manager, first, at step 202, a table package is received, including determining whether there is an abnormal unassigned work table package. A path is obtained, and a working directory is created to copy the table package file into the working directory. In an embodiment, it is assumed that a table package containing 1000 work tables to be updated is included in an ERP system. The deployment manager 110 in the table deployment system 100 receives the path of this table package file and creates a working directory in the ERP system where the table update is to be performed to copy this table package file into the working directory.

[0041] At step 204, the table package is unpacked. In an embodiment, the deployment manager 110 unpacks the table package to restore 1000 work tables to be updated.

[0042] At step 206, all work tables are split into multiple table work packages according to a certain quantity according to a setting, and table work package distribution is performed. In an embodiment, the deployment manager 110 can split 1000 work tables to be updated according to a certain quantity. For example, 1000 work tables to be updated are split into 250 table work packages according to a certain quantity of 5. Therefore, each table work package includes 5 work tables to be updated. In other embodiments, the work tables to be updated can be split according to other quantities, not limited to the above embodiment.

[0043] In step 208, it is determined whether all table work packages have been allocated. In one embodiment, after the deployment manager 110 splits all work tables into multiple table work packages according to a setting, these multiple table work packages can be sequentially assigned to subsequent multiple deployment executors 112 according to the system processing resources, and it is determined whether all table work packages have been allocated. If there are still unallocated table work packages, step 210 is executed to determine whether the upper limit of available system resources has been reached. In one embodiment, since the system resources are also required to execute other daily tasks, only a certain number of deployment executors 112 are allowed to execute the work table update program at the same time. Therefore, in step 210, the deployment manager 110 first determines whether the upper limit of the system resources available for executing the work table update has been reached. If the upper limit of the system resources has not been reached, in step 212, the deployment manager 110 continues with the assignment process. In one embodiment, the deployment manager 110 calls a deployment executor 112 to assign an unexecuted table work package to the deployment executor 112, execute the unpacking of the table work package and perform the work table change procedure, and set an initial record, such as an initial update record, for subsequent inspection, and then execute step 208 again to determine whether all table work packages 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 execution of the assignment and executes step 208 again to determine whether all table work packages have been allocated.

[0044] If it is determined in step 208 that all table work packages have been assigned, in step 214, it is determined whether there are abnormally unfinished table work packages. If there are no abnormally unfinished table work packages, the deployment of the table work packages is completed in step 218. On the contrary, if there are abnormally unfinished table work packages, for example, if a table work package is abnormally unfinished when splitting the table package into multiple table work packages, the update status of this abnormally unassignable table work package is recorded as an update failure in step 216.

[0045] Figure 3 The flowchart of the execution method of the deployment executor according to a preferred embodiment of the present invention is shown. The execution method 300 of the deployment executor first receives a table work package in step 302. This includes receiving the table work package path and creating a working directory to copy the table work package file into the working directory. In one embodiment, the deployment executor 112 in the table deployment system 100 receives this table work package file path and creates a working directory in the ERP system where the table update is to be performed to copy this table work package file into the working directory.

[0046] In step 304, the table work package is unpacked. In one embodiment, the deployment executor 112 unpacks the table work package to restore the five worksheets to be updated. In step 306, the worksheet execution order is sorted according to the list in the table work package. In one embodiment, the deployment executor 112 sorts the five worksheets according to a set execution program to execute the worksheet update change program in this order. In step 308, the table change program is called to perform the worksheet update change program. In one embodiment, the deployment executor 112 calls a table change program to perform the worksheet update change program. In step 310, the deployment executor 112 determines whether an exception occurs in the worksheet update change program. If an exception occurs in the worksheet update change program, in step 312, the update change is marked as failed. In one embodiment, when the deployment executor 112 is performing a worksheet update transaction, if an abnormal situation occurs, for example, the update process cannot be executed, the deployment executor 112 marks the update status of the worksheet as abnormal, and then executes step 314 to determine whether there are still worksheets that have not executed the form update transaction process. On the other hand, if the deployment executor 112 determines that the worksheet update transaction process has not occurred an abnormal situation in step 310, it also executes step 314 to determine whether there are still worksheets in the form work package that have not executed the form transaction process.

[0047] If there are still worksheets that have not executed the table change procedure, step 308 is executed again to call the table change procedure to update the worksheet. On the contrary, if the change procedures of all worksheets in a table work package have been executed, step 316 is executed. If there is an abnormal change in one worksheet, the record of this table work package is marked as failed to update the change, and the change procedure of the table work package is completed in step 318.

[0048] Figure 4The flowchart of the method for deploying and monitoring the execution of a preferred embodiment of the present invention is shown. For the method 400 for deploying and monitoring the execution, first, at step 402, the records of each form work package are retrieved and displayed. In one embodiment, the deployment monitor 114 in the form deployment system 100 retrieves the records of each form work package and displays the retrieval results, and the on-site staff confirms the execution results of each form work package. At step 404, a cycle time is waited for, and at step 406, the records of each form work package are retrieved again to update the execution results of each form work package. In one embodiment, since the deployment executor 112 continuously updates the work form, the deployment monitor 114 retrieves the records of the form work packages executed by the deployment executor 112 periodically, such as every 3 seconds, to update the change results of the form work packages. In other embodiments, this cycle is not limited to 3 seconds. At step 408, it is determined whether someone has manually specified to re-execute one of the form work packages. In one embodiment, when the record of one of the form work packages shows an abnormality, a back-end staff member can specify to re-execute the change procedure of this form work package. Accordingly, the deployment monitor 114 receives a re-execution instruction, and at step 410, the deployment monitor 114 calls the deployment executor 112 to re-execute the change procedure of this form work package. In one embodiment, after receiving the call from the deployment monitor, the deployment executor re-executes this form work package again, unpacks this form work package, and calls a form change procedure to update the work form. In another embodiment, if at step 408, it is determined that no one has manually specified to re-execute one of the forms, step 412 is executed to determine whether someone has manually pressed the exit button. If someone has manually pressed the exit button, then at step 414, this monitoring program is ended. On the contrary, if at step 412, it is determined that no one has manually pressed the exit button, step 404 is re-executed, a cycle time is waited for, and then the records of each form work package are retrieved again to update the execution results of each form work package.

[0049] Accordingly, when the present case executes the update and change of the work form, first, the deployment manager splits a large number of work forms into multiple form work packages each containing a certain number of work forms, and then distributes these form work packages to the deployment executor in sequence for the update and change of the work form. In addition, a deployment monitor is used for real-time monitoring and error handling procedures for the update and change. Therefore, through the above production scheduling mechanism, a large number of complex form change procedures are processed, the time required for additional manual judgment and processing is reduced, and the availability and reliability of the system are relatively improved. In addition, the present invention can be applied not only to the situation of a large number of form updates but also to the situation of a small number of form updates, meeting the requirements of small and multiple updates.

[0050] Although the present case is disclosed above by way of embodiments, it is not intended to limit the present case. Any person skilled in the art can make various modifications and refinements without departing from the spirit and scope of the present case. Therefore, the protection scope of the present case shall be subject to the scope defined by the appended claims.

Claims

1. A table deployment system, characterized in that, Comprising: A deployment manager for receiving multiple work sheets and splitting the work sheets into multiple table work packages and sequentially dispatching them, wherein each of the table work packages has a specific number of work sheets; A plurality of deployment executors coupled to the deployment manager, the deployment executors for sequentially receiving the table work packages dispatched by the deployment manager, wherein each of the deployment executors correspondingly unpacks the received table work package to obtain the specific number of work sheets, and respectively executes an update change program on the specific number of work sheets; And A deployment monitor coupled to the deployment executors for capturing and displaying the results of the deployment executors executing the update change program.

2. A method for table deployment, characterized in that, Comprising: Using a deployment manager to receive multiple work sheets, and splitting the work sheets into multiple table work packages and performing a dispatching process to dispatch the table work packages, wherein each of the table work packages has a specific number of work sheets; Using a plurality of deployment executors to sequentially receive the table work packages dispatched by the deployment manager, wherein each of the deployment executors correspondingly unpacks the received table work package to obtain the specific number of work sheets, and respectively executes an update change program on the specific number of work sheets; and Using a deployment monitor to capture and display the results of the deployment executors executing the update change program.

3. The table deployment method according to claim 2, wherein It further includes using the deployment manager to determine whether all the table work packages have been dispatched.

4. The table deployment method according to claim 3, wherein When the deployment manager determines that all the table work packages have been dispatched, it further includes determining whether there are abnormal table work packages among the table work packages; Wherein when there are no abnormal table work packages among the table work packages, the deployment manager completes the dispatching process, and Wherein when there are abnormal table work packages among the table work packages, the deployment manager marks the update record status of the abnormal table work package as update change failure.

5. The table deployment method according to claim 3, wherein, When the deployment manager determines that the table work packages have not been dispatched completely, it further includes determining whether a system resource usage limit has been reached; Wherein when the system resource usage limit is reached, the deployment manager suspends the dispatching process, and Wherein when the system resource usage limit is not reached, the deployment manager continues the dispatching process and dispatches a table work package that has not been updated to the deployment executor.

6. The table deployment method according to claim 2, wherein It further includes using the deployment executors to determine whether an abnormality occurs when respectively executing the update change program on the specific number of work sheets.

7. The table deployment method according to claim 6, wherein When an abnormality occurs during the execution of the update change program, the deployment executor marks the update record status of the corresponding work sheet as update change failure, and Wherein when no abnormality occurs during the execution of the update change program, the deployment executor further determines whether there are still work sheets on which the update change program has not been executed.

8. The table deployment method according to claim 7, wherein When the deployment executor determines that there are no work sheets on which the update change program has not been executed, the deployment executor further marks the update record status of the corresponding table work package of the work sheet with the update change failure mark as update change failure.

9. The table deployment method according to claim 2, wherein, Using the deployment monitor to capture the results of the update change program executed by the deployment executors further includes: using the deployment monitor to periodically capture an update record status of each of the table work packages.

10. The table deployment method according to claim 9, characterized in that, It further includes using the deployment monitor to receive a re-execution instruction, and calling a corresponding deployment executor to re-execute the update change program for the corresponding table work package according to the re-execution instruction.

Images