A visual data tracking method for the entire procurement chain

Abstract

The present invention discloses a method for visualizing data tracking of the entire procurement link. The method includes: collecting all document tables, abstracting each type of document into a node in a document link diagram, configuring the association relationship within the document and between documents; monitoring the binlog generated by the document table data update, and pushing it to a distributed publish-subscribe message system; storing the current document information in an operation record table, inserting the current document into a link data table, and using the association relationship between documents to find the upstream document of the current document in the link data table, and binding the current document to the upstream document; through the execution strategy, virtualizing the node of the document type determined downstream of the current document but not yet created; according to the upstream and downstream binding relationship of the current document, generating a link diagram of the current document and its parent document and downstream descendant documents, thereby simply and comprehensively realizing the visualization of the entire procurement document link.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a procurement supply chain data tracking method. Background Art

[0002] Procurement visibility is the ability of stakeholders in the entire procurement supply chain to access real-time data related to sourcing, orders, delivery, inventory, and settlement. Faced with many complex conditions, it is not easy to achieve procurement visualization. On the one hand, through the implementation of various software and hardware, the continuous promulgation of institutional processes, and the support of various new data sources, it has become easier and easier for enterprises to make a few reports and a few beautiful cockpits, which can indeed show the current status of procurement from a macro perspective to a certain extent. On the other hand, many companies are being overwhelmed by massive internal and external data. The lack of top-level design for procurement management analysis, the inability to coordinate and execute the supply chain in real time, the difficulty in horizontally connecting various business lines, and the chimney-style information construction have made the problem more complicated.

[0003] Therefore, it is becoming increasingly difficult to find problems from the first-hand business execution: What kind of processing process does the entire chain from application to settlement go through? How and why do the nodes in the entire execution chain flow in this way? From the completion of a transaction to the action of a user, can we see at a glance? Which links are abnormal, which links are blocked, and which links are risky? How to break through the improvement of procurement efficiency?

[0004] At present, most procurement supply chain data tracking solutions are that each module collects data by tracking the code when the document is executed, and then displays it in the workbench of each module. This solution has the following disadvantages:

[0005] 1. Serious code intrusion.

[0006] 2. Affect the overall performance.

[0007] 3. Each module is displayed in its own workbench and can only connect adjacent documents in series, which still cannot meet the full-link visualization of procurement documents. Summary of the invention

[0008] In response to the above technical problems, the present invention provides a method for visually tracing data in the entire procurement chain.

[0009] A procurement full-link visual data tracking method includes the following steps:

[0010] a) Collect all document tables, abstract each type of document into a node in the document link graph, and configure the association relationship within and between documents;

[0011] b) Use the data replication service provided by the cloud service provider to monitor the binlog generated by the data update of the document table and push it to the distributed publish-subscribe messaging system;

[0012] c) consuming messages in the distributed publish-subscribe message system in real time, storing the current document information in the operation record table, inserting the current document into the link data table, and finding the upstream document of the current document in the link data table by using the association relationship between documents, and binding the current document with the upstream document;

[0013] d) Abstract the current document table into a model and receive the user's configuration of node information and display content;

[0014] e) By executing the strategy, a node of a document of the document type determined downstream of the current document but not yet created is virtualized;

[0015] f) On the workbench query page where the document link diagram component is introduced, in response to the user's query instructions, a link diagram of the current document and its parent document and downstream descendant documents is generated based on the upstream and downstream binding relationship of the current document.

[0016] Optionally, step b) specifically includes: Huawei Cloud DRS monitors the binlog of the relevant table and pushes it to Kafka.

[0017] Optionally, the configuration of the node information and display content by the user in step d) includes node body configuration, table field configuration, node permission configuration, node operation record configuration and node detail configuration.

[0018] Optionally, the method further includes step s) collecting policy information for invoking between documents and within documents.

[0019] Furthermore, step s) specifically includes: when the user performs business operations related to documents, the uniformly encapsulated business rule component is called, the current document information is passed to the business rule component, the policy information is encapsulated and published through the business rule component, and the policy information publishing event is captured and collected by the transaction submission listener.

[0020] Furthermore, the business operations related to the documents include submitting documents, creating new documents, approving documents and modifying documents.

