Search Results req_date




Overview
Explore in AI Chat

Overview

FND_CONC_RELEASE_CLASS_UTILS is an internal PL/SQL utility package in the Oracle E-Business Suite Applications (APPS) schema that supports the Concurrent Manager release-class scheduling infrastructure. Its header comments identify the module as AFCPCRCB.pls, a naming convention associated with Oracle Concurrent Processing release class functionality. The package supplies the date-calculation and schedule-parsing logic required to translate a release class definition — stored as a compressed bitmap specification in the FND_CONC_RELEASE_CLASSES family of tables — into a concrete next-run date for a concurrent request.

The central business problem addressed is the determination of "the next date that a request should run according to this schedule," as stated in the source comments for CALC_SPECIFIC_STARTDATE. Given a requested start date and the class information describing a Specific-type schedule, the package evaluates the class bit-field and returns the earliest valid execution date, or NULL when no valid date is found. This logic underpins time-based release of concurrent programs in both 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents four program units. No parameter lists are published here, so only purposes are described.

  • CALC_SPECIFIC_STARTDATE — Core date engine. Accepts a requested start date and class information and returns the next date on which a request should execute under a Specific schedule. It interprets the class information as a bit-field (the first 31 bits representing day-of-month, the 32nd denoting last day of month, and bits 33 through 39 representing day-of-week), detects whether a date or weekday has been specified, and iterates forward until an executable day is found.
  • PARSE_NAMED_PERIODIC_SCHEDULE — Interprets class information for named periodic schedules, resolving schedule tokens into usable scheduling data.
  • PARSE_PERIODIC_SCHEDULE — Parses periodic schedule definitions, complementing the named-periodic variant.
  • ASSIGN_SPECIFIC_SCH — Assigns Specific schedule information to a release class context, supporting the assignment of a computed start date or schedule definition.

Tables Accessed

The package reads reference and definition data through APPS synonyms:

  • FND_CONC_RELEASE_CLASSES, FND_CONC_RELEASE_CLASSES_S, and FND_CONC_RELEASE_CLASSES_TL — the base, primary-key, and translation tables holding release class definitions and their multilingual descriptions.
  • FND_CONCURRENT_REQUESTS — the request repository against which schedule applicability and computed dates are evaluated.
  • FND_APPLICATION and FND_LANGUAGES — used to resolve application context and language-specific class information.
  • DUAL — used for scalar date arithmetic, including the SYSdate-relative offset calculation visible in the source.

Usage Notes

This is an internal utility package; it is not a public, customer-facing API. It is referenced by two other packages within the Concurrent Processing stack and is invoked indirectly when the Concurrent Manager evaluates release class schedules to decide when a concurrent request becomes eligible to run. The date computed by CALC_SPECIFIC_STARTDATE is derived relative to the requested start date, with a comment noting handling of "56 bits code for advance scheduling," indicating version-dependent class information widths.

Because the user search term "req_date" corresponds directly to the requested-start-date input consumed by CALC_SPECIFIC_STARTDATE, developers investigating scheduling anomalies — requests failing to release on the expected date — typically trace behavior here. Custom code should not call this package directly; instead, it should rely on the supported Concurrent Manager scheduling interfaces, since the class information bit-field layout is an internal implementation detail subject to change between 12.1.1 and 12.2.2.