A manufacturing material management and control method and system based on document driving and cross-department balancing

Abstract

The application discloses a manufacturing material management and control method and system based on document driving and cross-department balance, relates to the technical field of ERP system application and manufacturing material management and control, and comprises the following steps: creating / submitting permission and auditing / confirming permission of the same type of document are respectively granted to different department roles, and the system prohibits the same user from simultaneously holding the two types of permissions; a posting confirmation operation entrance of a material receiving and storing business is logically associated with a document approval state and a department mutual exclusion check result of a document maker and an operator; four control nodes of purchase warehousing, material taking, product warehousing and sales warehousing are configured, cross-department two-way balance is realized through permission separation of a document initiation department and a physical execution department, and a closed-loop control system is formed. The application does not depend on a specific ERP system brand or automatic hardware equipment, has low implementation cost, is suitable for a wide range of applications, and can reduce the inventory difference rate of a manufacturing enterprise from 15%-48% to below 1%.

Description

Technical Field

[0001] This invention relates to the fields of ERP system application and manufacturing material control technology. More specifically, this invention relates to a manufacturing material control method and system based on document-driven and cross-departmental checks and balances. Background Technology

[0002] In traditional manufacturing operations management, ERP systems have become the core tool for enterprise resource allocation, and the accuracy of inventory data is a fundamental prerequisite for the normal operation of ERP systems. However, many enterprises, despite deploying fully functional ERP systems, still commonly face the dilemma of "the system shows that the goods are available, but they cannot be found in the warehouse," a discrepancy between inventory records and actual stock. The root cause is that ERP systems themselves only provide data recording and calculation functions and lack process constraint mechanisms to ensure data accuracy. When business operations bypass the system or deviate from standards, the system cannot automatically correct these deviations.

[0003] In existing technologies, the following prominent problems exist in material control in traditional manufacturing: Discrepancies between inventory records and actual stock are widespread. Inventory data in ERP systems is fundamental information for business decisions such as procurement planning, production scheduling, and sales commitments. Distorted inventory data directly leads to blind purchasing or production line stoppages due to material shortages, thereby affecting order delivery and cost accounting. According to research, the inventory discrepancy rate of many traditional manufacturing enterprises reaches 15%-48%, severely restricting operational efficiency.

[0004] The business process lacks standardization. Warehouse material receiving, issuing, and storage operations lack unified standards; the inbound and outbound procedures are poorly defined; there are no standardized document formats; there is a lack of clear approval and signature levels; and a mandatory constraint mechanism of "documents first, then operations" has not been established. Operators perform material receiving and issuing based on no documents, verbal instructions, or retroactive documentation, resulting in a long-term disconnect between system data and physical inventory.

[0005] A lack of cross-departmental checks and balances exists. In actual operations, procurement, production, and warehousing departments operate independently, lacking mutual supervision and checks and balances at the process level. Typical violations include: procurement personnel directly confirming warehousing without warehouse inspection; production teams verbally instructing warehouse staff to issue materials or retrieving materials without system documentation; and placing finished products into the warehouse directly after production completion without reporting the work done in the system. These behaviors lead to a continuous accumulation of discrepancies between system data and actual inventory.

[0006] Data entry delays and human errors. Data inconsistencies frequently occur due to human factors such as data entry errors, improper system parameter configurations, and operational omissions. Typical manifestations include: the ERP system showing zero inventory when the actual goods are still in stock, or the system showing inventory when the actual goods are missing, severely impacting the timeliness and accuracy of management decisions.

[0007] Currently, mainstream ERP and WMS systems on the market focus on the implementation of functional modules and the design of the underlying technical architecture, without built-in process constraint mechanisms to ensure data authenticity. Existing material control-related technical solutions are mostly automation solutions for specific scenarios, with high technical barriers, high deployment costs, and high requirements for hardware and personnel skills, making it difficult to promote and apply them on a large scale in traditional manufacturing enterprises.

[0008] In summary, existing technologies share the following common shortcomings: they lack a material control method that is not dependent on a specific system brand or automated hardware, and can be implemented simply by refactoring the ERP system's own permission model and document processes. Therefore, this paper proposes a manufacturing material control method and system based on document-driven and cross-departmental checks and balances to address the above issues. Summary of the Invention

[0009] To overcome the aforementioned deficiencies of the prior art, embodiments of the present invention provide a manufacturing material control method and system based on document-driven and cross-departmental checks and balances, in order to solve the problem that the permission management of existing ERP systems only divides roles and lacks the technical constraints of mandatory separation and mutual exclusion of permissions between "document initiator" and "physical executor", which leads to business operations being able to bypass system supervision and causing long-term discrepancies between inventory records and actual inventory.

[0010] To address the aforementioned technical problems, this invention provides a manufacturing material control method based on document-driven and permission-exclusive mechanisms, applied to an ERP system. The ERP system includes a permission management module and a document management module. The method includes the following steps: Step S1: In the permission management module, the creation / submission operation permissions and the review confirmation / posting operation permissions of the same type of document are granted to different department roles, and the system prohibits the same user from holding the above two types of permissions at the same time; In the document management module, the posting confirmation operation entry of material receipt, dispatch and storage business is logically associated with the approval validity status of the current operation document and the mutual exclusion verification result between the current operation user and the department of the document creator. Step S2: Configure the purchase receipt control node, granting the purchase receipt creation permission to the purchasing department role and the receipt confirmation permission to the warehouse management department role, with the two being mutually exclusive; set the purchase receipt to be generated by the purchasing department role based on the approved purchase order through a push-down operation, recording the source purchase order number and locking the material code and quantity fields in the receipt; after the warehouse management role verifies the physical goods against the receipt, the system performs mutual exclusion verification of permissions and document status verification, and the receipt confirmation can only be executed after the verification is passed; Step S3: Configure the material requisition control node. Grant the creation permission for material requisition forms to the production department or PMC role, and the material issuance confirmation permission to the warehouse management department role, with the two being mutually exclusive. Set the material requisition form to be generated by the PMC role based on the issued production task order and BOM through calculation. The requisition form records the required work order number. The warehouse management department issues materials according to the form, and the system recommends the batch to be issued according to the first-in, first-out principle. When the requested quantity exceeds the standard usage in the BOM, an over-requisition approval process is required. If the material code does not match the BOM, posting is prohibited. Step S4: Configure the finished goods receiving control node, granting the production department role or PMC role the permission to create finished goods receiving orders, and granting the warehouse management role the acceptance confirmation permission, with the two being mutually exclusive; set the finished goods receiving order to be generated by the production department role through a push-down operation based on the reported production task order, and record the source production task order number in the receiving order; before receiving, the quality inspection department role must confirm its qualification in the system before the warehouse management role can perform the acceptance confirmation; Step S5: Configure the sales outbound control node, granting the sales department role the permission to create sales outbound orders and the warehouse management department role the permission to confirm outbound orders, with the two being mutually exclusive; set the sales outbound order to be generated by the sales department role through a push-down operation based on the approved sales order, and record the source sales order number in the outbound order; the warehouse management department role picks and verifies the goods according to the order, performs outbound confirmation, and associates and binds the outbound order number with the logistics waybill number in the system by scanning; Step S6: By configuring the separation of permissions between the document initiating department and the physical execution department in the above control nodes, a closed-loop control system is formed in the system, which is driven by document transmission and ensures that the accounts match the actual situation through mutual checks and balances among departments.

