Procurement data processing method, device, electronic equipment and medium

Abstract

The present application provides a procurement data processing method, device, electronic device, and medium. The method is applied to a network architecture including an OA system and an SRM system. After the OA system accepts a request to view a target procurement demand sheet, it obtains the synchronization data of the target procurement demand sheet from the SRM system. When the SRM system generates synchronization data upon reaching a synchronization node, it sends the synchronization data to the OA system. The synchronization data is used to indicate the stage identifier of each procurement stage. Based on the current progress data corresponding to the synchronization data, a progress display interface is generated. The method intuitively and reliably realizes the collaborative sharing of information and status visualization through a visualization interface that perceives information throughout the entire process.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a procurement data processing method, device, electronic device and medium. Background Art

[0002] With the development of society, information exchange between buyers and suppliers is becoming increasingly frequent. However, in most current procurement processes, purchasing by the buyer and invoicing by the supplier are two independent processes, without coordinated management. For suppliers, the lack of centralized management of multiple buyers makes invoicing cumbersome and inefficient. For buyers, the lack of tracking and management of the supplier's invoicing process is particularly problematic in service-type procurement: it is difficult to confirm the detailed list of deliverables in advance. Procurement systems can provide greater transparency, provide specific information and details about the delivery process, and enable upfront control. Summary of the Invention

[0003] The purpose of the embodiments of the present application is to provide a procurement data processing method, device, electronic device and medium, which are used to intuitively and reliably realize collaborative information sharing and status visualization through a visual interface for full-process information perception.

[0004] In a first aspect, a procurement data processing method is provided, which is applied to a network architecture including an OA system and an SRM system. The method may include:

[0005] After the OA system receives a request to view the target purchase demand form, it obtains the synchronization data of the target purchase demand form from the SRM system; wherein, after the SRM system generates the synchronization data when reaching the synchronization node, it sends the synchronization data to the OA system, and the synchronization data is used to indicate the stage identifier of each procurement stage;

[0006] A progress display interface is generated based on the current progress data corresponding to the synchronization data.

[0007] In a possible implementation, the progress display interface includes seven procurement stages: demand stage, sourcing and project establishment stage, bidding and procurement stage, result approval stage, contract stage, performance stage and settlement stage. Each of the seven procurement stages corresponds to a stage identifier.

[0008] In one possible implementation, obtaining synchronized data of the target purchase demand form from the SRM system includes:

[0009] After the OA system approves the target purchase demand form, it will be synchronized to the SRM system through the interface, and then the seven procurement stages will be executed in sequence: demand stage, sourcing and project establishment stage, procurement stage, result approval stage, contract stage, performance stage and settlement stage.

[0010] In one possible implementation, the method further includes:

[0011] After the OA system accepts the request to view the target procurement demand change order and approves the target procurement demand change order, the target procurement demand change order is synchronized to the SRM system through the interface, and the target procurement demand order is generated. Then, the seven procurement stages are executed in sequence: demand stage, sourcing and project establishment stage, procurement stage, result approval stage, contract stage, performance stage and settlement stage;

[0012] After the OA system accepts the request to view the authorized purchase order and approves the authorized purchase order, it will be synchronized to the purchase requisition in the SRM system through the interface, and the authorization link will be included;

[0013] The purchase requisition with authorization link will be automatically updated to a purchase requisition, and the execution progress will be updated. After that, the execution data of the purchase requisition will be automatically synchronized to the OA system through the interface.

[0014] In one possible implementation, the SRM system includes a management end, a cloud end, and a supplier end; the synchronization data is synchronized by the management end, and the management end and the supplier end collaborate through the cloud end.

[0015] In one possible implementation, the method further includes:

[0016] The management side determines the purchase order based on the purchase contract;

[0017] After reviewing the purchase order, the cloud automatically generates collaborative purchase orders corresponding to non-framework contracts and collaborative purchase orders corresponding to framework contracts, and sends them to the supplier.

[0018] The supplier side allows suppliers to review and confirm collaborative purchase orders corresponding to non-framework contracts, supplement collaborative purchase orders corresponding to framework contracts, maintain order materials, and send the supplemented purchase orders to the cloud for confirmation;

[0019] After receiving the changed purchase order, the management end changes the purchase contract and obtains a purchase order change document;

