Search Results variable_b
Overview
APPS.INV_LABEL_PVT9 is a private PL/SQL package body within the Oracle E-Business Suite Inventory (INV) module responsible for generating label variable data used in barcode and label printing. It forms part of the INV_LABEL API family, a set of sibling packages (INV_LABEL_PVT1 through INV_LABEL_PVTn) that partition label generation logic by label type or transaction category. INV_LABEL_PVT9 specifically targets WIP container label content, as reflected in the internal trace tag LABEL_WIP_CONT. The package supports the "Custom Labels" project introduced in 11i10, which extended the label framework to permit user-defined SQL statements and variables within label templates.
The package body declares a set of XML-style string constants (label_b, label_e, variable_b, variable_e, tag_e) that delimit label and variable sections in the generated template output. The identifier variable_b corresponds to the literal <variable name= ", used when emitting variable placeholder tags. These constants are concatenated with fnd_global.local_chr(10) to produce platform-appropriate line terminators.
Key Procedures and Functions
The package exposes a single public procedure, GET_VARIABLE_DATA (the only documented routine; a private TRACE helper also exists but is not part of the public API). GET_VARIABLE_DATA is responsible for resolving the variable content associated with a given label type and transaction context, populating an out parameter of type inv_label.label_tbl_type along with standard EBS concurrent-style out parameters for message count, message data, and return status. It accepts a label_type_rec describing the label, a transaction identifier, a row from mtl_material_transactions_temp, and a numeric transaction identifier. The procedure therefore acts as the variable-resolution entry point called by the master INV_LABEL driver when printing WIP container labels.
Tables Accessed
INV_LABEL_PVT9 queries a broad set of Inventory, WIP, Costing, Purchasing, and Projects tables through APPS synonyms to assemble label variables. MTL_MATERIAL_TRANSACTIONS_TEMP supplies the pending transaction data that drives the label. MTL_PARAMETERS, MTL_ITEM_LOCATIONS, MTL_LOT_NUMBERS, and MTL_TRANSACTION_LOTS_TEMP provide organization defaults, locator, and lot/serial context. WIP_DISCRETE_JOBS and WIP_ENTITIES supply work order and entity information, while BOM_DEPARTMENTS and CST_COST_GROUPS contribute departmental and costing group attributes. Requisition and sourcing references are drawn from MTL_TXN_REQUEST_LINES and PO_HAZARD_CLASSES. Project and task context comes from PA_PROJECTS, PA_PROJECTS_ALL, and PA_TASKS. FND_USER is referenced to capture user identity for audit and trace purposes.
Usage Notes
INV_LABEL_PVT9 is not intended for direct invocation by end users or custom integrations. It is called internally by the INV_LABEL package when a WIP container label type requires variable expansion, and it is referenced by one other package in the INV_LABEL API set. The package is invoked at runtime during label printing, typically from the Inventory transaction forms or from concurrent label-printing programs driven by the label definition and transaction data. The presence of standard out parameters (x_msg_count, x_msg_data, x_return_status) indicates it follows EBS API conventions for error propagation. Customizations should target the INV_LABEL public API rather than modifying this private package body, which is subject to patching. The embedded g_date_format_mask (Bug 2795525) ensures consistent date formatting across all label date fields.
-
APPS.INV_LABEL_PVT9 SQL Statements
12.2.2
-
APPS.INV_LABEL_PVT16 SQL Statements
12.2.2
-
APPS.INV_LABEL_PVT6 SQL Statements
12.1.1
-
APPS.INV_LABEL_PVT6 SQL Statements
12.2.2
-
APPS.INV_LABEL_PVT11 SQL Statements
12.2.2
-
APPS.INV_LABEL_PVT9 SQL Statements
12.1.1
-
APPS.INV_LABEL_PVT2 SQL Statements
12.2.2
-
APPS.INV_LABEL_PVT11 SQL Statements
12.1.1
-
APPS.INV_LABEL_PVT7 SQL Statements
12.1.1
-
APPS.INV_LABEL_PVT15 SQL Statements
12.1.1
-
APPS.INV_LABEL_PVT15 SQL Statements
12.2.2
-
APPS.INV_LABEL_PVT4 SQL Statements
12.2.2
-
APPS.INV_LABEL_PVT4 SQL Statements
12.1.1
-
APPS.INV_LABEL_PVT2 SQL Statements
12.1.1
-
APPS.INV_LABEL_PVT13 SQL Statements
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT9
12.1.1
-
APPS.INV_LABEL_PVT16 SQL Statements
12.1.1
-
APPS.INV_LABEL_PVT3 SQL Statements
12.1.1
-
APPS.INV_LABEL_PVT7 SQL Statements
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT9
12.2.2
-
APPS.INV_LABEL_PVT3 SQL Statements
12.2.2
-
APPS.INV_LABEL_PVT1 SQL Statements
12.1.1
-
APPS.INV_LABEL_PVT13 SQL Statements
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT16
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT7
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT6
12.2.2
-
APPS.INV_LABEL_PVT1 SQL Statements
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT6
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT16
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT7
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT2
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT2
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT4
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT11
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT15
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT11
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT4
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT5
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT5
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT15
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT13
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT13
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT3
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT1
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT1
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT3
12.2.2
-
APPS.INV_LABEL_PVT10 SQL Statements
12.1.1
-
APPS.INV_LABEL_PVT10 SQL Statements
12.2.2
-
PACKAGE BODY: APPS.INV_LABEL_PVT10
12.1.1
-
PACKAGE BODY: APPS.INV_LABEL_PVT10
12.2.2