TWI768982B - Table deployment system and method thereof - Google Patents

Abstract

The table deployment system includes a deployment manager, deployment executors and a deployment monitor. The deployment manager receives work tables and divides the work tables into table work packages for distribution in sequence. These table work packages have a specific number of work tables. The deployment executors sequentially receive these table work packages to unpack the received table work packages into the specific number of work tables, so as to perform an update transaction procedure on the work tables respectively. The deployment monitor retrieves and displays the results of these deployment executors executing the update transaction process.

Description

Form deployment system and method therefor

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

Enterprise Resource Planning (ERP) ERP system can integrate the operation information required by the operation process of finance, accounting, human resources, manufacturing, and sales within the enterprise, through the planning of organization and process and the application of information technology. It is an integrated information system that achieves effective integration and instantly reflects the use of internal resources of the enterprise to provide a reference for enterprise decision-making, thereby increasing the competitive advantage of the enterprise.

Since the ERP system can integrate the work processes of various departments, the ERP system must use many worksheets to effectively manage material characteristics and resource changes, such as using worksheets to manage inventory production, order production or order assembly. However, due to the operation process of the ERP system, it is often necessary to change the work table format according to the requirements. Once the revisions are accumulated over a period of time, there are a large number of worksheets that need to be updated, and the intervention and supervision of professionals are often required during the update, which consumes a lot of time and manpower. It is also easy to fail to update the worksheet due to human negligence or lack of proper supervision of the interface, which requires more manpower to carry out the aftermath.

An embodiment of the present application provides a form deployment system, including: a deployment manager for receiving a plurality of work forms, and dividing the work forms into a plurality of form work packages and dispatching them in sequence , wherein each of the form work packages has a specific number of work forms; a plurality of deployment executors are coupled to the deployment manager, and the plurality of deployment executors are used to sequentially receive the a plurality of form work packages, wherein each of the deployment executors correspondingly unpacks the received form work package to produce the specific number of work forms, and respectively executes an update change procedure for the specific number of work forms; and a deployment monitor coupled to the deployment executors for capturing and displaying the results of executing the update transaction procedure by the deployment executors.

Another embodiment of the present application provides a form deployment method, which includes: using a deployment manager to receive a plurality of work forms, and splitting the work forms into a plurality of form work packages and performing a dispatching process to dispatch the form work packages, wherein the form work packages have a specific number of work forms; use a plurality of deployment executors to sequentially receive the form work packages dispatched by the deployment manager, wherein Each of the deployment executors correspondingly unpacks the received form work package to produce the specific number of work forms, and respectively executes an update change procedure for the specific number of work forms; and uses a deployment monitor The results of executing the update transaction procedure by the deployment executors are captured and displayed.

In one embodiment, the table deployment method further includes using the deployment manager to determine whether the table work packages have all been dispatched.

In one embodiment, when the deployment manager determines that the table work packages have been dispatched, it further includes determining whether there are abnormal table work packages in the table work packages; when there is no abnormal table work package in the table work packages. form work package, the deployment manager completes the dispatch procedure, and when there is an abnormal form work package in the form work package, the deployment manager marks the status of an update record of the abnormal form work package as Update transaction failed.

In one embodiment, when the deployment manager determines that the table work packages have not been dispatched, it further includes determining whether a system resource usage upper limit has been reached; when the system resource usage upper limit is reached, the deployment manager suspends the The dispatch process, and when the system resource usage limit is not reached, the deployment manager continues the dispatch process, dispatching a table work package that has not yet performed an update to the deployment executor.

In one embodiment, the table deployment method further includes using the plurality of deployment executors to determine whether an exception occurs when executing the update operation procedure for the specific number of worksheets respectively.

In one embodiment, when an exception occurs in the execution of the update transaction procedure, the deployment executor marks an update record state of the corresponding work table as an update transaction failure, and when the execution of the update transaction procedure does not occur abnormally, The deployment executor further determines whether there are worksheets for which the update transaction procedure has not yet been executed.

In one embodiment, when the deployment executor determines that there is no work form for which the update transaction procedure has not been executed, the deployment executor further records an update record of one of the work forms corresponding to the work form with the update transaction failure flag Status marked as update transaction failed.

