Visual data processing method and device of enterprise order management system, computer program product and readable storage medium

Abstract

The invention discloses a visual data processing method and device of an enterprise order management system, a computer program product and a readable storage medium, and the method comprises the steps: receiving a business request, responding to the execution of the business request, determining a visual tag associated with a business operation according to the type of the business operation, updating the data of the visual label according to the data information of the business operation; according to the type of the business operation, judging whether the type of the downstream business operation associated with the business operation needs to be executed after approval; if yes, approval needs to be carried out, and if not, data of the downstream visual label is directly updated according to the data information of the business operation. By adopting the scheme, the statistical data of each service node in the sales and purchase periods can be synchronously presented and updated on the same interface.

Description

Technical Field

[0001] This invention relates to the field of enterprise management software technology, and in particular to a visual data processing method and apparatus, computer program product, and readable storage medium for an enterprise order management system. Background Technology

[0002] In the digital transformation of the manufacturing industry, especially small and medium-sized manufacturing enterprises, order and financial process management has long been a challenge. Currently, common solutions mainly fall into two categories: The first type is the traditional Enterprise Resource Planning (ERP) system. These systems are feature-rich, modular, and costly to implement and maintain, requiring specialized personnel for configuration and operation. For small and medium-sized manufacturing enterprises with relatively simple business processes and limited hardware and software resources, ERP systems are often too cumbersome, resulting in them being unusable or having only a few functions used.

[0003] The second category consists of relatively lightweight Manufacturing Execution Systems (MES) or various single-point business management software. While these tools digitize specific processes such as production or sales, the processes—e.g., sales orders, shipments, invoicing, and payments—are often discrete and disconnected. Sales staff manage orders through one interface, while finance staff handle invoicing and payments in another system. When business owners need to understand the overall operational status, they have to retrieve data from multiple independent systems, performing tedious summarization and verification, which is not only inefficient but also highly prone to errors. Summary of the Invention

[0004] To address the aforementioned problems, the present invention aims to provide at least one visual data processing method for an enterprise order management system, which can synchronously present and update statistical data of various business nodes in the sales and procurement cycle on the same interface.

[0005] In a first aspect, the present invention provides a visual data processing method for an enterprise order management system, the method comprising: The system receives a business request, which indicates the type of business operation and data information in the enterprise order management system. The enterprise order management system is configured with multiple visualization labels, which are used to present statistical data of each business node in the product sales or procurement cycle. The system receives a business request, which indicates the type of business operation and data information in the enterprise order management system. The enterprise order management system is configured with multiple visual labels that are displayed simultaneously on the same page. The multiple visual labels are used to present statistical data of each business node in the product sales or procurement cycle. In response to the completion of the business request, a visual label associated with the business operation is determined according to the type of the business operation, and the data of the visual label is updated according to the data information of the business operation; Based on the type of the business operation, determine whether the type of downstream business operation associated with the business operation requires approval before it can be executed; If the judgment result is yes, then wait for the approval instruction, and after receiving the approval instruction, update the data of the downstream visualization label associated with the type of the downstream business operation according to the data information of the business operation. The downstream visualization label is selected from the plurality of visualization labels. If the judgment result is negative, the data of the downstream visualization label is updated according to the data information of the business operation.

[0006] Optionally, the method further includes: in response to the selection of the visual tag, presenting a customer tag on the same page; in response to the selection of the customer tag, presenting an access link to a target customer's target business operation record on the same page, wherein the target customer is the customer indicated by the customer tag, and the target business operation record is a record of business operations associated with the visual tag.

[0007] Optionally, the enterprise order management system integrates multiple business modules, and the business request is executed by the business module associated with the type of the business request.

[0008] Optionally, in response to the selection of the visual label, access links to the business modules associated with the visual label are presented on the same page.

[0009] Optionally, the service request is generated by an operation targeting the service module.

[0010] Optionally, the multiple visualization labels are used to present statistical data for each business node in the sales cycle, and the types of business operations are selected from: creating a sales order, the sales order taking effect, creating a delivery note or return note, creating an accounts receivable note, and creating a payment details note.

