Packing Order Applet (Internal)

Overview

The Packing Order Applet (Internal) is the packing desk of the manufacturing module. A packing order is an internal document (INTERNAL_PACKING_ORDER) whose lines are the items and quantities to be packed, usually knocked off from a finalised sales order. Finalising the order pushes every line into an operator queue; a packing operator records what was packed, from which bins, with which length markings, and a supervisor approves or rejects each line. Approval cuts the physical bin, records the packed bins, releases any stock reservation held for the sales order and settles the queue balance.

The applet also carries a coiling variant of the shop-floor process-instance and work-log screens found in the Manufacturing Operations Applet (menus Auto Coil Operator and Auto Coil Supervisor), a packing container register of drums and reels, a scrap register, and read-only views of job orders, production requests and sales orders. The vocabulary of those screens — drum types, coiling direction, length markings, cable diameter — is that of a cable manufacturer, and ships to every tenant as is.

The packing order document itself neither posts a journal nor moves stock: its amount and quantity signums are both zero. Stock moves only when a coiling process instance is finalised, and that movement carries no cost (see Lifecycle and effects).

Where it fits

Screens and menus

The sidebar (models/menu-items.ts) has nine work menus and six settings menus. The applet opens on Operator Queue (the empty route redirects there, app.routing.ts).

The packing order edit form has these tabs (packing-order-edit.component.html): Main Details · Account · Delivery Details · Department Hdr · Lines · Contra · Payment · ARAP · Doc Link · Attachments · E-Invoice · Export · Search · Trace Document · Operator Queue. The last tab is specific to this applet: it lists the queue rows of this order and is where the supervisor approves, rejects or scraps a line. Account, Payment, ARAP and E-Invoice come with the shared document scaffold; with both signums at zero the ARAP balance of a packing order is always zero.

Adding a line opens a tab group (line-item-create.component.html): Search Item, then KO For Sales Order, KO For Jobsheet, KO For Delivery Order and KO For Sales Invoice, each shown only when enabled (see Document behaviour settings). “KO By …” and “Copy Quotation Item” tabs exist in the template but are commented out; there is no quotation knock-off.

Settings menus: Application Settings (field-settings), Default Selection, Printable Format Settings, Return Reasons Settings, Workflow Settings, Email Template, plus the shared Feature Visibility, Client Side Permission, Permission Wizard / Set, User, Team and Role Permission, and Webhook screens. Personalisation: Default Selection (personal) and Sidebar.

No screenshot of this applet is held in the wiki (static/images/internal-packing-order-applet/ is empty).

Configuration

Before you can use it

Applet settings

Settings live in four places: Default Selection (applet-local component, master settings), Personal Default Selection (applet-local, per user), the shared Feature Visibility screen (projects/shared-utilities/modules/settings/feature-visibility, which writes the HIDE_* / ENABLE_* keys this applet reads), and the shared Client Side Permission screen (which grants the SHOW_* codes). Anyone who can open Settings can change the master values; Personal Default Selection is per login.

Keys read at runtime that no screen in this applet writes: SALES_RETURN_WITH_PAYMENT — if it is set on this applet, Final is refused client-side unless the ARAP balance is zero (packing-order-edit.component.ts L232–238), a check copied from the Sales Return applet; on a zero-signum document the balance is always zero, so the check is inert unless the key is set by hand. DEFAULT_PROCESS_TYPE_CODE is declared in the Default Selection form but has no control in the template and is not read by any screen — model-only, not documented as a setting.

Application Settings (field-settings) does nothing. The menu opens an applet-local FieldConfigurationComponent whose template is eight unbound toggles (Unit Discount, SST/VAT/GST, WHT, Blanket Order; Segment, G/L Dimension, Profit Center, Project) and a Save button with no handler; the component class is empty (field-configuration.component.ts, .html, checked at commit 3d1d4e6). Nothing is persisted and nothing reads it.

Document behaviour settings

Settings in other applets that control this applet

Feature visibility / permissions

