Results for “csf_debrief_lab_lines_v”

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

Overview

CSF_DEBRIEF_LAB_LINES_V is a Field Service (CSF) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes Field Service Report labor line information, presenting the labor lines captured during a debrief — the point at which a field service technician records the work performed, materials consumed, labor time, and mileage against a service request or task. The view consolidates attributes from the underlying debrief line table with descriptive and validation information drawn from transaction types, item definitions, billing type categories, and lookup values.

The view plays a key role in reporting and integration scenarios where labor lines must be presented with human-readable descriptions rather than raw foreign keys. Because it resolves the transaction type name and description, the labor reason meaning, and confirms that the referenced item is billable within the appropriate billing category, it is suited to charge processing, service billing reconciliation, and operational reporting on field service activity. It is also relevant to developers searching for cs_transaction_types_vl, since that view is one of the referenced base objects supplying the transaction type name and description columns.

Underlying Base Objects

The view is defined as a UNION of two SELECT statements over the same core table, distinguishing rows by channel or processing context. Its documented base objects are:

• CSF_DEBRIEF_LINES (SYNONYM) — the driving table containing the debrief labor line records.
• CS_TRANSACTION_TYPES_VL (VIEW) — supplies TRANSACTION_TYPE_ID, NAME, and DESCRIPTION, translating the transaction type identifier into a displayable label.
• CS_BILLING_TYPE_CATEGORIES (SYNONYM) — joined to filter or categorize billable items by billing category.
• MTL_SYSTEM_ITEMS_B_KFV (VIEW) — the key-flexfield item view providing inventory item attributes, including the material billable flag.
• FND_LOOKUPS (VIEW) — an outer-joined lookup source on lookup type CSF_LABOR_REASON, yielding the FL.MEANING column for the labor reason code.
• CS_STD (PACKAGE) — invoked as CS_STD.GET_ITEM_VALDN_ORGZN_ID to resolve the item validation organization.
• FND_GLOBAL (PACKAGE) — typically used for session context such as user and responsibility.

The join logic links the debrief line's TRANSACTION_TYPE_ID to the transaction type view, the item to the item flexfield view restricted to the validation organization, and the item's billable flag to the billing type category where the billing category equals 'L' (labor).

Key Columns

• DEBRIEF_LINE_ID / DEBRIEF_HEADER_ID — primary identifier of the labor line and its parent debrief header.
• CHANNEL_CODE — identifies the channel through which the line was captured.
• TRANSACTION_TYPE_ID / NAME / DESCRIPTION — the transaction type and its descriptive text from CS_TRANSACTION_TYPES_VL.
• INVENTORY_ITEM_ID, UOM_CODE — the item and unit of measure for the labor line.
• QUANTITY — quantity of labor or material recorded.
• LABOR_START_DATE / LABOR_END_DATE, SERVICE_DATE — labor interval and service date.
• STARTING_MILEAGE / ENDING_MILEAGE — mileage captured for the service visit.
• LABOR_REASON_CODE and FL.MEANING — the reason code and its decoded meaning.
• CHARGE_UPLOAD_STATUS / CHARGE_UPLOAD_MSG_CODE / CHARGE_UPLOAD_MESSAGE / ERROR_TEXT — charge upload processing state and diagnostics.
• ATTRIBUTE1–15, ATTRIBUTE_CATEGORY — descriptive flexfield segments.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and ROWID.

Common Use Cases and Queries

Typical uses include extracting labor lines for a debrief header, reporting labor by transaction type, and auditing charge upload failures. A representative query selecting labor lines with their transaction type and item follows:

• SELECT debrief_header_id, debrief_line_id, name, inventory_item_id, quantity, labor_start_date, labor_end_date, meaning, charge_upload_status FROM csf_debrief_lab_lines_v WHERE debrief_header_id = :p_header_id;
• SELECT name, COUNT(*), SUM(quantity) FROM csf_debrief_lab_lines_v WHERE service_date BETWEEN :p_from AND :p_to GROUP BY name;
• SELECT debrief_line_id, charge_upload_status, error_text FROM csf_debrief_lab_lines_v WHERE charge_upload_status = 'ERROR';

Because it is a UNION view over debrief lines, callers should de-duplicate on DEBRIEF_LINE_ID where necessary. The view is read-only and should be consumed for reporting and integration rather than updated directly.