[0011] Optionally, the visual labels associated with creating a sales order, the sales order taking effect, creating a delivery note or return note, creating an accounts receivable note, and creating a payment details note are respectively: sales contract amount label, amount to be shipped label, amount to be invoiced label, amount to be received label, and amount received label.

[0012] Optionally, the statistical data presented by the multiple visualization labels are as follows: The statistical data presented in the sales contract amount label includes: number of orders. unit price Discount; The statistical data displayed on the pending shipment amount label is: (Number of approved orders - Number of shipped orders) unit price Discount; The statistical data displayed on the pending invoice amount label includes: the number of pending invoices. unit price Discount; The statistical data presented by the pending receivables label is: invoice amount - cumulative settlement amount; The statistical data displayed by the "Received Amount" label is: the amount received.

[0013] Optionally, the multiple visualization labels are used to present statistical data for each business node in the procurement cycle, and the types of business operations are selected from: creating a purchase order, purchase order taking effect, creating a receipt or return note, creating an accounts payable note, and creating a payment details note.

[0014] Optionally, the visual labels associated with creating a purchase order, making the purchase order effective, creating a receipt or return note, creating an accounts payable note, and creating a payment details note are respectively: purchase amount label, amount to be received label, amount to be invoiced label, amount to be paid label, and amount already paid label.

[0015] Optionally, the step of determining whether the type of downstream business operation associated with the business operation requires approval before execution, based on the type of the business operation, includes: Query predefined business rules, which contain approval attributes for each type of business operation; Based on the type of the business operation, obtain the corresponding approval attribute; Alternatively, the corresponding approval attribute can be determined by searching the pre-configured mapping relationship of approval attributes based on the type of business operation.

[0016] Secondly, the present invention provides a visual data processing device for an enterprise order management system, comprising: The request receiving unit is used to receive business requests, which indicate the type of business operation and data information. The enterprise order management system is configured with multiple visual labels that are displayed simultaneously on the same page. The multiple visual labels are used to present statistical data of each business node in the product sales or procurement cycle. A tag update unit is used to respond to the completion of the business request, determine the visual tag associated with the business operation according to the type of the business operation, and update the data of the visual tag according to the data information of the business operation; The process control unit is used to determine, based on the type of the business operation, whether the type of downstream business operation associated with the business operation needs to be approved before it can be executed; The downstream update unit, if the judgment result is yes, waits for the approval instruction, and after receiving the approval instruction, updates the data of the downstream visualization tag associated with the type of the downstream business operation according to the data information of the business operation, wherein the downstream visualization tag is selected from the plurality of visualization tags; if the judgment result is no, it updates the data of the downstream visualization tag according to the data information of the business operation.

[0017] Thirdly, the present invention also provides a computer-readable storage medium, which is a non-volatile storage medium or a non-transient storage medium, on which a computer program is stored, wherein the computer program is executed by a computer to perform the visualization data processing method of any of the above-described enterprise order management systems.

[0018] Fourthly, the present invention also provides a computer program product, including a computer program / instruction, wherein when the computer program / instruction is run by a computer, the visualization data processing method of any of the above-described enterprise order management systems is executed.

[0019] Compared with the prior art, the present invention has the following beneficial technical effects: In this embodiment of the invention, multiple visual labels are set for the statistical data of each business node and displayed simultaneously on the same page. After a business request is executed, not only are the visual labels directly associated with the business request updated, but also the downstream visual labels associated with the downstream business operations are updated. This allows for a comprehensive presentation of the latest statistical data of each business node, reducing the complexity of operations and improving the user experience.

[0020] Furthermore, in this embodiment of the invention, in response to the selection of a visual tag, a customer tag can be displayed on the same page, and in response to the selection of a customer tag, access links to the customer's history of business operations associated with the visual tag can be displayed on the same page, thereby enabling users to view the target customer's history by business node.

[0021] Furthermore, in this embodiment of the invention, in response to the selection of a visual label, an access link to the associated business module is presented on the same page, so that the user can enter the associated business module through the access link and perform the corresponding business operation. Attached Figure Description