[0011] Furthermore, in step S2, the purchasing department performs a push-down operation on the approved purchase order in the system. The system reads the supplier information, material code, specifications, and order quantity from the purchase order, and fills the read fields into the corresponding fields of the newly generated purchase receipt, and sets these fields to an uneditable state. The warehouse management department verifies the material code, specifications, actual quantity received, batch number, and production date item by item on the receipt. After verification, the department performs an inbound confirmation operation in the system. The system then performs mutual exclusion checks on permissions and document status checks in sequence. If the checks pass, the inbound receipt status is updated to "posted" and the inventory ledger is updated. If the physical goods do not match the receipt, the warehouse management department performs a rejection operation in the system, the inbound receipt status is changed to "suspended," and the system sends a discrepancy handling notification to the purchasing department.

[0012] Furthermore, in step S3, the PMC role performs material requirements calculation in the ERP system based on the issued production task order and product BOM to generate a material requisition form. The requisition form specifies the material code, specifications, application quantity, and work order number. The warehouse management department issues materials according to the order. The system queries the inventory ledger for all available batches of the material, sorts them in ascending order by the date of receipt according to the first-in-first-out strategy, and accumulates the inventory quantity of each batch until the requested quantity is met. The system then generates a batch recommendation plan and executes the posting after the warehouse management user confirms the operation. When the quantity requested in the requisition form exceeds the standard usage in the work order BOM, the system marks the requisition form as an over-limit status and automatically routes it to the over-limit material requisition approval process. Material issuance confirmation can only be executed after approval by a role with over-limit approval authority. If the approval is rejected, the status of the requisition form will be changed to approval rejection. When the material code in the requisition form does not match the material code specified in the BOM, the system will prohibit the posting operation of the requisition form during the material code verification process.

[0013] Furthermore, in step S4, the production department role performs a push-down operation in the system based on the reported production task order to generate a finished product warehousing order. Each finished product warehousing order is associated with the corresponding production task order through the source production task order number field. Before being put into storage, the goods pass the quality inspection department's inspection and the inspection results are entered into the system. The status of the storage order is then updated to pending acceptance. The warehouse management department can only perform acceptance confirmation operations on finished goods receipt orders with a status of "pending acceptance". The system sequentially performs mutual exclusion verification of permissions, document status verification and quality inspection status verification. Only after all three verifications pass can the receipt confirmation be completed and the finished goods inventory ledger be updated.

[0014] Furthermore, in step S5, the sales department role generates a sales delivery note by performing a push-down operation in the system based on the approved sales order. The delivery note specifies the customer name, material code, specifications, delivery quantity, and delivery date. After the warehouse management department checks the goods according to the order, it uses barcode scanning to associate and bind the outbound order number with the logistics waybill number in the system, and creates an association record in the outbound order logistics association table; Before posting, the system performs a logistics association verification. Only after verifying the existence of a logistics tracking number association record can the system continue to perform mutual exclusion verification and posting operations. After posting is completed, the finished goods inventory is deducted.

[0015] Furthermore, in the closed-loop control system of step S6, all business documents in the system database are associated with each other through the source document number field: the purchase receipt is associated with the purchase order through the source purchase order number field, the material requisition is associated with the production work order through the demand work order number field, and the production work order is associated with the product BOM, the finished product receipt is associated with the production work order through the source production task number field, the sales delivery is associated with the sales order through the source sales order number field, and each batch record in the inventory ledger is associated with the corresponding receipt through the source document number field; The system provides a full-chain traceability query function, enabling bidirectional traceability from procurement to sales along the aforementioned related fields; At the same time, a cycle of continuous improvement is formed, in which standardized processes ensure consistency between accounts and actual data, consistency between accounts and actual data ensures the accuracy of form data, accurate form data promotes compliant execution of processes, and compliant execution further consolidates the standardized processes.

[0016] Furthermore, the method also includes a supervision and assessment step: setting up supervisory roles in the system, configuring scheduled tasks to periodically scan key business documents for process compliance, data accuracy, and operational timeliness, and generating spot check reports; linking inventory accuracy indicators to the performance assessment of warehouse department roles, and linking daily clearance completion rate indicators to the performance assessment of all business department roles; setting assessment deduction items for the number of violations recorded in the system; configuring permission linkage rules so that when departmental performance assessments fail to meet standards or the number of individual violations exceeds a threshold, the system automatically restricts the corresponding operation permissions, forming a continuous improvement closed loop.

[0017] This invention also provides a manufacturing material control system based on document-driven and permission-exclusive mechanisms, running within an ERP system, comprising: The permission management module is used to grant creation / submission operation permissions and review / confirmation / posting operation permissions for the same type of document to different department roles, and prohibits the same user from holding both types of permissions at the same time; The document management module is used to logically associate the posting confirmation operation entry of material receipt, dispatch and storage business with the approval validity status of the current operation document and the mutual exclusion verification results of the current operation user and the department of the document creator. The procurement and warehousing control module is used to implement process control for the generation of procurement and warehousing orders, locking of key fields, physical verification and acceptance, mutual exclusion of permissions, handling of discrepancies, and confirmation of warehousing. The material requisition and control module has built-in material demand calculation logic, batch recommendation logic, and excess approval workflow control. It is used to realize the process control of material requisition form generation, recommendation of batches to be issued according to the first-in-first-out principle, excess material requisition approval, and material code consistency verification. The finished goods warehousing control module is used to implement process control for the generation of finished goods warehousing orders, quality inspection status verification, mutual exclusion of permissions verification, document status verification, and acceptance confirmation. The sales outbound control module has a built-in logistics tracking number association interface, which is used to realize the process control of sales outbound order push-down, picking verification, forced association binding of logistics tracking numbers, logistics association verification and outbound confirmation. The supervision and assessment module is used to perform random checks on document compliance, statistical analysis of process execution data, and calculation of performance assessment indicators, and automatically restricts corresponding operation permissions based on the assessment results.

[0018] Furthermore, the material requisition control module is further used to: generate material requisition forms based on the issued production task orders and product BOMs; query available batches from the inventory ledger when issuing materials, sort them in ascending order by receipt date according to the first-in-first-out strategy, and sequentially accumulate the inventory quantity of each batch until the requested quantity is met, generating a batch recommendation scheme; when the requested quantity exceeds the BOM standard usage, automatically mark the requisition form as an excess status and route it to the excess material requisition approval process; when the material code is inconsistent with the BOM specification, prohibit the posting operation in the material code verification stage.

