An integrated management information system message processing method, device and medium

Abstract

This invention discloses a message processing method, device, and medium for an integrated management information system, relating to the field of data processing technology. The method includes: receiving a business action message; generating a trial processing request (without data to be written) based on the business object number, target end name, and business action name; sending this request to the target end for a no-write check to obtain check information; if the check information indicates a missing prerequisite data item name, determining the management end that generated the prerequisite data item and sending a prerequisite data confirmation request; generating check data if the prerequisite data item has been formed; if it has not been formed but has preceding processed data, sending the preceding processed data to the target end for another trial processing, and generating check data after confirmation; combining the check data with the business action message to form an execution request, sending it to the target end for an entry check, and writing only the data to be written. This invention reduces the risk of direct cross-end message writing, avoids old data participating in entry checks, and promotes action messages when prerequisite data items have not been formed.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a message processing method, device and medium for an integrated management information system. Background Technology

[0002] In scenarios such as enterprise operation and management, warehouse collaboration, financial settlement, and personnel flow, integrated management information systems typically achieve business message transmission between different management terminals through interface services, message queues, or middleware. Conventional message processing methods mostly rely on business object numbers, business action types, and target terminal interface rules to convert business action messages generated by the source terminal into a message format that the target terminal can receive, and complete status updates, document generation, or business data writing on the target terminal to maintain consistent flow of business data across multiple terminals.

[0003] In the aforementioned conventional methods, on the one hand, the preceding data items often rely on the source end to be carried along with the business action message, and the target end has difficulty in confirming whether the preceding data items come from the actual generating end. Old data or non-attributed data may participate in the entry check. On the other hand, when the preceding data items have not yet been finally formed but there is already preceding processed data, the conventional method usually waits for the final data synchronization to be completed, and cross-end business action messages are prone to stagnation. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides an integrated management information system message processing method to solve the problems of uncontrollable progress of cross-terminal business action messages when the preceding data items have not been formed and insufficient verification of the source of the preceding data in the existing technology.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution: In a first aspect, the present invention provides a message processing method for an integrated management information system, comprising: receiving a business action message; generating a trial processing request without data to be written based on the business object number, target end name, and business action name; sending the request to the target end for a no-write check and obtaining check information; when the check information indicates a missing preceding data item name, determining the management end that generated the preceding data item based on the preceding data item name, sending a preceding data confirmation request, and obtaining preceding data confirmation information; when the preceding data item has been formed, generating check data through the preceding data item; when the preceding data item has not yet been formed but there is preceding processing data, sending the preceding processing data to the target end for another trial processing, and generating check data from the preceding processing data after confirmation at the target end; combining the check data with the business action message to generate an execution request with check data, sending the request to the target end, and performing an entry check based on the check data, only writing the data to be written in the business action message.

[0007] As a preferred embodiment of the message processing method for the integrated management information system described in this invention, the step of generating a trial processing request without data to be written includes: receiving a business action message sent by the source end; reading the business object number, target end name, business action name, and source serial number from the business action message; writing the business object number, target end name, business action name, source serial number, and read-only check flag into the trial processing request; and retaining the data to be written in the business action message in the local pending-send area without writing it into the trial processing request.

[0008] As a preferred embodiment of the message processing method for the integrated management information system described in this invention, the step of obtaining inspection information includes: the target end enters the read-only processing channel according to the read-only inspection mark, reads the existing local business records of the target end, and calls the business action entry program corresponding to the business action name; according to the inspection order in the business action entry program, it is determined whether the prerequisite data item required to enter the current business action exists in the existing local business records; if the prerequisite data item does not exist, the name of the first non-existent prerequisite data item is taken as the inspection information and returned; when there is a local action in the existing local business records that is opposite to the business action name, the opposite action information is returned; when the same data item name belongs to both the data item that needs to be satisfied before the current business action is entered and the data item generated after the current business action is completed, entry condition exception information is returned.

[0009] As a preferred embodiment of the message processing method for the integrated management information system described in this invention, the step of determining the management end that generates the preceding data item includes: using the name of the missing preceding data item as a search field, searching for a data item maintenance list with the same name that can generate the data item in the data item source relationship; when a management end name is found, the management end name is determined as the management end that generates the preceding data item; when multiple management end names are found, comparing the business action name with the business action name that generates the data item in the data item maintenance list, and selecting the management end belonging to the same business link; when multiple management end names still exist, selecting the preceding data source end registered by the target end in the business action entry program.

[0010] As a preferred embodiment of the message processing method for the integrated management information system described in this invention, the steps of sending a pre-confirmation data request and obtaining pre-confirmation data information are as follows: A pre-confirmation data request is sent to the management terminal that generated the pre-confirmation data item, and the business object number, business action name, target terminal name, missing pre-confirmation data item name, and source serial number are written into the pre-confirmation data request; when there is a missing pre-confirmation data item name in the local business record, and there is no cancellation action later than the formation time of the pre-confirmation data item in the local data item cancellation record, pre-confirmation data information indicating that the pre-confirmation data item has been formed is returned; when the local... If there is no missing preceding data item name in the business record, and there is a data item that has been formed and not cancelled in the preceding data item record, return the preceding data confirmation information that the preceding data item has not yet been formed but has preceding data for processing; if there is no missing preceding data item name in the local business record, no data item that has been formed and not cancelled in the preceding data item record, and there is a business action serial number being processed in the local business record, return the information that the preceding data item is being processed; if there is a cancellation action in the local data item cancellation record that is later than the time the preceding data item was formed, return the information that the preceding data item has been cancelled.

