Movements

A stock movement records a signed quantity, occurrence date, item, location, optional lot and parent request. Its posted flag identifies the entries used for stock position. The line number and revision help the team identify an effect within an authorized request. A source effect key gives a stable identity to the event so the same action is not counted twice.

The operation receipt records the action, expected revision, result state and time. It can also hold an external reference, effect references or failure reason. Reading the movement and receipt together tells the operator whether the requested action produced a local stock effect, needs review or failed.

• Keep signed quantity. Receipts and issues affect stock in opposite directions without rewriting a balance.
• Preserve the link. Every movement carries its request, item and location; lot and reversal links add the relevant detail.
• Review the outcome. Read the operation receipt before retrying a failed or uncertain action.

Agree how each operation key and source effect key is issued. Decide which source supplies the occurrence time and how to reconcile an external reference. Set the rule for movement lines that involve a lot so the recorded code and lot reference remain consistent. Determine who can post an approved request and who handles a failed receipt.

A reversal should be a new compensating movement linked to the original through Reverses. The original posted record remains. The team needs a rule to prevent total reversals from exceeding the original quantity and to keep a later correction tied to the accepted scope. A direct balance edit would break that trail. Rehearse duplicates, partial failures and reversals before releasing operations.

Use an approved request for a Released, unexpired lot. Post an issue with its signed quantity and inspect the movement’s request, item, location, lot, revision and effect key. Check that an operation receipt identifies the result. Run the same operation key again and confirm it does not create a second posted effect. Reverse part of the movement and inspect the new entry’s Reverses link. The original should still be readable, while the net signed quantity reflects the compensating entry.

• Posted movement history — Signed effects with occurrence time, request, lot and reversal link.
• Receipts needing attention — Pending, Failed or needs review outcomes that need investigation.
• Completed request history — Executed requests whose movement chain can be traced.

See reservation and movement, correction and reversal and outcome review.