[0019] Furthermore, the procurement warehousing control module, material requisition control module, finished goods warehousing control module, and sales outbound control module all automatically write the unique number of the upstream document into the data record of the downstream document, thus constructing an end-to-end data traceability link from the purchase order through material requisition and finished goods warehousing to sales outbound at the system database level; The supervision and assessment module is configured with timed tasks to automatically calculate inventory accuracy, daily clearance completion rate, and number of violations. These indicators are linked to the performance assessment data of the corresponding department roles, and permission linkage rules are configured to automatically restrict the corresponding operation permissions when the department's performance assessment fails to meet the standards or the number of individual violations exceeds the threshold.

[0020] Compared with the prior art, the present invention has the following beneficial effects: Achieving consistency between inventory records and physical inventory: Through strict document-driven and cross-departmental checks and balances processes, all four core business processes—procurement receipt, material requisition, finished goods receipt, and sales shipment—are brought under mandatory system control. This systematically eliminates various irregularities that lead to discrepancies between records and physical inventory, such as operations without documents, verbal instructions, and retroactive document processing. Actual application data shows that the inventory discrepancy rate can be reduced from 15%-48% to less than 1%.

[0021] Establish cross-departmental automatic checks and balances: By separating permissions for the four nodes of procurement warehousing, material requisition, finished goods warehousing, and sales outbound, the permissions for creating documents and confirming physical goods are forcibly granted to different departmental roles. At the system level, this forms mutual supervision and automatic checks and balances between the warehouse and the procurement, production, and sales departments, preventing operational errors and fraud risks from a systemic perspective.

[0022] Improve the standardization of business operations: Standardized processes ensure that each business node operation has a corresponding system document as the basis for execution, and the entire operation process is traceable and traceable, which significantly reduces the data error rate caused by human negligence, and the standardization rate of business operations can approach 100%.

[0023] Ensuring the reliability of financial data: Accurate inventory data provides a reliable data foundation for cost accounting and accounts receivable / payable management, avoids financial statement deviations caused by distorted inventory data, and provides data support for refined cost accounting based on work orders.

[0024] Reduce overall management costs: Replacing additional manual supervision positions with standardized system processes reduces management labor costs; and ensuring accurate procurement through accurate accounting supports reduces inventory backlog and capital occupation.

[0025] Widely applicable and easy to promote: This invention is a control method based on the ERP system's own permission model and document process. It does not depend on a specific ERP system brand or model, nor on automated hardware devices such as barcode scanners, RFID, and AGVs. As long as there are basic document management and permission configuration functions, this method can be implemented. It has the characteristics of low implementation cost and wide applicability. Attached Figure Description

[0026] Figure 1 This is a schematic diagram of the system module composition of the present invention; Figure 2 This is a schematic diagram of the system workflow of the present invention; Figure 3 This is a flowchart of the permission mutual exclusion verification process of the present invention; Figure 4 This is a diagram illustrating the checks and balances relationship in the procurement and warehousing process of this invention. Figure 5 This is a flowchart illustrating the first-in-first-out (FIFO) batch allocation process for material requisition in this invention. Detailed Implementation

[0027] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0028] As attached Figures 1 to 5 The following is a method and system for material control in the manufacturing industry based on document-driven and cross-departmental checks and balances, and its specific implementation details are as follows: In this embodiment of the invention, "ERP system" refers to an enterprise resource planning software system that has functional modules such as procurement management, sales management, inventory management, production management, and quality management, and supports user role division, permission configuration, and document flow.

[0029] The "permission management module" refers to a system function module used to define user roles, assign operation permissions, and perform permission verification when users perform operations.

[0030] The "Document Management Module" refers to the system function module used for the creation, editing, status transition, and field locking control of various types of business documents.

[0031] The "Purchase Inbound Control Module" refers to a system functional module used to control the process of generating purchase inbound orders and confirming inbound receipts.

[0032] The "Material Requisition and Control Module" refers to a system functional module that has built-in material demand calculation logic, batch recommendation logic, and excess approval flow control.

[0033] The "Finished Goods Warehousing Control Module" refers to a system functional module used to control the process of generating finished goods warehousing orders, verifying quality inspection status, and confirming acceptance.

[0034] The "Sales Outbound Control Module" refers to a system function module with a built-in logistics tracking number association interface, used to control the sales outbound order push-down and shipment confirmation process.

[0035] The "Supervision and Assessment Module" refers to the system functional module used for scheduled tasks, data statistics, and report generation.

[0036] Example 1 This embodiment provides a manufacturing material control method based on document-driven and permission-exclusive mechanisms. This method reconstructs the permission model, document flow rules, and process control logic of the ERP system to build a system that includes a permission management module, a document management module, and four core business control modules, thereby achieving mutual checks and balances among multiple departments to ensure consistency between accounts and actual inventory.

[0037] The method includes the following steps: Step S1: Establish the basic principles of material control In the ERP system's access control and document management modules, the principles of unique basis, daily and monthly reconciliation, and separation of authority and responsibility are configured as the institutional foundation for the operation of the entire control method. The specific configuration methods for these three principles are explained below.

[0038] (a) The principle of configuring a single basis In the system's document operation control interface, the forced generation rules are configured for the four types of key business documents.

[0039] Specifically, for purchase receipts, select the option "Must be generated from a purchase order". After this configuration takes effect, the system will hide the "Add" button in the purchase receipt list interface, and warehouse administrators will not be able to create purchase receipts directly.

[0040] For material requisition forms, select the option "Must be generated from production task order". After this configuration takes effect, the warehouse manager will not be able to directly create new material requisition forms.

[0041] For finished goods receipt slips, select the option "Must be generated from production task order". After this configuration takes effect, warehouse staff will no longer be able to directly create finished goods receipt slips.

[0042] For sales delivery orders, select the "Must be generated from sales orders" option. After this configuration takes effect, warehouse administrators will no longer be able to directly create new sales delivery orders.

[0043] The technical effect of the above configuration is that it forcibly binds the execution entry point of material receipt, dispatch, and storage operations to the approval status of upstream documents. When a user attempts to bypass the upstream documents and directly create a new downstream business document, the system refuses the operation and prompts "Please generate it from the upstream document," thus technically eliminating the possibility of operations without a document.

[0044] (ii) Configure the daily clearing and monthly settlement principle In the system's early warning settings interface, a new rule named "Document Delay Entry Early Warning" has been added to automatically monitor the timeliness of business data.

[0045] The rules monitor four types of business documents: purchase receipts, material requisitions, finished goods receipts, and sales delivery orders.

