Stock Requisition Applet(Internal)

Record a branch’s request for stock from another location — which items, how many, from where to where. It is a non-posting document: FINAL neither moves stock nor writes to the ledger, and the stock moves only when a Transfer Out is raised against it in the Stock Transfer applet, from that applet’s own search tab or from the CREATE ST button here. The approval settings screens in this applet have no effect today, because nothing here submits a requisition against them.

Overview

The Stock Requisition (Internal) applet records a branch’s request for stock from another location: which items, how many, from which location (sending) to which location (receiving). The document it creates is the Requisition Out (server document type INTERNAL_STOCK_REQUISITION, short code STKREQ). It is a non-posting document: FINAL neither moves stock nor writes to the general ledger, because both signums are fixed at 0 on the server (see Lifecycle and effects). The stock actually moves when a Transfer Out is raised against the requisition in the Stock Transfer applet — either by that applet’s Search Document › Stock Requisition tab or by the CREATE ST button here.

The applet also carries a per-line Line Items listing, a CSV File Import, and a set of settings screens (Branch Designation, Approval Settings, Custom Field Placement, Spreadsheet View) that were added for the optional position-based approval workflow. BigLedger’s approval engine does support this document type, but this applet gives you nowhere to submit a requisition against a setting — there is no approval tab on the document, no Approval Request screen and no Approval History screen — so a setting created here has no effect today. See Configuration and the Document Approvals guide.

Where it fits

Module: Inventory.

Screens and menus

Left menu

• Requisition Out — the document listing. Columns (each hideable, see Configuration): document numbers (tenant / company / branch), branch, transaction date, client document type and references, posting status, quantity ordered / received / outstanding, knock-off document from / to, remarks, reference, created date. Buttons: + (create), FINAL, DISCARD, VOID, DRAFT, CREATE ST, PRINT, plus a column toggle and Advanced Search. FINAL acts on every selected row that is not FINAL; DISCARD on selected DRAFT rows; VOID and DRAFT on selected rows that are FINAL and ACTIVE; CREATE ST only when every selected row is FINAL and none has already been knocked off to another document (the KO Doc To column is empty); PRINT on the selection using the default printable format.
• Line Items — a cross-document listing of requisition lines: SQ#, transaction date, item code, item name, location from, location to, qty ordered, qty received, qty outstanding, creation / updated date. Rows open a line editor with Item Details, Costing Details (hideable), Pricing Details, Issue Link and the Serial / Batch / Bin tab that matches the item’s sub-type.
• File Import — CSV upload of requisitions (see Fields › File Import) and a listing of import jobs with their process status and error message.

The left-menu entries Line Items and File Import are removed when the settings HIDE_LINE_ITEMS_MENU / HIDE_FILE_IMPORT_MENU are on, unless the user holds the matching SHOW_LINE_ITEMS_MENU / SHOW_FILE_IMPORT_MENU client-side permission.

Create screen — pressing + first creates a TEMP document on the server (so a document GUID exists before you type anything), then opens the form. Tabs: Details, Line, KO For (only Purchase GRN). With VERTICAL_ORIENTATION on, the same three sections render as expansion panels instead of tabs; the personal setting Tab Orientation then chooses which of the two layouts the current user sees.

View / edit screen — buttons RESET, FINAL, DRAFT, VOID, SAVE, CREATE ST, DISCARD, and a DELETE button when SHOW_DOCUMENT_DELETE_BUTTON is on. Sections: Details, Line (with sub-tabs Standard View and Spreadsheet View depending on the Spreadsheet View configuration), Doc Link, Attachment, Export. The order of the sections is what an administrator dragged into place under Settings › Default Selection; Doc Link, Attachment and Export can be hidden individually.

Adding a line — the item picker (Search Item) lists items with or without their stock balance; the line form then shows Item Details, Delivery Instruction, Department, Costing Details, Pricing Details, Issue Link and, by item sub-type, Serial Number / Batch Number / Bin Number.

Settings menu (System Configuration): Application Settings, Default Selection, Printable Format Settings, Branch Designation, Approval Settings, Custom Resource Bundle Configuration, Custom Field Placement, Spreadsheet View configuration. The routes additionally expose Webhook, Feature Visibility, Client-Side Permission, Permission Wizard, Permission Set, User / Team / Role Permission, Release Notes and Applet Log screens.

Personalization menu: Default Selection (Default Branch, Default Location, Tab Orientation), Sidebar.