[0022] Figure 1 This is a flowchart of a visual data processing method for an enterprise order management system according to the first embodiment of the present invention; Figure 2 This is a schematic diagram illustrating the presentation of multiple visual labels on the current page in a typical application scenario of an embodiment of the present invention; Figure 3 This is a schematic diagram of a visual data processing device for an enterprise order management system according to the second embodiment of the present invention. Detailed Implementation

[0023] As described in the background section, existing digital solutions mostly involve converting paper documents into isolated data records, requiring users to retrieve data from multiple independent systems to obtain the overall business situation of the enterprise. To address this technical problem, this invention provides a visualization data processing method for an enterprise order management system, comprising: receiving a business request, wherein the business request indicates the type and data information of a business operation in the enterprise order management system, the enterprise order management system being configured with multiple visualization labels displayed simultaneously on the same page, the multiple visualization labels being used to present statistical data of various business nodes in a product sales or procurement cycle; responding to the completion of the execution of the business request, determining the visualization label associated with the business operation based on the type of the business operation, and updating the data of the visualization label based on the data information of the business operation; determining whether the type of a downstream business operation associated with the business operation requires approval before execution based on the type of the business operation; if the determination result is yes, waiting for an approval instruction, and updating the data of the downstream visualization label associated with the type of the downstream business operation based on the data information of the business operation after receiving the approval instruction, the downstream visualization label being selected from the multiple visualization labels; if the determination result is no, updating the data of the downstream visualization label based on the data information of the business operation.

[0024] For statistical data of each business node, multiple visualization labels are set up to be displayed simultaneously on the same page. After a business request is executed, not only the visualization labels directly associated with the business request are updated, but also the downstream visualization labels associated with downstream business operations are updated as well. This enables a comprehensive presentation of the latest statistical data of each business node, reduces the complexity of operations, and improves the user experience.

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

[0026] like Figure 1 As shown, Figure 1 This is a flowchart illustrating a visual data processing method for an enterprise order management system according to a first embodiment of the present invention. The enterprise order management system (hereinafter referred to as the "system") can be a cloud-based manufacturing collaboration platform. The backend of the system can run on a cloud server for processing and storing data; the frontend of the system can be implemented based on a webpage or an app for inputting data and viewing various data processing results.

[0027] Specifically, the enterprise order management system is pre-configured with multiple visual tabs displayed on the same page. These tabs are rendered and displayed simultaneously on the same page of the system's user interface, encompassing various scenarios such as the same webpage or view. This is typically represented as a control panel or workbench homepage, where multiple tabs representing different business nodes are arranged side-by-side or in a grid, using cards or dashboard components. Users can view all key metrics at a glance without scrolling or switching pages, with each tab corresponding to a business node in the sales or procurement cycle.

[0028] The system can integrate multiple business modules, each responsible for handling specific business operations. Alternatively, other equivalent solutions can be used to execute corresponding business operations. Business modules and operation types can have a one-to-one correspondence, or the same module can execute multiple operation types. The division of business nodes is predefined by the system or pre-configured by the user. All business nodes cover all operations in the product sales or procurement cycle. Multiple visual labels presented on the same page can represent all business nodes or only a portion of them. Taking sales cycle management as an example, business nodes could include creating a sales order, approving the sales order to generate a pending shipment order, shipping, invoicing, and receiving payment. Multiple visual labels dynamically display the statistical amounts for the corresponding business nodes, such as... Figure 2As shown, the labels can be set as follows: sales contract amount label 211, amount to be shipped label 212, amount to be invoiced label 213, amount to be received label 214, and amount to be received label 215. All labels can be displayed on the same page, or some labels can be selected and displayed on the current page.

[0029] Multiple business modules can be used to execute corresponding business operations. For example, a request to create a sales order will be sent to the sales order creation module for logical processing, data verification, and storage. Similarly, order activation, delivery, invoicing, and payment collection are executed by the sales order activation module, the delivery note or return note creation module, the accounts receivable creation module, and the payment details creation module, respectively.