[0046] The monitoring fields for this rule are set to the document creation date and the transaction occurrence date. Each document record is required to include these two date fields. The transaction occurrence date is filled in by the operator on the actual date the transaction occurred, while the document creation date is automatically recorded by the system on the system date when the document was created.

[0047] The trigger condition for this rule is configured as follows: the document creation date is one day or more later than the transaction occurrence date. That is, when the system detects that the document creation date and the transaction occurrence date are not on the same calendar day, and the difference is one day or more, an alert is triggered.

[0048] The rule's execution action is configured as follows: send a system warning message to the supervisory role, and automatically mark the document as "post-entry" in the document query list for subsequent statistics and assessment.

[0049] (III) Principle of Separation of Authority and Responsibility In the system's role management interface, create or edit five business roles and forcibly assign operation permissions according to mutual exclusion rules.

[0050] The core definition of the mutual exclusion rule is: "Create / Edit" permissions and "Post / Audit" permissions for the same type of document must not be granted to the same role. The system automatically intercepts and alerts users when operations violate this rule in the permission allocation interface.

[0051] The specific permission assignments for the five business roles are as follows: The purchasing agent role is granted the authority to create and submit purchase receipts, but not the authority to confirm receipts.

[0052] The production planner role is granted permissions to create and submit material requisition forms and finished goods receipt forms, but not permissions to confirm material issuance or finished goods acceptance.

[0053] The salesperson role is granted permissions to create and submit sales delivery orders, but not to confirm delivery orders.

[0054] The warehouse manager role is granted the authority to perform operations such as confirming receipt, confirming issuance, and confirming delivery after verifying the physical goods based on upstream documents. However, it does not grant the authority to independently create various types of documents.

[0055] The quality inspector role is granted permissions to create inspection forms and enter inspection results, but not permissions to confirm inbound or outbound shipments.

[0056] After the above permission configuration takes effect, when a user attempts to perform an unauthorized operation, the system will refuse access during the permission verification process and display a message saying "You do not have permission to perform this operation".

[0057] Step S2: Configure and execute the procurement receipt control node This step is used to establish a two-way check and balance between the purchasing department and the warehouse management department in the procurement and warehousing process, ensuring that the procurement and warehousing operation must be initiated by the purchasing department and confirmed by the warehouse department.

[0058] (a) Push down to generate a purchase receipt. The user's role is that of a purchasing agent.

[0059] Once the supplier delivers the materials to the factory on the agreed delivery date, the purchasing agent logs into the system, selects the corresponding purchase order with the status "approved" in the purchase order query interface of the purchase management module, and clicks the "Push Down to Issue Inbound Slip" button in the operation bar.

[0060] In response to this pushdown operation, the system background performs the following processing steps: The first step is to read the source purchase order data. The system reads the supplier code and purchase order number from the purchase order master table; and the material code, specifications, and order quantity from the purchase order details table.

[0061] The second step is to create a purchase receipt. The system creates a new record in the main purchase receipt table, automatically generates a receipt number, and sets the status field to "Pending Acceptance". A corresponding detailed record is created in the purchase receipt details table, and the read material code, specifications, and order quantity are filled into the corresponding fields.

[0062] The third step is to lock the key fields. The system sets the edit attributes of the material code, specification model, and order quantity fields to read-only, making them grayed out and uneditable.

[0063] The fourth step is to establish document association. The system enters the unique system number of the source purchase order into the "Source Purchase Order Number" field of the inbound document, thus completing the association and binding between the source document and the target document.

[0064] The fifth step is to record the information of the person who created the order. The system enters the username of the user currently operating the order into the "Creater" field.

[0065] (ii) Physical verification and warehousing confirmation The user's role is warehouse manager.

[0066] After receiving the goods from the supplier, the warehouse manager logs into the system, finds the corresponding purchase receipt with the status "pending acceptance" in the purchase receipt query interface of the warehouse management module, and checks the goods item by item with the receipt.

[0067] The items to be checked include: whether the material code matches the document, whether the specifications and model match the document, whether the physical quantity matches the order quantity in the document, whether the batch number or serial number is clearly identifiable, and whether the production date and expiration date meet the requirements.

[0068] Depending on the verification results, the system enters different processing branches.

[0069] Scenario 1: The physical item matches the invoice perfectly. In the receiving slip editing interface, the warehouse manager fills in the acceptance information. Specifically, this includes: entering the actual quantity received in the "Actual Quantity Received" field, entering the supplier's batch number in the "Batch Number" field, entering the material's production date in the "Production Date" field, entering the expiration date in the "Expiration Date" field, and selecting the system-recommended storage location in the "Storage Location" field.

[0070] After completing the form, the warehouse manager clicks the "Post" button to trigger the receipt confirmation process. The system performs the following verification and processing steps: The first step is to perform a mutual exclusion check on permissions. The system checks whether the current user meets all three of the following conditions: the current user's role is "Warehouse Manager," the current document's creator is not the current user, and the current user and the creator belong to different departments. If all three conditions are met, the check passes, and the system continues with subsequent steps; if any condition is not met, the system displays an error message and aborts the operation.

[0071] The second step is to perform a document status check. The system checks whether the current document's status field value is "Pending Acceptance". If it is "Pending Acceptance", the check passes and the system continues with subsequent steps; if it is another status value, the system displays an error message and aborts the operation.

[0072] The third step is to perform the posting operation. The system updates the status field in the main table of the purchase receipt to "posted", records the poster field as the username of the current user, and records the posting time field as the current system time.

[0073] The fourth step is to update the inventory ledger. The system adds a new record to the inventory ledger table, writing the material code, batch number, storage location, and quantity received into the corresponding fields, writing the current receipt number into the source document number field, and setting the status field to "available".

[0074] Scenario 2: The actual item does not match the document. The warehouse manager clicks the "Reject" button and fills in the details of the discrepancy in the pop-up discrepancy description dialog box, such as "The actual quantity received is 450kg, which does not match the 500kg on the document, and 50kg is missing."

[0075] The system first performs a mutual exclusion check of permissions. After the check passes, the status field of the inbound order is changed to "temporarily suspended", and the difference description filled in by the warehouse manager is written into the rejection reason field of the inbound order.

[0076] Subsequently, the system generates a system message record in the message table, with the recipient role set to "Purchaser," the message title set to "Purchase Receipt Order Returned," the message content including a description of the discrepancy and the associated document number, the sending time recorded as the current system time, and the read status set to "No." After logging into the system, the purchaser can see this system message in the to-do list on the homepage, view the discrepancy details, and communicate with the supplier to resolve the issue.

[0077] Step S3: Configure and execute the material requisition control node This step is used to establish a two-way check and balance between the production department or PMC and the warehouse management department in the material requisition process, and to enforce first-in-first-out batch management and approval control for excessive material requisition.

[0078] (a) Calculate and generate material requisition forms The role is PMC planner.