[0020] After reviewing the purchase order change order, the cloud automatically generates a collaborative change order and sends it to the supplier.

[0021] Suppliers review and confirm the collaborative change order and generate an acceptance application based on the confirmed collaborative purchase order and collaborative change order.

[0022] After the cloud confirms the acceptance application form, it is sent to the management end;

[0023] After the management side receives the acceptance application form, it automatically generates a purchase acceptance form;

[0024] After the purchase acceptance document is automatically submitted for review in the cloud, the supplier can query the acceptance document and initiate reconciliation based on the summary of accepted orders;

[0025] After the management confirms the reconciliation results, the supplier issues the invoice, and the cloud signs for the invoice so that the management can generate the payable document and complete the payment process.

[0026] In one possible implementation, the SRM system collaborates with the expense control system through the expense control interface to enable the SRM system to connect with the supplier database of the expense control system through the expense control interface to implement the procurement contract execution process;

[0027] The SRM system collaborates with the OA system through a single sign-on interface to enable login and to-do processing;

[0028] The SRM system collaborates with the OA system through the business document interface to process purchase demand sheets, purchase execution data, and authorized purchase requirements;

[0029] The SRM system collaborates with the HR system through the HR interface to achieve the transmission of the company's organizational information and supplier information.

[0030] In a second aspect, a procurement data processing device is provided, which is applied to a network architecture including an OA system and an SRM system. The device may include:

[0031] an acquisition unit, configured to acquire synchronization data of the target procurement requisition from the SRM system after the OA system accepts a request to view the target procurement requisition; wherein, after the SRM system generates the synchronization data when reaching a synchronization node, the synchronization data is sent to the OA system, and the synchronization data is used to indicate a stage identifier of each procurement stage;

[0032] The generating unit is configured to generate a progress display interface based on the current progress data corresponding to the synchronization data.

[0033] In a third aspect, an electronic device is provided, the electronic device including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0034] Memory for storing computer programs;

[0035] The processor is configured to implement any of the method steps described in the first aspect when executing a program stored in the memory.

[0036] In a fourth aspect, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any of the method steps described in the first aspect is implemented.

[0037] The procurement data processing method provided in an embodiment of the present application is applied to a network architecture including an OA system and an SRM system. After the OA system receives a request to view a target procurement demand form, the method obtains the synchronization data of the target procurement demand form from the SRM system. When the SRM system generates synchronization data upon reaching a synchronization node, the synchronization data is sent to the OA system. The synchronization data is used to indicate the stage identifiers of each procurement stage. Based on the current progress data corresponding to the synchronization data, a progress display interface is generated. This method intuitively and reliably realizes the collaborative sharing of information and status visualization through a visual interface that perceives information throughout the entire process. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0039] Figure 1 A flowchart of a procurement data processing method provided in an embodiment of the present application;

[0040] Figure 2 A schematic diagram of a procurement business process provided in an embodiment of the present application;

[0041] Figure 3 A schematic diagram of the structure of a procurement data processing device provided in an embodiment of the present application;

[0042] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0043] The following, in conjunction with the accompanying drawings, provides a clear and complete description of the technical solutions in the embodiments of this application. Obviously, the described embodiments represent only a portion of the embodiments of this application and do not constitute a complete set of embodiments. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of this application without inventive effort are intended to fall within the scope of protection of this application. Unless otherwise defined, technical or scientific terms used in this application should have the same ordinary meanings as those understood by persons of ordinary skill in the art. The terms "first," "second," and similar expressions used in this application do not denote any order, quantity, or importance; they are merely used to distinguish between different components. Terms such as "include" or "comprising" mean that the element or object preceding the term includes the elements or objects listed after the term, and their equivalents, without excluding other elements or objects. Terms such as "connect," "couple," or "connected" are not limited to physical or mechanical connections but may include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are used solely to indicate relative positional relationships. When the absolute position of the described objects changes, the relative positional relationships may also change accordingly.

[0044] This application is a milestone and interim achievement in the enterprise's use of design procurement progress visualization and collaborative ordering. This plan is based on the current development status of the enterprise and is formulated in the procurement process, especially for Internet service categories (or project-based procurement) where progress is difficult to track and relies on manual responses and other efficiency measures. At the same time, it relies on the design method of order collaboration to transfer manual labor to the supplier, thereby greatly improving the efficiency of the company's purchasers. When realizing end-to-end online collaboration with suppliers, a more efficient, transparent, secure and standardized procurement execution system is created to promote the sustainable development of the supply system.

