Search Results csf_r_messages_s1

Overview

CSF_REQUESTS_PVT is the private implementation package body for the Oracle EBS Field Service (CSF) scheduling requests API. It resides in the APPS schema and carries the PVT designation, meaning it is not intended for direct invocation by external callers; the public-facing wrapper CSF_REQUESTS_PUB exposes the supported entry points, and CSF_REQUESTS_PVT contains the underlying procedural logic. The package orchestrates the persistence of scheduling requests and their associated sub-entities — plan options, plan option tasks, resource results, request tasks, spares options, and messages — within the EBS Field Service scheduler data model. Its status is VALID in both 12.1.1 and 12.2.2 environments.

Key Procedures and Functions

The package exposes eight documented procedures that span the breadth of the scheduling request lifecycle:

• CREATE_SCHEDULER_REQUEST — Establishes the top-level scheduler request record in the scheduling requests table, forming the parent context for all downstream child entities.
• CREATE_MULTI_TRIPS_REQUEST — Handles scheduler requests spanning multiple trips, coordinating the request-level data needed to represent multi-trip scheduling scenarios.
• CREATE_PLAN_OPTIONS — Persists a set of planning options associated with a request, supporting bulk creation of plan option rows.
• CREATE_PLAN_OPTION — Creates an individual plan option record, representing a candidate scheduling plan produced for the request.
• CREATE_PLAN_OPTION_TASK — Records the task-level detail belonging to a plan option, linking planning data to specific service tasks.
• CREATE_RESOURCE_RESULTS — Stores the resource-level outcomes arising from scheduling evaluation, capturing which resources were considered or selected.
• CREATE_MESSAGE — Inserts scheduling messages and diagnostics, used to communicate errors, warnings, or informational feedback to the calling application.
• CREATE_MESSAGE_TOKEN — Creates the token substitutions associated with messages, enabling parameterized message text to be resolved at display time.

Tables Accessed

The package operates over the CSF scheduling tables via APPS synonyms. The scheduler request and its schedule rows are held in CSF_R_SCHED_REQUESTS; request tasks are stored in CSF_R_REQUEST_TASKS. Planning data resides in CSF_R_PLAN_OPTIONS and its task detail in CSF_R_PLAN_OPTION_TASKS, while spares planning is captured in CSF_R_SPARES_OPTIONS. Resource evaluation results are written to CSF_R_RESOURCE_RESULTS. Message output is persisted through CSF_R_MESSAGES and its substitution tokens through CSF_R_MESSAGE_TOKENS. Each of these base tables has a corresponding _S1 sequence (CSF_R_REQUEST_TASKS_S1, CSF_R_PLAN_OPTIONS_S1, CSF_R_PLAN_OPTION_TASKS_S1, CSF_R_RESOURCE_RESULTS_S1, CSF_R_MESSAGES_S1, CSF_R_MESSAGE_TOKENS_S1, CSF_R_SCHED_REQUESTS_S1, CSF_R_PLAN_OPTIONS_S1, CSF_R_SPARES_OPTIONS_S1) used to generate primary keys. The package also depends on FND_API, FND_GLOBAL, FND_MSG_PUB, and the JTF_DATE_TABLE, JTF_NUMBER_TABLE, and JTF_VARCHAR2_TABLE_100 collection types, indicating use of the standard EBS API error-handling, message-stack, and table-based parameter conventions.

Usage Notes

Because CSF_REQUESTS_PVT is a private package body, direct invocation is discouraged. External callers — including Field Service forms, concurrent programs that create or reschedule service requests, and custom extensions — should call the corresponding public procedures in CSF_REQUESTS_PUB, which in turn delegate to this package. Three other database objects reference CSF_REQUESTS_PVT, but the package itself references no objects beyond those listed; it is a terminal consumer within its dependency graph. When troubleshooting the identifier "csf_r_request_tasks_s1," note that this is the sequence backing CSF_R_REQUEST_TASKS and is referenced directly by CSF_REQUESTS_PVT during request task creation. Diagnosing sequence-related errors typically involves validating that the synonym and grants for CSF_R_REQUEST_TASKS_S1 resolve correctly in the APPS schema and that the sequence has not been dropped or exhausted.