Search Results inv_validate




Overview
Explore in AI Chat

Overview

APPS.INV_VALIDATE is a foundational server-side validation package within Oracle Inventory (INV) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its central purpose is to enforce data integrity and business rules before inventory transactions, records, and descriptive attributes are committed to the database. Because inventory transactions touch a large number of dependent entities — items, subinventories, locators, lot and serial numbers, revisions, material statuses, and accounting flexfields — INV_VALIDATE consolidates the corresponding validation logic into a single reusable package rather than replicating checks across forms, concurrent programs, and PL/SQL APIs.

In the ETRM metadata the package is classified with an API classification of OTHER, and it is documented with 60 procedures and functions. It is marked as VALID in the APPS schema. Notably, the metadata records that the package is referenced by 45 other packages, confirming its role as a shared, low-level utility rather than a user-facing API.

Key Procedures and Functions

The documented entry points are predominantly single-column validation routines. Each is responsible for verifying that a supplied value for a specific inventory attribute is valid in the current context and returning an appropriate result or error.

  • GET_ATTR_TBL — Returns the attribute table structure used by the validation framework, providing the set of columns and descriptors the package evaluates.
  • CONCAT_SEGMENTS — Builds a concatenated key/value flexfield segment string, typically used when validating accounting or descriptive flexfield combinations.
  • DESC_FLEX — Validates and resolves descriptive flexfield segment values against the flexfield definitions.
  • CHECK_CREATION_UPDATION — Confirms that creation and update audit conditions are satisfied before a record is written.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO-column validators that verify audit information against the FND_USER registry.
  • CHECK_DATE — Validates the reasonableness and format of a supplied date value.
  • CONVERSION_RATE — Validates currency conversion information used for inventory valuation and accounting entries.
  • DESCRIPTION — Validates descriptive text supplied for an inventory entity.
  • EMPLOYEE — Confirms that a referenced employee exists and is valid as an actor or owner on a transaction.
  • FROM_SUBINVENTORY, TO_SUBINVENTORY — Validate the source and destination subinventories for a transfer, including material status and item eligibility.
  • ORGANIZATION — Validates the inventory organization context against organization definitions and parameters.
  • TO_ACCOUNT — Validates the destination accounting flexfield combination.
  • PROGRAM, PROGRAM_APPLICATION, PROGRAM_UPDATE_DATE — Identify and validate the concurrent program and application context under which a process executes.

Tables Accessed

The package reads and validates against a broad set of inventory and financial tables, accessed through APPS synonyms. Transactional and master data sources include MTL_SYSTEM_ITEMS, MTL_ITEM_LOCATIONS, MTL_ITEM_REVISIONS, MTL_ITEM_SUB_INVENTORIES, MTL_SECONDARY_INVENTORIES, MTL_LOT_NUMBERS, MTL_SERIAL_NUMBERS, MTL_KANBAN_CARDS, MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_PARAMETERS, and MTL_TRANSACTION_TYPES. Financial and cross-application sources include CST_COST_GROUPS, GL_CODE_COMBINATIONS, FND_USER, and HZ_LOCATIONS. These are consulted to confirm existence, status, and eligibility of the values being validated.

Usage Notes

INV_VALIDATE is invoked primarily from inventory transaction forms, open interfaces, and the public INV transaction APIs, which call the individual validators to pre-screen data before processing. Custom extensions and concurrent programs that load inventory data should call the same routines to maintain consistency. Because the package is referenced by 45 other packages and is not itself referenced as a database object, it operates purely as internal validation infrastructure and should not be modified or called in ways that bypass its documented procedures.