Sync Item Master stock to inventory ledger - #13
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
OmegaLSKJ
force-pushed
the
codex/item-master-stock-sync
branch
from
September 23, 2026 16:48
6c4c369 to
4412c0f
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Item Master stock values were saved only as form data, while all stock screens calculate balances from
stock_movements. This left saved master stock unchanged in inventory, purchase, and sales.This change creates or updates the submitted item batches and posts only the ledger adjustment needed to reach each entered balance. It also serves the live stock-position rows for the
stockAPI resource, preventing the productionUnknown ERP resourceerror.Validation:
next buildcompiled successfully; the final TypeScript check remains blocked by the existing unrelatedTransactionImport.tsxunknownvalue error.