[0079] When a PMC planner selects a production task order with a status of "issued" in the system and clicks the "Generate Material Requisition Form" button in the operation bar, the system performs the following material requirements calculation.

[0080] The first step is to read the production task order information. The system queries and reads the finished product material code field value and the task quantity field value from the production task order table based on the task order number.

[0081] The second step is to read the BOM table. The system queries the BOM table for all sub-item material records whose parent item material code is the aforementioned finished product material code, and reads the sub-item material code, sub-item name, unit usage, and unit field value for each record.

[0082] The third step is to calculate the quantity to be issued. The system iterates through each record in the BOM query results and performs the following calculation for each record: Quantity to be issued = Unit usage × Number of tasks.

[0083] The fourth step is to generate a material requisition form. The system creates a new record in the main material requisition form table. The requisition form number is automatically generated by the system. The "Requirement Order Number" field contains the source production task order number, the "Preparer" field contains the current user, and the "Status" field is set to "Pending Issuance." Detailed records are created one by one in the material requisition form details table, recording the material code, specifications, quantity due, and unit for each material. The "Requested Quantity" field is filled with the same value as the quantity due by default. The "Quantity Due" field is set to non-editable.

[0084] (ii) Issuance of materials according to orders and batch recommendations The user's role is warehouse manager.

[0085] The warehouse manager opens the requisition form in the system and clicks the "Issue Materials" button to enter the material issuance interface. The system automatically executes the batch recommendation logic.

[0086] First, the system queries the inventory ledger table for all batch records of the material whose status is "available". The query criteria are: the material code field value is equal to the material issued code, the inventory quantity field value is greater than zero, and the status field value is equal to "available".

[0087] Secondly, the system sorts the query results according to a preset outbound batch strategy. In this embodiment, a first-in, first-out (FIFO) strategy is used, that is, the results are sorted in ascending order by the inbound date field, and if the inbound dates are the same, they are sorted in ascending order by batch number.

[0088] It should be noted that the system also supports a first-to-last-out (FTILE) strategy. When an enterprise selects this strategy, the system sorts batches in ascending order by the expiration date field, prioritizing the batch with the closest expiration date. Enterprises can switch between these two strategies in the system settings based on the material characteristics.

[0089] Then, the system calculates the batch allocation plan. Starting from the first record in the sorted results, the system sequentially adds the inventory quantity field value of each batch record until the added value meets the application quantity of the requisition order. If the added value still does not meet the application quantity after iterating through all available batches, the system displays a message "Insufficient inventory, current available inventory total is XX", and the operation is aborted.

[0090] The system will display the recommended batches and their allocated quantities as a suggested solution on the material issuance interface for warehouse staff to confirm. The interface will display the material name, requested quantity, recommended batch number, storage location, and allocated quantity for each batch.

[0091] After verifying that the batch recommended by the system matches the physical location of the goods, the warehouse manager picks the goods according to the system's recommendation and clicks the "Confirm Issuance" button. The system performs a mutual exclusion check to verify that the current user is a warehouse manager and belongs to a different department from the person who created the order. After the check passes, the status of the requisition form is updated to "Posted," and the inventory quantity field value of the corresponding batch record in the inventory ledger is deducted batch by batch.

[0092] (iii) Approval and control of excessive material requisition When a production team needs to requisition materials exceeding the BOM standard quantity due to special circumstances, the warehouse manager modifies the requested quantity field in the requisition form to a value greater than the required quantity. When "Confirm Requisition" is clicked, the system triggers the excess judgment logic.

[0093] The system reads the values ​​of the "Quantity Due" and "Requested Quantity" fields from the requisition details table and determines whether the requested quantity exceeds the "Quantity Due". If the result is true, the system performs the following excess processing operation.

[0094] The first step is to mark the excess status. The system updates the status field in the material requisition form master table to "Excess pending approval".

[0095] The second step is to locate the approver. The system locates the user record of the person who created the current requisition form in the system user table, reads the value of the superior supervisor field, and obtains the user account of the superior supervisor.

[0096] The third step is to generate an approval pending task. The system creates an approval record in the approval pending task table, with the approval type field set to "Approval for Excess Material Requisition", the associated document number set to the current requisition document number, the applicant field set to the current operating user, the approver field set to the found superior user account, and the status field set to "Pending Approval".

[0097] Step 4: Abort the current operation. The system will display a prompt dialog box stating, "The requested quantity exceeds the quantity required by the BOM. This requisition form has been transferred to the over-requisition approval process. Please wait for approval." The material issuance confirmation operation will be suspended.

[0098] After logging into the system, the supervisor can view the approval item in the to-do list and choose to "Approve" or "Reject". If approved, the system will change the requisition form status from "Pending Approval for Excess" to "Pending Issuance", and the warehouse manager can continue to perform the issuance confirmation operation. If rejected, the system will change the requisition form status to "Approval Rejected", and the warehouse manager needs to modify the requested quantity to be within the issuance quantity range and resubmit.

[0099] (iv) Prohibition and control of substitute material requisition After the mutual exclusion of permissions is verified and before the inventory deduction is executed, the system also performs a material code consistency verification.

[0100] The system queries the BOM table for all sub-item material codes corresponding to the finished product code of the production task order, obtaining a result set. Then, the system checks each record in the requisition details to see if all material codes are included in the above result set.

[0101] If a material code is found to be missing from the result set, the system will display a dialog box indicating that "this material code is not in the bill of materials specified in the BOM. Posting is prohibited. Substitute material requisition must be processed through a separate material substitution approval process," and the operation will be suspended. This verification effectively prevents unauthorized substitute material requisitions from a technical standpoint.

[0102] Step S4: Configure and execute the finished goods warehousing control node This step is used to establish a three-way check and balance among the production department, quality inspection department, and warehouse management department in the finished goods warehousing process, and to enforce the "quality inspection first, then warehousing" operational sequence.

[0103] (a) Push down to generate finished goods receipt slip The user's role is production planner.

[0104] After the production team completes its production task, it performs a work reporting operation on the production task order in the system, filling in information such as the quantity completed, the quantity qualified, and the quantity scrapped. After the work reporting is completed, the task order status changes from "issued" to "reported".

[0105] The production planner selects the reported production task order and clicks the "Push Down to Issue Finished Goods Receipt" button in the operation bar. The system backend reads the finished goods material code and qualified quantity of the task order, creates a new record in the finished goods receipt main table, automatically assigns the receipt number to the system, sets the status field to "Pending Inspection," enters the current task order number in the source production task order number field, and enters the current user in the document creator field. The finished goods material code and planned receipt quantity fields are automatically filled in by the system and set to non-editable status.

[0106] (ii) Quality inspection confirmation The user's role is a quality inspector.

[0107] Quality inspectors inspect finished products according to product inspection standards. After inspection, the quality inspector logs into the system, selects the corresponding finished product receiving slip in the "Associated Receiving Slip Number" field of the quality management module's new inspection slip interface, and the system automatically populates the finished product material code.

