Stock Conversion

Re-label, re-pack or kit stock at one location without a bill of materials or a production order: Input lines and Output lines on one header, saved as a draft and then finalised. It is not a generic document, so no knock-off queue and no journal; finalising is built to write one signed line per item to the stock ledger, but nothing is connected to that posting run, so a FINAL marks the document and moves no stock. Read the tabs as Input = into stock, Output = out of stock, and note that nothing here checks what is on hand before an Output line takes it out.

Overview

The Stock Conversion applet records a conversion of stock at one location: a set of Input lines and a set of Output lines on one header, saved as a draft and then posted with FINAL. It is the tool for re-labelling, re-packing and simple kitting when no bill of materials or production order is wanted — for example turning ten single-pack accessories into one retail bundle item, or splitting a master carton into sellable units at branch GS-KV-01.

It is not a generic document: it has its own records, its own posting step and its own processing chain. Nothing about it passes through the sales/purchase document engine, the knock-off queue or the GL journal. What a FINAL is built to do is append one signed line per item line to the stock ledger. That step is built but not connected: FINAL queues the conversion’s posting run, and the run passes the work only to jobs subscribed to it — and none is, for any tenant. The document says FINAL and Stock Balance does not move. Check the balance after your first FINAL rather than assuming it. When the chain is connected, the direction of each line is fixed by the tab it was entered on — see Lifecycle and effects, because the direction is the opposite of what the tab names suggest to most readers.

Where it fits

Modules: Inventory (the applet’s home) and Manufacturing (light kitting without a production order).

Screens and menus

One menu item, Stock Conversion, opens the listing. Settings has Application Settings, Default Selection and Printable Format Settings under System Configuration, then the shared server-side permission screens (Permission Wizard, Permission Set, User Permission, Role Permission), Team access and the developer tools. A shared Webhook screen is also routed under Settings but is not in the menu; it can be opened by typing its address, and nothing on it touches this applet’s own settings. Personalization has Default Selection and Sidebar.

Stock Conversion Listing

Listing with columns Posting Status (blank shown as DRAFT), Conversion Code, Conversion Name, Location, Txn Date, Status, Created By, Date Created, Updated By, Date Updated. A FINAL button above the grid posts every ticked row that is not yet FINAL and has status ACTIVE, one at a time. The + button opens the create form; clicking a row opens the edit form. The search box filters: what you type is matched anywhere inside the Conversion Code, the Conversion Name or the internal running number (a contains-match, case-insensitive), so bundle finds Accessory bundle 03 and BUNDLE-KV01 alike. The advanced search panel (Code, Name, Description, Created Date and Updated Date ranges) does not: the panel builds a query the listing never sends, so searching from it simply reloads the full list. For a date range, use the grid’s own column filters and sorting on Date Created / Date Updated. There is no print, void, discard or delete action on the listing or the forms.

Create / Edit form

Tabs Main Details, Input, Output; the edit form adds Job Order Link. Header buttons: RESET, SAVE, and on the edit form FINAL (shown while the document is not FINAL and its status is ACTIVE). SAVE is disabled until Main Details is valid and both the Input and the Output tab have at least one line. After FINAL every Main Details control is disabled and SAVE / RESET stay disabled.

Each line is added through a three-step side panel — Search Item → Item Details (Item Code, Item Name, UOM, Quantity Base, Remarks) → extra tabs by sub-item type: Serial Number (scan / import), Batch Number (batch no., quantity, issue and expiry dates) or Bin Number (bin list with container quantity and base quantity). Input and Output lines use the same panel; only the sign applied to the quantity differs.

The two listing captures that used to sit here were removed (test data with people’s names); a recapture from a demo tenant is on the lane’s list.

Configuration

Before you can use it

Applet settings

Settings are applet-local. Anyone who can open Settings can change them (no permission check).

DEFAULT_COMPANY is saved alongside the two defaults (from the selected branch’s company), but nothing uses the value.

Personalization › Default Selection renders the same Default Branch / Default Location pair and saves them as personal settings, but the personal values are stored and never applied. Only the applet-level defaults take effect.

Application Settings opens the shared Field Settings screen — the same multi-tab screen the document applets use, with its generic document tabs (Unit Discount, SST/VAT/GST, WHT, Blanket Order and the rest). Two toggles on its Lines tab act on this applet: Hide unit price (standard pricing scheme) hides the UOM selector on the line panel, and Hide quantity base hides Quantity Base. Everything else on the screen saves and changes nothing here — the twenty-odd other price and amount toggles on the Lines tab have no control on this applet’s line panel to hide, and the other tabs describe documents this applet does not raise. (The applet also carries its own eight-toggle Field Settings stub in code, but nothing routes to it.)

Key honoured without a control. HIDE_BIN set to true hides the Bin Number tab on the line panel. No screen sets it; ask support if you need it applied to your tenant.

Document behaviour settings

None exposed. Posting status is driven by the FINAL button; there is no custom-status, approval, e-Invoice or numbering toggle in the applet.

Settings in other applets that control this applet

Feature visibility / permissions

Server-side. Saving needs API_TNT_DM_ERP_INVENTORY_STOCK_CONVERSION_HDR_CREATE; editing needs _UPDATE; deleting needs _DELETE; opening, listing and FINAL need _READ; discard needs _UPDATE; _OWNER and _ADMIN cover everything. Lines (read-only) use the ..._LINE_* codes; job-order links use ..._JOB_ORDER_LINK_*. None of the header permissions is targeted (no branch / location scoping).

