Stock requests

Stock Requests is the work record for put-away, movement and issue activity. It identifies the request number, subject, owner, organization, item, location, counterparty, requested units and due date. Its status and revision tell the team which version is awaiting review and which work has been executed. The Inventory Coordinator prepares the request; the Inventory Reviewer reads the request when deciding a related submitted put-away plan.

• Ownership. Inventory Coordinator handles the decisions and records in this area; keep the named owner visible on each request.
• References. Follow the organization, item, location and parent request links when checking related work.
• Evidence. Read the current status and revision together with the related decision or effect before a handoff.

The request is the common parent for Put Away Plans, Review Decisions, Record Attachments, Stock Movements and Operation Receipts. Its number helps staff discuss the same case, but the relationships carry the durable link. During migration, load the organization, team, item and locations first so every imported request can point to its actual references. Rehearse a request linked to both an approved and a rejected put-away plan.

Agree how record numbers are assigned and when an owner may change the requested units. A request that has entered Review should have a clear correction path so a related plan is not decided against obsolete request details. Decide how the counterparty location is used for movements between locations. The required date should reflect the actual operating commitment, not a default entered simply to complete a form.

Take a request to move a lot-tracked item from one location to another. The Inventory Coordinator selects the organization, item, current location and counterparty location and enters the quantity and required date. The Inventory Reviewer checks the revision and supporting evidence when a related put-away plan is submitted. If the quantity changes after submission, check the changed request against the submitted plan before its decision. For any existing movement, compare its parent request and item with the case.

• My stock requests — See assigned work and due dates together.
• Requests for review — Find requests whose current status calls for a decision.
• Open request board — Compare draft, review and approved work by owner.

Follow the operating process and implementation steps with a real request. Confirm that the item, location and organization references still point to the intended records after each handoff. Use the data model when preparing migration mappings, and bring the team’s actual codes and review authority to the rehearsal.