• Route guard. Seven of the nine work menus (Manual Packing, Auto Coil Supervisor, Packing Request, Job Order, Urgent Sales Order, Packing Containers, Scrap & Short) require the client-side permission SHOW_SUPERVISOR_VIEW; the guard also passes when the user holds the server permission TNT_API_DOC_INTERNAL_PACKING_ORDER_READ_TGT_GUID, TNT_TENANT_ADMIN or TNT_TENANT_OWNER (permission-gaurd.ts L56–61). Operator Queue and Auto Coil Operator are unguarded.
• Client-side codes read by the applet: SHOW_SUPERVISOR_VIEW, SHOW_GENDOC_FINAL_BUTTON, SHOW_GENDOC_VOID_BUTTON, SHOW_GENDOC_DISCARD_BUTTON, SHOW_ARAP_BAL, SHOW_ARAP_CONTRA, SHOW_ARAP_DOC_OPEN, SHOW_ARAP_PNS, SHOW_ARAP_SETTLEMENT, SHOW_COSTING_DETAILS, SHOW_DOC_NO_BRANCH, SHOW_DOC_NO_COMPANY, SHOW_DOC_NO_TENANT, SHOW_CLIENT_DOC_TYPE, SHOW_TRANSACTION_DATE, SHOW_SALES_AGENT, SHOW_DESCRIPTION, SHOW_QTY_BASE, SHOW_QTY_UOM, SHOW_UOM_TO_BASE_RATIO, the SHOW_UNIT_PRICE_* / SHOW_UNIT_DISCOUNT* / SHOW_AMOUNT_* line-column codes, SHOW_LAST_PURCHASE_PRICE, SHOW_TAX_CONFIG_SELECTION, SHOW_WHT_CONFIG_SELECTION. The registry defines only two codes for internalPackingOrderApplet — SHOW_SUPERVISOR_VIEW and SHOW_OPERATOR_VIEW (2 ACTIVE rows in bl_applet_client_side_perm_dfn, queried 2026-09-15) — and SHOW_OPERATOR_VIEW is defined but read by nothing in this applet (the Client permission map in app.component.ts L227 holds SHOW_SUPERVISOR_VIEW alone). Every other code in the list is compared against the loaded permission store (packing-order-listing.component.ts L180, L248; packing-order-edit.component.ts L137; add-line-item.component.ts L123) but has no definition row, so the Client Side Permission screen cannot grant it and the check can never be true; wherever the matching HIDE_* setting is on, that column or button is hidden for everyone, administrators included (P-0396, the P-0256 class).
• Server-side: the four document permissions above; the mrp/ endpoints check API_TNT_DM_MRP_* permissions built per target (TntMrpPermissions.java).

Fields

Packing order — Main Details

Packing order — Delivery Details

Packing order — Lines (Item Details › Main)

Line tabs: Batch Number, Bin Number, Serial Number (scan / import), Costing Details (behind SHOW_COSTING_DETAILS), Pricing Details, Delivery Details, Delivery Instruction, Department, Doc Link, Issue Link.

Operator queue row (Operator Queue › Main Details)

Packing container (bl_mrp_container_size)

Lifecycle and effects

Posting proof (backend commit c4a3545d7c).

What Final does. onFinal puts posting_status = FINAL (packing-order-edit.component.ts L220–240). On success, the effect postToFiPickPackQueue$ maps every line to a bl_fi_pick_pack_queue row (gendoc-to-ppq.mapper.ts: qty_balance = base_qty = quantity_base, priority and running number null) through POST …/pick-pack-queues/ad-hoc/backoffice-ep (FinancialPickPackQueueController.java L107), then postToMRPPickPackQueue$ calls POST mrp/mrp-pick-pack-queues/insert-mrp-picking-queue/backoffice-ep, which copies each FI row into bl_mrp_pick_pack_queue and deletes the FI row (MRPPickPackQueueService.java L66–95). That is the whole meaning of Final here: the lines enter the Operator Queue. Nothing else is written.

Operator step. Saving a queue row (operator-queue.effects.ts L24–69) puts the bl_mrp_pick_pack_queue row and sets the packing order line’s packing_status to PENDING_APPROVAL. Length markings are created and updated as bl_inv_bin_marking rows (L163–246).

Supervisor approval (packing order › Operator Queue tab › Approve; queue.effects.ts):