In one embodiment, using the deployment monitor to capture the results of executing the update transaction procedure by the deployment executors further includes: using the deployment monitor to periodically capture the results of each of the table work packages. The update record status.

In one embodiment, the table deployment method further includes using the deployment monitor to receive a re-execution instruction, so as to call a corresponding deployment executor to re-execute the update transaction procedure for the corresponding table work package according to the re-execution instruction.

Therefore, according to the technical content of this case, when the worksheet update change is performed in this case, the deployment manager first splits a large number of worksheets into multiple worksheets containing a certain number of worksheets, and then divides these worksheets according to The sequence is dispatched to the deployment executor to perform the work table update transaction, and the deployment monitor is used to perform real-time monitoring and troubleshooting processing procedures for the update transaction. Therefore, the above production scheduling mechanism is used to handle a large number of complex table transaction procedures. , reducing the time required for additional manual judgment and processing, and relatively improving the availability and reliability of the system.

The following will clearly illustrate the spirit of this case with drawings and detailed descriptions. Anyone with ordinary knowledge in the technical field who understands the embodiments of this case can make changes and modifications by using the techniques taught in this case, which does not deviate from the principles of this case. spirit and scope.

The language used herein is for the purpose of describing particular embodiments and is not intended to be limiting. The singular forms such as "a", "the", "the", "this" and "the", as used herein, also include the plural forms.

As used herein, "coupling" or "connection" may refer to two or more elements or devices in direct physical contact with each other, or in indirect physical contact with each other, and may also refer to two or more elements or devices with each other action or action.

The terms "comprising", "including", "having", "containing", etc. used in this document are all open-ended terms, meaning including but not limited to.

As used herein, "and/or" includes any and all combinations of the stated things.

Regarding the terms (terms) used in this article, unless otherwise specified, they usually have the ordinary meaning of each term used in this field, in the content of this case and in the special content. Certain terms used to describe the present case are discussed below or elsewhere in this specification to provide those skilled in the art with additional guidance in the description of the present case.

Please refer to FIG. 1 , which is a schematic diagram of a table 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 that need to be updated in the ERP system, so as to successfully complete the update of the multiple work forms under the condition that the system resources are satisfied. 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 used for dividing a form package including a plurality of work forms to be updated in the ERP system into a plurality of form work packages, and assigning them to the plurality of deployment executors 112 for execution in sequence. Wherein, each form work package has the same number of work forms to be updated. In one embodiment, assuming that an ERP system includes a form package of 1000 work forms to be updated, the deployment manager 110 can split the form package, for example, split the form package into 250 work forms. Package, each form work package includes 5 work forms to be updated. The deployment manager 110 sequentially assigns the 250 form work packages to the multiple deployment executors 112 according to the system's processing resources. For example, only five deployment executors 112 are allowed to work in the same system according to the system's processing resources. The update procedure of the work form is executed during the time. According to this, the deployment manager 110 will first assign the form work package to the five deployment executors 112 for execution. Form work package assignment. It is worth noting that the number of splits of the table package is not limited to the above, and can 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 is used to unpack the form work package dispatched by the deployment manager 110 into a plurality of work forms, so as to update the work forms in the form work package. In one embodiment, the deployment The executor 112 executes the form change processing program on the work form to update the form. The deployment executor 112 further indicates that the update transaction fails when the table update transaction is abnormally processed. The deployment monitor 114 is coupled to the plurality of deployment executors 112 for monitoring the execution results of the deployment executors 112 . In one embodiment, the deployment monitor 114 periodically captures the execution result of the deployment executor 112 and reports it to the logistics personnel, so that when the execution result is abnormal, the record of the deployment monitor 114 can be immediately checked and handled.

