Results for “inv_label”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.INV_LABEL is the core PL/SQL package responsible for label printing within Oracle Inventory. It assembles the XML label stream consumed by the Oracle label printing engine, resolves label formats and rules, expands variable values, and manages label request history and reprints. In the EBS 12.1.1 / 12.2.2 code line, the package body is identified by the header $Header: INVLABPB.pls 120.17.12010000.3 2008/12/15 14:03:00 satishku ship $, confirming it belongs to the long-lived 12.x source branch. Functionally, INV_LABEL bridges transactional inventory data — receipts, material transactions, serials, lots, LPNs, and on-hand quantities — and the label definition metadata stored in the label tables, producing either a rendered label, a manual-wrap document, or a raw variable set for a given format.

The package is declared as an OTHER API, meaning it is not formally classified as a public or private business API in ETRM, but it is nevertheless referenced by 48 other packages, making it a high-fan-in utility within the Inventory and shipping label ecosystem.

Key Procedures and Functions

Fifteen documented procedures and functions make up the public surface of the package:

• PRINT_LABEL — The principal label emission routine. It drives the sequence of resolving a format, gathering variable values, and producing the label output for a given label request.
• PRINT_LABEL_WRAP — A wrapping variant of PRINT_LABEL used when label content must be wrapped programmatically rather than relying solely on the format definition.
• PRINT_LABEL_MANUAL_WRAP — Implements explicit, caller-controlled line wrapping for label content.
• GET_VARIABLES_FOR_FORMAT — Returns the set of variables declared for a chosen label format, which the printing routines then populate.
• GET_DEFAULT_FORMAT — Retrieves the default label format applicable to the requested printing context.
• GET_FORMAT_WITH_RULE — Resolves the applicable label format by evaluating format selection rules rather than returning a fixed default.
• TRACE — Debug tracing utility. The package defines TRACE_LEVEL CONSTANT NUMBER := 12 and TRACE_PROMPT CONSTANT VARCHAR2(10) := 'LABEL_MAIN', so callers tracing with level 12 and prompt LABEL_MAIN receive the package's diagnostic output.
• GET_NUMBER_BETWEEN_RANGE — Expands range expressions (for example serial or container ranges) into an explicit table of values, honouring prefix and numeric-portion parsing.
• UPDATE_HISTORY_RECORD — Writes or updates the label request history row so that prior print activity is auditable.
• RESUBMIT_LABEL_REQUEST — Re-queues a previously submitted label request for printing.
• INV_LABEL_REQUESTS_REPRINT — Provides the reprint path for historical label requests.
• IS_ITEM_GTIN_ENABLED — Determines whether an item carries GTIN support, affecting barcode content in the label.
• GET_TXN_LPN_STATUS — Returns the LPN status associated with a transaction, which influences label content for licence-plate-numbered material.

Tables Accessed

The package reads and writes across the Inventory and Receiving schemas through APPS synonyms. Transactional sources include MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_SERIAL_NUMBERS, MTL_SERIAL_NUMBERS_TEMP, MTL_TRANSACTION_LOTS_TEMP, MTL_LOT_NUMBERS, RCV_TRANSACTIONS, and RCV_TRANSACTIONS_INTERFACE. Item and revision data come from MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, MTL_SYSTEM_ITEMS_KFV, MTL_ITEM_REVISIONS_B, and MTL_CROSS_REFERENCES (used for GTIN and barcode cross-reference resolution). On-hand and status lookups use MTL_ONHAND_QUANTITIES_DETAIL and MTL_MATERIAL_STATUSES. FND_USER is consulted for user context, typically when recording label request history and who requested or reprinted a label.

Usage Notes

INV_LABEL is normally invoked indirectly. Shipping and receiving forms, the label printing concurrent programs, and LPN/carton printing flows call into it rather than executing it directly, and its 48 dependent packages confirm that it sits beneath higher-level flows. Custom extensions that need label output should call the documented procedures (GET_FORMAT_WITH_RULE, GET_VARIABLES_FOR_FORMAT, PRINT_LABEL) rather than replicating format resolution logic. When troubleshooting, set trace level 12 with prompt LABEL_MAIN to capture the package's own diagnostics. Because the body defines the XML envelope constants (XML_HEADER1, XML_HEADER2, and the label tag constants), any change to label XML structure originates here and must remain compatible with the label.dtd definition.