Results for “est_line_source_type_code”

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

Overview

CSD.CSD_REPAIR_ESTIMATE_LINES is a transactional table in the Depot Repair (CSD) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores the individual estimate lines associated with a repair order estimate, functioning as the bridge between a depot repair estimate header and the underlying service charge lines defined in Oracle Service. Each row represents one charge line or cost element presented to the customer for approval before repair work proceeds.

The table holds a reference to CS_ESTIMATE_DETAILS, which supplies the canonical charge line definition, while additional depot-specific attributes such as item cost, resource associations, and override flags are stored locally. In Data Vault modeling terms, the metadata classifies this object heuristically as a link, since it resolves many-to-many style relationships between the repair estimate header, the service estimate detail, and BOM resources. It carries descriptive and foreign-key attributes rather than serving as a standalone hub or satellite.

Key Information Stored

The physical schema documents 35 columns. The most significant include:

• REPAIR_ESTIMATE_LINE_ID — surrogate primary key, enforced by CSD_REPAIR_ESTIMATE_LINES_PK and mirrored in the unique index CSD_REPAIR_ESTIMATE_LINES_U1. This is the single unique business-key candidate documented.
• REPAIR_ESTIMATE_ID — foreign key to CSD_REPAIR_ESTIMATE, tying each line to its parent estimate header.
• ESTIMATE_DETAIL_ID — foreign key to CS_ESTIMATE_DETAILS, linking to the Service charge line definition.
• RESOURCE_ID — foreign key to BOM_RESOURCES, identifying the resource (labor, material, or equipment) consumed.
• RO_SERVICE_CODE_ID — foreign key to CSD_RO_SERVICE_CODES, associating a depot service code.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org data security.
• ITEM_COST and ORIGINAL_COST — monetary values capturing the current and pre-override cost of the line.
• OVERRIDE_CHARGE_FLAG — indicates whether the calculated charge was manually overridden.
• EST_LINE_SOURCE_TYPE_CODE, EST_LINE_SOURCE_ID1, EST_LINE_SOURCE_ID2 — identify the originating source object for the estimate line.
• JUSTIFICATION_NOTES — free-text rationale, useful in approval and audit workflows.
• OBJECT_VERSION_NUMBER — optimistic locking column for concurrent updates.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and 15 extensible ATTRIBUTE1–15 columns with a CONTEXT discriminator.

Common Use Cases and Queries

Typical reporting retrieves all estimate lines for a given repair order to present an itemized quote. A representative query joins the header, line, and service detail:

• SELECT l.repair_estimate_line_id, l.item_cost, l.original_cost, l.override_charge_flag, e.estimate_detail_id FROM csd.csd_repair_estimate_lines l JOIN csd.csd_repair_estimate h ON h.repair_estimate_id = l.repair_estimate_id WHERE h.repair_estimate_id = :p_estimate_id;
• Cost variance analysis comparing ITEM_COST against ORIGINAL_COST to detect overridden charges.
• Resource usage reporting by joining RESOURCE_ID to BOM_RESOURCES.
• Audit queries filtering on JUSTIFICATION_NOTES to review override approvals.
• Multi-org reporting constrained by SECURITY_GROUP_ID derived from FND_SECURITY_GROUPS.

Because EST_LINE_SOURCE_TYPE_CODE and the source ID columns identify upstream origin, these are frequently used to trace estimate lines back to service requests or orders in reconciliation reports.

Related Objects

The following objects are most significant, based on documented foreign-key relationships:

• CSD_REPAIR_ESTIMATE — parent header; joined via REPAIR_ESTIMATE_ID.
• CS_ESTIMATE_DETAILS — Service charge line definition; joined via ESTIMATE_DETAIL_ID (documented twice, indicating a repeated or composite relationship).
• BOM_RESOURCES — resource master; joined via RESOURCE_ID.
• CSD_RO_SERVICE_CODES — depot service code reference; joined via RO_SERVICE_CODE_ID.
• FND_SECURITY_GROUPS — multi-org security reference; joined via SECURITY_GROUP_ID.

These relationships make the table central to depot repair estimate reporting and to integration with Oracle Service and Bills of Material costing.