Search Results get_today

Overview

APPS.POA_TIME_API is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite, classified in ETRM as an API. It supplies date-arithmetic services used primarily by Oracle Procurement (POA) functionality — the naming convention and the referenced profile option POA_FIXED_DATE strongly suggest it is used by Procurement-related date derivation logic. The package exposes a focused set of date functions that return "today," current-year and last-year period boundaries, and current-quarter and year-ago-quarter boundaries, all resolved against the enterprise calendar. Its central design feature is sensitivity to the POA_FIXED_DATE profile option, which allows the effective "current date" to be frozen for testing, cutover validation, or period-close simulations without altering the database server clock.

Key Procedures and Functions

• GET_TODAY — Returns the current date with a time element. If the POA_FIXED_DATE profile option is set, the fixed date is returned; otherwise SYSDATE is returned.
• GET_CQTR_START — Returns the quarter start date for the current year, current quarter (cycq) in the enterprise calendar, derived from SYSDATE, with the result cached after initial access.
• GET_CQTR_END — Returns the quarter end date for the current year, current quarter in the enterprise calendar, also cached after initial access.
• GET_LYCQ_START — Returns the quarter start date for last year, current quarter (lycq) in the enterprise calendar.
• GET_LYCQ_END — Returns the quarter end date for last year, current quarter in the enterprise calendar.
• GET_LYCQ_TODAY — Returns the equivalent day in last year's current quarter, i.e., today's date mapped back by one year within the quarter context.
• GET_CY_START — Returns the start date of the current enterprise-calendar year.
• GET_CY_END — Returns the end date of the current enterprise-calendar year.
• GET_LY_START — Returns the start date of last enterprise-calendar year.
• GET_LY_END — Returns the end date of last enterprise-calendar year.

All ten functions return DATE and raise an exception if an underlying SQL error occurs. Each function takes no documented parameters.

Tables Accessed

The documented table reference is GL_PERIODS, accessed through an APPS synonym. GL_PERIODS is the General Ledger period definition table that stores accounting period names, start dates, and end dates for each period set and calendar. The package reads GL_PERIODS to resolve enterprise-calendar quarter and year boundaries for the current-period functions (GET_CQTR_START, GET_CQTR_END, GET_CY_START, GET_CY_END, and their prior-year counterparts). Prior-period functions such as GET_LYCQ_START and GET_LY_START obtain their date ranges by shifting the resolved enterprise-calendar values rather than by maintaining separate reference data. The date-generation profile check for POA_FIXED_DATE relies on the FND profile mechanism, not on a physical table read exposed to the caller.

Usage Notes

POA_TIME_API is invoked from standard EBS server-side code — typically concurrent programs, PL/SQL batch logic, and forms-based client extensions — wherever a consistent, profile-aware "effective date" is required. Because GET_TODAY honors POA_FIXED_DATE, developers should prefer it over SYSDATE in Procurement-related customizations so that test and cutover scenarios reproduce correctly. The quarter- and year-boundary functions are intended for period-relative reporting and accrual processing; their results are cached after first access, which means a caller that changes the POA_FIXED_DATE profile mid-session may not see the change reflected in cached quarter/year values. ETRM records no other packages referencing POA_TIME_API, so it is effectively a leaf utility API. Callers should handle the raised exceptions, since every documented function signals SQL errors rather than returning a null date. Standard APPS schema grants and AUTHID CURRENT_USER semantics apply.