Search Results dt_pkg

Overview

DT_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, documented under the ETRM (E-Business Suite Technical Reference Manual) repository for releases 12.1.1 and 12.2.2. Its object status is recorded as VALID, confirming that the package and its package body compile cleanly against the standard database objects on which they depend. The ETRM classification for this package is OTHER, indicating that it is neither a public Oracle-supplied API nor a formalized open interface; it falls outside the standard seeded API categories and is treated as an internal or auxiliary utility unit.

The package name, prefixed with "DT_", is consistent with the naming conventions used by Oracle's Date/Time utility family. In practice, DT_PKG provides date-derivation services — returning calendar, period, or range values used by other EBS components when date logic must be resolved at runtime rather than hard-coded. It is a dependency-level utility, invoked by application logic rather than by end users directly.

Key Procedures and Functions

The documented package exposes a single program unit:

• GET_DATES — the sole documented procedure or function in DT_PKG. Based on the package's naming and classification, GET_DATES returns one or more derived date values, such as start and end dates, the current accounting period boundaries, or a date range applicable to a given processing context. It forms the entire public surface of the package.

No parameter lists are recorded in the ETRM metadata, and no overloading or additional private subprograms are documented. Because the package body carries no published specification beyond this single unit in the ETRM listing, integrators should inspect the compiled source (via the "show dependent code" link in the ETRM entry) before invoking it from custom code.

Tables Accessed

The ETRM documentation for DT_PKG lists no referenced application tables through APPS synonyms. The only recorded dependencies are SYS and the STANDARD package, meaning the unit is a pure PL/SQL construct that does not read or write Oracle EBS base tables, interface tables, or temporary staging structures. There are therefore no data-integrity or locking considerations associated with its use.

Usage Notes

DT_PKG is referenced only by itself within the ETRM dependency graph; it is not called by any other documented package. This self-referential footprint suggests the package is invoked directly from trigger or form-level code, from concurrent program logic, or from custom client extensions that require date derivation. Typical invocation scenarios include:

• Form personalizations or custom library code that need standardized start/end dates.
• Concurrent program wrapper logic requiring consistent date ranges across multiple runs.
• Supplied or customized database triggers relying on a single authoritative date source.

Because the package is classified as OTHER and carries no published parameter metadata, any custom invocation should reproduce the exact call signature observed in the compiled package specification. Substituting locally coded date logic is generally preferable where the underlying behavior cannot be verified against the source, as the package is not covered by Oracle's public API stability guarantees.