[0011] As a preferred embodiment of the message processing method for the integrated management information system described in this invention, the step of generating inspection data through preceding data items includes: when the confirmation type of the preceding data confirmation information is that the preceding data item has been formed, reading the preceding data item name, the preceding data item value, the provider name, and the processing serial number; writing the preceding data item name into the inspection data name, writing the preceding data item value into the inspection data value, writing the provider name into the inspection data provider, and writing the processing serial number into the inspection data processing serial number; writing the inspection data source type as the preceding data item, and writing the "check only, no writing" flag into the inspection data.

[0012] As a preferred embodiment of the message processing method for the integrated management information system described in this invention, the steps of sending the preprocessing data to the target end for reprocessing and generating check data from the preprocessing data after confirmation at the target end are as follows: A reprocessing request is generated, and the business object number, target end name, business action name, missing pre-processing data item name, pre-processing data name, pre-processing data value, provider name, processing serial number, and read-only check flag are written into the reprocessing request; the target end enters the read-only processing channel according to the read-only check flag and searches for the allowed early entry data item name corresponding to the missing pre-processing data item name in the business action entry program; when the pre-processing data name matches the allowed early entry data item name, the pre-processing data value indicates that it has been completed or taken effect, and there is no local action opposite to the business action name in the target end's local business records, the pre-processing data is returned as "pre-processing data can enter" information; after receiving the "pre-processing data can enter" information, the pre-processing data name, pre-processing data value, provider name, and processing serial number are written into the check data, and the check data source type is written as "pre-processing data".

[0013] As a preferred embodiment of the message processing method for the integrated management information system described in this invention, the steps of sending the data to the target end and performing an entry check based on the check data, and only writing the data to be written in the business action message, are as follows: After receiving the execution request with check data, the target end puts the check data into the entry check process according to the "check only, no write" flag; the target end reads the check data name, check data value, check data provider, and check data processing serial number, and calls the business action entry program to perform the entry check according to the business action name; after the entry check passes, the target end generates a restricted write instruction, which only reads the data to be written in the business action message; the target end completes the business data processing according to the restricted write instruction. Write and return execution feedback; when all the data names actually written belong to the data names to be written in the business action message, and there is no check data name among the data names actually written, mark the business action message as completed; when the execution feedback indicates that the target end has written the check data name, generate a target end write exception record; when the execution feedback indicates that the target end lacks a new preceding data item name, re-determine the management end that generates the new preceding data item based on the new preceding data item name, and regenerate the preceding data confirmation request; the execution feedback includes the business object number, target end name, business action name, execution status, actual data name written, actual check data name used, and actual processing serial number used.

[0014] In a second aspect, the present invention provides a computer device including a memory and a processor, wherein the memory stores a computer program, wherein when the computer program is executed by the processor, it implements any step of the message processing method for an integrated management information system as described in the first aspect of the present invention.

[0015] Thirdly, the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein, when the computer program is executed by a processor, it implements any step of the message processing method for an integrated management information system as described in the first aspect of the present invention.

[0016] The beneficial effects of this invention are as follows: by attempting to process requests and not writing checks, the identification of pre-processing data items before business actions are written is realized, reducing the risk of direct writing of cross-terminal messages; by obtaining pre-processing data confirmation information from the management end that generates the pre-processing data items, the accuracy of the data source is ensured, and old data is avoided from participating in the entry check; by re-processing the pre-processing data, the controllable advancement of business action messages when pre-processing data items have not been formed is realized, reducing message stagnation. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Fig. 1 This is a flowchart of a message processing method for an integrated management information system.

[0019] Fig. 2 This is a diagram illustrating the process of handling requests and checking information.

[0020] Fig. 3 This is a schematic diagram illustrating the linkage between preliminary data confirmation and re-trial processing.

[0021] Fig. 4 This is a schematic diagram illustrating the determination of restricted write operations and execution feedback. Detailed Implementation

[0022] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0023] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0024] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0025] Reference Figs. 1-4 As one embodiment of the present invention, this embodiment provides an integrated management information system message processing method, including the following steps: S1. Receive the business action message, generate a trial processing request without data to be written based on the business object number, target name, and business action name, send it to the target to perform a no-write check, and obtain the check information.

[0026] Furthermore, it receives business action messages sent from the source.

[0027] Among them, the business action message is generated by the source end when the business action is triggered.

[0028] The business action message contains the business object number, source name, target name, business action name, source serial number, and the data that the business action needs to be written to the target.

[0029] Among them, the business object number is one of the following: order number, contract number, inventory batch number, personnel file number, and purchase order number, used to identify the object being processed in the current business action; the source end name is the name of the management end that sends the business action message; the target end name is the name of the management end that receives the business action message and executes the business action; the business action name is one of the following: invoice application, outbound confirmation, contract effective, personnel transfer, and purchase receipt; the source serial number is the unique serial number generated when the source end generates the business action message; the data that the business action needs to write to the target end is the data that needs to be saved to the target end after the current business action is executed.

[0030] Furthermore, upon receiving a business action message, the system first reads the business object number, target name, business action name, and source serial number, and then generates a trial processing request.

[0031] The trial processing request includes the business object number, target name, business action name, source serial number, and read-only check flag, but does not include the data that the business action needs to be written to the target.