[0045] In other words, this application primarily introduces the process of visualizing procurement progress and order collaboration, demonstrating how to set up and display each procurement process, enabling stakeholders to access procurement progress in a timely manner. This order collaboration also addresses the dilemma of enterprise service procurement, particularly market procurement, where only the project name alone cannot clearly define the material delivery details before the project. This also frees up procurement personnel to complete pre-confirmation communication within the system when there's no clear bid, further improving procurement efficiency and reducing the risk of operations through transparent procurement processes.

[0046] 1) Regarding procurement progress visualization:

[0047] Figure 1 This is a flow chart of a procurement data processing method provided in an embodiment of the present application. Figure 1 As shown, the method may include:

[0048] Step S110: After the SRM system generates synchronization data when reaching the synchronization node, the synchronization data is sent to the OA system.

[0049] This synchronized data is used to indicate the stage identifiers of each procurement stage. The progress display interface can include seven procurement stages: demand stage, sourcing and project establishment stage, procurement stage, result approval stage, contract stage, performance stage, and settlement stage. Each of the seven procurement stages corresponds to a stage identifier.

[0050] Step S120: After the OA system accepts the request to view the target purchase demand form, it obtains the synchronized data of the target purchase demand form from the SRM system.

[0051] In the specific implementation, after the OA system approves the target procurement demand form, the target procurement demand form is synchronized to the SRM system through the interface, and then seven procurement stages such as the sourcing and project establishment stage and the procurement stage are executed.

[0052] Furthermore, after the OA system accepts a request to view the target procurement requirement change order and the OA system approves the target procurement requirement change order, it synchronizes the target procurement requirement change order to the SRM system through the interface, generates a target procurement requirement order, and then executes seven procurement stages, including the sourcing project establishment stage and the procurement stage; among them, if there is a personnel change and documents (target procurement requirement orders and / or target procurement requirement change orders) need to be transferred in batches in the SRM system, batch transfer can be carried out, and then seven procurement stages, including the sourcing project establishment stage and the procurement stage, are executed.

[0053] After the OA system accepts a request to view the authorized purchase order and the OA system approves the authorized purchase order, the authorized purchase order is synchronized to the purchase requisition in the SRM system through the interface, and the authorization link is carried; the purchase requisition carrying the authorization link is automatically updated to the purchase requisition, and the purchase requisition execution progress is updated, and then the purchase execution data of the purchase requisition execution progress is automatically synchronized to the OA system through the interface.

[0054] In one example, the above process can be referred to as Figure 2 The content shown.

[0055] Step S130: Generate a progress display interface based on the current progress data corresponding to the synchronization data.

[0056] 2) Regarding purchase order collaboration:

