Search Results validate_exp_action_date

Overview

APPS.INV_LOT_ATTR_PUB is a public PL/SQL package in Oracle E-Business Suite that centralizes validation logic for lot and grade attribute data managed by Oracle Inventory. Its header comment (INVVLOTS.pls, version 120.0) identifies it as the container for generic lot-attribute validation routines, beginning with grade code validation against item grade control and the MTL_GRADES table. In releases 12.1.1 and 12.2.2 the package remains the published interface used by Inventory forms, lot entry flows, and dependent application modules to confirm that lot-level attribute values comply with item, organization, and date rules before database changes are committed. Because the API is classified as PUB under the APPS schema, it is supported for direct invocation by custom code, subject to Oracle's API usage conventions. The package exposes ten documented programs, each scoped to a discrete validation or conversion concern, which allows callers to reuse Inventory's own error-message framework rather than reimplementing validation rules.

Key Procedures and Functions

• VALIDATE_GRADE_CODE — Confirms that a supplied grade code is valid for a grade-controlled item and exists in the grades table for the given organization.
• VALIDATE_MATURITY_DATE — Verifies that the maturity date is later than the origination date; assumes origination date validation has already been performed.
• VALIDATE_HOLD_DATE — Confirms that the hold date is later than the origination date, following the same precondition as maturity date validation.
• VALIDATE_EXP_ACTION_DATE — Validates the expiration action date associated with a lot, ensuring the action date is consistent with the lot's expiration and attribute date logic. This is the program referenced by the search term "validate_exp_action_date."
• VALIDATE_RETEST_DATE — Validates the retest date for a lot, applying the analogous date-ordering rules used for maturity and hold dates.
• VALIDATE_EXP_ACTION_CODE — Checks that the supplied expiration action code is a recognized value, typically drawn from the action codes maintained in MTL_ACTIONS.
• VALIDATE_REASON_CODE — Validates a transaction reason code against the reasons defined in MTL_TRANSACTION_REASONS.
• VALIDATE_ORIGINATION_TYPE — Confirms that the lot origination type is a permitted value.
• VALIDATE_CHILD_LOT — Validates a child lot relative to a parent lot, supporting genealogy and parent-child lot structures.
• CREATE_LOT_UOM_CONV_WRAPPER — Wrapper program that creates unit-of-measure class conversion entries for lots, persisting data through the lot UOM conversion table.

Tables Accessed

The package reads and writes the following tables through APPS synonyms. MTL_LOT_NUMBERS is the primary lot master table against which lot attributes and dates are validated. MTL_GRADES supplies the valid grade codes referenced by VALIDATE_GRADE_CODE. MTL_SYSTEM_ITEMS provides item-level attributes, notably the grade control flag, that determine whether grade validation is required. MTL_ACTIONS holds the valid expiration action codes used by VALIDATE_EXP_ACTION_CODE. MTL_TRANSACTION_REASONS supplies valid reason codes for VALIDATE_REASON_CODE. MTL_LOT_UOM_CLASS_CONVERSIONS stores the conversion records inserted by CREATE_LOT_UOM_CONV_WRAPPER.

Usage Notes

INV_LOT_ATTR_PUB is typically invoked from Oracle Inventory lot entry forms and lot attribute maintenance screens, and from concurrent or batch processes that import or update lot data. The package is referenced by three other packages, indicating that Inventory and adjacent modules call these validations internally. Custom code should invoke the individual validation functions before inserting or updating lot attributes, since each routine populates the standard return status, message count, and message data outputs, allowing callers to surface Inventory's own error messages. Because date validations assume prior validation of the origination date, callers must respect the documented ordering of calls. Direct modification of the underlying tables is not advised; the wrapper and validation programs are the supported integration points.