Search Results csf_auto_commit

Overview

The CSF_AUTO_COMMIT concurrent program, presented to users under the name Auto Commit Tasks, is a standard Oracle E-Business Suite utility belonging to the CSF – Field Service product family. Its documented purpose is to commit all field service tasks that currently hold the default Planned status. In Field Service workflows, tasks are frequently created in an intermediate, uncommitted state before a dispatcher, scheduler, or planning engine has validated them. The Auto Commit Tasks program performs that final transition, promoting every eligible Planned task to a committed state so that downstream scheduling, dispatch, and billing processes can act upon it. The program is shipped enabled in both Oracle EBS 12.1.1 and 12.2.2 and requires no additional licensing or product installation beyond the CSF module itself.

Execution Details

The ETRM documentation records the following execution metadata for the program:

• Product: CSF – Field Service
• User-facing name: Auto Commit Tasks
• Enabled: Yes
• Execution Method: PL/SQL Stored Procedure
• Argument Method: Standard
• Executable: CSF_AUTO_COMMIT
• Execution Filename: CSF_AUTO_COMMIT_PVT.Update_Planned_Task_Status

The execution filename identifies the actual database package and procedure invoked at runtime: CSF_AUTO_COMMIT_PVT.Update_Planned_Task_Status. Because the program runs as a PL/SQL stored procedure rather than as a report or SQL*Loader script, it operates directly against the Field Service task tables within the same database session, committing work as it completes. The Standard argument method indicates that Oracle's standard concurrent program argument framework applies; the program is not driven by a custom or token-based parameter mechanism.

How to Run

Users submit the program through the standard Submit Requests (SRS) window, navigating to Requests → Run and selecting Auto Commit Tasks from the list of available concurrent programs. Depending on configuration, it may also be scheduled as a recurring request through the Schedule button, or attached to a request set so that it executes as part of a larger Field Service batch. Because the documented argument method is Standard and the metadata lists no mandatory parameters, the program is generally submitted without runtime arguments; the scope of the commit is determined by the population of tasks currently holding the Planned status rather than by user-entered selection criteria. Administrators should confirm the concurrent manager queue assigned to the CSF product and verify that the program is enabled before scheduling it.

Related Objects

The program is closely associated with the Field Service task model and the CSF_AUTO_COMMIT_PVT package that it calls. Related components typically encountered alongside it include:

• CSF_AUTO_COMMIT_PVT – the PL/SQL package housing Update_Planned_Task_Status, the entry point executed by the program.
• Field Service task entities in the CSF schema, which hold the Planned-versus-committed status flag the program updates.
• Concurrent manager and request set definitions for the CSF product, used to schedule or chain the program with related Field Service requests.
• Other CSF concurrent programs that operate on task planning and dispatch, which may run before or after the commit step in a larger scheduling cycle.

Because the ETRM excerpt is limited to program-level metadata, administrators seeking parameter or table-level detail should consult the CSF technical reference and the package body of CSF_AUTO_COMMIT_PVT in the database.