[0057] The purchase order execution business process refers to the business process for subsequent order confirmation, changes, receipt, acceptance, payment, and other scenarios after signing a contract with the supplier (if the business side is authorized to place purchase orders, it is necessary to comply with the procurement department's identity configuration system process, and approval can be directly captured through the business side reporting path).

[0058] Among them, orders are divided into project orders (non-framework collaborative orders) and framework collaborative orders:

[0059] Project orders are placed after the normal project contract is approved, with specific deliverables to be ordered and accepted by the supplier;

[0060] Framework collaborative orders are based on specific project requirements. Framework suppliers must submit materials and quantities for the services within the framework. Procurement then confirms and approves the order. This ensures clear deliverables before implementation and improves procurement efficiency.

[0061] For procurement order collaboration, the SRM system can include the management side (i.e. procurement management on the SRM side), the cloud (procurement collaboration cloud on the SRM side), and the supplier side (supplier portal on the SRM side); synchronized data is synchronized by the management side, and the management side and the supplier side collaborate through the cloud.

[0062] Specifically, (1) the management side can determine the purchase order based on the purchase contract; that is, execute the purchase contract business process to sign the purchase order with the supplier.

[0063] After reviewing the confirmed purchase order, the cloud automatically generates collaborative purchase orders corresponding to non-framework contracts and collaborative purchase orders corresponding to framework contracts, and sends them to the supplier side. Among them, for collaborative purchase orders, the supplier can select materials from the BOM content of the cloud top in the framework contract, and the unit price is carried over, and the unit price can be modified downward.

[0064] The supplier side allows suppliers to view and confirm collaborative purchase orders corresponding to non-framework contracts, and for suppliers to supplement and maintain order materials for collaborative purchase orders corresponding to framework contracts, and send the supplemented purchase orders to the cloud for confirmation.

[0065] (2) After receiving the changed purchase order, the management end changes the purchase contract and obtains a purchase order change form;

[0066] After reviewing the purchase order change order, the cloud automatically generates a collaborative change order and sends it to the supplier.

[0067] Suppliers review and confirm the collaborative change order and generate an acceptance application based on the confirmed collaborative purchase order and collaborative change order.

[0068] After the cloud confirms the business of the acceptance application form, it is sent to the management end.

[0069] (3) After the management side receives the acceptance application form, it automatically generates a purchase acceptance form;

[0070] After the purchase acceptance document is automatically submitted for review in the cloud, the supplier can query the acceptance document and perform purchase reconciliation based on the summary of accepted orders;

[0071] After the management side confirms the reconciliation results, the supplier side issues the invoice, and the cloud side signs for the invoice, so that the management side can generate the payable document and complete the payment process.

[0072] In some embodiments, during the purchase reconciliation process, the supplier side includes: the supplier side can send the information of the collaborative receipt to be invoiced to the supplier; the supplier pre-invoices based on the information of the received collaborative receipt, and feeds back the pre-invoice information to the supplier side, wherein the pre-invoice information is an electronic file generated in the bill format; the supplier side reviews the pre-invoice information fed back by the supplier, and sends the review result to the supplier, including the steps: the supplier side compares the pre-invoice information fed back by the supplier with the information of the collaborative receipt; if the comparison result is consistent, the invoice confirmation information is sent to the supplier, and the management side performs reconciliation confirmation at the same time; if the comparison result is inconsistent, the pre-invoice information is corrected, and the corrected pre-invoice information and invoice confirmation information are sent to the supplier; the supplier issues an invoice based on the received review result and generates an electronic invoice format file, and sends the electronic invoice format file to the supplier side, and the management side performs reconciliation confirmation; wherein, the electronic invoice format file is the same as the electronic invoice format or the same as the paper invoice format but without a signature, which is used to verify the authenticity of the bill and compare the consistency of information.

[0073] (4) After the payment application form in the cost control system is approved and paid, it is transmitted to the management end through the interface and automatically linked to the purchase contracts associated with the upstream documents. After that, the payment application query can be viewed on the cloud, and the supplier end can receive the payment notification.

[0074] (5) When the management side receives the payment application form after approval and payment, the payment application form will automatically generate a payment order. The payment query can then be viewed on the cloud, and the supplier side can conduct a payment query.

[0075] Furthermore, the SRM system also needs to collaborate with other systems within the enterprise organization, such as the human resources system, OA system, financial system, contract system module approval, cost control system, HR system, etc.

[0076] In some embodiments, A. The SRM system can collaborate with the cost control system through the cost control interface to enable the SRM system to connect with the supplier library of the cost control system through the cost control interface to implement the procurement contract execution process.

[0077] The process overview of the SRM and fee control interface is as follows:

[0078] (1) Supplier Addition: When a supplier is added, the supplier addition interface is directly called to perform a search and name verification with the supplier database of the cost control system. If the supplier already exists, the supplier code is directly returned. If not, a new supplier is directly added. Specifically, the SRM system reviews the received request for adding a new supplier. When the review is passed, the supplier addition interface is called when the supplier is added. The name is searched and verified with the supplier database of the cost control system. If the supplier already exists, the supplier code is directly returned to the SRM system. If not, a new supplier is added.

[0079] (2) Procurement contract execution: After the procurement contract in the cost control system is approved, it is transferred to the SRM "Procurement Contract" through the interface and automatically linked to the upstream document signing order. Contract changes are initiated from the cost control system. After the procurement supplementary contract is approved, it is transferred to the SRM system "Procurement Contract Change Order" and the source procurement contract is updated. The payment application is initiated from the cost control system and then reviewed and paid. It is transferred to the SRM system "Payment Application Form" and automatically linked to the upstream document procurement contract, and the payment order is automatically generated. Specifically, the OA system sends the procurement application to the SRM system through the interface. After executing the sourcing and procurement process, the SRM system generates a procurement result report (and signing order) and automatically links it with the approved procurement contract transferred from the cost control system.

[0080] When a contract requires changes or additions, the cost control system initiates and reviews it, then transmits it to the SRM system via an interface. The SRM system generates a purchase contract change order and automatically updates the source purchase contract. Simultaneously, the cost control system initiates a payment request, approves the payment, and transmits it to the SRM system via an interface. The cost control system transmits the payment request to the SRM system, automatically links it to upstream documents, and automatically generates a payment order.

[0081] B. The SRM system collaborates with the OA system through a single sign-on interface to enable login and to-do processing. Furthermore, the SRM system collaborates with the OA system through a business document interface to process purchase requisitions, purchase execution data, and authorized purchase requests. To-do processing can include adding to-do items, deleting to-do items, and approving to-do items.

[0082] Among them, the OA system calls the interface to log in to SRM; when the SRM system generates a to-do list, it is passed to the OA system through the interface; the approval scenario is to enter the SRM system through OA for approval. After the approval is completed, the to-do list in the OA system will be converted to completed through the interface and the to-do list message will be deleted; the purchase demand form created by the OA system is passed to the SRM system through the interface to generate a purchase application form after approval; the purchase execution data in the SRM system is updated to the OA system through the interface; the authorized purchase demand form in the OA system is passed to the SRM through the interface to generate a purchase application form after review; the purchase execution data in the SRM system is updated to the OA system through the interface; the purchase application form is passed to the SRM system through the interface; the supplier information in the SRM system is queried through the interface.

[0083] C. The SRM system collaborates with the HR system through the HR interface to realize enterprise organizational information and capture data at the bottom of the process approval process to perform matrix approval according to the HR organizational structure information.

[0084] Among them, the HR system transmits the enterprise's organizational information changes to SRM through the interface; the HR system also transmits the information to SRM through the interface when there are employee changes.

[0085] In some embodiments, in terms of procurement progress visualization, the progress display interface may include seven main node identifiers. When a main node identifier is lit, it indicates that the corresponding link of the node has been completed. Between the latest lit main node identifier (i.e., the currently lit main node identifier) ​​and its nearest unlit main node identifier (the main node identifier after the currently lit main node identifier in the process sequence), multiple sub-node identifiers are set. The ratio of the multiple sub-node identifiers to be lit is used to indicate the execution progress between the two main nodes.

[0086] When the nearest unlit master node identifier is lit, multiple sub-node identifiers between the two are hidden, and multiple sub-node identifiers between the current latest lit master node identifier and its nearest unlit master node identifier are displayed. The initial state of the multiple sub-nodes is unlit.

[0087] The lighting principles of subnodes include:

[0088] 1. The latest master node identifier that is lit up has been lit up for a preset time interval, wherein the time when the latest master node identifier is lit up is determined based on the timestamp in the synchronization data;

[0089] 2. Receive progress indication data sent by other systems; other systems can be OA systems, HR systems, and cost control systems, etc.

[0090] 3. When the time conflicts with the progress data, the progress data shall prevail.

[0091] The progress data may include to-do items from other systems, for example, to-do items from a cost control system.

[0092] Among them, the preset time interval can be estimated based on project data or be a default value. For example, the total time between the main nodes can be estimated and the total time can be divided into multiple parts, where the lighting time interval of the first sub-node is smaller than the lighting time interval of the second sub-node.

[0093] In some embodiments, an active query strategy is added to the synchronization strategy:

[0094] For example, when progress indication data sent by other systems is received or synchronization data is not received for a preset period of time, a latest status query request is sent to the SRM system.

[0095] Corresponding to the above method, the embodiment of the present application also provides a procurement data processing device, such as Figure 3 As shown, the device includes:

[0096] The acquisition unit 310 is configured to acquire the synchronization data of the target purchase requisition from the SRM system after the OA system accepts the request to view the target purchase requisition. When the SRM system generates the synchronization data at the synchronization node, the synchronization data is sent to the OA system. The synchronization data is used to indicate the stage identifier of each procurement stage.

[0097] The generating unit 320 is configured to generate a progress display interface based on the current progress data corresponding to the synchronization data.

[0098] The functions of each functional unit of the procurement data processing device provided in the above embodiments of the present application can be realized through the above method steps. Therefore, the specific working process and beneficial effects of each unit in the procurement data processing device provided in the embodiments of the present application will not be repeated here.

[0099] The present application also provides an electronic device, such as Figure 4 As shown, it includes a processor 410 , a communication interface 420 , a memory 430 and a communication bus 440 , wherein the processor 410 , the communication interface 420 , and the memory 430 communicate with each other via the communication bus 440 .

[0100] Memory 430, for storing computer programs;

[0101] The processor 410 is configured to execute the program stored in the memory 430 by performing the following steps:

[0102] After the OA system receives a request to view the target purchase demand form, it obtains the synchronization data of the target purchase demand form from the SRM system; wherein, after the SRM system generates the synchronization data when reaching the synchronization node, it sends the synchronization data to the OA system, and the synchronization data is used to indicate the stage identifier of each procurement stage;

[0103] A progress display interface is generated based on the current progress data corresponding to the synchronization data.

[0104] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not mean that there is only one bus or only one type of bus.

[0105] The communication interface is used for communication between the above electronic device and other devices.

[0106] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage. Alternatively, the memory may be at least one storage device located away from the processor.

[0107] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.

[0108] The implementation methods and beneficial effects of the various components of the electronic device in the above embodiments to solve the problems can be found in Figure 1 The various steps in the embodiment shown are implemented, therefore, the specific working process and beneficial effects of the electronic device provided by the embodiment of the present application are not repeated here.

[0109] In another embodiment provided in the present application, a computer-readable storage medium is also provided, in which instructions are stored. When the computer-readable storage medium is run on a computer, the computer executes the procurement data processing method described in any one of the above embodiments.

[0110] In another embodiment provided by the present application, a computer program product containing instructions is also provided, which, when executed on a computer, enables the computer to execute the procurement data processing method described in any one of the above embodiments.

[0111] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the embodiments of the present application can be implemented in the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the embodiments of the present application can be implemented in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0112] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0113] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0114] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0115] Although preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they become aware of the basic creative concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0116] Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims and their equivalents, the embodiments of the present application are also intended to include these modifications and variations.