[0030] In this embodiment, refer to Figure 1 First, step S110 is executed to receive a business request, indicating the type of business operation and data information in the enterprise order management system. More specifically, the request can come from any business module in the enterprise order management system where the user performs a specific business operation, generating and sending a business request containing the business operation type and data information. Taking the business node of creating a sales order as an example, a sales order for a customer can be created and submitted through the interface of the "Create Sales Order" business module. This request encapsulates at least two types of key information: first, the type of this business operation, such as "Create Sales Order"; and second, the data information related to this operation, which may include, but is not limited to, order number, customer name, product details, unit price, quantity, and discount.

[0031] Then, step S120 is executed, updating the data of the visualization label in response to the completion of the business request. After confirming the completion of the business request, the associated visualization label is determined according to the type of business operation, and the associated visualization label is updated. Specifically, this can be done by searching for the directly associated visualization label in a preset mapping relationship and driving the display content of the label to be updated in real time based on the data information in the business request. For example, the business operation of creating a sales order is associated with a label that can display the sales contract amount. After the creation of a new sales order in the business module of creating a sales order, the associated visualization label, namely the sales contract amount label 211, is triggered to update, so as to accumulate the contract amount of the newly created sales order into the value of the sales contract amount label 211 and refresh the display.

[0032] Next, step S130 is executed to determine whether the type of downstream business operation associated with this business operation requires approval. After the current tag is updated, based on the predefined business process rules, it is determined whether this operation will trigger a downstream business operation requiring manual review. The specific query is based on the type of business operation; that is, it queries whether review is triggered based on the type of business operation.

[0033] After judgment, if the judgment result in S130 indicates that approval is required, then step S141 is executed to wait for the approval instruction, and the data of the downstream visualization label associated with the type of downstream business operation is updated upon receiving the approval instruction; or if the judgment result in S130 indicates that approval is not required, then step S142 is executed to update the data of the downstream visualization label based on the data information of the business operation. Specifically, if the judgment result is yes, i.e., approval is required: the system enters a waiting state, suspends the automatic update of the downstream label, and waits until the corresponding approval instruction is received. Once the instruction arrives, the downstream visualization label associated with the type of downstream business operation is updated according to the data information in the business request. If the judgment result is no, i.e., approval is not required: the system immediately executes the automated process and directly updates the data of the downstream visualization label based on the data information of the current business operation. In a typical application scenario, taking order management in the sales cycle as an example, the rules can be set as follows: the downstream business operation type for creating a sales order is "sales order effective," which means confirming how many of the created sales orders are already effective. The effectiveness of downstream business sales orders requires approval. On the other hand, the downstream business operation for creating a delivery note is "creating an accounts receivable note," because an invoice can be issued directly after delivery, so no approval is required.

[0034] By setting up multiple visualization labels for statistical data of each business node to be displayed simultaneously on the same page, after a business request is executed, not only are the visualization labels directly associated with the business request updated, but also the downstream visualization labels associated with downstream business operations are updated as well. This allows for a comprehensive presentation of the latest statistical data of each business node, reducing operational complexity and improving user experience.

[0035] Further, continue to refer to Figure 2When a visual label is selected, a link to the target customer's business operation record is displayed on the same page. The target customer is the customer indicated by customer label 220, and the target business operation record is the record of the business operation associated with the visual label. Customer label 220 can be a list of all customer labels 220 or a search box. Customer labels 220 appear through search. When the user selects a specific customer (the target customer), the page provides a "View Details" button 221. This button contains a link to the target business operation record, which can reflect information from a period of time or all historical documents. By using the business operation type associated with the currently selected visual label and the specific customer as limiting conditions, the system filters and displays links to all relevant business records for that customer under that business operation type, allowing for one-click viewing of detailed historical documents. This enables a comprehensive overview of macro indicators, allowing for quick drill-down to specific customers and the most detailed documents, obtaining historical data information for a specific order, thus improving the accuracy of management.

[0036] In some implementations, the underlying architecture of an enterprise order management system consists of multiple business modules. These modules are divided according to business process nodes, and each module is responsible for handling a specific business operation. Whenever a business request specifying the operation type is received, it is assigned to the corresponding specific business module for execution, based on the type of business operation in the request. For example, a request to create a sales order would be sent to the sales order creation module for logical processing, data validation, and storage.