It should be noted that, the table deployment system 100 disclosed in this application can be implemented in various ways, including software, hardware, or any combination thereof. In one embodiment, the table deployment system 100 can be, but is not limited to, a microprocessor, a microcontroller, a complex instruction set arithmetic microprocessor, a reduced instruction set arithmetic microprocessor, a very long instruction block microprocessor, Parallel instruction set computing microprocessor, graphics processor, digital signal processor or any other type of processor. In another embodiment, the table deployment system 100 may include a processor and a memory, and the memory stores a computer program code that can be accessed and executed by the processor. The functions of the deployment manager 110, a plurality of deployment executors 112, and a deployment monitor 114 are implemented in this case when the computer code in the memory is executed by the processor. Elements for reading instructions, such as but not limited to read only memory (ROM), random access memory (RAM), erasable programmable read only memory (erasable programmable read only memory); EPROM), and electronically erasable programmable read only memory (EEPROM). The account database 140 can be any type of fixed or removable random access memory (Random Access Memory, RAM), read-only memory (Read-Only Memory, ROM), flash memory (flash memory), Hard Disk Drive (HDD), Solid State Drive (SSD) or similar components or a combination of the above components. Computer code can be assembled language instructions, instruction set architecture instructions, machine instructions, machine-related instructions, microinstructions, firmware 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., as well as conventional procedural programs language, such as C or a similar programming language.

FIG. 2 is a flowchart of a method for executing a deployment manager according to a preferred embodiment of the present invention. The deployment manager executes the method 200, and firstly receives the form package in step 202, including determining whether there is an abnormal undistributed work form package. path, and establish a working directory to copy the form package archive into the working directory. In one embodiment, it is assumed that an ERP system includes a form package containing 1000 work forms to be updated. The deployment manager 110 in the form deployment system 100 receives the file path of the form package, and executes the form package in the form to be updated. A working directory is created in the ERP system to copy the form package file into the working directory.

In step 204, the form package is unpacked. In one embodiment, the deployment manager 110 unpacks the form package to restore 1000 worksheets to be updated.

In step 206, according to a setting, all worksheets are divided into a plurality of worksheets according to a certain number, and worksheets are allocated. In one embodiment, the deployment manager 110 may split the 1000 worksheets to be updated according to a certain number, for example, split the 1000 worksheets to be updated into 250 worksheets according to a certain number of 5 sheets , therefore, each form work package includes 5 work forms to be updated. In other embodiments, the worksheet to be updated may be split according to other quantities, which is not limited to the above-mentioned embodiment.

In step 208, it is determined whether all form work packages have been allocated. In one embodiment, after the deployment manager 110 divides all worksheets into a plurality of worksheets according to a certain number according to a setting, the plurality of worksheets can be sequentially assigned to subsequent worksheets according to system processing resources. multiple deployment executors 112 and determine whether all form work packages have been allocated. If there is still an unassigned form work package, step 210 is executed to determine whether the upper limit of available system resources has been reached. In one embodiment, since system resources still have to perform other routine tasks, only a certain number of deployment executors 112 are allowed to execute the worksheet update procedure at the same time. Therefore, in step 210, the deployment manager 110 will first determine whether the upper limit of system resources that can be used to perform worksheet updates has been reached. If the upper limit of system resources has not been reached, in step 212, the deployment manager 110 continues the dispatching process. In one embodiment, the deployment The manager 110 will call a deployment executor 112 to assign a form work package that has not yet been updated to the deployment executor 112, execute the unpack form work package and the work form change procedure, and set the initial record, such as the initial The record is updated for subsequent checking, and step 208 is executed again to determine whether all form 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 the table work packages have been allocated.

If, in step 208, it is determined that all form work packages have been dispatched, in step 214, it is determined whether there are abnormal uncompleted form work packages. If there is no abnormal uncompleted form work package, the deployment of the form work package is completed in step 218 . On the other hand, if there is an abnormally uncompleted form work package, for example, when the form package is split into a plurality of form work packages, the form work package is abnormally uncompleted, then in step 216, the abnormal uncompleted form work package is assigned. The update status record is that the update transaction failed.

FIG. 3 is a flowchart of a method for executing a deployment executor according to a preferred embodiment of the present invention. The deployment executor executes the method 300 and first receives the form work package in step 302 . Include the path to receive the form work package and create a working directory to copy the form work package archive into the working directory. In one embodiment, the deployment executor 112 in the form deployment system 100 receives the form work package file path, and creates a work directory in the ERP system where the form update is to be performed to copy the form work package file to the work package. in the directory.