Claims

1. A procurement data processing method, characterized in that: Applied to a network architecture including an OA system and an SRM system, the method includes: After the OA system receives a request to view the target purchase demand form, it obtains the synchronization data of the target purchase demand form from the SRM system; wherein, after the SRM system generates the synchronization data when reaching the synchronization node, it sends the synchronization data to the OA system, and the synchronization data is used to indicate the stage identifier of each procurement stage; Generate a progress display interface based on the current progress data corresponding to the synchronization data; The progress display interface includes seven procurement stages: demand stage, sourcing and project establishment stage, procurement stage, result approval stage, contract stage, performance stage, and settlement stage. Each of the seven procurement stages corresponds to a stage identifier. The progress display interface also includes seven main node identifiers, which correspond one to one with the seven procurement stages. If a main node identifier is lit, it indicates that the procurement stage corresponding to the main node identifier has been completed, and multiple sub-node identifiers are set between the currently lit main node identifier and its nearest unlit main node identifier, and the ratio in which the multiple sub-node identifiers are lit is used to indicate the execution progress between the corresponding two main node identifiers. The nearest unlit main node identifier refers to the main node identifier that is adjacent to the currently lit main node identifier in the execution order of the seven procurement stages. When the nearest unlit main node identifier is lit, the multiple sub-node identifiers between the nearest lit main node identifier and the currently lit main node identifier are hidden, and the nearest lit main node identifier is determined as the new currently lit main node identifier, and the multiple sub-node identifiers between the new currently lit main node identifier and its nearest unlit main node identifier are displayed, and the initial state of the multiple sub-node identifiers is an unlit state.