[0108] The quality inspector enters the measured values ​​and individual judgment results for each inspection item in the inspection sheet details. After all items have been inspected, select "Qualified" in the comprehensive judgment field and click "Save and Review".

[0109] The system performs the following processing: Create a new record in the main inspection form table, write the corresponding warehouse entry number into the associated warehouse entry number field, and write "qualified" into the comprehensive judgment field; automatically update the status field of the corresponding record in the main finished product warehouse entry form table from "pending inspection" to "pending acceptance".

[0110] If the quality inspection results in a "non-compliant" status, the finished product receiving slip will remain in the "pending inspection" status. The warehouse manager will not be able to view or operate the receiving slip, and the batch of finished products will need to be reworked or scrapped by the production department.

[0111] (III) Warehouse Inspection and Confirmation The user's role is warehouse manager.

[0112] After logging into the system, the warehouse manager can only see and select documents with a status of "Pending Acceptance" in the finished goods receipt query interface of the warehouse management module. For documents with a status of "Pending Inspection", the "Post" button in the interface is grayed out and unavailable, which enforces the "quality inspection first, then warehousing" operation sequence at the system level.

[0113] The warehouse clerk verifies the quantity, production batch number, and packaging condition of the finished products against the order. After confirming everything is correct, the clerk clicks the "Post" button. The system performs the following triple verification: The first step is to perform a mutual exclusion check. The system verifies whether the current user is a warehouse administrator and belongs to a different department from the person who created the order. If the check fails, the system displays an error message and aborts the operation.

[0114] The second step is to perform a document status check. The system checks whether the current inbound document's status field value is "Pending Acceptance". If it is not "Pending Acceptance", the system will display an error message and abort the operation.

[0115] The third step is to perform a quality inspection status check. The system queries the comprehensive judgment field value of the corresponding inspection order by associating it with the warehouse entry order number. If it is not "qualified", the system will display a message saying "This warehouse entry order has not yet passed quality inspection confirmation and cannot be accepted" and stop the operation.

[0116] After all three verifications pass, the system will update the status of the inbound order to "posted" and add a new record to the finished goods inventory ledger, writing the finished goods material code, batch number, storage location, inbound quantity and source document number, and setting the status to "available".

[0117] Step S5: Configure and execute the sales outbound control node This step is used to create a two-way check and balance between the sales department and the warehouse management department in the sales outbound business process, and to enforce the association of logistics tracking numbers to achieve shipment traceability.

[0118] (a) Push down to generate a sales delivery order The user's role is that of a salesperson.

[0119] The salesperson selects a sales order with an approved status in the system and clicks the "Issue Sales Outbound Order" button in the operation bar. The system reads the customer name, material code, specifications, order quantity, required delivery date, and sales order number of the sales order, and creates a new record in the main sales outbound order table. The outbound order number is automatically assigned by the system, the status field is set to "Pending Shipment," the source sales order number field is entered with the current sales order number, and the creator field is entered with the current user. The material code, specifications, order quantity, and required delivery date fields are automatically filled in by the system and set to non-editable status.

[0120] (ii) Scanning the connection between shipment and logistics The user's role is warehouse manager.

[0121] The warehouse clerk picks goods from the finished goods warehouse based on the sales order, and arranges for packaging after verifying that the physical goods match the information on the order. In the system's shipping interface, the warehouse clerk enters the actual quantity shipped in the "Actual Quantity Shipped" field.

[0122] Subsequently, the warehouse manager used a barcode scanner to scan the barcodes printed on the sales order and the barcodes on the logistics waybill provided by the logistics company. After the system recognized the sales order number and the logistics waybill number, it created a related record in the sales order logistics association table, writing the sales order number field and the logistics waybill number field to the two scanned barcode values ​​respectively, recording the scanning time field as the current system time, and the operator field as the current user.

[0123] After scanning is complete, the warehouse manager clicks the "Post" button. The system performs the following verification and operations: The first step is to perform a logistics association verification. The system counts the number of records in the outbound order logistics association table whose outbound order number field value is the current outbound order number. If the number of records is zero, it means the logistics waybill number has not been successfully associated, and the system will display a prompt "Please scan the logistics waybill number to complete the association binding," and the operation will be suspended. If the number of records is greater than zero, the verification passes, and subsequent steps continue.

[0124] The second step is to perform a mutual exclusion check on permissions. The system verifies that the current user is a warehouse administrator and belongs to a different department than the person who created the order. If the verification fails, the system displays an error message and aborts the operation.

[0125] The third step is to perform the posting operation. The system updates the status field in the main sales order table to "posted" and records the person who posted the order and the posting time.

[0126] The fourth step is to deduct from the finished goods inventory. The system locates the inventory record with the corresponding finished product code, batch number, and storage location in the finished goods inventory ledger, and subtracts the quantity issued in this shipment from the inventory quantity field value.

[0127] This mandatory tracking number association mechanism enables shipment traceability. In the event of a customer complaint, the system can trace the package by looking up the tracking number from the outbound tracking number, and track the personnel and time of each step of the picking, scanning, and shipping process along the operation log.

[0128] Step S6: Establish an end-to-end data traceability chain After completing the operation of the above four core business nodes, each document in the system database forms an end-to-end data traceability chain through preset association fields.

[0129] The specific data association methods are as follows: The purchase receipt form is linked to the purchase order from which it was generated through the "Source Purchase Order Number" field.

[0130] Material requisition forms are linked to the production task order from which they were generated via the "requirement work order number" field. The production task order is further linked to the corresponding product BOM table.

[0131] The finished goods receipt form is linked to the production task form from which it was generated through the "Source Production Task Number" field.

[0132] The sales order is linked to the sales order from which it was generated through the "Source Sales Order Number" field.

[0133] The sales delivery note is also linked to the corresponding logistics tracking number through the records in the delivery note logistics association table.

[0134] In addition, each batch record in the inventory ledger is linked to the corresponding purchase receipt or finished goods receipt through the "Source Document Number" field. When materials are requisitioned, the system traces the consumption record to the corresponding inventory ledger batch through the batch number field; when goods are sold and shipped, the system also uses the batch number field to trace and link the finished goods shipment and receipt batches.

[0135] The system provides a "full-chain traceability query" function in the report center. When a user enters any document number, the system first identifies the document type based on the document number prefix. If the document is an upstream document, the system searches downwards along the aforementioned related fields to find all downstream documents; conversely, if the document is a downstream document, the system searches upwards along the aforementioned related fields to find all upstream documents. All found documents are displayed in a tree structure in the traceability results interface, enabling two-way traceability from procurement to sales and from raw materials to finished products.

[0136] Step S7: Establish and operate a monitoring and assessment mechanism Configure a monitoring and assessment module in the system to continuously monitor and quantitatively assess the execution of the above-mentioned business nodes, thus forming a closed-loop management system.

