Search Results inv_default_trohdr




Overview
Explore in AI Chat

Overview

INV_DEFAULT_TROHDR is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, carrying a VALID status in both release 12.1.1 and 12.2.2. Its role is to supply defaulting logic for transfer order headers within the Oracle Inventory module. The package name itself reflects its purpose: "INV" for Inventory, "DEFAULT" for the defaulting behavior it performs, and "TROHDR" for Transfer Order He. In EBS, transfer orders are the documents used to move material between organizations and, where enabled, between subinventories. The transfer order header is the parent record that captures the shipping and receiving organizations, the transaction type, the date required, and related control attributes before lines are attached.

INV_DEFAULT_TROHDR packages the rules that determine what those header attributes should be when a user creates a transfer order but does not explicitly supply every value. Rather than forcing the operator to key every field, the form or calling program invokes this package to derive sensible defaults from inventory setup data. In this way the package enforces consistency between transfer order documents and the underlying Inventory organization configuration.

Key Procedures and Functions

ETRM documentation records two entry points for this package: LOAD_REQUEST_HEADER and ATTRIBUTES. Consistent with Oracle naming conventions, ATTRIBUTES is the defaulting routine. It is responsible for populating the header-level attribute structure with values derived from inventory setup, such as the source organization, destination organization type, and related control flags. It supplies the caller with a complete header record rather than a partial one.

LOAD_REQUEST_HEADER is the loading routine. It takes the request context supplied by the caller and assembles the transfer order header information into the structure the inventory transfer order application programming interface expects. Together the two procedures separate concerns: ATTRIBUTES determines what the defaults should be, and LOAD_REQUEST_HEADER places the resulting header data into the form the downstream API can consume. The documentation does not publish parameter lists, and none are inferred here.

Tables Accessed

Per the documented metadata, the package references two tables through APPS synonyms: MTL_PARAMETERS and MTL_SECONDARY_INVENTORIES. MTL_PARAMETERS holds the organization-level Inventory parameters, including defaults that govern how transactions and documents behave within a given inventory organization. Reading it allows the package to derive header defaults that are consistent with the organization's configured behavior.

MTL_SECONDARY_INVENTORIES stores the subinventory definitions for each organization, including subinventory status and attributes. The package consults it when a transfer order header involves subinventory-level movement, ensuring the defaulted subinventory is valid and active for the organization in scope. Access through APPS synonyms confirms the package executes with the standard EBS schema indirection rather than referencing base tables directly.

Usage Notes

INV_DEFAULT_TROHDR is an internal helper rather than an end-user-facing API. The dependency information shows it is referenced by INV_TRANSFER_ORDER_PVT and by itself, while it in turn depends on INV_MOVE_ORDER_PUB and the SYS.STANDARD package. The reference from INV_TRANSFER_ORDER_PVT is significant: that private package carries the core transfer order processing logic in Oracle Inventory, and it calls INV_DEFAULT_TROHDR when it needs header attributes defaulted during transfer order creation.

Typical invocation therefore occurs indirectly, when a user creates or processes a transfer order through the Inventory transfer order forms or through concurrent processing that builds transfer orders programmatically. Custom code should not generally call INV_DEFAULT_TROHDR directly, because its interface is unsupported and may change between patch levels. Developers extending transfer order behavior are advised to use the supported public APIs, such as INV_MOVE_ORDER_PUB, and to treat INV_DEFAULT_TROHDR as an implementation detail of the standard transfer order flow.