Results for “check_min_max_dates”

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

Overview

DT_API is a PL/SQL package owned by the APPS schema and classified in the ETRM repository as an API. It belongs to the DateTrack (DT) infrastructure of Oracle E-Business Suite, the framework that governs how datable ("DateTracked") entities maintain multiple effective-dated versions of the same logical record. In Oracle EBS 12.1.1 and 12.2.2 this package centralizes the logic used to evaluate effective dates and to decide which DateTrack maintenance mode applies to a given row before any DML is issued.

The package header (dtapiapi.pkh, version 120.0, dated 2005/05/27) shows a deliberately small, stable surface consisting of date-comparison and mode-resolution utilities. Rather than performing inserts, updates or deletes itself, DT_API answers questions: what is the latest effective end date for a row, does a row exist within a given date range, and which update or delete mode should the caller use. The fact that the package is referenced by 1,739 other packages confirms its role as a foundational dependency shared across DateTracked application modules and their generated APIs. The "e devt" search string corresponds to the ETRM naming convention for DateTrack-related developer objects.

Key Procedures and Functions

• RETURN_MAX_END_DATE — Returns the maximum effective_end_date for a specified base table and primary key. This is a private function and returns NULL when no rows exist for the supplied table and key values.
• FIND_DT_UPD_MODES — A public procedure that derives the applicable DateTrack update modes for a record, including correction, update, update override, and update change insert.
• FIND_DT_DEL_MODES — The delete-side counterpart, returning the DateTrack delete modes that apply to a record for a given effective date and key.
• VALIDATE_DT_MODE — Validates that a requested DateTrack mode is legal in the current context.
• VALIDATE_DT_UPD_MODE — Mode-specific validation for update operations.
• VALIDATE_DT_DEL_MODE — Mode-specific validation for delete operations.
• GET_OBJECT_VERSION_NUMBER — Retrieves the object version number used for optimistic locking on DateTracked rows.
• ROWS_EXIST — Determines whether any rows exist for the supplied table and key criteria.
• CHECK_MIN_MAX_DATES — Verifies that requested date ranges fall within the permitted minimum and maximum bounds.
• FIND_DT_UPD_MODES_AND_DATES — Combines mode resolution with the effective dates that the update would produce.
• FIND_DT_DEL_MODES_AND_DATES — Combines delete-mode resolution with the associated effective dates.

Tables Accessed

The documented table reference for DT_API is the APPS synonym PLITBLM, which serves as the generic lookup table for DateTrack mode information. The package's public routines are parameterized by p_base_table_name, p_base_key_column and p_base_key_value, meaning that callers supply the target DateTracked table and its primary key; DT_API then reads the effective-dated rows of that base table to compute maximum end dates and mode outcomes. No direct DML against application data is documented, consistent with the package's classification as a decision and validation API.

Usage Notes

DT_API is invoked indirectly rather than by end users. DateTracked PL/SQL APIs, Forms-based "DateTracked" blocks, and concurrent programs call it to resolve which mode applies before issuing their own DML, ensuring consistent behavior across the 12.1.1 and 12.2.2 file systems. Custom code extending DateTracked entities should treat DT_API as the authoritative source for mode validation, row existence checks, and object version numbers rather than reimplementing this logic. Because the package is referenced by 1,739 dependent objects, changes to its behavior should be assessed for broad downstream impact, and the package body carries no ship flag, indicating it is supplied as a standard seeded component.