WMS Fine Chemical — Warehouse business map

Fine Chemical (FC) · Module WMS · v2.1 · 09/10/2026 · Module overview — one box per business process, click a box to open the detail flow

Warehouse processes and module interactions

WMS Fine Chemical — Warehouse business map by module · WMS at the centreGeneral SetupPurchaseSalesMES PackageLabels · BarcodeReceiptStock ·internal movesIssueApproval · closing· stock countMonitoring ·stock alertsWMSPO → Stock In Requestprint labels · scanMOR → Stock Outmaterial issuesurplus materialStock Out note → vendorStock Out Curing noteSO approved → Product Income RequestA + A- ready for receiptprint labels · scanSlip APPROVED → stock +FG stock +Restock → stock +Pallet BCSlip APPROVED → print new labelsSlip APPROVED → stock −FG stock −ShipmentFI CompletedSO / Shipping Plan → DOto customerG/D Slip APPROVEDApprove / Cancel → stock ±closed period → blocks the screens' Slipsapproved note → stock ±▣ Storage LocationWarehouse · Location (Bin)Item · UOMGeneral Setup provides the master data every warehouse screen uses: warehouse, Location (Bin), Item, UOM. Input: master data maintained by the administrator. Result: every Request / Slip picks warehouse, Bin and Item from these lists. System: Bin is mandatory on every Slip line; Grade is mandatory on every receipt line. Open: the Module Function List says "Storage Location", DEV names the screen "Location Master". Source: WMS_BUSINESS_RULE §1.2 · flow product-income Input I-1Start▣ PO CreationPurchase OrderPurchase raises the Purchase Order — the source document for receiving raw material through Stock In. Result: the Stock In Request carries the PO number; the supplier delivers with a Delivery Note No. System: the Slip quantity cannot exceed (Requested − Received) of the Request line. Test: - PO 1,000 kg, supplier delivers 600 kg → Stock In Slip 600 kg; the Request keeps Remaining 400 kg and is not CLOSED Detail flow: Inbound (Merged) Source: BRD WMS Ch2 · WMS_BUSINESS_RULE §1.2 · flow inbound-merged Input I-0Start▣ Sales OrderApprove Sales OrderSales approves the Sales Order; on approval the system creates the Product Income Request for the SO quantity. Result: the Product Income Request is SAVED; the warehouse submits it (SUBMITTED) before printing FG QR labels once production is done; the SO lines also feed Goods Delivery. System: this is the only automatic source of the Product Income Request — Packing Result does not create a new Request. Test: - Approve an SO of 3 sizes × 500 pairs → a Product Income Request (SAVED) carrying the SO number covers all 1,500 pairs Open: BRD WMS Ch1 takes goods "from the Production Order" and makes Work Order (WO) mandatory on the Request — the BRD must be aligned; recalling an SO whose Request already has a Slip or labels is not documented. Source: WMS_BUSINESS_RULE §3 Product Income · Q-20261009-04▣ Shipment PlanningShipment planSales plans shipments from the SO lines; Goods Delivery creates the DO from the SO or the Shipping Plan. Result: the Shipping Plan feeds the DO and the shipment-based Final Inspection. Detail flow: Goods Delivery Source: BRD WMS Ch10 · flow goods-delivery · Q-20260917-22▣ MRP & Material ReadyMaterial Out Requestper WIMES sends the Material Out Request (MOR) per WO / WI to the warehouse to issue material for production. Input: MORs created on Work Order / WI and on Packing Planning (packing material). Result: MOR → REQUESTED, passed to WMS Outbound; the warehouse makes the Stock Out per WO / WI; the APPROVED Outbound Slip reports the issued quantity back to MES. System: each Stock Out Request is tied to exactly one Work Order. Test: - A WI's MOR is REQUESTED → the warehouse makes the Stock Out for that WO / WI, approves the Slip → the MOR in MES becomes ISSUED Open: whether the Stock Out references the MOR number or the WO / WI number (Q-20261009-06); DEV creates the Stock Out Request automatically when the MOR is sent — this differs from the detail flow. Detail flow: Material Issue & Return Source: BRD MES §6.3 · BRD WMS Ch9 · Q-20260917-22 · flow material-issue-return▣ Work Order / WIProduction lineper WIThe production line receives material per WI and returns surplus material to the warehouse. Input: material issued by an APPROVED Stock Out Slip tied to the Work Order. Result: surplus material comes back through Return From Line, taking the item list from the old issue note (PXK). Test: - Issue 100 kg to a WO, use 92 kg → Return From Line 8 kg referencing that WO's Stock Out Slip; approve → stock +8 kg Open: who raises Return From Line (Line Leader on WMS or the MES Return & Variance note) and which warehouse receives it. Detail flow: Work Order / WI Source: BRD WMS Ch5 (US04) · flow material-issue-return · io-map inbound-merged▣ Trimming PlanningPlan APPROVED→ Stock Out Curing noteThe system creates the Stock Out Curing note that moves a LOT from the Curing warehouse to the Trimming process warehouse WH-TRM-01. When: the Trimming plan is approved with LOTs that have finished curing; for LOTs not yet cured, the note is created in Curing Confirmation when the LOT is ready. Result: one note per LOT × plan, APPROVED at once; Curing stock decreases, the to-trim stock in WH-TRM-01 increases; editing or cancelling the plan sets the note CANCELLED and the stock goes back to Curing. Open: whether the Curing warehouse and WH-TRM-01 belong to the WMS stock pool; whether the note appears on the Outbound and Inventory Approve screens. Detail flow: Trimming Planning Source: Q-20260930-05 · flow trimming-planning · flow curing-confirmation · io-map curing-stockout▣ Outsourcing PlanningPlan Spray→ Stock Out note to vendorOutsourcing Planning: approving a Spray plan creates the Stock Out note from WH-TRM-01 to the paint vendor. Result: once the warehouse approves the Stock Out note in WMS Outbound, the Spray plan becomes SENT. Open: the Outbound flow has no Input for this note yet, and whether it goes to Inventory Approve is unclear; prototype v0.82 replaces Approve with Release, the flow is not updated yet (OQ-107). Detail flow: Outsourcing Planning (Spray Out) Source: Q-20261005-01 … Q-20261005-05 · flow spray-out▣ Packing Result Logo / SprayA + A- packedby Customer P.OPacking Result records A / A- / C / Pending repair per size; packed A + A- goods are received into FG stock against the Product Income Request created from the SO. Result: the warehouse prints FG QR labels for the Request, scans on Mobile and makes the Product Income Slip; Packing Result does not create a new Request. System: a Slip against the Request cannot exceed Remaining; the surplus is received on a standalone Slip. Test: - Request 500 pairs, packed A 480 + A- 30 → at most 500 pairs on the Slip against the Request; the 10 extra pairs go on a standalone Slip with no Customer P.O Open: the Packing Result Logo / Spray flows and mes-overview still say Packing creates a receipt request per Customer P.O — to be changed per Q-20261009-04. Detail flow: Packing Result Logo · Packing Result Spray Source: WMS_BUSINESS_RULE §3 Product Income · Q-20261009-04 · Q-20261009-05▣ Final Inspection GateFinal Inspectionper ShipmentQA performs the Final Inspection per Shipment; Goods Delivery ships only when the Final Inspection is Completed. Input: the Shipment from Shipment Planning. Result: the Final Inspection result is the condition for the warehouse to ship to the customer. Open: the Goods Delivery flow has no FI Completed check yet; the QA BRD puts warehouse / shipping execution outside QA scope. Source: Q-20260917-22 · BRD QA (Final Inspection) · mes-overview▣ Material Label IssueRaw-material labelsper source documentThe warehouse generates and prints raw-material labels from a source document; the labels are scanned when making the receipt Slip. Input: Material receipt (GRN) · PO, Production output (surplus material from production), Return / re-pack documents. Result: label ISSUED → PRINTED; scanned into a receipt Slip, the label becomes CONSUMED. System: labels can be applied in several passes, always showing what is still unlabelled on the source document. Test: - GRN 1,000 kg, printed in two passes 600 + 400 → 0 left; scan 600 kg into the receipt Slip → 600 kg of labels become CONSUMED Detail flow: Material Label Issue Source: BRD Label Issue · WMS_BUSINESS_RULE §3 Material Label Issue · flow material-label-issue▣ Product Label IssueFG QR labelsper Product Income RequestThe warehouse generates and prints FG QR labels for the Product Income Request; the labels are scanned on Mobile when making the Product Income Slip. Input: a SUBMITTED Product Income Request with quantity outstanding (created on SO approval, submitted by the warehouse). Result: label ISSUED → PRINTED → SCANNED; the QR locks the quantity, the serial is single-use. System: stock increases only when the Product Income Slip is approved. Open: BRD Label Issue says scanning "posts the encoded quantity", conflicting with the stock-on-approve rule; DEV names the screen "Finished Goods QR Label Issue". Detail flow: Product Label Issue Source: BRD Label Issue · WMS_BUSINESS_RULE §3 · flow product-label-issue▣ Pallet Label IssuePallet BC labelsThe warehouse generates and prints Pallet BC labels used to group barcodes onto a pallet in Product Mapping Pallet. Result: pallet label GENERATED → PRINTED, not yet holding goods. Open: whether at least one child barcode must be scanned before printing (BRD WMS Summary and BRD Label Issue differ); the detail flow is drawn but not yet on the site. Source: BRD Label Issue · BRD WMS Summary · WMS_BUSINESS_RULE §3▣ Exchange Label IssueNew labels afterStock ExchangeThe warehouse prints new labels for goods whose Lot / PO / Barcode changed in Stock Exchange and voids the old labels. Input: APPROVED Stock Exchange Slip lines that change Barcode, Lot or PO. Result: old label ACTIVE → VOID, new label PENDING → ACTIVE with the "Confirm Replacement" button. Open: BRD Label Issue lets the user pick an old label in stock without an Exchange Slip; the screen is not on DEV; the detail flow is not yet on the site. Source: WMS_BUSINESS_RULE §3 Exchange Label Issue · BRD Label Issue▣ InboundStock In · Return From Line· Other InMobileThe merged Inbound screen receives goods in three types: Stock In against a PO, Return From Line (surplus material from the line), Other In. Input: PO and Delivery Note · Stock Out Slip tied to a WO · receipt reason · raw-material labels. Result: Request → Mobile scan → Slip SUBMITTED → Approve → stock increases at the Bin; the Request is CLOSED when every line has Remaining = 0. System: an APPROVED Slip can be cancelled only if Available Stock ≥ the Slip quantity and the Slip has no later action on another screen. Test: - Receive 600 kg into a Bin holding only this lot, 200 kg already issued → cancelling the Slip is blocked because Available 400 < 600 Open: who raises Return From Line and which warehouse receives it. Detail flow: Inbound (Merged) Source: BRD WMS Ch2 · Ch5 · Ch8 · WMS_BUSINESS_RULE §1.2 · §3 Inbound Merged▣ Product IncomeReceive FG per Request(created on SO approval)MobileThe warehouse receives finished goods against the Product Income Request created when Sales approved the SO. Input: the Product Income Request · A + A- goods reported packed by Packing Result · FG QR labels. Result: Submit Request → print FG QR labels for the Request → Mobile scan → Make Slip → Manager Approve → FG stock increases; the Request is CLOSED when every line has Remaining = 0. System: a Slip against the Request cannot exceed Remaining; surplus and goods without an SO go on a standalone Slip with no Customer P.O. Test: - Request 500 pairs, 510 packed → the Slip against the Request takes at most 500, the 10 extra pairs go on a standalone Slip Open: where the FG QR labels for surplus on a standalone Slip come from; whether the Slip takes defective / scrap goods (Defective / Scrap); whether manual Request creation is kept. Detail flow: Product Income Source: WMS_BUSINESS_RULE §3 Product Income · Q-20261009-04 · Q-20261009-05 · BRD WMS Ch1▣ Goods ReturnReceive customer returnsRestock · Rework · ScrapMobileThe warehouse receives goods returned by the customer against the delivered G/D Slip. Input: APPROVED G/D Slip · the customer's return request. Result: Request → Mobile scan → Slip → Approve; only Restock lines increase stock. System: each line is set to Restock · Rework · Scrap. Test: - Customer returns 50 pairs: Restock 40, Scrap 10 → approve, stock +40 Open: where Rework / Scrap goods go next; whether a QC step comes before stock increases (BRD Mobile defaults to QC Pending). Detail flow: Goods Return Source: WMS_BUSINESS_RULE §3 Goods Return · BRD WMS Ch4 · BRD Mobile §6.10StockWarehouse · Location (Bin) · Barcode/QRLot · PO · GradeThe shared WMS stock pool — receipts increase it, issues decrease it, internal screens only change location or attributes. Input: APPROVED Slips of Inbound, Product Income, Goods Return; approved Stock Adjust notes. Result: stock by Warehouse · Location (Bin) · Barcode/QR · Lot · PO · Grade, read by the stock monitoring screens. System: Available = Physical − Reserved; cancelling a Slip reverses stock symmetrically; in a closed period the screens' Slips are blocked. Test: - Approve Stock In 600 kg → Location Stock Monitoring +600 kg at the Slip's Bin; cancel the Slip → back to the old figure Open: no screen creates Reserved (held) stock yet; which WMS document moves FG in stock to another Customer P.O (MES Exchange Customer PO). Source: WMS_BUSINESS_RULE §1.7 · §1.8 · BRD WMS Ch9 · io-map exchange-customer-po▣ Product Mapping PalletGroup barcodesonto a Pallet BCMobileThe warehouse groups several child barcodes onto one Pallet BC to manage and ship by pallet. Input: barcoded goods in stock · Pallet BC label from Pallet Label Issue. Result: Request → Mobile scan → Slip → Approve; Cancel detaches the child barcodes from the Pallet BC. Open: whether pallet mapping changes stock quantity, goes through Inventory Approve and is blocked by a closed period (the site flow and BRD Mobile differ); Goods Delivery does not take a Pallet BC yet. Detail flow: Prod Mapping Pallet Source: WMS_BUSINESS_RULE §3 Prod Mapping Pallet · BRD Mobile §6.15 · flow prod-mapping-pallet▣ Product Mapping PalletPallet Dividesplit the palletMobileThe warehouse splits a mapped Pallet BC into new pallets; approval is done on the Product Mapping Pallet screen. Input: mapped Pallet BC · Pallet-Divide Request. Result: the Mobile draft divide slip counts as SUBMITTED → Manager Approve → the child barcodes move to the new Pallet BC. System: stock quantity does not change. Open: the detail flow is drawn but not yet on the site; DEV has no screen. Source: WMS_BUSINESS_RULE §3 Pallet Divide · BRD Mobile §6.16▣ Stock ExchangeChange Lot · PO· Barcode · GradeMobileThe warehouse changes the Lot / PO / Barcode / Grade of stock without changing the quantity. Input: current stock by Barcode. Result: Request → Mobile scan → Slip → Approve updates the stock attributes; lines changing Barcode, Lot or PO need new labels. System: Cancel is blocked once the goods have a later transaction. Test: - Change Grade A → A- for 30 pairs, then issue 10 pairs → cancelling the Grade-change Slip is blocked Open: BRD Mobile describes a swap between two pallets (side A / side B), unlike the Web BRD. Detail flow: Stock Exchange Source: WMS_BUSINESS_RULE §3 Stock Exchange · BRD WMS Ch7 · BRD Mobile §6.14▣ Stock TransferWarehouse transfer· relocationMobileThe warehouse moves goods between warehouses or locations; source stock decreases, destination stock increases. Input: stock at the source warehouse / Bin. Result: Request → Mobile scan → Slip → Approve moves the stock; the Slip can be made on Mobile, on Web or standalone without a Request. System: Approve is blocked when Available at the source is below the transfer quantity. Test: - Available at the source Bin 80, transfer 100 → Approve is blocked Open: BRD Mobile splits it into Transfer Out → In Transit → Transfer In; the site flow has one step. Detail flow: Stock Transfer Source: WMS_BUSINESS_RULE §3 Stock Transfer · BRD WMS Ch6 · BRD Mobile §6.12–6.13▣ OutboundStock Out · Return to Supplier· Stock Discard · Other OutMobileThe merged Outbound screen issues goods in four types: Stock Out (material for production), Return to Supplier, Stock Discard, Other Out. Input: MOR / Work Order · Stock In and PO (Return to Supplier) · discard reason · Stock Out notes created by MES. Result: an APPROVED Slip decreases stock; Return to Supplier creates a Debit Note for Purchasing / Accounting and the supplier. System: each Stock Out Request is tied to one Work Order; the APPROVED Stock Out Slip reports the issued quantity to MES. Test: - Return to Supplier 50 kg approved → stock −50 kg and a Debit Note is created Open: the Outbound flow has no Input for Stock Out notes created by MES; whether Stock Discard goes through Inventory Approve; which module produces the QC report. Detail flow: Outbound (Merged) Source: BRD WMS Ch3 (BR-13) · Ch9 · Ch12 · WMS_BUSINESS_RULE §3 Outbound Merged▣ Goods DeliveryShip to customerper SO / Shipping PlanMobileThe warehouse ships finished goods to the customer against the SO or Shipping Plan. Input: APPROVED SO / Shipping Plan · FG stock · Final Inspection result. Result: DO → Mobile scan → G/D Slip → Approve → FG stock decreases; the APPROVED G/D Slip is the source of Goods Return. System: cancelling a G/D Slip is blocked once the goods have left the warehouse. Test: - SO 1,000 pairs shipped in two lots 600 + 400 → the DO is CLOSED after the second Slip is approved Open: no Final Inspection Completed check yet; no Pallet BC intake from Product Mapping Pallet yet. Detail flow: Goods Delivery Source: WMS_BUSINESS_RULE §3 Goods Delivery · BRD WMS Ch10 · Q-20260917-22End▣ Inventory ApproveApprove / cancel Slipsof every warehouse screenThe Warehouse Manager approves / cancels, in one place, the Slips of every warehouse screen whose Slips need approval. Input: Slips of Stock In, Return From Line, Other In, Stock Out, Return To Supplier, Other Out, Product Income, Goods Delivery, Goods Return, Stock Transfer, Stock Exchange. Result: Approve / Cancel follow the source screen's own rules; batch approval succeeds partially and reports "X succeeded · Y failed". System: this screen does not apply the closed-period block yet — a Slip refused on its own screen because the period is closed can still be approved / cancelled here. Test: - Select 5 Slips, one Cancel is blocked for lack of Available → "4 succeeded · 1 failed", that Slip keeps its status Open: whether Stock Discard is in the list (DEV has it, WMS_BUSINESS_RULE does not); Product Mapping Pallet is not in the list. Detail flow: Inventory Approve Source: WMS_BUSINESS_RULE §3 Inventory Approve · §1.8▣ Stock ClosingClose the stock periodThe Warehouse Manager closes the stock period; a closed period blocks every action on the Slips of screens with transactions in it. Input: stock by Barcode/QR and transactions up to the close date. Result: period OPEN → CLOSED with a Snapshot for stock counting; Release reopens the period. System: Submit · Approve · Cancel · Delete are refused with the message "This action cannot be completed because the affected inventory period is closed through [Close Date]"; Inventory Approve, Stock Evaluation Checking and Stock Adjust do not apply it yet. Test: - Close the period through 30/09, cancel a Slip dated 28/09 → blocked with the message above; release the period → the cancel goes through Detail flow: Stock Evaluation Checking Source: WMS_BUSINESS_RULE §1.8 · §3 Stock Evaluation Checking / Stock Closing / Stock Adjustment▣ Stock Evaluation CheckingCount by scanningcompare with stockMobileThe warehouse counts stock by Mobile scanning and compares it with the Snapshot of the closed period. Input: Snapshot from Stock Closing · physical goods in the Bin. Result: a comparison grid with Barcode Status (e.g. Matched) and an Excel file; variance lines go to Stock Adjust. System: the screen only compares; it does not change stock. Test: - Snapshot 100, counted 97 → a variance line of 3 enters the Stock Adjust waiting list Open: the name of the Web screen that creates the count; DEV has two menu entries both named "Stock Evaluation Checking". Detail flow: Stock Evaluation Checking Source: WMS_BUSINESS_RULE §3 Stock Evaluation Checking · BRD WMS Ch14 · BRD Mobile §6.17▣ Stock Adjust (In/Out)Adjustthe varianceThe warehouse adjusts the variance found by the count; stock changes as soon as the note is approved. Input: variance lines from Stock Evaluation Checking. Result: note DRAFT → PENDING APPROVAL → APPROVED or REJECTED; APPROVED adjusts quantity, Lot, Location or Warehouse. System: the closed-period block does not apply yet. Test: - A variance line of −3 approved → stock at the Bin −3 Detail flow: Stock Evaluation Checking Source: WMS_BUSINESS_RULE §3 Stock Evaluation Checking / Stock Closing / Stock Adjustment · BRD WMS Ch11▣ Safety Stock (Max/ Min Qty) SettingMax / Min thresholdsThe Warehouse Manager sets Max / Min thresholds, the responsible person and the shelf-life policy per Item / warehouse. Result: the thresholds drive Max/Min Stock Status Checking and Expired Stock Checking. Open: DEV names the screen "Inventory Setup". Source: BRD WMS Summary (Stock Alarm) · BRD Inventory Web▣ Max/Min Stock Status CheckingStock outside thresholdsThe screen compares current stock with the Max / Min thresholds and emails an alert to the responsible person. Result: an email with Excel suggesting to reorder or reduce the next PO — no document is created. Source: BRD Inventory Web · BRD WMS Summary▣ Expired Stock CheckingNear / past expiryThe screen lists lots near or past expiry under the shelf-life policy and emails an alert. Open: BRD Label Issue allows moving expired lots to quarantine, relabelling or raising them for disposal — no edge to Stock Discard yet; DEV places the screen in the Stock Checking group. Source: BRD Inventory Web §2.4 · BRD Label Issue▣ W/H Stock Checking 1 (In-Out)In · out per itemThe screen shows Begin / In / Out / End per item over a date range — read only. Open: the numbering of the four W/H Stock Checking screens differs between the catalogue, BRD Inventory Web and DEV ("W/H Stock Checking - Items In out"). Source: BRD WMS Summary · BRD Inventory Web▣ W/H Stock Checking 2 (Transaction)By transactionThe screen looks up every transaction posted to the stock ledger (Item Ledger Entries) — it never posts a transaction itself. Open: DEV names the screen "W/H Stock Checking - Transaction". Source: BRD Inventory Web · BRD WMS Summary▣ W/H Stock Checking 5 (Tr Detail Slip)Detail per SlipThe screen looks up and prints the detail of each posted Slip. Open: DEV names the screen "W/H Stock Checking - Detail Slip". Source: BRD WMS Summary · BRD Inventory Web▣ W/H Stock Checking 1 (Daily/ Monthly/ Quarter/ Yearly)Stock per periodThe screen reports opening, in, out and closing stock by day, month, quarter, year. Open: DEV names the screen "Inventory Report". Source: BRD WMS Summary · BRD Inventory Web▣ Location Stock MonitoringStock per LocationThe screen shows stock by Location and QR; the Mobile stock inquiry reads the same data. Open: no dedicated BRD for this screen; linking the Mobile "Stock Checking" action to it is a proposal, not yet confirmed. Source: Module Function List · BRD Mobile §6.18▣ FIFO Stock CheckingFIFO order checkThe screen checks the FIFO issue order of each lot. Open: BRD Label Issue has a Pick list and Count sheet, DEV adds "Put lot on hold" — FC has no screen that takes the Pick list. Source: Module Function List · BRD Label Issue
Goods / document flow Information exchange · labels · unconfirmed flow ⬮ Stock pool Mobile Process with a Mobile scanning stage Start End Hover to read the note · click a box to open its detail flow