[0137] (a) Supervisory positions and scheduled tasks In the system's user management interface, create a separate "Supervisor" role. Grant this role only viewing permissions for all business documents and access to the report center, but do not grant any permissions to create, edit, or post any documents.

[0138] In the warning settings interface, create two scheduled tasks.

[0139] The first item is "Weekly Spot Check Warning for Document Compliance". This task is automatically triggered every Monday at 9:00 AM, scanning all four types of business documents that have been posted from the previous Monday to the previous Sunday.

[0140] The inspection items include: scanning records where the value of the "preparer" field is equal to the value of the "poster" field, marking them as violations; and scanning records where the value of the "preparation date" field differs from the value of the "transaction date" field by one day or more, marking them as retroactively submitted records. Scan results are automatically generated into a report and pushed to the monitoring user.

[0141] The second item is "Daily Clearance Completion Rate Statistics". This task is automatically triggered at 22:00 every calendar day and counts the total number of all documents that should be processed that day, as well as the number of documents that were posted on that day.

[0142] The calculation logic is as follows: Daily clearance completion rate = Number of documents posted on the day ÷ Total number of documents to be processed on the day × 100%. The statistical results are written into the daily clearance completion rate statistics table and pushed to the supervisory users.

[0143] (ii) Performance appraisal reports and access control linkage Create the following three types of statistical reports in the Report Center.

[0144] The monthly inventory accuracy report is based on data from the system's inventory ledger, which is compared with the physical inventory count in the monthly end-of-month inventory count sheet.

[0145] The calculation logic is as follows: Inventory accuracy rate = 1 - (Σ|physical inventory count - system book count| ÷ Σ system book count × 100%).

[0146] This metric is linked to the performance evaluation data of the warehouse department role, with a target value set at greater than or equal to 99.5%.

[0147] The monthly daily completion rate report calculates the monthly average of the daily completion rate data for the current month. This indicator is linked to the performance evaluation data of all business department roles, with a target value set at 100%.

[0148] The monthly statistical report on the number of violations includes data sources such as the number of operation log entries rejected by the system due to the lack of valid upstream documents, the number of documents marked as corrected after the fact, the number of excessive material requisition applications rejected during approval, and the number of operations rejected by the system due to material code verification failures. This indicator is linked to all business department roles and serves as a deduction item in performance evaluations.

[0149] In the performance evaluation linkage settings interface for access control, further configuration of access linkage rules is available. When the warehouse department's inventory accuracy rate falls below the target value for two consecutive months, the system automatically disables the ability of users in that department to create new inbound or outbound documents, retaining only query permissions. When any user accumulates more than three violations in a month, the system automatically disables the user's document posting permission. These permission restrictions are manually restored by the system administrator after rectification and compliance. This forms a continuous improvement closed loop of "problem identification through performance evaluation, automatic permission restriction by the system, restoration after rectification, and further consolidation of process standardization."

[0150] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the technical concept and spirit of the present invention should be included within the scope of protection of the present invention.

Claims

1. A manufacturing material control method based on document-driven and cross-departmental checks and balances, applied to an ERP system, wherein the ERP system includes an access control module and a document management module, characterized in that, Includes the following steps: Step S1: In the permission management module, grant the creation / submission operation permission and the review confirmation / posting operation permission of the same type of document to different department roles, and the system prohibits the same user from holding the above two types of permissions at the same time; In the document management module, the posting confirmation operation entry for material receipt, dispatch and storage business is logically associated with the approval validity status of the current operation document and the mutual exclusion verification result between the current operation user and the department of the document creator. Step S2: Configure the purchase receipt control node, grant the purchase receipt creation permission to the purchase department role and the receipt confirmation permission to the warehouse management department role, with the two being mutually exclusive; The purchase receipt is set to be generated by the purchasing department role through a push operation based on the approved purchase order. The source purchase order number is recorded in the receipt and the material code field and quantity field are locked. After the warehouse management department verifies the physical goods against the order, the system performs mutual exclusion verification of permissions and document status verification. Only after the verification is passed can the warehouse entry confirmation be executed. Step S3: Configure the material requisition control node, grant the creation permission of material requisition forms to the production department role or PMC role, and grant the material issuance confirmation permission to the warehouse management department role, with the two being mutually exclusive; The material requisition form is set to be generated by the PMC role based on the issued production task order and BOM through calculation. The requisition form records the required work order number. The warehouse management department issues materials according to orders, and the system recommends the batches to be issued based on the first-in, first-out principle. When the requested quantity exceeds the standard usage in the BOM, an excess material requisition approval process must be followed. Posting is prohibited if the material code does not match the BOM. Step S4: Configure the finished goods warehousing control node, grant the production department role or PMC role the permission to create finished goods warehousing orders, and grant the warehouse management department role the acceptance confirmation permission, with the two being mutually exclusive; The finished goods receipt form is set to be generated by the production department role through a push operation based on the reported production task order, and the source production task order number is recorded in the receipt form; Before the goods are put into storage, the quality inspection department must confirm their compliance in the system before the warehouse management department can perform the acceptance confirmation. Step S5: Configure the sales outbound control node, granting the sales department role the permission to create sales outbound orders and the warehouse management department role the permission to confirm outbound orders, with the two being mutually exclusive; The sales delivery order is set to be generated by the sales department role through a push operation based on the approved sales order, and the source sales order number is recorded in the delivery order; After the warehouse management department checks the order and confirms the outbound shipment, it links and binds the outbound order number with the logistics waybill number in the system by scanning. Step S6: By configuring the separation of permissions between the document initiating department and the physical execution department in the above control nodes, a closed-loop control system is formed in the system, which is driven by document transmission and ensures that the accounts match the actual situation through mutual checks and balances among departments.

2. The manufacturing material control method based on document-driven and cross-departmental checks and balances according to claim 1, characterized in that, Step S2 includes: In the system, the purchasing department performs a push-down operation on the approved purchase order. The system reads the supplier information, material code, specifications, and order quantity from the purchase order, and fills the corresponding fields in the newly generated purchase receipt into the corresponding fields, and sets these fields to an uneditable state. The warehouse management department verifies the material code, specifications, actual quantity received, batch number, and production date item by item on the receipt. After verification, the department performs the receiving confirmation operation in the system. The system then performs mutual exclusion verification of permissions and document status verification in sequence. After the verification is successful, the receiving order status is updated to "posted" and the inventory ledger is updated. When the physical goods do not match the documents, the warehouse management department will refuse to accept the goods in the system, the status of the receiving order will be changed to pending, and the system will send a discrepancy handling notification to the purchasing department.