[0032] Specifically, the read-only check flag is used to require the target end to perform only entry checks and not to write business data; when generating a trial processing request, the data to be written in the business action message is kept in the local waiting area and is not sent to the target end with the trial processing request.

[0033] Therefore, the target end cannot obtain the data to be written during the trial processing phase, nor can it change the business data in advance based on the data to be written.

[0034] After receiving the trial processing request, the target end opens the read-only processing channel according to the read-only check flag.

[0035] The read-only processing channel only allows the target to read existing local data and does not allow the call to add, modify, or delete write interfaces.

[0036] Preferably, the target end records the source serial number and business object number of the trial processing request in the read-only processing channel, and uses the read local data only for this entry check.

[0037] The target end reads the existing business records on the target end based on the business object number, and calls the local business action entry program on the target end based on the business action name.

[0038] The business action entry program stores the names of the prerequisite data items that must be met before the current business action can be entered, as well as the names of the data items generated by the target end after the current business action is completed.

[0039] The target end checks each item in the order of the business action entry procedure to determine whether the prerequisite data items required to enter the current business action already exist in the target end's local business records.

[0040] If all the pre-existing data items already exist, and there is no local action with the opposite name to the business action in the existing local business records on the target end, the target end generates an access permission message and returns the access permission message as inspection information to the integrated management information processing platform.

[0041] After receiving the access permission information, the integrated management information processing platform retrieves the data that the business action needs to be written to the target end from the local waiting area, and combines the business object number, target end name, business action name, source serial number, and the data that the business action needs to be written to the target end into a request to be executed.

[0042] When a preceding data item does not exist in the existing business records on the target end, the target end does not continue to return all subsequent inspection content. Instead, according to the actual inspection order of the business action entry program, it takes the name of the first non-existent preceding data item as the name of the missing preceding data item and returns the name of the missing preceding data item as inspection information to the integrated management information processing platform.

[0043] After receiving the name of the missing prerequisite data item, the integrated management information processing platform does not generate a request to be executed, but saves the business action message and the name of the missing prerequisite data item together for subsequent confirmation of the prerequisite data item.

[0044] As an example, the target is the financial management end, the business action name is invoice application, and when the financial management end does not find the outbound completion data in the existing business records, the financial management end returns the name of the missing preceding data item as outbound completion data; the integrated management information processing platform does not send the invoice amount and invoice application data directly to the financial management end for execution, but saves the invoice application message and the outbound completion data name.

[0045] When the target device already has a local action with the opposite name in its existing business records, the target device generates the opposite action information and returns the opposite action information as inspection information to the integrated management information processing platform.

[0046] The reverse action information is obtained by the target end by reading existing local business records based on the business object number.

[0047] As an example, if the business action is named "Invoice Application" and the target end already has order cancellation, order closure, or invoice cancellation actions in its local business records, the target end will return the opposite action information.

[0048] After receiving the reverse action information, the integrated management information processing platform sends an action verification request to the source end; if the source end confirms that the business action has expired, it terminates the business action message; if the source end confirms that the business action still needs to be executed, it generates a reverse action exception record and stops automatic sending.

[0049] When the target determines that the prerequisite data item required to enter the current business action is a data item that will only be generated after the current business action is completed, the target generates an entry condition exception message and returns the entry condition exception message as inspection information to the integrated management information processing platform.

[0050] Specifically, the target end compares the names of the prerequisite data items in the business action entry program with the names of the data items generated by the target end after the current business action is completed. If the same data item name appears in both the data items that need to be met before entry and the data items generated after the action is completed, the target end determines that the current business action has an abnormal entry condition. After receiving the abnormal entry condition information, the integrated management information processing platform generates an abnormal entry condition record for the target end and stops automatically sending the same business action message.

[0051] In addition, during the non-write check, the target end does not write any content to the target end business data in the trial processing request, nor does it change the business state of the business object; the trial processing request is only used to trigger the target end to expose the first blocking item when the current business action enters, so that the integrated management information processing platform can determine whether the business action message directly forms a pending execution request, confirms the entry pre-data item, verifies the execution action, or generates an entry condition abnormal record without sending complete business data.

[0052] S2. When the check information indicates that the name of the preceding data item is missing, determine the management terminal that generated the preceding data item based on the preceding data item name, send a preceding data confirmation request, and obtain the preceding data confirmation information.

[0053] Furthermore, after receiving the name of the missing preceding data item returned by the target end, the business object number, business action name, source end name, target end name and source serial number in the business action message are read, and the name of the missing preceding data item is retrieved in the data item source relationship.

[0054] The data item source relationships are generated from the data item maintenance list submitted by each management terminal when it connects to the integrated management information processing platform.

[0055] The data item maintenance list records the management terminal name, the name of the data item that can be generated, the name of the business action that generates the data item, the data item formation stage, the name of the data item cancellation action, and the name of the preceding data item.

[0056] The integrated management information processing platform arranges the data item maintenance lists of each management terminal according to the names of the data items that can be generated, forming the data item source relationship.

[0057] Specifically, the integrated management information processing platform uses the missing name of the preceding data item as a search field to search the maintenance list of data items that can generate the same name in the data item source relationship, and obtains the management end name. If only one management end name is obtained, the obtained management end name is determined as the management end that generates the preceding data item. If multiple management end names are obtained, the business action name is further compared with the business action name that generates the data item in the data item maintenance list, and the management end whose business action name belongs to the same business link is selected as the management end that generates the preceding data item. If multiple management end names still exist, the preceding data source end registered by the target end in the business action entry program is selected as the management end that generates the preceding data item.

