Results for “dt_api”

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

Overview

DT_API is a date-tracking API in the Oracle EBS Applications (APPS) schema, delivered as a PL/SQL package body and classified as an API object. The package encapsulates the business rules that govern the "DT" (date-track) mode assignments used across Oracle HRMS-derived functionality, providing a reusable, validated interface for determining which update and delete modes are permitted for date-tracked entities and for bounding those entities within valid date ranges. Its role is defensive and centralized: rather than embedding mode-validation and date-range logic in every calling form or concurrent program, the EBS codebase delegates that logic to DT_API, ensuring consistent behavior and a single point of maintenance.

The package body is documented as VALID and references a small, well-defined dependency set: APPS.DT_API (its own specification), FND_DATE, HR_API, HR_GENERAL2, and HR_UTILITY from the APPS schema, plus the PLITBLM PL/SQL table type and the SYS STANDARD package. This dependency profile confirms that DT_API is an HR-family utility leaning on Oracle's HR date and general-purpose utilities. It is a heavily depended-upon leaf node: the ETRM metadata records that DT_API is referenced by 1,739 other database objects while itself being referenced by none of them in a downstream direction, indicating it sits near the bottom of the dependency hierarchy as core shared infrastructure.

Key Procedures and Functions

The documented interface exposes thirteen procedures and functions. The core validation routines are VALIDATE_DT_MODE, VALIDATE_DT_UPD_MODE, and VALIDATE_DT_DEL_MODE, which enforce that a supplied date-track mode (and specifically the update or delete mode variant) is one of the permitted values. The lookup routines FIND_DT_UPD_MODES and FIND_DT_DEL_MODES return the set of valid update modes and delete modes respectively, while FIND_DT_UPD_MODES_AND_DATES and FIND_DT_DEL_MODES_AND_DATES extend those lookups by returning associated date information alongside the mode. RETURN_MAX_END_DATE supplies the effective maximum end date used to bound date-tracked records.

The remaining routines are supporting utilities. GET_OBJECT_VERSION_NUMBER implements optimistic locking by returning the object version number, a standard EBS concurrency-control idiom. ROWS_EXIST performs an existence check, typically used to determine whether a given date-tracked row is already present before insert, update, or delete. CHECK_MIN_MAX_DATES validates that a supplied date range falls within the permitted minimum and maximum bounds. Together these routines form a complete, self-contained date-track service: validate the mode, locate the mode (with or without dates), verify that the row exists, confirm the date range, and read the version number.

Tables Accessed

The ETRM metadata documents only one table reference for this package, reached through an APPS synonym: PLITBLM. PLITBLM is the standard PL/SQL table (index-by table) type used throughout EBS for passing collections of IDs or values into and out of PL/SQL APIs; it is not a business data table in the conventional sense. The absence of other documented table references indicates that DT_API operates primarily on data supplied by its callers and on date-track mode metadata rather than persisting rows directly. Where mode and date values are derived from underlying HR date-track configuration, that access is mediated through the referenced HR_API, HR_GENERAL2, and HR_UTILITY packages rather than being performed inline. UPDATE and DELETE operations on business entities remain the responsibility of the calling routines; DT_API supplies the rules and the date boundaries those routines apply.

Usage Notes

DT_API is typically invoked from Oracle Forms-based date-track maintenance screens, from concurrent programs that process date-tracked records in bulk, and from custom PL/SQL code that must honor the same date-track semantics as the standard product. A conventional call pattern is to first invoke FIND_DT_UPD_MODES or FIND_DT_DEL_MODES to obtain the selectable modes for presentation, pass the user's choice through VALIDATE_DT_UPD_MODE or VALIDATE_DT_DEL_MODE before committing, confirm the target row with ROWS_EXIST, validate the effective range with CHECK_MIN_MAX_DATES, and read GET_OBJECT_VERSION_NUMBER to support optimistic locking.

Because it is referenced by 1,739 objects and references none, DT_API should be treated as shared infrastructure: callers must not depend on undocumented internals, and any modification carries broad downstream impact. Its public contract is the thirteen documented routines listed above. As with any APPS-schema API, it is intended to be called from the APPS schema context so that the synonyms and HR utility dependencies resolve correctly. All procedures are validated against the same centralized rules, which is precisely why the EBS product line routes date-track logic through this package rather than duplicating it.