2. The method according to claim 1, wherein Acquire synchronized data of the target purchase requisition from the SRM system, including: After the OA system approves the target purchase demand form, it is synchronized to the SRM system through the interface, and then the seven procurement stages are executed in sequence.

3. The method according to claim 2, wherein The method further comprises: After the OA system accepts the request to view the target purchase demand change order and approves the target purchase demand change order, the target purchase demand change order is synchronized to the SRM system through the interface, and the target purchase demand order is generated. Then, the seven procurement stages are executed in sequence. After the OA system accepts the request to view the authorized purchase order and approves the authorized purchase order, it will be synchronized to the purchase requisition in the SRM system through the interface, and the authorization link will be included; The purchase requisition with authorization link will be automatically updated to a purchase requisition, and the execution progress will be updated. After that, the execution data of the purchase requisition will be automatically synchronized to the OA system through the interface.

4. The method according to claim 1, wherein The SRM system includes a management end, a cloud end, and a supplier end; the synchronization data is synchronized by the management end, and the management end and the supplier end collaborate through the cloud end.

5. The method according to claim 4, wherein The method further comprises: The management side determines the purchase order based on the purchase contract; After reviewing the purchase order, the cloud automatically generates collaborative purchase orders corresponding to non-framework contracts and collaborative purchase orders corresponding to framework contracts, and sends them to the supplier. The supplier side allows suppliers to review and confirm collaborative purchase orders corresponding to non-framework contracts, supplement collaborative purchase orders corresponding to framework contracts, maintain order materials, and send the supplemented purchase orders to the cloud for confirmation; After receiving the changed purchase order, the management end changes the purchase contract and obtains a purchase order change document; After reviewing the purchase order change order, the cloud automatically generates a collaborative change order and sends it to the supplier. The supplier side allows suppliers to review and confirm collaborative change orders, and generate acceptance application forms based on the confirmed collaborative purchase orders and collaborative change orders; After the cloud confirms the acceptance application form, it is sent to the management end; After the management side receives the acceptance application form, it automatically generates a purchase acceptance form; After the purchase acceptance document is automatically submitted for review in the cloud, the supplier can query the acceptance document and initiate reconciliation based on the summary of accepted orders; After the management confirms the reconciliation results, the supplier issues the invoice, and the cloud signs for the invoice so that the management can generate the payable document and complete the payment process.