Screenshots of this applet have not been added to this page yet (the previous page had none either).

Configuration

Before you can use it

• Locations — at least two active stock locations, linked to branches, in Warehouse Management. The sending and receiving drop-downs list the locations of the selected branch; without a branch selection they list every location.
• Location permission targets — the create button needs TNT_API_DOC_INTERNAL_STOCK_REQUISITION_CREATE_TGT_GUID (or tenant admin / owner). The Location (Sending) list is filtered to the locations targeted by the user’s TNT_API_DOC_INTERNAL_STOCK_REQUISITION_READ_TGT_GUID, the Location (Receiving) list to the targets of TNT_API_DOC_INTERNAL_STOCK_REQUISITION_LOCATION_TO_READ_TGT_GUID; tenant admins and owners see all locations. Assign these with the Permission Wizard under this applet’s Settings.
• Items — the items you will request, in Inventory Item Maintenance. Serial-, batch- and bin-tracked items add the corresponding tab on the line, but BigLedger does not check serial / batch quantities on a requisition (signum 0 — see Lifecycle).
• Knock Off Configuration (company level, Organisation › Company) — two rows matter here: Purchase GRN → Stock Requisition if you want the KO For › Purchase GRN tab to list anything, and Stock Requisition → Outbound Stock Transfer if you want the Stock Transfer applet’s Search Document › Stock Requisition tab to find FINAL requisitions. CREATE ST does not need the second row (it copies lines directly), but the transfer queue is only maintained when the row exists.
• Document numbering — a running number for INTERNAL_STOCK_REQUISITION on the company, otherwise the tenant / company / branch document numbers stay empty after FINAL.
• A printable format uploaded under Settings › Printable Format Settings and marked as default, otherwise PRINT has nothing to render.
• No GL codes, tax codes or cashbooks are involved: the document never posts.

Applet settings

Settings live in four places. Application Settings is the shared settings screen that document applets share. It shows this applet several hundred controls, and most of them save a key this applet never reads; the tables below list the ones that change something here. Default Selection, Printable Format Settings, Branch Designation, Approval Settings and Spreadsheet View configuration are applet-local screens. Custom Resource Bundle Configuration and Custom Field Placement are shared screens fed by this applet’s label list and screen registry. Personalization › Default Selection is per user. Anyone who can open the applet’s Settings menu can change tenant-wide settings; personal settings affect only the user who saves them.

Every key below has a control on a settings screen and is read by the applet. Defaults are the control’s initial value (all toggles start off; a fresh tenant sees everything until Application Settings is saved once).

Listing and buttons

Document header (Details)

Lines

Miscellaneous

Default Selection (applet-local) saves DEFAULT_BRANCH, DEFAULT_LOCATION, a default company, the default language and the drag-ordered list OUTBOUND_STOCK_REQUISITION_DETAILS_TAB_ORDER. Only the tab order and the language are consumed: the view screen sorts its sections by the saved order, and the language code selects the resource bundle. DEFAULT_BRANCH / DEFAULT_LOCATION are persisted but nothing on the create screen reads them — the Details form always starts with empty locations.

Personalization › Default Selection saves the same branch / location keys per user (also unread by the form) and DEFAULT_ORIENTATION (Tab Orientation), which the create and view screens honour when VERTICAL_ORIENTATION is on.

Spreadsheet View configuration stores, per line tab, a Line View Mode (standard only, spreadsheet only, or both tabs; default standard only) and, per column, label, visible, editable and order. The inline line grid on the create and view screens builds its columns from this configuration.