[0037] Furthermore, such as Figure 2 As shown, when a visualization label is selected, such as by clicking a label, the associated functional area dynamically expands or loads within the same page. This area provides access links to business modules related to the statistical data of the selected label. Specifically, a "Create Sales Order" button 230 can be displayed in this area, configured with access links to business modules, allowing direct execution of specific business operations. This eliminates the cumbersome steps of exiting the visualization label page and searching for the corresponding business module, shortening the path between data monitoring and business operations, and achieving a highly efficient workflow of "see, manage, and execute immediately."

[0038] Furthermore, the source and triggering method of business requests are triggered by the user's active operation on the front-end graphical interface targeting a specific business module, ensuring a high degree of consistency and directness between data visualization and user intent. Specifically, for example, when a user creates a sales order and clicks the confirm / submit button on the sales order creation interface, this click instantly generates a business request containing the business operation type of creating the sales order and the specific data information entered in the order, and submits it to the business module.

[0039] In some implementations, the method of this embodiment is applied to manage the sales cycle, with the following business operation types: creating a sales order, sales order activation, creating a delivery note or return note, creating an accounts receivable note, and creating a payment details note. These five business operation types define a standard sales business process chain from contract signing to fund recovery. Correspondingly, as... Figure 2As shown, the associated visual labels can be: Sales Contract Amount Label 211, Amount to be Shipped Label 212, Amount to be Invoiced Label 213, Amount to be Collected Label 214, and Amount to be Collected Label 215, to achieve visualization of the entire sales process. Specifically, after a customer selects a product, fills in the quantity, unit price, and discount, and clicks submit, a sales order is generated. This order records the data information of this transaction. After the business request to create a sales order is received and the order is created and stored through a business module or other means, the data on the associated Sales Contract Amount Label 211 is automatically updated. The downstream business of creating a sales order is the sales order taking effect, which is a business type that requires approval. The approval instruction is a necessary step for the sales order to take effect and allow subsequent business operations to be executed. The specific implementation of the approval process can be that an administrator with approval authority views the submitted sales orders in the to-do list, selects single-line approval or batch approval, that is, gives the approval instruction, and the Amount to be Shipped Label 212 is updated accordingly after approval. For sales orders that have taken effect, if the downstream business node is shipment, the process proceeds directly to the downstream business node without approval. Warehouse staff select the details to be shipped and click the "ship" button to generate a shipping order, recording the actual goods shipped. If a return occurs, a return order is generated to offset the original shipment record. Creating either a shipping order or a return order will simultaneously update the statistical data on the pending invoice amount label 213. After a shipment or return operation is completed, no approval is required. Based on the shipment details, an accounts receivable invoice is generated, and the data on the pending receivable amount label 214 is updated. Alternatively, business rules can be pre-configured to require approval; in this case, an accounts receivable invoice is generated and the pending receivable amount label 214 is updated only after approval is received. The accounts receivable invoice, based on previous data, clarifies the amount due from the customer. When payment is received from the customer, a collection details invoice is created, recording the actual amount received, the date of receipt, and the method of payment, thus completing the cash recovery process. Similarly, this business node can be directly transferred to the downstream according to predefined business rules, or it can be transferred to the downstream business and update the tag corresponding to the next business operation after approval instructions, that is, update the sales contract amount tag 211, thus realizing the sales cycle closed loop.

