Search Results csf_auto_commit_pvt




Overview
Explore in AI Chat

Overview

CSF_AUTO_COMMIT_PVT is a private (PVT) PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the CSF (Common Service Foundation) module, which underpins the Field Service and Service/TeleService product families. Its functional purpose is to automatically update the status of planned service tasks, allowing the system to progress task execution without manual intervention from a field service administrator or technician. The package supports the "auto-commit" concept in service task management: when predefined business conditions are satisfied, planned task records are advanced to an appropriate status automatically. The "PVT" suffix indicates that this is an internal implementation package rather than a public API. It is not designed for direct invocation by customers, and Oracle does not guarantee its interface across releases. In practice, it is consumed by other service foundation objects—most notably the CSF_AUTO_COMMIT package—which orchestrate the auto-commit workflow and delegate the low-level status update to this private unit. The package is documented as VALID in ETRM and references only SYS.STANDARD as a database-level dependency, while relying on APPS synonyms for all business data access.

Key Procedures and Functions

The ETRM metadata documents a single program unit within this package: UPDATE_PLANNED_TASK_STATUS. As the name implies, this procedure is responsible for writing a status value to a planned service task record. It is the mechanism by which the auto-commit logic persists a task's new status after the calling code has determined that the defined auto-commit criteria are met. The procedure operates on a single task at a time, consistent with the row-level nature of status transitions. No parameter list is documented in the ETRM extract, so its exact signature (task identifier, target status value, and any return status or error message outputs) should be confirmed by inspecting the package specification and body in the target environment before any custom dependency is introduced. No additional functions or procedures are recorded for this package, and it is not referenced by any other documented package, which reinforces its position as a leaf-level internal utility within the CSF auto-commit call chain.

Tables Accessed

Per the documented metadata, the package accesses one business table through an APPS synonym: JTF_TASKS_B. This is the base table of the JTF Tasks entity, the shared task model used throughout Oracle's service and CRM applications. UPDATE_PLANNED_TASK_STATUS reads and writes JTF_TASKS_B to retrieve the planned task and apply the new status. In addition to the business table, the metadata lists two non-application dependencies: DBMS_LOCK and PLITBLM. DBMS_LOCK indicates that the procedure acquires a lock before updating task status, preventing concurrent auto-commit routines from modifying the same task simultaneously. PLITBLM is the standard Oracle-supplied package supporting PL/SQL table operations and is typically a transitive dependency rather than a functional component of the auto-commit logic. No date-tracked columns or interface tables are documented, so any auditing of status changes must be inferred from the owning service application modules.

Usage Notes

CSF_AUTO_COMMIT_PVT is an internal utility and should not be called directly from custom forms, concurrent programs, or extensions. It is invoked by the higher-level CSF_AUTO_COMMIT package during the automatic task status update process, which may be triggered from service task management forms, from concurrent programs that sweep planned tasks, or from workflow/business event processing within the Service Foundation layer. Because the package is classified PVT and is subject to change without notice between EBS 12.1.1 and 12.2.2, any customer requirement to automate task status changes should be implemented through the supported public API surface or by extending the auto-commit configuration, not by referencing this package. When diagnosing unexpected task status transitions, DBAs and developers should inspect the JTF_TASKS_B row and the calling CSF_AUTO_COMMIT logic; the dependency on DBMS_LOCK is a useful reminder that status updates are serialized and that lock contention may surface as slow auto-commit processing.