Glossary

GlossaryMeaning in this flow
Request · SlipRequest = receipt / issue request (SAVED → SUBMITTED → CLOSED; cancelling an APPROVED Slip returns a CLOSED Request to SUBMITTED); Slip = the execution document scanned on Mobile (SAVED → SUBMITTED → APPROVED ⇄ CANCELLED)
RemainingQuantity still to receive / issue on a Request line = Requested − Received; the Request closes itself when every line reaches 0 (Stock Exchange: when every linked Exchange Slip is APPROVED)
Slip standaloneA Slip with no Request — used for packed surplus or goods without an SO
Location (Bin)Storage position in the warehouse, mandatory on every Slip line
Barcode/QR · Pallet BCIdentifier of goods on the label; Pallet BC is the pallet barcode holding several child barcodes after Product Mapping Pallet
Available · PhysicalPhysical = stock on hand; Available = Physical − Reserved
MORMaterial Out Request — MES request to issue material per WI; it becomes a Stock Out Request in the warehouse
WH-TRM-01MES Trimming process warehouse; receives lots through the Stock Out Curing note and sends goods to the paint vendor through a Stock Out note
Customer P.OThe customer order finished goods are tied to
Closed period (Stock Closing)A stock period that is CLOSED; Slips whose date or warehouse falls in it are blocked from every action
SnapshotStock frozen at the close date, compared with the counted quantity
Restock · Rework · ScrapThe three dispositions of a Goods Return line; only Restock increases stock
Debit NoteSupplier debit document created when Return to Supplier is approved
Final Inspection (FI)QA final check per Shipment; Goods Delivery ships only when FI is Completed
MobileThe barcode-scanning stage on a handheld device; approval is always done on Web