[0021] Furthermore, the policy information is encapsulated and published through the rule component, and the policy information publishing event is captured and collected by the transaction submission listener. Specifically, when the program calls the component, the policy information event is published when returning to execute the rule based on the incoming document information. When the transaction submission listener listens to the transaction submission action and the event type is an event for collecting document policy information, the policy information is asynchronously inserted into the database.

[0022] Correspondingly, the present invention also provides a big data platform for executing the above-mentioned procurement full-link visual data tracking method.

[0023] The present invention has at least the following beneficial effects:

[0024] The present invention captures all changes to the document non-invasively by monitoring binlog, records them, and assembles them into trees according to the document link relationship, thereby simply and comprehensively realizing the full-link visualization of the purchase document, avoiding the problem of embedding points in the code of each module, affecting performance, and requiring collaboration among various teams, which is time-consuming and labor-intensive.

[0025] The present invention calls a uniformly encapsulated business rule component, encapsulates policy information in the rule component, publishes it, and collects such events captured by the transaction submission listener. This can avoid the collection of dirty data caused by transaction rollback, and the query interface calls the policy contained in the same downstream interface to collect such data that does not need to be collected. Under the premise of uniformly calling this component, if each team needs to collect the policy rule information called by the document, they only need to pass the current document type and primary key value to the original calling interface. By making the display interface highly configurable, the personalized demands of different tenants can be covered. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 It is a schematic diagram of the principle of an embodiment of the present invention;

[0027] Figure 2 The figure is an example of a document link diagram presented to a user in one embodiment of the present invention. DETAILED DESCRIPTION

[0028] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0029] In order to quickly determine which links in the procurement process are abnormal and which links are blocked; capture the user's important operations on each document in the document link; how documents flow between each other. In order to clear the blind spots in the procurement link, fully release the data energy in business execution, and realize the visualization of the entire procurement link. At the same time, in order to unify the execution document process tracking of each module, the embodiment of the present invention provides a procurement full-link visualization data tracking method, refer to Figure 1 The platform architecture shown in the figure comprises the following steps:

[0030] (1) Collect all document tables and abstract each type of document into a node in the document link diagram (document flow diagram). Configure the association relationship within and between documents.

[0031] (2) Huawei Cloud DRS monitors the binlog generated by the document table data update and pushes the binlog to Kafka.

[0032] (3) Big data platform, the consumer side consumes messages in Kafka in real time.

[0033] Store the document information in the operation record table, insert the document into the link data table (rendering the link data table can obtain a document link diagram), and use the relationship between documents to find its upstream document in the link data table and bind it to the upstream document.

[0034] (4) Collect policy information for calls between documents and within documents.

[0035] The business rule component is uniformly encapsulated. When the program calls the component, it is necessary to pass in additional document information, and then publish the policy information event when returning to execute the rule. When the transaction submission listener listens to the transaction submission action and the event type is an event for collecting document policy information, the policy information is asynchronously inserted into the database.

[0036] (5) The current document table is abstracted into a model, and the node main information, overview, processing progress, etc. are highly configurable, allowing tenants to customize the display content.

[0037] (6) By executing the strategy, a node of a document whose document type is determined downstream of the current document but has not yet been created is virtualized.

[0038] (7) The front-end encapsulates the document link diagram component, which is introduced into the detailed query page of each module workbench. By clicking the icon, you can query the link diagram of the current document and its parent document and downstream descendant documents.

[0039] It should be understood that the numerical sequence of the above steps does not represent a strict execution order, but is only used to distinguish different links; for example, for step (4), when the user performs business operations related to the document, the uniformly encapsulated business rule component will be called to pass the current document information to the business rule component.

[0040] In the above-mentioned procurement full-link visual data tracking method, all changes to the document are captured non-invasively by monitoring binlog, and recorded, and assembled and rendered into a document link diagram according to the upstream and downstream binding relationship of the document, avoiding the problem of embedding points in the code of each module, affecting performance, and requiring the collaboration of each team, which is time-consuming and labor-intensive. Encapsulate the business rule component, call this component to pass some business rule policy configurations to determine the next business to be executed when executing the business process, encapsulate the policy information in the rule component, publish it, and capture such events by the transaction submission listener for collection, so as to avoid the collection of dirty data caused by transaction rollback, and avoid the query interface calling the policy contained in the same downstream interface, and collect such data that does not need to be collected. Under the premise of unified calling of this component, if each team needs to collect the policy rule information called by the document, they only need to pass the current document type and primary key value to the original calling interface. By making the display interface highly configurable, it can cover the personalized demands of different tenants.

