Results for “csf_r_sched_requests_n1”

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

Overview

CSF.CSF_R_SCHED_REQUESTS is the scheduler request header table within the Oracle E-Business Suite Field Service (formerly Service) application, owned by the CSF schema. Each row represents a single scheduling request — a unit of work submitted by an interactive session, a semi-interactive concurrent program, or an internal API call — that the Field Service scheduler processes to assign resources, tasks, and time slots. The table acts as the transactional anchor for an entire scheduling operation, holding the request's status, mode, plan parameters, and descriptive metadata. In Oracle EBS 12.1.1 and 12.2.2, the object resides in the APPS_TS_TX_DATA tablespace (PCTFREE 10) and is documented in the ETRM repository as VALID, with 32 columns and a primary key constraint, CSF_R_SCHED_REQUEST_PK, on SCHED_REQUEST_ID.

The metadata carries an explicit Oracle Internal Use Only warning: the table is not supported for direct customer access except through standard Oracle Applications programs. Data Vault classification is heuristic and hub-leaning, since the table's identity is defined by a single surrogate key and it is referenced by several dependent child tables. Under a Data Vault modeling suggestion, CSF_R_SCHED_REQUESTS would be treated as a hub, with its child tables (request tasks, filters, values, and message tokens) behaving as link or satellite structures attached to that hub.

Key Information Stored

The most significant columns include:

• SCHED_REQUEST_ID — surrogate primary key and the sole business-key candidate, enforced by the unique index CSF_R_SCHED_REQUESTS_U1. All child tables join on this column.
• RESULT_FLAG — outcome of the scheduler request: NULL means no result yet; 'S' indicates success; 'E' indicates one or more errors; 'U' indicates an unexpected error, such as a cancelled concurrent program.
• CONCURRENT_REQUEST_ID — foreign key to FND_CONCURRENT_REQUESTS, populated when the request runs in semi-interactive mode so callers can locate the concurrent output file. Null for purely interactive requests.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — standard concurrent program columns. PRODUCT_APPLICATION_ID 513 designates Field Service ('CSF').
• PARENT_REQUEST_ID — self-referencing pointer to a parent scheduling request; indexed by the non-unique index CSF_R_SCHED_REQUESTS_N1.
• SCHED_REQUEST_NAME — user-facing descriptive name for the request.
• PLANMODE — planning mode governing how the scheduler is invoked.
• EXTENDED_EFFORT — effort measure carried into the scheduling computation.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org security partitioning.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework.
• TARGET_STATUS_ID — intended status identifier applied to scheduled tasks.
• ROUTE_BASED_FLAG — indicates whether the request is driven by route-based scheduling.
• CHANGED_OPTION_START, CHANGED_OPTION_END, CHANGED_PLANNED_START, CHANGED_PLANNED_END — time windows the scheduler should respect for changed options and planned dates.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — plus several spares-related columns (SPARES_LIKELIHOOD, SPARES_LIKLIHOOD, SPARES_SOURCE, SPARES_MANDATORY) that govern spare-parts availability during scheduling.

Common Use Cases and Queries

Typical reporting and diagnostics include monitoring scheduler request results, tracing requests that spawned concurrent jobs, and correlating child task and filter rows back to the parent request. A common pattern joins the header to its concurrent request and result flag:

• Locate failed scheduler requests: SELECT s.SCHED_REQUEST_ID, s.SCHED_REQUEST_NAME, s.CONCURRENT_REQUEST_ID FROM CSF.CSF_R_SCHED_REQUESTS s WHERE s.RESULT_FLAG IN ('E','U') ORDER BY s.CREATION_DATE DESC;
• Find the concurrent output for a semi-interactive request: join CSF_R_SCHED_REQUESTS.CONCURRENT_REQUEST_ID to FND_CONCURRENT_REQUESTS.REQUEST_ID, then FND_CONCURRENT_PROGRAMS, to obtain the log/output filenames.
• Drill into child detail: join to CSF_R_REQUEST_TASKS, CSF_R_REQUEST_FILTERS, and CSF_R_REQUEST_VALUES on SCHED_REQUEST_ID to reconstruct the scope of a scheduling run.
• Audit plan windows: query CHANGED_PLANNED_START/END and CHANGED_OPTION_START/END to verify constraints applied during rescheduling.

Related Objects

The table sits at the center of the CSF scheduler object model and interacts with the following documented relationships:

• CSF_R_REQUEST_TASKS — child table; SCHED_REQUEST_ID FK to CSF_R_SCHED_REQUESTS.
• CSF_R_REQUEST_FILTERS — child table; SCHED_REQUEST_ID FK to CSF_R_SCHED_REQUESTS.
• CSF_R_REQUEST_VALUES — child table; SCHED_REQUEST_ID FK to CSF_R_SCHED_REQUESTS.
• CSF_R_MESSAGE_TOKENS — child table; MESSAGE_ID FK to CSF_R_SCHED_REQUESTS.
• FND_SECURITY_GROUPS — parent of SECURITY_GROUP_ID; governs data security partitioning.
• FND_CONCURRENT_REQUESTS — referenced through CONCURRENT_REQUEST_ID for semi-interactive execution output.

All access should occur through supported Oracle Field Service concurrent programs and APIs; the object is documented by Oracle as internal-use only.