Custom Field Placement registers two screens for custom fields: Internal Stock Requisition › Details (12 slots after Doc Short Code, the three document numbers, Good Issue Date, Location (Sending), Driver Code, Tracking ID, Location (Receiving), Remarks, Reference #, Doc Description) and Line Details (12 slots after GRN No., ST-GRN ID, Location From / To, Item Code, Tracking ID, Item Name, Quantity, UOM, Doc Reference, Doc Description, Remarks).

Custom Resource Bundle Configuration relabels the applet’s texts (menu names, Location From / Location To, Stock Requisition Good Issue Date, Created By, Created Date, button captions such as FINAL).

Further keys on the shared Application Settings screen, read by the listing or the shell:

• Listing columns, each paired with a SHOW_* permission: HIDE_SERVER_DOC_1 / _2 / _3 (document numbers — the listing has only a Doc No (Tenant) column, so HIDE_SERVER_DOC_1 hides it for roles without SHOW_DOC_NO_TENANT, and _2 / _3 change nothing here), HIDE_TRANSACTION_DATE, HIDE_CLIENT_DOC_TYPE, HIDE_CLIENT_DOC_1 … _5, HIDE_ARAP_PNS, HIDE_ARAP_SETTLEMENT, HIDE_ARAP_DOC_OPEN, HIDE_ARAP_CONTRA, HIDE_ARAP_BAL, SHOW_GL_DIMENSION, SHOW_SEGMENT, SHOW_PROFIT_CENTER, SHOW_PROJECT. The ARAP and dimension columns are always empty on a requisition.
• DEFAULT_STATUS — which document statuses the listing loads (ALL or on = every status; otherwise the named status; unset = ACTIVE only).
• DEFAULT_POSTING_STATUS — which posting statuses the listing loads (ALL or unset = every posting status; otherwise only the one named — DRAFT, FINAL, VOID or DISCARDED). This is the posting status, a separate column from the status above.
• SORT_ORDER — the listing’s sort: created date, updated date (the default) or transaction date, newest first.
• FUZZY_SEARCH_COLUMNS — the comma-separated columns the listing’s search box matches against. Unset, it searches the tenant document number, the five client document numbers and the reference.
• HIDE_LINE_ITEMS_MENU — removes the Line Items left-menu entry.
• HIDE_FILE_IMPORT_MENU — removes the File Import left-menu entry.
• SHOW_DOCUMENT_DELETE_BUTTON — shows DELETE on the view screen.
• HIDE_DOC_LINK_TAB, HIDE_ATTACHMENT_TAB, HIDE_EXPORT_TAB and EXPAND_DOC_LINK, EXPAND_ATTACHMENT, EXPAND_EXPORT — hide or pre-expand those view sections.

Read by the applet but with no control on any settings screen for this applet code (no screen in this applet sets them): HIDE_LISTING_BRANCH, HIDE_QTY_MAIN_LISTING, HIDE_AMOUNT_MAIN_LISTING, HIDE_QUOTATION, HIDE_ORDER, HIDE_DELIVERY_ORDER, HIDE_INVOICE, HIDE_OTHERS, SHOW_DESCRIPTION, SHOW_REMARKS_MAIN_LISTING, SHOW_REFERENCE_MAIN_LISTING, the relabel branch to job group switch (Branch Designation screen labels). ENABLE_FILTER_BY_TODAYS_TXN is read when the listing opens, but the date it computes is never sent with the search, so setting it changes nothing — the listing does not narrow to today’s documents.

Document behaviour settings

• Status flow — DRAFT → FINAL → VOID, with FINAL → DRAFT when SHOW_DRAFT_BUTTON is on and DISCARD for drafts. There is no custom-status hook in this applet.
• Posting — not configurable; the document never posts (see Lifecycle).
• Printables — one default format (PRINTABLE) chosen under Printable Format Settings; the same format serves PRINT on the listing and Export on the view screen.
• Approval — Approval Settings records an approval setting (code, name, submitter designation code, branch and company, server document type fixed to INTERNAL_STOCK_REQUISITION, total required approval levels, and per level a quorum, a logic — ANY_TO_APPROVE or ALL_TO_APPROVE — and an approver designation). Branch Designation creates approval designations per branch (each bound to one approval setting) and assigns employees to a designation with an approval level, and links employees to the branch with an approval rank. Nothing in this applet submits a requisition against these rows. BigLedger’s approval engine accepts INTERNAL_STOCK_REQUISITION and would run the levels, e-mails and history exactly as it does for a purchase order — but there is no way to submit from here: unlike the Purchase Order and Purchase Requisition applets this one has no approval tab on the document, no Approval Request screen and no Approval History screen. Separately, and true of every document type: the DRAFT → FINAL path itself contains no approval check, so FINAL never waits for an approval even where the loop is complete.
• e-Invoice — not applicable.

Settings in other applets that control this applet

Feature visibility / permissions

Server-side (targeted, assigned through the Permission Wizard; targets are locations): TNT_API_DOC_INTERNAL_STOCK_REQUISITION_CREATE_TGT_GUID, …_READ_TGT_GUID, …_UPDATE_TGT_GUID, …_DELETE_TGT_GUID, and TNT_API_DOC_INTERNAL_STOCK_REQUISITION_LOCATION_TO_READ_TGT_GUID for the receiving-location list. File Import listings additionally require API_TNT_DM_ERP_INTERNAL_STOCK_REQUISITION_HDR_OWNER / _ADMIN / _READ. The + button appears only with the create permission (or tenant admin / owner); FINAL, DRAFT and VOID are checked against the update permission on the server.

Client-side permissions defined for this applet (24): SHOW_CREATE_STOCK_TRANSFER_BUTTON, SHOW_TRANSACTION_DATE (makes the Good Issue Date editable — without it the date picker is disabled for everyone), SHOW_COSTING_DETAILS, HIDE_PRICE (the one code that hides rather than shows: it removes every price, discount and UOM-ratio field of the Line Items editor at once, whatever the SHOW_* codes below say), and the per-field SHOW_* counterparts of the pricing toggles listed above (SHOW_UNIT_PRICE_STD_PRICING_SCHEME, SHOW_UNIT_PRICE_STD_INCL_TAX, SHOW_UNIT_PRICE_STD_EXCL_TAX, SHOW_UNIT_PRICE_STD_UOM_INCL_TAX, SHOW_UNIT_PRICE_STD_UOM_EXCL_TAX, SHOW_UNIT_PRICE_NET_UOM_EXCL_TAX, SHOW_UNIT_PRICE_NET_EXCL_TAX, SHOW_UNIT_DISCOUNT, SHOW_UNIT_DISCOUNT_UOM_EXCL_TAX, SHOW_UNIT_PRICE_TXN_UOM_INCL_TAX, SHOW_UNIT_PRICE_TXN, SHOW_QTY_BASE, SHOW_QTY_UOM, SHOW_UOM_TO_BASE_RATIO, SHOW_AMOUNT_STD_EXCL_TAX, SHOW_DISCOUNT_AMOUNT_EXCL_TAX, SHOW_AMOUNT_NET_EXCL_TAX, SHOW_AMOUNT_TXN, SHOW_TAX_CONFIG_SELECTION, SHOW_WHT_CONFIG_SELECTION).

Honoured by the applet but not yet defined for it (assigning them is not possible from the Client-Side Permission screen until they are): SHOW_GENDOC_FINAL_BUTTON, SHOW_GENDOC_DISCARD_BUTTON, SHOW_GENDOC_VOID_BUTTON, SHOW_DRAFT_BUTTON, SHOW_LINE_ITEMS_MENU, SHOW_FILE_IMPORT_MENU, SHOW_KO_DOC_FROM, SHOW_KO_DOC_TO, and the SHOW_* partners of the listing-column keys (SHOW_DOC_NO_TENANT, SHOW_TRANSACTION_DATE is the one exception that is defined, SHOW_CLIENT_DOC_TYPE, SHOW_ARAP_*, SHOW_QTY_MAIN_LISTING, …).

Fields

Details

Doc Short Code (always STKREQ) sits at the top, view only. The three document numbers are counters BigLedger keeps for this document type, so there is no numbering to set up in another applet; the company and branch numbers are drawn in the step that makes the document FINAL.

Line (item form)

Item Code comes from the item picker and is required; Item Name follows the item.

KO For › Purchase GRN

Lists GRN documents that have open-queue rows with source type INTERNAL_PURCHASE_GOODS_RECEIVED_NOTE and target type INTERNAL_STOCK_REQUISITION; search by keyword, document number, reference, branch and date range. Selecting lines copies them with quantity = open quantity and creates DRAFT-status links back to the GRN lines.

File Import

CSV only: the upload screen offers a delimiter choice and the drop zone, nothing else, and the file is processed as stock requisitions. Column headers, in any order: LOCATION_CODE_FROM, LOCATION_CODE_TO, HDR_REFERENCE_NO, TXN_DATE, ITEM_CODE, QTY, HDR_REMARKS, HDR_DESCRIPTION, ITEM_NAME, ITEM_REF_NO, ITEM_REMARKS, ITEM_DESCRIPTION, UOM, POSTING_STATUS. Rows are grouped into Requisition Out documents with the posting status from the file (default DRAFT). A document whose rows say FINAL is created and then put through the same FINAL step as the FINAL button — running numbers drawn, open-queue rows created per the Knock Off Configuration — with the serial and stock-balance checks switched off. That makes the import a way to raise a batch of ready-to-fulfil requisitions from a replenishment spreadsheet without opening each one; leave the column DRAFT (or empty) when someone should check them first. The job records Wrong Columns: …, Mandatory Columns Missing: … or Empty CSV File in the import’s error message.

Lifecycle and effects

Statuses — a requisition carries two separate fields: its status (TEMP, ACTIVE, …) and its posting status (empty, DRAFT, FINAL, VOID). + creates a TEMP document with no posting status; the first save sets the status to ACTIVE and still leaves the posting status empty. The listing shows an empty posting status as DRAFT, and DISCARD treats empty and DRAFT alike, so to the reader it behaves as a draft — but a report or API query that filters on posting status = DRAFT will not find a requisition that has only been saved. FINAL sets the posting status (bulk from the listing, single from the view). VOID (FINAL and ACTIVE only), DRAFT (FINAL → DRAFT) and DISCARD (DRAFT and ACTIVE only) are the other transitions. Locations are locked once FINAL.

Posting proof:

FINAL validation that applies: a refusal when the date falls in a LOCK_ALL / LOCK_TXN period (only the two stock-transfer types are exempt); a second FINAL is refused with Generic Document has already been posted to FINAL; serial, batch and stock-balance checks skip signum-0 lines unless the caller sends the signum-zero validation flags, which this applet does not.

FINAL → DRAFT and VOID — the server requires the document to be FINAL and refuses ("… has already been linked with the following documents: OBDSTF-…") when any ACTIVE link has this requisition as its source — i.e. after a Transfer Out was created from it (CREATE ST or the Stock Transfer applet’s knock-off). The DRAFT button shows the server’s message; the VOID button replaces it with The stock requsition has already been returned. Remove or void the transfer first.

CREATE ST (listing: enabled only when every selected row is FINAL and has no knock-off-to document yet; view screen: enabled only when the document is FINAL and has no link to a Transfer Out yet) — the applet creates a TEMP INTERNAL_OUTBOUND_STOCK_TRANSFER document and asks the server to knock the requisition off into it. The knock-off requires the target to be a fresh TEMP document (Target Gen Doc is not in TEMP status) and copies every ACTIVE requisition line at its full quantity: for a Transfer Out target the server does not subtract what earlier transfers already took (read from the code, not tried). It creates one link per line for that quantity, copies the header’s sending / receiving locations in the same order (the swap applies only to inbound transfers), tracking id, reference and external references, updates the requisition’s open-queue rows if the Knock Off Configuration created any, and skips the same-entity-and-branch check for this target type. The result is a new, unfinalised Transfer Out in the Stock Transfer applet; stock moves when that transfer is finalised there. The success toast is Stock Transfer Succesfuly Created.

What stops a second Transfer Out is the screen, not the server. The greyed-out CREATE ST button is the only guard: a requisition that already has a Transfer Out cannot be sent again from this applet. Anything that calls the knock-off directly — an integration, a script — gets a second Transfer Out for the whole quantity, and finalising both ships the stock twice. If you integrate, check the requisition’s links first. Partial fulfilment (sending part now, the rest later) is done from the Stock Transfer applet’s Search Document › Stock Requisition tab, which works from the open quantity, not from CREATE ST.

Permissions CREATE ST needs — two, both outside this applet’s own: the create permission for the Transfer Out (INTERNAL_OUTBOUND_STOCK_TRANSFER), targeted at the sending location, for the TEMP transfer; and the generic document-link create permission (API_TNT_DM_ERP_GENERIC_DOC_LINKS_CREATE) for the knock-off. Missing the first gives Creation Error; missing the second refuses the knock-off and leaves an empty TEMP transfer behind.

Related applets

• Stock Transfer — the document that fulfils the requisition and moves the stock; its Transfer Out knocks the requisition off (or is created from it by CREATE ST).
• Purchase GRN (Internal) — the only document the requisition can knock off (KO For › Purchase GRN).
• Organisation — company Knock Off Configuration, branches, document numbering.
• Warehouse Management — the sending and receiving locations.
• Inventory Item Maintenance and Doc Item Maintenance — the items requested.
• Employee — employees assigned to approval designations under Branch Designation.
• Stock Balance and Stock Availability — where to check what the sending location actually holds; the requisition itself changes neither.

Troubleshooting

Related documentation

• Stock Transfer — the fulfilment document.
• Purchase GRN (Internal) — the upstream knock-off source.
• Organisation — Knock Off Configuration.
• Inventory module.