Results for “line_status”

50+ results




Overview
Explore in AI Chat

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

Overview

INV_VALIDATE_TROLIN is an Oracle E-Business Suite validation package that belongs to the Inventory (INV) module and supports the Transfer Order (TO) processing framework. The package body, registered under the APPS schema, provides attribute-level and business-rule validation for transfer order lines. It works in conjunction with its companion header-level validator, INV_VALIDATE_TROHDR, and is designed to be called before a transfer order line is inserted, updated, or processed through the Inventory transaction engine. The API classification is listed as OTHER, indicating that the package is treated as an internal validation utility rather than a public transactional API, although it exposes callable functions that can be reused in custom extensions. The package header comment references version 120.12.12020000.2, and the implementation traces its lineage to the Inventory transaction and move-order validation logic introduced in earlier 11i releases and retained in 12.1.1 and 12.2.2.

Key Procedures and Functions

  • LINE — Validates that a line identifier has been supplied. It raises the standard INV_ATTRIBUTE_REQUIRED message when the line ID is null or equal to FND_API.G_MISS_NUM.
  • LINE_NUMBER — Confirms that the line number is present and unique within the transfer order header, invoking INV_Transfer_Order_PVT.Unique_Line and reporting INV_ALREADY_EXISTS when a duplicate is detected. A fix tied to Bug 4347016 ensures a clear error message is returned for non-unique line numbers.
  • LINE_STATUS — Validates the value supplied for the transfer order line status, ensuring it maps to a permitted state before the line is processed.
  • QUANTITY_DELIVERED — Verifies the delivered quantity on the line, applying business rules that prevent negative, excessive, or otherwise invalid quantities.
  • QUANTITY_DETAILED — Validates the detailed quantity associated with the line, typically used when lot, serial, or subinventory detail is captured.
  • SECONDARY_QUANTITY_DELIVERED — Applies the same delivery quantity checks for secondary units of measure, where the item supports dual UOM tracking.
  • SECONDARY_QUANTITY_DETAILED — Validates secondary detailed quantities captured against the line.
  • ENTITY — Performs entity-level validation, confirming that the referenced inventory entity exists and is valid for the transfer order context.
  • ATTRIBUTES — Executes the collective attribute checks for a transfer order line, aggregating the individual validations described above.
  • ENTITY_DELETE — Handles validation logic used when a line or its associated entity is being deleted from the transfer order.
  • INIT — Initializes package-level global state, including the organization identifier and the WMS organization flag, before the validation routines are invoked.

Tables Accessed

The package validates against core Inventory and transfer order tables accessed through APPS synonyms. MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, and MTL_SYSTEM_ITEMS_KFV are used to confirm item validity, while MTL_TXN_REQUEST_HEADERS anchors the header context for line validation. MTL_ITEM_LOCATIONS, MTL_LOT_NUMBERS, MTL_SERIAL_NUMBERS, and MTL_ITEM_SUB_INVENTORIES support location, lot, serial, and subinventory checks performed through the quantity and entity routines. MTL_SECONDARY_INVENTORIES and MTL_PARAMETERS provide organizational context, MTL_TRANSACTION_TYPES supports transaction type validation, and WIP_ENTITIES is referenced for entity resolution where work-in-process entities are involved.

Usage Notes

INV_VALIDATE_TROLIN is typically invoked from the Inventory Transfer Order forms, from concurrent programs that process transfer order lines in batch, and from custom code that needs to enforce the same line-level validation rules before calling the transfer order transaction APIs. The package is referenced by two other packages, which indicates it is a shared validation component within the Inventory module. Customizations should call the individual functions rather than bypassing them, since the routines add messages to the FND_MSG_PUB stack and return Boolean-style result codes consistent with the FND_API conventions used throughout Inventory. Trace output can be enabled through the INV_DEBUG_TRACE profile option.