Search Results check_creation_updation

Overview

APPS.INV_VALIDATE is a public PL/SQL package in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that provides the central validation layer for Oracle Inventory (INV) transaction processing. Its principal business function is to supply reusable validation functions that confirm the integrity, legality, and contextual correctness of Inventory data before records are inserted, updated, or committed. Rather than embedding validation logic directly into each calling form or API, Oracle exposes INV_VALIDATE so that its generator-driven routines and hand-written checks can be shared across the Inventory schema.

The package carries the header identifier INVSVATS.pls 120.3 and is classified under ETRM as an OTHER API. It is referenced by 45 other packages and exposes 60 documented procedures and functions. A distinctive internal parameter, p_is_creation, is used to distinguish insertion-time validation from update-time validation, which is precisely the behavior surfaced by the searched term check_creation_updation.

Key Procedures and Functions

The package is organized around a generator-driven core, denoted by the START GEN validate marker, whose prototype block is extended automatically. Documented routines include:

• GET_ATTR_TBL — internal generator support routine that prevents duplication or overriding of existing validation functions; the source explicitly instructs "DO NOT MODIFY."
• CHECK_CREATION_UPDATION — determines whether a supplied user identifier represents a creation or an update, using the p_is_creation flag to return a validation result.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit-column validators ensuring WHO and WHEN columns are populated correctly.
• CONCAT_SEGMENTS — builds a concatenated key flexfield segment string from an application short name, key flexfield code, and structure number.
• DESC_FLEX — resolves a descriptive flexfield and returns its identifying number.
• CHECK_DATE — validates a date value against a supplied message.
• CONVERSION_RATE, DESCRIPTION, EMPLOYEE, ORGANIZATION, PROGRAM, PROGRAM_APPLICATION, PROGRAM_UPDATE_DATE — attribute validators for currency conversion, descriptive text, personnel, organization, and concurrent program context.
• FROM_SUBINVENTORY, TO_SUBINVENTORY, TO_ACCOUNT — location and account validators used during material movement.

Tables Accessed

INV_VALIDATE resolves its references through APPS synonyms. The primary Inventory tables include MTL_PARAMETERS, MTL_SYSTEM_ITEMS, MTL_SECONDARY_INVENTORIES, MTL_ITEM_LOCATIONS, MTL_LOT_NUMBERS, MTL_SERIAL_NUMBERS, MTL_TRANSACTION_TYPES, MTL_ITEM_REVISIONS, MTL_ITEM_SUB_INVENTORIES, MTL_KANBAN_CARDS, and MTL_MATERIAL_TRANSACTIONS_TEMP. These are read to confirm that organizations, items, subinventories, locators, lots, serials, and transaction types exist and are valid for the transaction in context. Supporting lookups include FND_USER, CST_COST_GROUPS, GL_CODE_COMBINATIONS, and HZ_LOCATIONS, used for user, costing, accounting, and party location validation respectively.

Usage Notes

INV_VALIDATE is invoked by Inventory forms, concurrent programs, and other PL/SQL packages during transaction entry and validation. Because it is referenced by 45 packages, it functions as shared infrastructure rather than an end-user API. Custom integrators typically call individual validation functions—particularly CHECK_CREATION_UPDATION, CREATED_BY, and the date validators—before performing direct DML, ensuring values conform to Inventory rules. The generator-managed section must not be edited; extensions should be placed outside the generate markers.