[0040] Furthermore, by solidifying business rules into executable computational logic, the real-time nature and consistency of data are ensured. Specifically, the statistical data presented by the sales contract amount tag 211 includes: number of orders. unit price The discount value represents the estimated total revenue from all created sales orders, including both approved and unapproved sales orders. Any business event affecting the formula variable, such as adding an order, modifying the order quantity or unit price, deleting an order, or adjusting the discount, will trigger a change in the data on the Sales Contract Amount label 211. The pending shipment amount label 212 presents the following statistics: (Number of approved orders - Number of shipped orders). unit price The discount tag dynamically reflects the approved, pending shipment value. Specifically, when upstream approval is granted, an effective sales order is added, leading to an increase in the number of approved orders. When a shipping order or return order is created for the business type associated with this tag, the number of shipped orders increases or decreases. The occurrence of any of these business operations triggers the data calculation for the pending shipment amount tag 212, recalculating the quantity of each changed order. Through calculations of unit price and discount, the total amount of all changed orders is summarized and updated, ensuring strict synchronization between the tag data and the actual pending shipment tasks in the warehouse. The statistics presented by the pending invoice amount tag 213 are: pending invoice quantity. unit price Discounts: After each successful shipment, not only is the shipment recorded, but data is also updated synchronously for its downstream business operations. This involves generating pending invoice records for these shipment details, and accumulating the pending invoice amount based on the quantity, unit price, and discount data in the details. The statistics presented by the "Pending Receivables Amount" label 214 are: Invoice Amount - Cumulative Settlement Amount. The value of this label depends on two financial data sources: Invoice Amount and Cumulative Settlement Amount. This data is obtained from the data information contained in the business operations associated with the pending receivables amount and the received amount, respectively, from each account receivable and receipt detail document generated by triggering the creation of an accounts receivable document and a receipt detail document. The statistics presented by the "Received Amount" label 215 are: Settlement Amount, i.e., the business operation corresponding to the received amount itself. The increase and summary of settlement amount data in the created receipt detail document will cause the "Received Amount" label 215 to accumulate accordingly. Optionally, after settlement, the contract amount can be deducted from the "Sales Contract Amount" label 211. In some implementations, the deduction can be made immediately upon completion of each order; in other variations, the deduction can be made uniformly over a specific financial period to reflect the overall changes in sales contracts within each period. The tag values ​​are calculated based on a preset formula; changes in business data are reflected on the tags through this formula, achieving truly real-time data updates.

[0041] In other implementations, the same data processing engine and interface rendering logic are used. When the scenario switches to procurement, the system loads the pre-set business operation types and visual tags for procurement. The technical solution is logically identical to the sales cycle, demonstrating the reusability of the system's core architecture. In the procurement scenario, each operation automatically triggers the update of the corresponding tags, just like in the sales scenario, and these tags are displayed in real time on the tags corresponding to each business node in the procurement process. Specifically, this is applied to managing the procurement cycle. The business operation types are selected from: creating a purchase order, purchase order taking effect, creating a receiving note or return note, creating an accounts payable note, and creating a payment details note. Correspondingly, the associated visual tags are: procurement amount tag, amount to be received tag, amount to be invoiced tag, amount to be paid tag, and amount already paid tag. This achieves a fully closed-loop order management system from purchase request to payment.

[0042] In this embodiment of the invention, the approval judgment mechanism based on predefined rules can be implemented in various ways. In some implementations, an approval attribute is pre-configured for each business operation type in a centralized set of business rules through a management backend. This attribute can be a Boolean value or an enumerated value. When a business operation is completed and it is necessary to determine whether its downstream operation needs approval, a rule query is triggered. The query is initiated to the business rule set with the type of the current business operation as the parameter. The record corresponding to the operation type is retrieved from the rule base, and the value of its approval attribute field is obtained. Based on the returned approval-required or approval-free attribute value, a judgment result is directly obtained, thereby determining whether the process enters the waiting approval state or continues to be automatically executed.

[0043] In other implementations, the mapping between business operation types and approval attributes is loaded into memory during initialization to form an efficient key-value mapping table. When approval is required, the type of the current business operation is used as the key to directly look up the value of the approval attribute bound to that key in the memory mapping table, thus avoiding database access for each decision and making it suitable for high-concurrency scenarios.

[0044] In a preferred embodiment, if the user logging into the system has preset permissions, such as administrator permissions, then after logging in, multiple visual labels are displayed permanently and continuously on the same page, such as the user's login interface. Even if the user navigates to a different location by selecting a visual label, such as accessing a corresponding business module through various links or viewing the record of a target business operation, the multiple visual labels will continue to be displayed on the login interface for easy viewing. Furthermore, after one or more visual labels are updated, the presentation of the updated visual label will differ from other visual labels for a preset period of time. For example, if a user accesses a corresponding business module and performs certain business operations, causing the statistical data of one or more visual labels to be updated, then this visual label can be highlighted, allowing the user to quickly locate the data change and at which business node the change occurred.

