Search Results validate_item_no

Overview

APPS.GMF_VALIDATIONS_PVT is a private PL/SQL package belonging to the Oracle Process Manufacturing (OPM) / Process Manufacturing Financials (GMF) product family in Oracle E-Business Suite. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking session rather than the definer, a common pattern for shared validation libraries that must respect the caller's security context. Its declared purpose is to centralize validation logic for OPM master data: calendars, accounting periods, cost methods and cost types, analysis codes, company and organization codes, warehouses, inventory items (item IDs and item numbers), cost component classes, GL classes, formula effectiveness records, resources, allocation IDs and basis accounts, and usage units of measure. Because validation rules for these reference entities are shared by many OPM forms and APIs, encapsulating them in a single _PVT package avoids duplicated logic and inconsistent error handling across the suite. The header comment shows the file as GMFVVALS.pls, last shipped at version 120.6.12020000.2 (July 2012), placing it within the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

The package exposes 55 documented procedures and functions. For most validations a FUNCTION form returns BOOLEAN (or, for cost type, NUMBER), while a companion PROCEDURE form returns one or more OUT parameters carrying descriptive attributes.

• VALIDATE_CALENDAR_CODE — validates a calendar code against CM_CLDR_HDR; the procedure form additionally returns the owning company code and default cost method code for the calendar.
• VALIDATE_PERIOD_CODE — confirms a period code belongs to the supplied calendar and returns the period status.
• VALIDATE_COST_MTHD_CODE — checks a cost method code; the procedure form returns the associated cost type, rollup/raw material calculation type, and production calculation type.
• VALIDATE_COST_TYPE_CODE — overloaded function returning a numeric indicator for the cost type implied by a cost method, with a variant accepting an explicit type argument.
• VALIDATE_ANALYSIS_CODE — verifies a cost analysis code exists in CM_ALYS_MST.
• VALIDATE_COMPANY_CODE and VALIDATE_ORGN_CODE — validate company and organization codes against the OPM organization master.
• VALIDATE_WHSE_CODE — validates a warehouse code.
• VALIDATE_ITEM_ID, VALIDATE_ITEM_NO, VALIDATE_ITEMCOST_CLASS — validate inventory item identifiers, item numbers, and item cost class assignments; direct relevance to the search term validate_inventory_item_id, which in OPM tooling maps to VALIDATE_ITEM_ID operating on IC_ITEM_MST.ITEM_ID.
• VALIDATE_COST_CMPNTCLS_ID / _CODE — validate cost component class identifiers and codes.
• VALIDATE_GL_CLASS — validates a GL class used for cost accounting integration.
• VALIDATE_FMEFF_ID — validates a formula effectiveness record.
• VALIDATE_RESOURCES — validates production resources.
• VALIDATE_ALLOC_ID and FETCH_ALLOC_ID — validate and retrieve allocation identifiers.
• VALIDATE_BASIS_ACCOUNT_KEY — validates a GL allocation basis account key.
• VALIDATE_USAGE_UM — validates the usage unit of measure for an item or resource.

Tables Accessed

Reads are performed through APPS synonyms against OPM reference tables: CM_CLDR_HDR and CM_CLDR_HDR_B (calendar headers), CM_CLDR_DTL (period lines), CM_MTHD_MST (cost methods), CM_ALYS_MST (cost analyses), CM_ADJS_DTL (adjustment details), CM_CMPT_MST (cost components), CR_RSRC_MST (resources), GMF_PERIOD_STATUSES (period statuses), GL_ALOC_MST and GL_ALOC_BAS (GL allocations and bases), FM_FORM_EFF (formula effectiveness), IC_ITEM_MST (items), IC_LOTS_MST (lots), IC_GLED_CLS (GL classes), and SY_ORGN_MST for company/organization validation. The package performs existence and attribute lookups; no significant writes are documented.

Usage Notes

GMF_VALIDATIONS_PVT is referenced by seven other packages, indicating it functions as a shared validation service layer rather than a standalone API. It is typically invoked from OPM setup and transaction forms, from concurrent programs that pre-validate imported reference data, and from custom extensions that must apply the same item, calendar, period, and cost method rules as standard OPM. Custom code should call the public procedure/function signatures and never rely on internal implementation, since the package is classified PVT and its body may change between patches.