[0058] It should be noted that the same business link refers to the business action that generates the data item being able to form the missing preceding data item before the current business action enters. When making the judgment, the business action name in the business action message is read, and the business action name that generates the data item and the data item formation stage in the data item maintenance list are read. When the data item formation stage is earlier than the current business action entry stage, and the business action name that generates the data item can form the missing preceding data item name, it is determined that the management end belongs to the same business link.

[0059] After identifying the management end that generates the prerequisite data items, the integrated management information processing platform generates a prerequisite data confirmation request.

[0060] The preceding data confirmation request includes the business object number, business action name, target name, name of the missing preceding data item, and source serial number. It does not include the data that the business action needs to write to the target, nor does it include business data that is unrelated to the missing preceding data item.

[0061] After receiving the preceding data confirmation request, the management terminal that generates the preceding data item reads the local business record according to the business object number, and reads the local data item formation record, local data item cancellation record, and same-precedence data item record according to the name of the missing preceding data item.

[0062] Furthermore, the management end that generates the preceding data items first checks whether there are any missing preceding data item names in the local business records.

[0063] If there is a missing preceding data item name in the local business record, and there is no cancellation action later than the time the preceding data item was formed in the local data item cancellation record, then it is determined that the preceding data item has been formed.

[0064] The management terminal that generates the preceding data item writes the preceding data item name, preceding data item value, provider name and processing serial number into the preceding data confirmation information, and sends the preceding data confirmation information to the integrated management information processing platform.

[0065] As an example, if the target end lacks outbound completion data, but the warehouse management end already has outbound completion data in its local business records, and there is no outbound cancellation action later than the outbound completion data, then the warehouse management end returns preliminary data confirmation information including the outbound completion data name, outbound completion data value, warehouse management end name, and outbound completion serial number.

[0066] If the missing preceding data item name is not present in the local business records, the management terminal that generated the preceding data item reads the same preceding data item record.

[0067] Among them, the preceding data item record is generated by the management terminal that generates the preceding data item according to the local business processing order. It records data items that were formed earlier than the missing preceding data item and can indicate that the business object has entered the same processing direction. The management terminal that generates the preceding data item searches for data items that have been formed and have not been canceled in the preceding data item record, and determines the data item that is closest to the formation stage of the missing preceding data item as the preceding processing data.

[0068] It should be noted that "closest to the formation stage of the missing preceding data item" means searching backwards from the formation stage of the missing preceding data item according to the order of the data item formation stages registered in the data item maintenance list, and determining the first formed and not cancelled data item found as the preceding data to be processed; when there are multiple formed and not cancelled data items in the same formation stage, the data item with the latest formation time is determined as the preceding data to be processed.

[0069] Preferably, the preceding processed data must satisfy the following two conditions A1-A2: A1: The preceding data was formed before the missing preceding data items; A2: The business direction to which the preceding processed data belongs is the same as the business direction to which the missing preceding data item belongs.

[0070] It should be noted that whether the business direction of the preceding processed data is the same as that of the missing preceding data item is determined based on the name of the same preceding data item registered in the data item maintenance list; when the name of the preceding processed data belongs to the same preceding data item name corresponding to the missing preceding data item, it is determined that the two belong to the same business direction.

[0071] As an example, if the target end lacks outbound completion data and the warehouse management end has not yet generated outbound completion data, but has generated verification completion data or handover order generation data, and the verification completion data or handover order generation data has not been revoked, then the warehouse management end will determine the verification completion data or handover order generation data as the preceding processing data.

[0072] When a preceding data item has not yet been formed but there is preceding data, the management terminal that generated the preceding data item writes the preceding data name, the preceding data value, the provider name, the processing serial number, and the name of the missing preceding data item into the preceding data confirmation information and sends it to the integrated management information processing platform.

[0073] After receiving the preliminary data confirmation information, the integrated management information processing platform binds and saves the preliminary data confirmation information with the business action message, so that the preliminary processing data can be used as input data for the re-processing request.

[0074] If there is no missing preceding data item name in the local business record, and there is no data item that has been formed and not cancelled in the preceding data item record, but there is a business action serial number being processed in the local business record, then the management terminal that generated the preceding data item will return information about the preceding data item being processed.

[0075] After receiving the information of the preceding data item being processed, the integrated management information processing platform writes the business action message, the name of the missing preceding data item, the name of the management terminal that generated the preceding data item, and the source serial number into the pending processing area.

[0076] When the management terminal that generates the preceding data item subsequently generates another preceding data item or preprocessed data, it sends a formation notification to the integrated management information processing platform.

[0077] Based on the business action messages and missing preceding data item names stored in the pending processing area, the integrated management information processing platform sends a preceding data confirmation request to the management terminal that generated the preceding data item.

[0078] If there was a missing preceding data item name in the local business record, and there was a cancellation action in the local data item cancellation record that was later than the time the preceding data item was created, then the management end that generated the preceding data item will return the information that the preceding data item has been cancelled; after receiving the information that the preceding data item has been cancelled, the integrated management information processing platform will terminate the business action message and return the information that the preceding data item has been cancelled to the source end.

[0079] If the management terminal that generated the prerequisite data item confirms, based on the data item maintenance list, that the missing prerequisite data item should be generated after the execution of the current business action represented by the business action name, then the management terminal that generated the prerequisite data item returns an entry condition exception information.

