Search Results csf_requests_pvt




Overview

APPS.CSF_REQUESTS_PVT is a private PL/SQL package within the Oracle E-Business Suite Field Service (CSF) module. It serves as the request-handling engine responsible for creating and persisting the transactional records that underlie Field Service scheduling activities. The package consolidates the insert and construct logic for scheduler requests, resource results, plan options, plan option tasks, messages, and message tokens into a single cohesive unit. Its PVT (private) API classification indicates that it is not intended to be called directly by external consumers; instead, it is invoked by public packages such as CSF_RESOURCE_PUB, CSF_TRIPS_PUB, and CSR_SCHEDULER_PVT, which expose validated, supported entry points. In EBS 12.1.1 and 12.2.2 the package resides in the APPS schema and is reported with a status of VALID in the ETRM metadata repository.

Key Procedures and Functions

The documented API surface comprises eight procedures, each responsible for constructing a specific category of request data record:

  • CREATE_SCHEDULER_REQUEST — Establishes a scheduler request header, recording the parameters that drive a Field Service scheduling or optimization run.
  • CREATE_MULTI_TRIPS_REQUEST — Creates a request spanning multiple trips, supporting scheduling scenarios in which a resource completes a sequence of related visits.
  • CREATE_RESOURCE_RESULTS — Persists the outcome data returned for resources evaluated during a scheduling run.
  • CREATE_PLAN_OPTION — Inserts an individual planning option associated with a scheduler request.
  • CREATE_PLAN_OPTIONS — Creates planning options in bulk, allowing multiple options to be written in a single invocation.
  • CREATE_PLAN_OPTION_TASK — Records an individual task belonging to a plan option.
  • CREATE_MESSAGE — Writes diagnostic or informational messages generated during request processing.
  • CREATE_MESSAGE_TOKEN — Inserts the substitutable token values that parameterize a stored message.

No parameter lists are documented in the ETRM repository; callers should reference the package specification in the target release for exact signatures.

Tables Accessed

The package reads from and writes to the CSF_R_* family of request tables, resolved through APPS synonyms. Request headers are stored in CSF_R_SCHED_REQUESTS, with its CSF_R_SCHED_REQUESTS_S1 sequence supplying primary keys. Task-level detail is held in CSF_R_REQUEST_TASKS and CSF_R_REQUEST_TASKS_S1. Resource outcomes are persisted in CSF_R_RESOURCE_RESULTS and CSF_R_RESOURCE_RESULTS_S1. Planning data is distributed across CSF_R_PLAN_OPTIONS, CSF_R_PLAN_OPTION_TASKS, and CSF_R_SPARES_OPTIONS, each supported by its corresponding _S1 sequence. Messaging data is written to CSF_R_MESSAGES and CSF_R_MESSAGE_TOKENS, likewise sequenced by CSF_R_MESSAGES_S1 and CSF_R_MESSAGE_TOKENS_S1. These tables collectively represent the transient and persistent state of a Field Service scheduling request and its results.

Usage Notes

CSF_REQUESTS_PVT is invoked indirectly. The ETRM dependency listing shows that it is referenced by CSF_RESOURCE_PUB, CSF_TRIPS_PUB, and CSR_SCHEDULER_PVT — the last being the package most closely associated with the search term csr_scheduler_pvt. In practice, scheduling or trip-planning operations initiated from Field Service forms or concurrent programs flow through these public or scheduler-facing packages, which in turn delegate record creation to CSF_REQUESTS_PVT. The package also references the JTF_DATE_TABLE, JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, and JTF_VARCHAR2_TABLE_4000 collection types, a common pattern for bulk-binding arrays used within the JTF framework. Because it is a private package, customizations and extensions should target the public wrappers rather than CSF_REQUESTS_PVT directly, and any direct invocation risks bypassing validation logic enforced by the calling layer.