Client-side. The line components honour SHOW_QTY_BASE, SHOW_UNIT_PRICE_STD_PRICING_SCHEME and the rest of the SHOW_UNIT_PRICE_* / SHOW_AMOUNT_* / SHOW_*_CONFIG_SELECTION family as the re-enable half of the HIDE_* pairs (SHOW_COSTING_DETAILS is read too, but its only consumer is a tab that is commented out). None exists for this applet, so the Client Side Permission screen has nothing to assign and the HIDE_* keys, if ever set, cannot be reopened per role.

Fields

Main Details tab

Conversion Name (required on the form) and Description (optional) are free text; the listing shows the name and the search box matches inside it (Description is matched by nothing — see Stock Conversion Listing). Neither is copied onto the stock ledger lines the posting writes; those carry only a link back to the conversion, so put anything a stock reader needs to see in the line Remarks.

The header also has job-order, process, machine, duration, process type (sequential / parallel / cyclic / conditional), start / end date and void-reason fields; none is rendered by the form.

Input and Output tabs — line panel

Item Name is a copy of the item’s name that you can overwrite, and Remarks is free text. Both are carried onto the stock ledger line the posting writes, so an overwritten name is what the ledger line records for that movement, while the item master keeps its own name.

There is no price or amount control on the line panel (Item Code, Item Name, UOM, Quantity Base, Remarks only). Prices and amounts are saved empty or zero. Line grids on the Input / Output tabs show Item Code, Item Name, UOM, Qty (signed) and Last Updated.

Job Order Link tab (edit form only)

Links the saved conversion to MRP job orders (columns Job Order No, Item Code, Container Measure, Container Qty, Priority, Remarks). BigLedger validates only that the header and job order exist; nothing in the posting chain reads the link.

Lifecycle and effects

Statuses. Posting Status is blank (shown DRAFT) → FINAL → VOID; DISCARDED also exists. Status is ACTIVE and is never changed by the applet.

Posting proof block.

• Server document type: the lines carry the literal Stock Conversion Applet; it is not one of the standard generic document types.
• Quantity signum: 1 on every line. Direction lives in the sign of the quantity: Input lines are stored +qty, Output lines −qty.
• Amount signum: 0 — no value moves; the applet has no journal.
• Balance equation: new ledger quantity = previous ledger quantity + signed quantity. An Input line therefore increases the location balance and an Output line decreases it. Serial numbers follow the same arithmetic: each serial on a line has its own balance, an Input line adds one to it and an Output line takes one off — nothing is deleted, and a serial the tenant has never seen is created first on either tab, so an Output line naming an unknown serial creates it and leaves it at −1. Bins likewise. Read the tabs as Input = into stock, Output = out of stock.
• Which balance moves (once the chain runs): the location balance only. The screens stamp a line with its store and header only — no company, no branch — and the server fills neither, so the processor that keeps the company-level balance and company moving average has nothing to update. Stock Balance’s per-location figure would move; the company total and the company average cost on Stock Availability would not (read from the code, not tried).
• Moving-average cost (once the chain runs): the line’s amount is ignored, because Stock Conversion Applet is not one of the document types whose amount enters the average. An Input line comes in at the price that item last carried at that location — zero if the location has never held it — and an Output line leaves at the running average. Neither item’s unit average moves. What also does not move is value between them: the components’ cost leaves inventory, and the new item arrives at its own history, never at the cost of what went into it. Weighted average reads only the amount-bearing types too, so it ignores the conversion the same way. A backdated rebuild treats the line the same way.
• GL precedence: not applicable — no journal is posted.
• Stock processor chain (as built; not connected on 2026-10-01): FINAL queues the posting run, which skips the whole document if its stock has already been posted, builds one ledger line per item line whose item resolves, with the store = header location → line branch’s main location → header branch’s main location, marks the document’s stock as posted, then updates the location balance per line. No knock-off queue, no open-queue row, no tax, no e-Invoice.
• What VOID reverses: the reversal rebuilds the same lines, negates them, marks them as VOID lines, creates them only if the stock had been posted, marks the document’s stock as voided, and per line re-runs the backdated recalculation, future brought-forward / carried-forward balances and the balance / serial / bin / batch records. Nothing is deleted.

Printing. A batch PDF print exists server-side and printable formats can be uploaded under Settings › Printable Format Settings, but no screen in the applet triggers a print.

Related applets

• Related Applets - Stock Balance — where conversion lines join the other 25 stock-moving document types and the processor chain.
• Stock Balance — see the result of a FINAL per item and location; conversions do not show as documents there.
• Stock Availability — same balance with open orders; a draft conversion is invisible to it (no open-queue rows).
• Stock Report — movement reports list conversion lines under server document type Stock Conversion Applet.
• Stock Adjustment — the generic-document alternative with a reason code and, unlike this applet, a journal.
• Stock Take — count after a conversion to confirm the on-hand figures.
• Packing Order (Internal) — production-side kitting from a packing list.
• Inventory Item Maintenance, Doc Item Maintenance — item links, package ratios and sub-item types that decide what a line posts.
• Organisation — branches, locations and the branch main location.

Troubleshooting

Related documentation

• Related Applets - Stock Balance — the processor chain this applet feeds and the refresh / recalculation jobs
• Inventory module and Manufacturing module — where the applet is listed
• Stock Adjustment — when a single-item correction is the better tool