Search Results debrief_status_id

Overview

CSF_DEBRIEF_HEADERS is the master header table for Field Service Report (debrief) information within the CSF — Field Service module of Oracle E-Business Suite. Each row represents a single field service debrief document, capturing the outcome, timing, and travel details recorded by a field service technician after completing a service task or task assignment. The table is owned by the CSF schema and carries a VALID status in both 12.1.1 and 12.2.2, with a documented physical schema of 33 columns in the 12.2.2 ETRM repository.

Functionally, the table operates as the parent of the debrief line detail structure. The header holds document-level attributes such as debrief number, debrief date, processing state, and travel measurements, while the corresponding lines — held in CSF_DEBRIEF_LINES — capture the individual service, material, labor, or charge entries that make up the report. A single debrief header therefore anchors a one-to-many relationship with its lines, and a many-to-one relationship with the underlying task assignment that the technician executed.

From a Data Vault modeling perspective, the ETRM relationship metadata classifies this object as satellite-leaning. This is a heuristic suggestion rather than a normative declaration: the table carries a surrogate primary key, a natural business key (the debrief number), and a set of descriptive and status attributes that otherwise behave as a satellite surrounding a task assignment hub. The presence of CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE confirms that the table maintains standard Oracle EBS audit columns, and the OBJECT_VERSION_NUMBER column supports optimistic locking during concurrent updates through the OAF-based Field Service application pages.

Key Information Stored

The primary key of the table is CSF_DEBRIEF_HEADERS_PK, defined on the surrogate column DEBRIEF_HEADER_ID. This identifier is system-generated and is the value carried into CSF_DEBRIEF_LINES as the foreign key DEBRIEF_HEADER_ID, making it the principal join column across the debrief structure.

• DEBRIEF_HEADER_ID — surrogate primary key; the unique internal identifier of the debrief.
• DEBRIEF_NUMBER — the user-visible business key; uniquely constrained by unique index CSF_DEBRIEF_HEADERS_U1 and referenced as a second business-key candidate by CSF_DEBRIEF_HEADERS_U2.
• DEBRIEF_DATE — the date the field service debrief was recorded; the primary time dimension for reporting.
• DEBRIEF_STATUS_ID — status lookup for the debrief lifecycle, distinguishing draft, submitted, and processed reports.
• TASK_ASSIGNMENT_ID — foreign key to JTF_TASK_ASSIGNMENTS; identifies the task assignment to which the debrief belongs.
• PROCESSED_FLAG — indicates whether the debrief has been consumed by downstream processing.
• STATISTICS_UPDATED — flag tracking whether associated statistical aggregates have been refreshed.
• TRAVEL_START_TIME and TRAVEL_END_TIME — travel window for the visit, supporting elapsed-time calculations.
• TRAVEL_DISTANCE_IN_KM — recorded distance travelled, typically used for mileage reimbursement or cost allocation.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; enforces multi-tenant data segregation.
• OBJECT_VERSION_NUMBER — optimistic locking control for the Field Service UI.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, used for customer-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard auditing columns.

Common Use Cases and Queries

The most frequent access pattern is retrieving debriefs for a given task assignment, or retrieving all lines for a given debrief header. A typical join uses the primary key against the child table:

• Header-to-line retrieval: join CSF_DEBRIEF_HEADERS.DEBRIEF_HEADER_ID to CSF_DEBRIEF_LINES.DEBRIEF_HEADER_ID to produce a complete field service report.
• Assignment-based lookup: query by TASK_ASSIGNMENT_ID to list every debrief raised against a task assignment, joined to JTF_TASK_ASSIGNMENTS for task context.
• Business-key lookup: search by DEBRIEF_NUMBER when the user supplies a document number rather than an internal ID.
• Processing and reconciliation reports: filter on PROCESSED_FLAG or STATISTICS_UPDATED to find unprocessed debriefs awaiting integration.
• Travel and mileage reporting: aggregate TRAVEL_DISTANCE_IN_KM over DEBRIEF_DATE ranges, grouped by technician or organization, using TRAVEL_START_TIME / TRAVEL_END_TIME to derive elapsed trip duration.
• Multi-org aware queries: constrain SECURITY_GROUP_ID where data segregation applies.

A representative query joining header and lines is:

SELECT h.debrief_number, h.debrief_date, l.debrief_line_id FROM csf_debrief_headers h, csf_debrief_lines l WHERE h.debrief_header_id = l.debrief_header_id AND h.task_assignment_id = :assignment_id;

Related Objects

• CSF_DEBRIEF_LINES — the child detail table; joined on CSF_DEBRIEF_LINES.DEBRIEF_HEADER_ID = CSF_DEBRIEF_HEADERS.DEBRIEF_HEADER_ID.
• JTF_TASK_ASSIGNMENTS — the parent task assignment; joined on CSF_DEBRIEF_HEADERS.TASK_ASSIGNMENT_ID = JTF_TASK_ASSIGNMENTS.TASK_ASSIGNMENT_ID.
• FND_SECURITY_GROUPS — security grouping reference; joined on SECURITY_GROUP_ID.
• CSF_DEBRIEF_HEADERS_PK — the primary key constraint; supports single-row lookup by DEBRIEF_HEADER_ID.
• CSF_DEBRIEF_HEADERS_U1 and CSF_DEBRIEF_HEADERS_U2 — unique indexes on DEBRIEF_HEADER_ID and DEBRIEF_NUMBER respectively.
• Field Service Report APIs and concurrent programs that consume debrief headers and lines in the CSF module.