Results for “fnd_concurrent_request_class”

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

Overview

FND_CONCURRENT_REQUEST_CLASS is a reference table in the APPLSYS schema belonging to the FND — Application Object Library product. It stores the definition of concurrent request types, sometimes described as request classes. A request class groups concurrent programs into categories that determine how the Concurrent Manager schedules and processes their requests — for example, high-priority, low-priority, or resource-specific workloads. Each row represents one named request type owned by a specific Oracle application.

Because the table holds relatively stable classification data that is referenced by many operational objects, it behaves as a hub in Data Vault terms: a heuristic, mined classification of the FK structure suggests "hub-leaning," meaning it is best modeled as a central business entity referenced by multiple dependent tables, rather than as a transactional link or an audited satellite.

Key Information Stored

• APPLICATION_ID — Identifies the owning Oracle application (FK to FND_APPLICATION). Part of the primary key and of both unique indexes.
• REQUEST_CLASS_ID — Surrogate/primary identifier for the request class; part of the FND_CONC_REQUEST_CLASS_PK primary key and of the unique index FND_CONC_REQUEST_CLASS_U1.
• REQUEST_CLASS_NAME — Business name of the request type; the business-key candidate indexed by FND_CONC_REQUEST_CLASS_U2 (APPLICATION_ID, REQUEST_CLASS_NAME).
• DESCRIPTION — Free-text description of the request class purpose.
• LAST_UPDATE_DATE / CREATION_DATE — Standard audit timestamps describing when the row was last modified and originally created.
• LAST_UPDATED_BY / CREATED_BY / LAST_UPDATE_LOGIN — Who-attributes identifying the application user who created or last modified the row and the login session.

The table contains 9 documented columns. Two unique keys exist: FND_CONC_REQUEST_CLASS_U1 on (APPLICATION_ID, REQUEST_CLASS_ID) and FND_CONC_REQUEST_CLASS_U2 on (APPLICATION_ID, REQUEST_CLASS_NAME), so REQUEST_CLASS_ID functions as the surrogate key while REQUEST_CLASS_NAME serves as the alternate business key.

Common Use Cases and Queries

Typical usage includes administrative reporting on which request classes exist per application, resolving class names for concurrent requests, and validating queue-content assignments. A common query joins the class to its owning application:

• SELECT rc.request_class_id, rc.request_class_name, rc.description, fa.application_short_name
• FROM fnd_concurrent_request_class rc, fnd_application fa
• WHERE rc.application_id = fa.application_id
• ORDER BY fa.application_short_name, rc.request_class_name;

A second pattern lists requests grouped by request class by joining FND_CONCURRENT_REQUESTS on REQUEST_CLASS_APPLICATION_ID and CONCURRENT_REQUEST_CLASS_ID. Reporting use cases include capacity analysis of high-priority versus low-priority classes, checking which classes are assigned to queue content, and auditing which concurrent programs reference each class.

Related Objects

• FND_APPLICATION — referenced by FND_CONCURRENT_REQUEST_CLASS.APPLICATION_ID.
• FND_CONCURRENT_PROGRAMS — references this table via CLASS_APPLICATION_ID and CONCURRENT_CLASS_ID.
• FND_CONCURRENT_QUEUE_CONTENT — references this table via TYPE_APPLICATION_ID and TYPE_ID.
• FND_CONCURRENT_REQUESTS — references this table via REQUEST_CLASS_APPLICATION_ID and CONCURRENT_REQUEST_CLASS_ID.
• FND_CONCURRENT_COMPLEX_LINES — references this table via TYPE_APPLICATION_ID and TYPE_ID.

These relationships confirm the table's role as a hub: it is a parent to concurrent programs, queue content, request submissions, and complex (request set) lines, while itself depending only on FND_APPLICATION.