[0080] Specifically, the management end that generates the prerequisite data items compares the name of the missing prerequisite data item with the name of the data item generated after the current business action is completed in the data item maintenance list; if the two names are the same, it means that the target end sets the data item that will only be generated after the current business action is completed as the data item that needs to be satisfied before the current business action begins.

[0081] After receiving abnormal entry conditions information, the integrated management information processing platform generates an abnormal entry condition record for the target end and stops automatically sending the same business action message.

[0082] In addition, the pre-data confirmation request only focuses on the name of the missing pre-data item, and does not request complete business documents or data to be written from the source to the target. The pre-data confirmation information only provides the integrated management information processing platform with information on whether the pre-data item has been formed, whether there is preceding data, whether it is being processed, whether it has been canceled, or whether it belongs to an abnormal entry condition. This enables the integrated management information processing platform to obtain the minimum amount of data based on the missing pre-data items actually exposed by the target and continue to complete the business action message processing.

[0083] S3. When the preceding data item has been formed, check data is generated through the preceding data item. When the preceding data item has not yet been formed but there is preceding processing data, the preceding processing data is sent to the target end for reprocessing, and check data is generated from the preceding processing data after confirmation at the target end.

[0084] After receiving the prior data confirmation information, read the confirmation type from the prior data confirmation information.

[0085] The confirmation types include: the preceding data item has been formed, the preceding data item has not yet been formed but there is preceding data to be processed, the preceding data item is being processed, the preceding data item has been cancelled, and the entry condition is abnormal.

[0086] When the confirmation type in the previous data confirmation information is "previous data item has been formed", read the previous data item name, previous data item value, provider name and processing serial number, and write the previous data item name into the check data name, the previous data item value into the check data value, the provider name into the check data provider, the processing serial number into the check data processing serial number, the check data source type into the previous data item, and write the "check only, do not write" flag into the check data to form the check data.

[0087] Specifically, the inspection data is not business data that the target end needs to save; the inspection data is used by the target end to confirm whether the entry conditions of the business action are met before executing the business action; the "check only, write not" flag is used to constrain the target end to only use the inspection data as the entry inspection basis and not to save the inspection data to the target end's business records.

[0088] After the inspection data is generated, the business object number, target name, business action name, source serial number, and data that the business action needs to write to the target are read from the business action message. The business object number, target name, business action name, source serial number, data that the business action needs to write to the target, and inspection data are written into the same message body to generate an execution request with inspection data.

[0089] Furthermore, after generating an execution request with check data, the integrated management information processing platform writes the execution request with check data into the pending-send area, waiting to send it to the target end.

[0090] As an example, if the target end lacks outbound completion data, and the warehouse management end returns the outbound completion data name, outbound completion data value, warehouse management end name, and outbound completion serial number, the integrated management information processing platform will write the outbound completion data name, outbound completion data value, warehouse management end name, and outbound completion serial number into the inspection data, and combine the inspection data with the invoice application message to generate an invoice execution request with the inspection data; the financial management end will subsequently only determine whether the invoice application can be entered based on the outbound completion data, and will not save the outbound completion data.

[0091] When the confirmation type in the current data confirmation information is that the previous data item has not yet been formed but there is previous processing data, the business object number, target end name, business action name, missing previous data item name, previous processing data name, previous processing data value, provider end name and processing serial number are read, and a reprocessing request is generated.

[0092] When reprocessing the request, write the business object number, target name, business action name, missing preceding data item name, preceding processing data name, preceding processing data value, provider name, processing serial number, and read-only check flag, but do not write the data that the business action needs to write to the target.

[0093] Furthermore, the integrated management information processing platform will resend the processing request to the target end.

[0094] After receiving the request to retry processing, the target end enters the read-only processing channel based on the read-only check flag.

[0095] The target end reads the business action name and the missing prerequisite data item name in the read-only processing channel, and searches for the data item name that is allowed to enter in advance under the missing prerequisite data item name in the target end's business action entry program.

[0096] It should be noted that the name of the data item that can be entered in advance is registered by the target end when accessing the integrated management information processing platform. It is used to indicate the name of the pre-processing data that can participate in the entry check before the preceding data item is formed.

[0097] The target will re-process the name of the preceding data in the request and compare it with the name of the data item that is allowed to enter in advance. If the names match, the target will continue to read the value of the preceding data.

[0098] When the value of the preceding processing data indicates that it has been completed or has taken effect, and there is no local action with the opposite name to the business action in the target's local business records, the target confirms that the preceding processing data can meet the conditions for entering the business action, and returns the information that the preceding processing data can enter to the integrated management information processing platform.

[0099] It should be noted that whether the value of the preceding processing data indicates that it has been completed or has taken effect is determined based on the name of the data item that can be entered in advance and the value that can be entered, which are registered by the target end in the business action entry procedure. The value that can be entered is registered by the target end when it connects to the integrated management information processing platform, and indicates the value that the target end allows the preceding processing data to participate in the entry check, such as the review completed, the handover form generated, or the approval taken effect.

[0100] When the target side determines whether the preceding processed data can meet the conditions for entering a business action, it does not write business data, generate business action records, or change the business state of the business object on the target side.

[0101] It should be noted that the target end only returns information such as whether the preceding processed data can be entered, whether the preceding processed data cannot be entered, or whether the entry condition is abnormal.