[0041] Figure 2 An example of a document flow chart presented to the user is given.

[0042] ① Document relationship map: With each document transfer transaction, the document flow platform will record the upstream and downstream traceability relationship of the document and then assemble them in series, and creatively present the document relationship in the form of a tree relationship diagram. Users can trigger based on the document line in any business object workbench and intuitively view the source and destination of each line of the document.

[0043] ② Overview of link progress: Document icons, connection lines, connection points and other elements will change color (green for completed, yellow for in progress, and gray for not in progress) as the business progresses. It is easy to see where the business is paused, and you can initiate a one-click reminder in the link.

[0044] ③ Link prediction: Considering the complexity of the business, the rules for business execution in different scenarios are not the same (for example, some materials require quality inspection, while others do not); if the entire link data flow is regarded as a subway map, users are no longer passive "arranged persons", but planners and participants of traffic routes. The document flow platform will automatically preload icons of upcoming business based on upstream transaction data and business rules, so that users can clearly know which node is currently being executed, which nodes are to follow, and even the real-time business rules for each action call can be displayed, making the system no longer mysterious.

[0045] ④ Operational Audit: Efficiently and accurately analyze the captured SQL statements and front-end operations according to the audit rules, and conduct a comprehensive audit of the database operation behavior of the target business object, including operational risk audit and session event audit.

[0046] ⑤ Quick document query: You can perform an overview query on any document upstream and downstream of the document flow (predefined streamlined documents). If the permission check passes, the user can also directly access the original document to obtain more detailed original document information.

[0047] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0048] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A procurement full-link visual data tracking method, characterized in that: The following steps are involved: a) Collect all document tables, abstract each type of document into a node in the document link graph, and configure the association relationship within and between documents; b) Use the data replication service provided by the cloud service provider to monitor the binlog generated by the data update of the document table and push it to the distributed publish-subscribe messaging system; c) consuming messages in the distributed publish-subscribe message system in real time, storing the current document information in the operation record table, inserting the current document into the link data table, and finding the upstream document of the current document in the link data table by using the association relationship between documents, and binding the current document with the upstream document; d) Abstract the current document table into a model and receive the user's configuration of node information and display content; e) By executing the strategy, a node of a document of the document type determined downstream of the current document but not yet created is virtualized; f) In the workbench query page where the document link diagram component is introduced, in response to the user's query instruction, a link diagram of the current document and its parent document and downstream descendant documents is generated according to the upstream and downstream binding relationship of the current document; The method also includes: step s) collecting policy information called between documents and within documents; specifically including: when a user performs business operations related to documents, calling a uniformly encapsulated business rule component, and passing the current document information to the business rule component; encapsulating the policy information through the business rule component and publishing it, and the transaction submission listener capturing the policy information publishing event and collecting it; the encapsulating the policy information through the business rule component and publishing it, and the transaction submission listener capturing the policy information publishing event and collecting it, specifically includes: when the program calls the rule component, according to the passed-in document information, the policy information event is released when returning to execute the rule, and when the transaction submission listener listens to the transaction submission action and the event type is an event for collecting document policy information, the policy information is asynchronously inserted into the database.

2. The procurement full-link visual data tracking method according to claim 1 is characterized in that: Step b) is as follows: Huawei Cloud DRS monitors the binlog of the relevant table and pushes it to Kafka.

3. The procurement full-link visual data tracking method according to claim 1 is characterized in that: The configuration of the node information and display content by the user in step d) includes node body configuration, table field configuration, node permission configuration, node operation record configuration and node detail configuration.

4. The procurement full-link visual data tracking method according to claim 1 is characterized in that: In step s), the business operations related to the document include submitting a document, creating a new document, approving a document, and modifying a document.

5. A big data platform for executing the procurement full-link visual data tracking method described in claim 1.

Images