6. The method according to claim 1, wherein The SRM system collaborates with the expense control system through the expense control interface to connect the SRM system with the supplier database of the expense control system through the expense control interface to implement the procurement contract execution process; The SRM system collaborates with the OA system through a single sign-on interface to enable login and to-do processing; The SRM system collaborates with the OA system through the business document interface to process purchase demand sheets, purchase execution data, and authorized purchase requirements; The SRM system collaborates with the HR system through the HR interface to achieve the transmission of the company's organizational information and supplier information.

7. A procurement data processing device, characterized in that: Applied to a network architecture including an OA system and an SRM system, the device includes: an acquisition unit, configured to acquire synchronization data of the target procurement requisition from the SRM system after the OA system accepts a request to view the target procurement requisition; wherein, after the SRM system generates the synchronization data when reaching a synchronization node, the synchronization data is sent to the OA system, and the synchronization data is used to indicate a stage identifier of each procurement stage; A generating unit, configured to generate a progress display interface based on current progress data corresponding to the synchronization data; Among them, the progress display interface includes seven procurement stages, namely, demand stage, sourcing and project establishment stage, bidding and procurement stage, result approval stage, contract stage, performance stage and settlement stage, and each of the seven procurement stages corresponds to a stage identifier; the progress display interface also includes seven main node identifiers, and the seven main node identifiers correspond to the seven procurement stages one by one; if the main node identifier is lit, it means that the procurement stage corresponding to the main node identifier has been completed, and a plurality of sub-node identifiers are set between the currently lit main node identifier and its nearest unlit main node identifier, and the ratio of the lit sub-node identifiers is used to indicate the difference between the corresponding two main node identifiers. the execution progress between the two stages; the nearest unlit master node identifier refers to the master node identifier that is adjacent to the currently lit master node identifier according to the execution order of the seven procurement stages; when the nearest unlit master node identifier is lit, the multiple sub-node identifiers between the nearest lit master node identifier and the currently lit master node identifier are hidden, and the nearest lit master node identifier is determined as the new currently lit master node identifier, and the multiple sub-node identifiers between the new currently lit master node identifier and the nearest unlit master node identifier are displayed, and the initial state of the multiple sub-node identifiers is the unlit state.

8. An electronic device, characterized in that: The electronic device includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory for storing computer programs; A processor, configured to implement the method according to any one of claims 1 to 6 when executing a program stored in a memory.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images