Search Results calc_specific_startdate




Overview
Explore in AI Chat

Overview

FND_CONC_RELEASE_CLASS_UTILS is an Oracle E-Business Suite internal PL/SQL utility package owned by the APPS schema. It supports the Concurrent Request Release Class framework, which governs the scheduling behavior of concurrent programs and request sets placed on a release class schedule. A release class determines when a submitted concurrent request is eligible to execute — immediately, on a defined periodic interval, or at a specific calendar-driven point in time. This package supplies the date-arithmetic and class-parsing logic that the concurrent manager relies upon to translate a stored schedule definition into a concrete next-run date.

The package is declared AUTHID CURRENT_USER, meaning its unqualified database references resolve against the privilege domain of the calling user rather than the definer. All callable subprograms are exposed through the package specification, which also carries the legacy header identifier AFCPCRCS.pls (version 115.6). The package is classified as OTHER in the ETRM metadata and is referenced by two other packages within the release-class subsystem.

Key Procedures and Functions

  • calc_specific_startdate — The function most commonly associated with this package. Given a requested start date and the class information string describing a Specific schedule, it returns the next date on which a request should run according to that schedule. The function may return null when no valid date can be derived from the supplied inputs.
  • parse_named_periodic_schedule — A procedure that accepts an application name and a Periodic schedule name and returns the repeat interval, interval unit, interval type, start date, and repeat end date for that schedule. Output values are null if the schedule is not found or an error occurs during resolution.
  • parse_periodic_schedule — A procedure performing the same decomposition as the named variant but resolving the schedule by application identifier and release class identifier rather than by name. As with the named variant, unresolved or erroneous lookups yield null outputs.
  • assign_specific_sch — A function that assigns a specific schedule to a concurrent request and returns a Boolean indicating success or failure.

Tables Accessed

  • 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, including schedule type and class information consumed by the parsing routines.
  • FND_APPLICATION — used to resolve an application name to its application identifier when parsing a named periodic schedule.
  • FND_CONCURRENT_REQUESTS — the concurrent request repository, consulted or updated when binding a specific schedule to a request.
  • FND_LANGUAGES — supports translation-aware resolution of release class descriptive data.
  • DUAL — used for single-row expression evaluation.

All references are made through APPS synonyms, reflecting the package's position inside the standard EBS data model.

Usage Notes

This package is not an end-user API. It is invoked internally by the concurrent manager and by higher-level release-class processing packages — two such dependents are documented in the ETRM repository. The calc_specific_startdate function is the entry point most frequently sought by developers and support personnel investigating why a request submitted against a Specific schedule received an unexpected or absent start date; its documented behavior of returning null when no valid date exists is a common root cause of requests remaining unstarted.

Custom code should call these subprograms under the APPS schema and should never reference the package body directly. Because the package is AUTHID CURRENT_USER and is flagged NOSHIP in its original header, its interfaces are unsupported for customer extension and may change across EBS point releases such as 12.1.1 and 12.2.2. Diagnostic queries against fnd_concurrent_requests, combined with the output of the parsing routines, remain the standard means of validating release class scheduling behavior.