[0045] Figure 3 This is a schematic diagram of the structure of a visualization data processing device for an enterprise order management system according to an embodiment of the present invention. Those skilled in the art will understand that the visualization data processing device described in this embodiment can be used to implement the technical solutions described in the above embodiments.

[0046] Specifically, refer to Figure 3 The visualization data processing device 3 of the enterprise order management system according to the second embodiment of the present invention may include: The request receiving unit 31 is used to receive business requests, which indicate the type of business operation and data information. The enterprise order management system is configured with multiple visual labels that are displayed simultaneously on the same page. The multiple visual labels are used to present statistical data of each business node in the product sales or procurement cycle. The label update unit 32 is used to respond to the completion of a business request, determine the visual label associated with the business operation according to the type of the business operation, and update the data of the visual label according to the data information of the business operation. The process control unit 33 is used to determine, based on the type of business operation, whether the type of downstream business operation associated with the business operation needs to be approved before it can be executed; Downstream update unit 34, if the judgment result is yes, waits for the approval instruction, and after receiving the approval instruction, updates the data of the downstream visualization label associated with the type of downstream business operation according to the data information of the business operation. The downstream visualization label is selected from multiple visualization labels; if the judgment result is no, it updates the data of the downstream visualization label according to the data information of the business operation.

[0047] In specific implementation, the modules / units included in the various devices and products described in the above embodiments can be software modules / units, hardware modules / units, or a combination of both.

[0048] For example, for various devices and products applied to or integrated into a chip, each module / unit can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits; for various devices and products applied to or integrated into a chip module, each module / unit can be implemented using hardware methods such as circuits, and different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The components can be implemented using software programs that run on the processor integrated within the chip module. The remaining (if any) modules / units can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into the terminal, each of its components / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or in different components within the terminal. Alternatively, at least some modules / units can be implemented using software programs that run on the processor integrated within the terminal, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits.

[0049] Furthermore, embodiments of the present invention also disclose a storage medium storing computer instructions, which, when executed, perform the above-described... Figure 1 The method described in the illustrated embodiment is a technical solution. Preferably, the storage medium may include a computer-readable storage medium. The storage medium may include ROM, RAM, a magnetic disk, or an optical disk, etc.

[0050] Furthermore, the present invention also provides a computer program product, including a computer program / instruction, wherein when the computer program / instruction is run by a computer, the visualization data processing method of any of the above-described enterprise order management systems is executed.

[0051] While the present invention has been disclosed above, it is not limited thereto. Any person skilled in the art can make various modifications and alterations without departing from the spirit and scope of the invention; therefore, the scope of protection of the present invention should be determined by the scope defined in the claims.

Claims

1. A visual data processing method for an enterprise order management system, characterized in that, include: The system receives a business request, which indicates the type of business operation and data information in the enterprise order management system. The enterprise order management system is configured with multiple visual labels that are displayed simultaneously on the same page. The multiple visual labels are used to present statistical data of each business node in the product sales or procurement cycle. In response to the completion of the business request, a visual label associated with the business operation is determined according to the type of the business operation, and the data of the visual label is updated according to the data information of the business operation; Based on the type of the business operation, determine whether the type of downstream business operation associated with the business operation requires approval before it can be executed; If the judgment result is yes, then wait for the approval instruction, and after receiving the approval instruction, update the data of the downstream visualization label associated with the type of the downstream business operation according to the data information of the business operation. The downstream visualization label is selected from the plurality of visualization labels. If the judgment result is negative, the data of the downstream visualization label is updated according to the data information of the business operation.

2. The visual data processing method for the enterprise order management system as described in claim 1, characterized in that, Also includes: In response to the selection of the visual label, a customer label is displayed on the same page; In response to the selection of the customer tag, an access link to the target customer's target business operation record is presented on the same page, wherein the target customer is the customer indicated by the customer tag, and the target business operation record is the record of the business operation associated with the visual tag.