[0102] After receiving the preceding processed data, the integrated management information processing platform writes the preceding processed data name into the inspection data name, the preceding processed data value into the inspection data value, the provider name into the inspection data provider, the processing serial number into the inspection data processing serial number, the inspection data source type into the preceding processed data, and the "check only, no writing" flag into the inspection data, thus forming the inspection data.

[0103] After the inspection data is generated, the business object number, target name, business action name, source serial number, and data that the business action needs to write to the target are read from the business action message. The business object number, target name, business action name, source serial number, data that the business action needs to write to the target, and inspection data are written into the same message body to generate an execution request with inspection data.

[0104] Once an execution request with check data is generated, the integrated management information processing platform writes the execution request with check data into the pending-send area, waiting to send it to the target end.

[0105] As an example, if the financial management end lacks outbound completion data, and the warehouse management end has not yet generated outbound completion data but has generated review completion data, the integrated management information processing platform will send the outbound completion data name and review completion data to the financial management end for reprocessing. When the financial management end confirms in the invoice application entry program that the review completion data belongs to the data items that can be entered in advance, and that the value of the review completion data indicates that the review has been completed, the financial management end will return the previously processed data that can be entered information. The integrated management information processing platform will generate inspection data from the review completion data and combine it with the invoice application message to generate an invoice execution request with inspection data.

[0106] When the target end returns a message that the preceding data cannot be entered, no execution request with check data is generated. Instead, the business action message, the name of the missing preceding data item, the name of the management end that generated the preceding data item, and the source serial number are written to the pending processing area. The pending processing area stores the data to be written for the business action message and the source serial number. After the management end that generated the preceding data item subsequently forms the preceding data item, the integrated management information processing platform sends a preceding data confirmation request to the management end that generated the preceding data item again, based on the business object number and the name of the missing preceding data item stored in the pending processing area.

[0107] When the target terminal returns an entry condition exception message, an entry condition exception record is generated and the automatic sending of the same business action message is stopped.

[0108] Among them, the abnormal entry condition record of the target end is written with the business object number, target end name, business action name, missing preceding data item name, preceding processing data name and source serial number, which is used to record the inconsistency between the target end entry check conditions and the order of business action data formation.

[0109] Furthermore, when generating inspection data, the inspection data name, inspection data value, inspection data provider, and inspection data processing serial number are all derived from the preceding data confirmation information and are not extracted from the data carried by the source.

[0110] Therefore, the data used for the target entry check comes from the management end that generates the preceding data items, thus avoiding the source end from carrying old data to participate in the target entry check.

[0111] In addition, the inspection data can only be generated after the preceding processed data has been processed and confirmed again at the target end.

[0112] It should be noted that the integrated management information processing platform cannot directly generate an execution request with check data based solely on the preceding processing data returned by the management end that generates the preceding data items. By reprocessing the request, the target end can determine whether the preceding processing data can replace the preceding data items that have not yet been formed to participate in the entry check, so that the business action messages when the preceding data items have not yet been finally formed still have a controllable progression path.

[0113] S4. Combine the inspection data with the business action message to generate an execution request with inspection data, send it to the target end, and perform an entry check based on the inspection data, only writing the data to be written in the business action message.

[0114] The integrated management information processing platform reads the pending requests or execution requests with check data from the pending area and sends them to the target end.

[0115] After receiving the request to be executed, the target end reads the source serial number and the business action name, and retrieves the target end's local execution record. If the same source serial number and the same business action name already exist in the target end's local execution record, the target end will not write the business data again, and will return the processed feedback to the integrated management information processing platform.

[0116] After receiving the processed feedback, the integrated management information processing platform marks the business action message as processed and will not resend the pending execution request.

[0117] When there is no identical source serial number and identical business action name in the target's local execution record, the target reads the data that the business action in the request to be executed needs to be written to the target and generates a write instruction based on the business action name.

[0118] It should be noted that the write command only takes the data that the business action needs to write to the target end, and does not take the inspection data other than the source serial number.

[0119] Once the target device has completed the write operation, it generates an execution completion feedback.

[0120] The execution completion feedback includes the business object number, target name, business action name, execution status, actual data name written, and source serial number.

[0121] Furthermore, after receiving the feedback on the completion of the execution, the integrated management information processing platform compares the actual data names written with the data names that the business action needs to write to the target end item by item.

[0122] When all the data names actually written belong to the data names that the business action needs to write to the target end, the business action message is marked as completed; when there is content in the data names actually written that does not belong to the data names that the business action needs to write to the target end, a target end write exception record is generated, and automatic execution requests with the same business object number and the same business action name are stopped from being sent to the same target end.

[0123] After receiving the execution request with inspection data, the target end first puts the inspection data into the entry inspection process according to the "check only, write not" flag. The target end reads the inspection data name, inspection data value, inspection data provider and inspection data processing serial number, and calls the business action entry program according to the business action name.

[0124] Specifically, the target end searches for the name of the prerequisite data item that needs to be met before the current business action can be entered in the business action entry program, and determines whether the check data name can meet the prerequisite data item name; when the check data name is consistent with the prerequisite data item name, the target end determines whether the business action entry condition is met based on the check data value; when the check data name is the name of the preceding processing data, the target end determines whether the preceding processing data can meet the business action entry condition based on the preceding processing data that has been confirmed to be able to enter in the re-trial processing stage.

