Results for “date_required”

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

Overview

INV_VALIDATE_TROHDR is an Oracle EBS Applications (APPS) PL/SQL package that provides header-level validation logic for Transfer Order (TO) transactions within Oracle Inventory. Transfer Orders represent the movement of material between inventory organizations, and this package serves as the validation layer that ensures TO header data conforms to the rules defined for move orders and transfer orders prior to processing. It is classified as an OTHER API in the ETRM metadata and falls within the broader Transfer Order processing framework that includes companion packages such as INV_VALIDATE_TROLIN (line-level validation), INV_DEFAULT_TROHDR and INV_DEFAULT_TROLIN (defaulting logic), and INV_TRANSFER_ORDER_PVT (the core processing private API). The package is owned by the APPS schema and carries a VALID status in both the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

ETRM documents nine procedures and functions within this package. Their names indicate a structured validation architecture:

• HEADER — The primary validation entry point for the transfer order header record itself, orchestrating the overall header validation flow.
• HEADER_STATUS — Validates the header status value against permitted states within the transfer order lifecycle.
• STATUS_DATE — Performs validation of status-relevant date values applied to the transfer order header.
• DATE_REQUIRED — Determines whether a date attribute is mandatory in the current processing context, supporting conditional validation.
• REQUEST — Handles validation associated with the transfer order request reference.
• REQUEST_NUMBER — Validates the request number supplied on the header, typically ensuring uniqueness or consistency with the request context.
• ENTITY — Supports entity-level validation, verifying that the referenced entity (for example, source or destination organization) is valid.
• ATTRIBUTES — Validates descriptive flexfield or attribute column content on the transfer order header.
• ENTITY_DELETE — Validates or permits deletion processing against the associated entity.

Each routine contributes to a layered validation strategy, allowing callers to invoke granular checks or the consolidated HEADER routine as appropriate.

Tables Accessed

The package references two documented tables through APPS synonyms:

• MTL_PARAMETERS — The Inventory organization parameters table. Validation routines consult this table to confirm organization-level settings, including whether transfer order functionality is enabled and what defaulting or control rules apply to the inventory organization context.
• MTL_TRANSACTION_TYPES — The transaction type definition table. This is used to validate that the transaction type associated with the transfer order is valid, enabled, and permitted for the movement being requested.

In addition, the package depends on the FND_API foundation package and INV_MOVE_ORDER_PUB, indicating reliance on standard Oracle API error-handling conventions and shared move order publication logic.

Usage Notes

INV_VALIDATE_TROHDR is an internal validation utility rather than an end-user-facing interface. It is invoked programmatically by other packages in the Transfer Order stack. Per the ETRM dependency data, it is referenced by INV_DEFAULT_TROHDR, INV_DEFAULT_TROLIN, INV_TRANSFER_ORDER_PVT, INV_VALIDATE_TROLIN, and by itself, confirming its role as a shared validation service. In practice, validation is triggered from the Transfer Orders and Move Orders forms, from concurrent programs that process pending transfer order headers, and from custom extensions that create or modify transfer orders through the published APIs. Because the package resides in the APPS schema and its procedures are not documented as a public API surface, custom code should prefer calling the supported INV_TRANSFER_ORDER_PVT or move order public APIs, which in turn invoke this package. Direct invocation of INV_VALIDATE_TROHDR routines should be limited to scenarios where header-level validation must be re-executed independently, and callers must respect the FND_API error-handling contract expected by the surrounding framework.