3. The visual data processing method for the enterprise order management system as described in claim 1, characterized in that, The enterprise order management system integrates multiple business modules, and the business request is executed by the business module associated with the type of the business request.

4. The visual data processing method for the enterprise order management system as described in claim 3, characterized in that, In response to the selection of the visual label, access links to the business modules associated with the visual label are displayed on the same page.

5. The visual data processing method for the enterprise order management system as described in claim 3, characterized in that, The business request is generated by an operation performed on the business module.

6. The visualization data processing method for the enterprise order management system as described in claim 1, characterized in that, The multiple visualization labels are used to present statistical data for each business node in the sales cycle. The types of business operations are selected from: creating a sales order, the sales order taking effect, creating a delivery note or return note, creating an accounts receivable note, and creating a payment details note.

7. The visual data processing method for the enterprise order management system as described in claim 6, characterized in that, The visual labels associated with creating a sales order, making the sales order effective, creating a delivery note or return note, creating an accounts receivable note, and creating a payment details note are respectively: sales contract amount label, amount to be shipped label, amount to be invoiced label, amount to be received label, and amount received label.

8. The visualization data processing method for the enterprise order management system as described in claim 7, characterized in that, The statistical data presented by the various visual labels are as follows: The statistical data presented in the sales contract amount label includes: number of orders. unit price Discount; The statistical data displayed on the pending shipment amount label is: (Number of approved orders - Number of shipped orders) unit price Discount; The statistical data displayed on the pending invoice amount label includes: the number of pending invoices. unit price Discount; The statistical data presented by the pending receivables label is: invoice amount - cumulative settlement amount; The statistical data displayed by the "Received Amount" label is: the amount received.

9. The visual data processing method for the enterprise order management system as described in claim 1, characterized in that, The multiple visualization labels are used to present statistical data for each business node in the procurement cycle. The types of business operations are selected from: creating a purchase order, the purchase order taking effect, creating a receipt or return note, creating an accounts payable note, and creating a payment details note.

10. The visualization data processing method for the enterprise order management system as described in claim 9, characterized in that, The visual labels associated with creating a purchase order, making a purchase order effective, creating a receipt or return note, creating an accounts payable note, and creating a payment details note are respectively: Amount in Purchase, Amount to be Received, Amount to be Invoiced, Amount to be Paid, and Amount Paid.

11. The visualization data processing method for the enterprise order management system as described in claim 1, characterized in that, The step of determining whether the type of downstream business operation associated with the business operation requires approval before execution, based on the type of the business operation, includes: Query predefined business rules, which contain approval attributes for each type of business operation; Based on the type of the business operation, obtain the corresponding approval attribute; Alternatively, the corresponding approval attribute can be determined by searching the pre-configured mapping relationship of approval attributes based on the type of business operation.

12. A visual data processing device for an enterprise order management system, characterized in that, include: The request receiving unit is used to receive business requests, which indicate the type of business operation and data information. The enterprise order management system is configured with multiple visual labels that are displayed simultaneously on the same page. The multiple visual labels are used to present statistical data of each business node in the product sales or procurement cycle. A tag update unit is used to respond to the completion of the business request, determine the visual tag associated with the business operation according to the type of the business operation, and update the data of the visual tag according to the data information of the business operation; The process control unit is used to determine, based on the type of the business operation, whether the type of downstream business operation associated with the business operation needs to be approved before it can be executed; If the downstream update unit determines the result to be yes, it waits for the approval instruction and, after receiving the approval instruction, updates the data of the downstream visualization tag associated with the type of the downstream business operation according to the data information of the business operation. The downstream visualization tag is selected from the plurality of visualization tags. If the judgment result is negative, the data of the downstream visualization label is updated according to the data information of the business operation.

13. A computer-readable storage medium, said computer-readable storage medium being a non-volatile storage medium or a non-transient storage medium, having stored thereon a computer program, characterized in that, The computer program is executed by a computer, and the visual data processing method of the enterprise order management system according to any one of claims 1 to 11 is executed.

14. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the computer, the visualization data processing method of the enterprise order management system according to any one of claims 1 to 11 is executed.

Images