[0125] It should be noted that the check data name is the field name in the check data, and is not limited to the name of the preceding data item; when the preceding data item has been formed, the check data name is written as the preceding data item name, and the check data source type is written as the preceding data item; when the preceding data item has not yet been formed but there is preceding processed data and it has been confirmed by the target end, the check data name is written as the preceding processed data name, and the check data source type is written as the preceding processed data; the target end distinguishes between the preceding data item check and the preceding processed data check based on the check data source type.

[0126] After the target end entry check passes, the target end generates a restricted write command.

[0127] Among them, the restricted write instruction only reads the data that the business action needs to write to the target end, does not read the check data value, does not read the check data provider, and does not read the check data processing serial number.

[0128] The target end completes the writing of business data according to the restricted write command and generates execution feedback.

[0129] The execution feedback includes the business object number, target name, business action name, execution status, actual data name written, actual check data name used, and actual processing serial number used.

[0130] After receiving the execution feedback, the integrated management information processing platform compares the actual data name written with the data name that the business action needs to write to the target end. If all the actual data names written belong to the data names that the business action needs to write to the target end, and the check data name is not among the actual data names written, the business action message is marked as completed.

[0131] When the execution feedback indicates that the same business action already exists on the target side, the integrated management information processing platform marks the business action message as processed and stops repeatedly sending execution requests under the same source serial number.

[0132] When the execution feedback indicates that the target end has written the check data name, the integrated management information processing platform generates a target end write exception record.

[0133] The exception record written to the target end includes the business object number, target end name, business action name, inspection data name, inspection data provider, inspection data processing serial number, and source serial number.

[0134] Furthermore, after generating the exception record written to the target end, the integrated management information processing platform stops sending execution requests with the same check data name to the same target end.

[0135] When the execution feedback indicates that the target end is still missing the same preceding data item, and the target end has previously confirmed through reprocessing that the preceding data can meet the conditions for entering the business action, the integrated management information processing platform generates an inter-end inconsistency check record.

[0136] The inconsistency record between endpoints includes the business object number, target endpoint name, business action name, missing prerequisite data item name, actual check data name, actual processing serial number, and source serial number.

[0137] Furthermore, after generating the inter-end inconsistency record, the integrated management information processing platform will no longer repeatedly send execution requests containing the same business object number, the same business action name, and the same inspection data name to the same target end.

[0138] When the execution feedback indicates that the target end lacks a new preceding data item name, the integrated management information processing platform reads the new preceding data item name and determines the management end that generated the new preceding data item based on the new preceding data item name. The integrated management information processing platform regenerates the preceding data confirmation request based on the business object number, the new preceding data item name, and the source serial number, and sends the preceding data confirmation request to the management end that generated the new preceding data item.

[0139] As an example, after receiving an invoice execution request with inspection data, the financial management terminal first determines whether the invoice application can proceed based on the outbound completion data or review completion data in the inspection data. After the entry check is passed, the financial management terminal only writes the invoice application data and the invoice amount, and does not write the outbound completion data, review completion data, warehouse management terminal name, or warehouse processing serial number. After the financial management terminal returns the execution feedback, the integrated management information processing platform determines whether the invoice application message has been processed based on the actual data name written. If outbound completion data or review completion data is written in the execution feedback, an exception record is generated for the target end.

[0140] In addition, the inspection data only participates in the entry inspection at the target end and does not participate in the target end business data storage; the inspection data provider and the inspection data processing serial number are only used as the basis for entry inspection and execution feedback verification; through restricted write processing, the integrated management information processing platform can promote the continued execution of business action messages when the target end needs the preceding data items but the target end has not yet fully saved the preceding data items locally, while avoiding the preceding data items or previous processing data being incorrectly written to the target end business data.

[0141] This embodiment also provides a computer device applicable to the message processing method of an integrated management information system, comprising: a memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to implement the message processing method of the integrated management information system proposed in the above embodiment.

[0142] The computer device can be a terminal, comprising a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0143] This embodiment also provides a storage medium storing a computer program, which, when executed by a processor, implements the message processing method for an integrated management information system as proposed in the above embodiments. The storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0144] In summary, this invention achieves the identification of pre-processing data items before business actions are written by trial processing requests and non-write checks, reducing the risk of direct cross-terminal message writing; by obtaining pre-processing data confirmation information from the management end that generates the pre-processing data items, it ensures the accuracy of the data source and avoids old data from participating in the entry check; and by re-trial processing of the pre-processing data, it achieves the controllable advancement of business action messages when pre-processing data items have not been formed, reducing message stagnation.

[0145] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A message processing method for an integrated management information system, characterized in that, include: Receive business action messages, generate a trial processing request without data to be written based on the business object number, target name and business action name, send it to the target to perform a no-write check and obtain check information; When the check information indicates that the name of the preceding data item is missing, the management end that generated the preceding data item is determined based on the name of the preceding data item, a preceding data confirmation request is sent, and the preceding data confirmation information is obtained. When the preceding data item has been formed, check data is generated from the preceding data item. When the preceding data item has not yet been formed but there is preceding processed data, the preceding processed data is sent to the target end for reprocessing. After the target end confirms, the preceding processed data is used to generate check data. The inspection data is combined with the business action message to generate an execution request with inspection data, which is sent to the target end and the entry check is performed based on the inspection data. Only the data to be written in the business action message is written.