3. The manufacturing material control method based on document-driven and cross-departmental checks and balances according to claim 1, characterized in that, Step S3 includes: Based on the issued production task order and product BOM, the PMC role performs material requirements calculation in the ERP system to generate a material requisition form. The requisition form specifies the material code, specifications, quantity requested, and work order number. The warehouse management department issues materials according to the order. The system queries the inventory ledger for all available batches of the material, sorts them in ascending order by the date of receipt according to the first-in-first-out strategy, and accumulates the inventory quantity of each batch until the requested quantity is met. The system then generates a batch recommendation plan and executes the posting after the warehouse management user confirms the operation. When the quantity requested in the requisition form exceeds the standard usage in the work order BOM, the system marks the requisition form as an over-limit status and automatically routes it to the over-limit material requisition approval process. Material issuance confirmation can only be executed after approval by a role with over-limit approval authority. If the approval is rejected, the status of the requisition form will be changed to approval rejection. When the material code in the requisition form does not match the material code specified in the BOM, the system will prohibit the posting operation of the requisition form during the material code verification process.

4. The manufacturing material control method based on document-driven and cross-departmental checks and balances according to claim 1, characterized in that, Step S4 includes: The production department generates finished goods receipt slips by performing a push-down operation on the reported production task orders in the system. Each finished goods receipt slip is associated with the corresponding production task order through the source production task order number field. Before being put into storage, the goods pass the quality inspection department's inspection and the inspection results are entered into the system. The status of the storage order is then updated to pending acceptance. The warehouse management department can only perform acceptance confirmation operations on finished goods receipt orders with a status of "pending acceptance". The system sequentially performs mutual exclusion verification of permissions, document status verification and quality inspection status verification. Only after all three verifications pass can the receipt confirmation be completed and the finished goods inventory ledger be updated.

5. The manufacturing material control method based on document-driven and cross-departmental checks and balances according to claim 1, characterized in that, Step S5 includes: Based on the approved sales orders, the sales department generates a sales delivery note by performing a push-down operation in the system. The delivery note specifies the customer name, material code, specifications, quantity, and delivery date. After the warehouse management department checks the goods according to the order, it uses barcode scanning to associate and bind the outbound order number with the logistics waybill number in the system, and creates an association record in the outbound order logistics association table; Before posting, the system performs a logistics association verification. Only after verifying the existence of a logistics tracking number association record can the system continue to perform mutual exclusion verification and posting operations. After posting is completed, the finished goods inventory is deducted.

6. The manufacturing material control method based on document-driven and cross-departmental checks and balances according to claim 1, characterized in that, In the closed-loop control system of step S6: All business documents in the system database are linked through the source document number field: the purchase receipt is linked to the purchase order through the source purchase order number field; the material requisition is linked to the production work order through the demand work order number field, and the production work order is linked to the product BOM; the finished goods receipt is linked to the production work order through the source production task order number field; the sales delivery is linked to the sales order through the source sales order number field; and each batch record in the inventory ledger is linked to the corresponding receipt through the source document number field. The system provides a full-chain traceability query function, enabling bidirectional traceability from procurement to sales along the aforementioned related fields; At the same time, a cycle of continuous improvement is formed, in which standardized processes ensure consistency between accounts and actual data, consistency between accounts and actual data ensures the accuracy of form data, accurate form data promotes compliant execution of processes, and compliant execution further consolidates the standardized processes.

7. The manufacturing material control method based on document-driven and cross-departmental checks and balances according to any one of claims 1 to 6, characterized in that, It also includes monitoring and assessment steps: Set up supervisory roles in the system, configure scheduled tasks to periodically scan key business documents to ensure process compliance, data accuracy, and operational timeliness, and generate spot check reports; Link the inventory accuracy rate metric to the performance evaluation of warehouse department roles, and link the daily clearance completion rate metric to the performance evaluation of all business department roles; Set performance evaluation deduction items for the number of violations recorded in the system; Configure permission linkage rules so that when a department's performance evaluation fails to meet the standards or an individual's number of violations exceeds the threshold, the system will automatically restrict the corresponding operation permissions, forming a closed loop for continuous improvement.

8. A manufacturing material control system based on document-driven and cross-departmental checks and balances, running in an ERP system, characterized in that... include: The access control module is used to grant creation / submission permissions and review / confirmation / posting permissions for the same type of document to different department roles, and prohibits the same user from holding both types of permissions at the same time; The document management module is used to logically associate the posting confirmation operation entry of material receipt, dispatch and storage business with the approval validity status of the current operation document and the mutual exclusion verification results of the current operation user and the department of the document creator. The procurement and warehousing control module is used to implement process control for the generation of procurement and warehousing orders, locking of key fields, physical verification and acceptance, mutual exclusion of permissions, handling of discrepancies, and confirmation of warehousing. The material requisition and control module has built-in material demand calculation logic, batch recommendation logic, and excess approval workflow control. It is used to realize the process control of material requisition form generation, recommendation of batches to be issued according to the first-in-first-out principle, excess material requisition approval, and material code consistency verification. The finished goods warehousing control module is used to implement process control for the generation of finished goods warehousing orders, quality inspection status verification, mutual exclusion of permissions verification, document status verification, and acceptance confirmation. The sales outbound control module has a built-in logistics tracking number association interface, which is used to realize the process control of sales outbound order push-down, picking verification, forced association binding of logistics tracking numbers, logistics association verification and outbound confirmation. The supervision and assessment module is used to perform random checks on document compliance, statistical analysis of process execution data, and calculation of performance assessment indicators, and automatically restricts corresponding operation permissions based on the assessment results.

9. The manufacturing material control system based on document-driven and cross-departmental checks and balances according to claim 8, characterized in that, The material requisition and control module is further used for: Material requisition forms are generated based on the issued production task orders and product BOMs. When issuing materials, query the available batches from the inventory ledger, sort them in ascending order by the date of receipt according to the first-in-first-out strategy, and accumulate the inventory quantity of each batch until the requested quantity is met, and generate a batch recommendation plan. When the requested quantity exceeds the standard usage in the BOM, the requisition form will be automatically marked as exceeding the limit and routed to the excess material requisition approval process. When the material code is inconsistent with the BOM specification, the posting operation will be prohibited in the material code verification stage.

10. The manufacturing material control system based on document-driven and cross-departmental checks and balances according to claim 8 or 9, characterized in that: The procurement warehousing control module, material requisition control module, finished goods warehousing control module, and sales outbound control module all automatically write the unique number of the upstream document into the data record of the downstream document, thus constructing an end-to-end data traceability link from the purchase order through material requisition and finished goods warehousing to sales outbound at the system database level. The supervision and assessment module is configured with timed tasks to automatically calculate inventory accuracy, daily clearance completion rate, and number of violations. These indicators are linked to the performance assessment data of the corresponding department roles, and permission linkage rules are configured to automatically restrict the corresponding operation permissions when the department's performance assessment fails to meet the standards or the number of individual violations exceeds the threshold.

Images