In step 304, unpack the form work package. In one embodiment, the deployment executor 110 unpacks the form work package to restore five work forms to be updated. In step 306, the worksheet execution order is sorted according to the list in the worksheet work package. In one embodiment, the deployment executor 110 sorts the five worksheets according to a set execution procedure to execute the worksheet update transaction procedure in this order. In step 308, the table transaction program is called to perform the work table update transaction program. In one embodiment, the deployment executor 110 calls a table transaction procedure to perform the work table update transaction procedure. In step 310, the deployment executor 110 determines whether an abnormality occurs in the worksheet update transaction procedure. If an exception occurs in the worksheet update transaction procedure, in step 312, it is indicated that the update transaction failed. In one embodiment, when the deployment executor 110 is performing a worksheet update transaction procedure, if an abnormal condition occurs, for example, the update procedure cannot be executed, the deployment executor 110 marks the update status of the worksheet as abnormal, and then executes the Step 314, it is determined whether there is any work form for which the form update transaction procedure has not been executed. On the other hand, in step 310, if the deployment executor 110 determines that no abnormality has occurred in the worksheet update procedure, then step 314 is executed to determine whether there are worksheets in the sheet work package for which the sheet transition procedure has not been executed.

If there are still work forms for which the form change program has not been executed, step 308 is executed again, and the form change program is called to perform the work form update change. On the other hand, if the transaction procedure of all the worksheets in a worksheet has been executed, step 316 is executed. If there is an abnormality in one worksheet, the record of this worksheet is marked as failed to update the worksheet, and the work of the form is completed in step 318. Package handlers.

FIG. 4 is a flow chart illustrating an execution method for deploying a monitor according to a preferred embodiment of the present invention. To execute the method 400 for the deployment monitor, firstly, in step 402, records of each form work package are captured and displayed. In one embodiment, the deployment monitor 114 in the table deployment system 100 will capture the records of each table work package, and display the retrieval result, and the worker at the construction end will confirm the execution result of each table work package. In step 404, waiting for a period of time, and in step 406, the records of each form work package are retrieved again to update the execution result of each form work package. In one embodiment, since the deployment executor 110 continuously updates the work table, the deployment monitor 114 periodically, for example, every 3 seconds, captures the records of the table work package executed by the deployment executor 110 . to update the transaction result of the table work package. In other embodiments, this period is not limited to 3 seconds. In step 408, it is determined whether one of the form work packages has been re-executed manually. In one embodiment, when the record of one of the form work packages is displayed as abnormal, a back-end worker can specify to re-execute the change procedure of the form work package. Accordingly, the deployment monitor 114 receives a re-execution command, and in step 410 , the deployment monitor 114 calls the deployment executor 112 to re-execute the transaction procedure of the table work package. In one embodiment, after receiving the call from the deployment monitor, the deployment executor will re-execute the table work package again, unpack the table work package and call a table change program to update the work table. In another embodiment, if it is determined in step 408 that one of the form jobs has not been designated to be re-executed, step 412 is executed to determine whether someone has manually pressed the leave button. If someone manually presses the leave button, in step 414, the monitoring procedure ends. On the other hand, if it is determined in step 412 that no one presses the leave button, step 404 is re-executed, and after waiting for a period of time, the records of each form work package are retrieved again to update the execution result of each form work package.

Accordingly, in this case, when a worksheet update transaction is performed, the deployment manager first divides a large number of worksheets into a number of worksheets containing a certain number of worksheets, and then assigns these worksheets to the deployment in sequence. The executor performs the work table update transaction, and the deployment monitor is used for real-time monitoring and troubleshooting of the update transaction process. Therefore, the above production scheduling mechanism is used to process a large number of complex table transaction procedures, reducing the need for extra labor. The time of judgment and processing is relatively improved, and the availability and reliability of the system are relatively improved. In addition, the present invention can be used in the case of updating a small number of tables in addition to being applicable to a large number of table updates, which meets the needs of a small number of multiple updates.