2. The message processing method for an integrated management information system as described in claim 1, characterized in that, The generation of a trial processing request that does not contain data to be written includes: Receive business action messages sent by the source end, and read the business object number, target end name, business action name, and source serial number from the business action message; Write the business object number, target name, business action name, source serial number, and read-only check flag into the trial processing request; The data to be written in the business action message is kept in the local pending area and is not written to the trial processing request.

3. The message processing method for an integrated management information system as described in claim 1 or 2, characterized in that, The acquisition of inspection information includes: The target end enters the read-only processing channel based on the read-only check mark, reads the existing business records on the target end, and calls the business action entry program corresponding to the business action name; According to the inspection order in the business action entry procedure, determine whether the prerequisite data items required to enter the current business action exist in the existing local business records; If a preceding data item does not exist, the name of the first non-existent preceding data item is returned as the check information. If a local action with the opposite name to the business action exists in an existing local business record, return the information of the opposite action; When the same data item name belongs to both the data item that needs to be satisfied before the current business action is initiated and the data item generated after the current business action is completed, an entry condition exception message is returned.

4. The message processing method for an integrated management information system as described in claim 1, characterized in that, The management terminal that determines the generation of the preceding data items includes: Using the name of the missing preceding data item as the retrieval field, search for a maintenance list of data items that can generate the same data item name in the data item source relationship; When a management terminal name is found, the management terminal name is identified as the management terminal that generated the preceding data items; When multiple management terminal names are found, compare the business action name with the business action name that generates the data item in the data item maintenance list, and select the management terminal that belongs to the same business link; When multiple management terminal names still exist, select the front-end data source terminal registered in the business action entry program of the target terminal.

5. The message processing method for an integrated management information system as described in claim 1, characterized in that, The specific steps for sending a pre-confirmation data request and obtaining pre-confirmation data information are as follows: Send a pre-data confirmation request to the management terminal that generated the pre-data item, and write the business object number, business action name, target terminal name, missing pre-data item name and source serial number into the pre-data confirmation request; If there is a missing preceding data item name in the local business record, and there is no cancellation action later than the time the preceding data item was formed in the local data item cancellation record, return the preceding data confirmation information that the preceding data item has been formed; If there is no missing preceding data item name in the local business record, and there is a data item that has been formed and has not been cancelled in the preceding data item record, return the preceding data confirmation information that the preceding data item has not yet been formed but has preceding processed data. If the local business record does not contain the name of the missing preceding data item, the preceding data item record does not contain any data items that have been formed and not canceled, and the local business record contains a business action serial number that is being processed, the information of the preceding data item being processed will be returned. If there is a cancellation action in the local data item cancellation record that is later than the creation time of the previous data item, the information that the previous data item has been cancelled is returned.

6. The message processing method for an integrated management information system as described in claim 1, 4, or 5, characterized in that, The process of generating inspection data through preceding data items includes: When the confirmation type of the previous data confirmation information is that the previous data item has been formed, read the name of the previous data item, the value of the previous data item, the name of the providing end, and the processing serial number. Write the name of the preceding data item into the name of the inspection data, write the value of the preceding data item into the value of the inspection data, write the name of the provider into the inspection data provider, and write the processing serial number into the inspection data processing serial number. Write the source type of the inspection data as a preceding data item, and write the "inspect only, do not write" flag into the inspection data.

7. The message processing method for an integrated management information system as described in claim 1, characterized in that, The steps for sending the pre-processed data to the target end for reprocessing and generating inspection data from the pre-processed data after confirmation at the target end are as follows: Generate a retry processing request and write the business object number, target end name, business action name, missing preceding data item name, preceding processing data name, preceding processing data value, provider end name, processing serial number, and read-only check flag into the retry processing request. The target end enters the read-only processing channel based on the read-only check mark, and searches in the business action entry program for the name of the data item that can be entered in advance, which corresponds to the name of the missing preceding data item. If the name of the preceding processed data is the same as the name of the data item that can be entered in advance, the value of the preceding processed data indicates that it has been completed or has taken effect, and there is no local action in the target end's local business record that is opposite to the business action name, the preceding processed data can be entered information. After receiving the preceding processing data and entering the information, the preceding processing data name, preceding processing data value, provider name and processing serial number are written into the inspection data, and the inspection data source type is written as the preceding processing data.

8. The message processing method for an integrated management information system as described in claim 1, characterized in that, The steps for sending data to the target end and performing an entry check based on the check data, and only writing the data to be written in the business action message, are as follows: After receiving the execution request with the inspection data, the target end puts the inspection data into the entry inspection process according to the "check only, write not" flag. The target reads the inspection data name, inspection data value, inspection data provider, and inspection data processing serial number, and calls the business action entry program to perform entry inspection based on the business action name; After the entry check passes, the target end generates a restricted write instruction, which only reads the data to be written from the business action message; The target end completes the writing of business data according to the restricted write command and returns execution feedback; When all the data names actually written belong to the data names to be written in the business action message, and there are no check data names in the actual data names written, the business action message is marked as completed. When the execution feedback indicates that the target has written the check data name, a target write exception record is generated. When the execution feedback indicates that the target end lacks a new preceding data item name, the management end that generates the new preceding data item is re-determined based on the new preceding data item name, and the preceding data confirmation request is regenerated. The execution feedback includes the business object number, target name, business action name, execution status, actual written data name, actual used check data name, and actual used processing serial number.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, it implements the steps of the message processing method for the integrated management information system according to any one of claims 1 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by the processor, it implements the steps of the message processing method for the integrated management information system according to any one of claims 1 to 8.

Images