1. cutBins$ (L40–95): for each marking, loads the bin, and if the marked quantity is less than the bin line’s quantity, reduces the bin line and creates a new bin line for the packed quantity; if it exceeds it, throws “Packing Quantity exceeds bin’s quantity” — a client-side error, not a backend rejection.
2. createPackedBins$ (L96–119): one bl_fi_packing_order_packed_bins row per new bin line, with packed_container_qty and packed_base_qty. Note the row’s packing_order_hdr_guid is set to the queue row’s guid, not the packing order header’s (L104).
3. reservationRelease$ (L124–160): reads the sales order behind the queue row, finds its bin-reservation links and sets them and the stock reservation header to RELEASED.
4. supervisorApproval$ (L165–210): sets the line’s packing_status = APPROVED and calls PUT mrp/mrp-pick-pack-queues/update-qty-balance/backoffice-ep with qty_balance − awaiting_approval; the backend checkAndUpdatePPQAndGenDoc (MRPPickPackQueueService.java L102–165) then updates the packing status on the connected generic document header and lines.

Reject sets the line’s packing_status = REJECTED (L221–240). Scrap from the same tab posts a bl_inv_bin_lock with lock_type = SCRAP, server_doc_type = INTERNAL_PACKING_ORDER and the line guid (scrap-create.component.ts L140–147, queue.effects.ts L252); that is what the Scrap & Short menu lists.

Packing statuses are PackingStatusEnum: IN_QUEUE, PLANNED, IN_PROGRESS, ON_HOLD, COMPLETED, PENDING_APPROVAL, APPROVED, REJECTED, INCOMPLETE, PENDING_STOCK. The applet’s own filter list uses INCOMPLETE, PENDING_APPROVAL, COMPLETED, REJECTED (applet-constants.ts).

No approval engine. The generic approval engine covers only PO / PR / Stock Requisition; here “approval” is the supervisor’s Approve button above and, on the coiling screens, the work-log approval_status (PENDING, APPROVED, REJECTED, REWORK) set through PUT mrp/mrp-process-instance-work-log/update-approval-status/{guid} (ProcessInstanceWorkLogService.java L39–47). Neither uses Approval Settings.

Coiling process instances (Auto Coil Supervisor / Operator). The supervisor creates a bl_mrp_process_instance_hdr with instance_type = PACKING and process_status = PLANNED, input items (bins, locked with a bl_inv_bin_lock) and output items (the Default Item / default coiling item); the operator posts work logs (shift date and type, machine, length produced, length discrepancy, line speed, OD start/mid/end, in/out die, heater temperature, time consumed). Final on the supervisor screen puts posting_status = POSTED, process_status = FINAL and then calls GET mrp/mrp-process-instances/backoffice-ep/update-inventory-from-process-instance/{guid} (supervisor-coiling.effects.ts L22–60; MrpProcessInstanceController.java L191–204). The backend writes one bl_inv_txn_line per INPUT line (quantity signum −1) and per OUTPUT line (+1) and queues InventoryTxnLineToCurrentStockBalanceProcessor for each (MrpProcessInstanceService.java L68–98, L117–160). Every such line is written with amount_txn = 0 (L149). The coil that leaves stock leaves at the running moving average; the coil that enters stock enters at zero value — the same defect as P-0255 for Stock Conversion, and the only place this applet moves stock.

Packing Request. Save writes mrp_request_status_exists and mrp_request_remarks onto the sales order line and puts the sales order (production-request.effects.ts L23–39). Nothing else changes.

Container register. Create / delete bl_mrp_container_size rows. The backend additionally exposes POST mrp/bl-mrp-container-sizes/insert-for-cable-reel/backoffice-ep (computes the reel volume) and GET …/get-drum-recommendation-for-coils (recommends a reel for an item, cable length, diameter and drum type — MRPContainerSizeService.java L38–52); the applet’s packing-container screens call only create and delete (packing-controller effects, checked at commit 3d1d4e6).

Related applets

• Sales Order (Internal) — the backend-registered previous document; its lines are knocked off here and its reservation is released on approval.
• Job Sheet (Internal), Outbound Delivery Order (Internal), Sales Invoice (Internal) — knock-off tabs when their Doc Flow row is enabled.
• Production Planning and Monitoring Applet — creates the job orders and production requests this applet lists.
• Manufacturing Operations Applet — the same process-instance and work-log screens for non-packing instances.
• Process Maintenance Applet — machines, process types, templates.
• Stock Reservation Applet — what approval releases.
• Stock Balance Applet — where the zero-value coil movements land.
• Organisation Applet — Doc Flow Config, branches, locations.
• Workflow Design Applet — the process referenced by Workflow Settings.

Troubleshooting

Related documentation

• Manufacturing Module
• Manufacturing applets
• No user guide covers this applet yet.