Although this case is disclosed above with examples, it is not intended to limit this case. Anyone who is familiar with this technique can make various changes and modifications without departing from the spirit and scope of this case. Therefore, the protection scope of this case should be regarded as attached hereto. The one defined in the scope of the patent application shall prevail.

100: Form Deployment System 110: Deployment Manager 112: Deploy the executor 114: Deploy monitor 200: Deployment Manager Execution Method 202-218: Steps 300: Deploy the executor execution method 302-318: Steps 400: Deploy monitor execution method 402-414: Steps

The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, and these drawings illustrate embodiments consistent with the present invention, and together with the description, serve to explain the technical solutions of the embodiments of the present invention. FIG. 1 is a schematic diagram of a table deployment system using production scheduling according to a preferred embodiment of the present invention. FIG. 2 is a flowchart of a method for executing a deployment manager according to a preferred embodiment of the present invention. FIG. 3 is a flowchart of a method for executing a deployment executor according to a preferred embodiment of the present invention. FIG. 4 is a flow chart illustrating an execution method for deploying a monitor according to a preferred embodiment of the present invention.

100: Form Deployment System

110: Deployment Manager

112: Deploy the executor

114: Deploy monitor

Claims (9)

A form deployment system, comprising: a deployment manager for receiving a plurality of work forms, and dividing the work forms into a plurality of form work packages and dispatching them in sequence, wherein the form work packages are all There is a specific number of work forms; a plurality of deployment executors are coupled to the deployment manager, and the deployment executors are used to sequentially receive the form work packages dispatched by the deployment manager, wherein each The deployment executors correspondingly unpack the received form work package to produce the specific number of work forms, and respectively execute an update transaction procedure for the specific number of work forms; and a deployment monitor is coupled to The deployment executors are used for retrieving and displaying the results of executing the update transaction procedure by the deployment executors, wherein the deployment manager further determines whether all the table work packages have been dispatched. A form deployment method, comprising: using a deployment manager to receive a plurality of work forms, and splitting the work forms into a plurality of form work packages and performing a dispatch procedure to distribute the form work packages, Each of the form work packages has a specific number of work forms; a plurality of deployment executors are used to sequentially receive the form work packages dispatched by the deployment manager, wherein each of the deployment executors corresponds to unpacking the received form work package to produce the specific number of work forms, and respectively executing an update and change program for the specific number of work forms; and a deployment monitor is used to capture and display the results of executing the update transaction procedure by the deployment executors, and use the deployment manager to determine whether all the table work packages have been dispatched. The form deployment method according to claim 2, wherein when the deployment manager determines that the form work packages have been dispatched, it further includes judging whether there are abnormal form work packages in the form work packages; There is no abnormal table work package in the table work package, the deployment manager completes the dispatching process, and when there is an abnormal table work package in the table work package, the deployment manager completes the abnormal table work package. One of the work packages has an update record status marked as update transaction failed. The table deployment method according to claim 2, wherein when the deployment manager determines that the table work packages have not been dispatched, it further includes determining whether a system resource usage upper limit has been reached; wherein when the system resource usage upper 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 yet been updated to the deployment executor. The form deployment method as described in claim 2, further It includes using the deployment executors to determine whether an exception occurs when the update transaction procedure is respectively executed for the specific number of worksheets. The form deployment method as claimed in claim 5, wherein when an exception occurs when executing the update transaction procedure, the deployment executor marks an update record status of the corresponding work form as an update transaction failure, and wherein when executing the update When no exception occurs in the transaction procedure, the deployment executor further determines whether there is still a work form for which the update transaction procedure has not been executed. The form deployment method of claim 6, wherein when the deployment executor determines that there is no work form for which the update transaction procedure has not been executed, the deployment executor further assigns the corresponding work form with the update transaction failure flag The update record status of one of the form work packages is marked as failed. The table deployment method of claim 2, wherein using the deployment monitor to capture the results of executing the update transaction procedure by the plurality of deployment executors further comprises: using the deployment monitor to periodically capture each the update record status of the form work packages. The table deployment method as claimed in claim 8, further comprising receiving a re-execution command by using the deployment monitor to call a corresponding deployment executor to re-execute the update to the corresponding table work package according to the re-execution command Variation program.

Images