Results for “csf_task_debrief”

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

Overview

CSF_DEBRIEF_PUB is the public PL/SQL interface for Debrief transactions within Oracle E-Business Suite. Debrief is the field service business process through which a technician records the complete set of activities, materials, labor, and expenses consumed while executing a task assignment. This package provides the programmatic entry point for creating and maintaining that debrief data, exposing a controlled API surface rather than permitting direct DML against the underlying debrief and debrief line tables.

The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling session rather than the package owner. It is registered with the ETRM repository under the product code CSF, with a display name of Debrief, an active lifecycle, and a compatibility rating of S (supported). The associated business entity is CSF_TASK_DEBRIEF, and the documented scope is public. The header comment explicitly states that the interface permits upload of Material, Labor, and Expense transactions, which corresponds to the three standard debrief line types captured during field service execution.

Key Procedures and Functions

Seven documented entry points are exposed by the package:

• CREATE_DEBRIEF — Creates a new debrief header record, establishing the debrief number, debrief date, status, and the task assignment to which the debrief relates.
• CREATE_DEBRIEF_WITH_DFF_VALS — Performs the same header creation function while additionally accepting values for the descriptive flexfield segments defined on the debrief header, allowing caller-supplied attribute data to be persisted in the same operation.
• UPDATE_DEBRIEF — Modifies an existing debrief header, supporting changes to status and other header-level attributes over the lifespan of the debrief. This is the routine most commonly targeted by callers searching for debrief update behavior.
• CREATE_DEBRIEF_LINES — Inserts debrief lines beneath an existing debrief header, covering material, labor, and expense transaction types in accordance with the package's stated purpose.
• UPDATE_DEBRIEF_LINE — Amends a previously created debrief line, permitting correction of quantities, amounts, or associated reference data prior to debrief completion and transfer to downstream costing and billing processes.
• CALL_INTERNAL_HOOK — Invokes a registered internal hook, integrating the debrief transaction flow with the JTF hook mechanism so that business events raised during debrief processing can trigger subscribed custom logic.
• SET_AUTO_DEBRIEF — Controls the automatic debrief behavior, allowing the caller to establish whether debrief records are generated automatically for a given task assignment context.

Tables Accessed

The package references its tables through APPS synonyms. The documented references are JTF_HOOKS_DATA, used by CALL_INTERNAL_HOOK to resolve and execute hook subscriptions; DBMS_SQL, employed for dynamic SQL execution; and PLITBLM, the PL/SQL integer table type used for bulk operations and array-based processing. The debrief header and line records themselves are modeled by the DEBRIEF_Rec_Type record structure declared in the package specification, which includes the debrief header identifier, debrief number, debrief date, debrief status identifier, task assignment identifier, the standard WHO audit columns, and eight or more descriptive flexfield attribute columns.

Usage Notes

CSF_DEBRIEF_PUB is invoked from the Debrief user interface in the Field Service forms, from concurrent programs that process or import debrief transactions, and from custom PL/SQL code performing integrations. The package is referenced by seventeen other packages within the E-Business Suite, indicating that it functions as a foundational dependency for higher-level debrief processing logic.

Because the package uses FND_API.G_MISS_NUM, G_MISS_CHAR, and G_MISS_DATE as default sentinel values in its record type, callers must populate only the attributes they intend to change and leave remaining attributes at their G_MISS defaults to signal "no value supplied." The package constant G_DEFAULT_NUM_REC_FETCH is set to 30, controlling the default fetch size for bulk retrieval operations. G_USER_ID and G_LOGIN_ID are initialized from FND_GLOBAL at package instantiation. Callers should treat these APIs as the supported integration path, as direct DML against debrief tables bypasses validation and audit logic applied by the public interface.