Search Results csp_req_line_details




Overview
Explore in AI Chat

Overview

CSP_REQ_LINE_DETAILS is a table within the CSP (Spares Management) schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. The object is registered as VALID with a documented physical schema of nine columns. It serves as the detail-level repository for requirement line information captured through the Spares Management sourcing process, holding the individual source references that fulfill a given requirement line. Each row associates a requirement line with a specific source record, allowing the application to trace how demand for spare parts was satisfied — for example, from inventory, an internal order, or a procurement document.

From a heuristic Data Vault classification perspective, mined from the foreign key structure, this table is classified as standalone. A suggested modeling interpretation is that the table behaves as a satellite-like detail entity attached to its parent requirement line: it carries descriptive source attributes plus the standard EBS audit columns, and its grain is one row per requirement-line detail. Because the mining produced a standalone classification rather than a hub or link, the table should be treated as a dependent detail structure rather than an independent business key hub.

Key Information Stored

The table's documented columns include a single-column surrogate primary key and the following business-relevant attributes:

  • REQ_LINE_DETAIL_ID — the surrogate primary key, defined by constraint CSP_REQ_LINE_DETAILS_PK. It uniquely identifies each detail row and is not a meaningful business key.
  • REQUIREMENT_LINE_ID — the foreign key to CSP_REQUIREMENT_LINES, linking each detail record to its parent requirement line. This is the principal join column and the strongest candidate for a business-key relationship.
  • SOURCE_TYPE — classifies the nature of the originating source that satisfies the requirement line.
  • SOURCE_ID — identifies the specific source record referenced by SOURCE_TYPE. Together, SOURCE_TYPE and SOURCE_ID form the polymorphic business reference that points into the relevant upstream entity.
  • CREATED_BY, CREATION_DATE — the standard audit columns recording the user and timestamp of row insertion.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE — the standard audit columns recording the most recent modification and its timestamp.
  • LAST_UPDATE_LOGIN — the session login identifier associated with the last update.

No unique business-key index is documented beyond the primary key, so REQUIREMENT_LINE_ID does not enforce uniqueness; multiple source details may exist per requirement line.

Common Use Cases and Queries

Typical usage centers on tracing the sourcing of a requirement line and on supplying detail rows to the Spares Management requirement workbench. A standard query joins the detail table to its parent:

SELECT d.req_line_detail_id,
       d.requirement_line_id,
       d.source_type,
       d.source_id
FROM   csp.csp_req_line_details d
WHERE  d.requirement_line_id = :p_requirement_line_id;

Reverse-lookup reporting identifies which requirement lines reference a given source, using SOURCE_TYPE and SOURCE_ID as filters. Audit-oriented extracts use CREATION_DATE and LAST_UPDATE_DATE for incremental or change-data-capture style reporting. Data-quality checks commonly detect rows where SOURCE_ID is null or where SOURCE_TYPE is inconsistent, since these prevent the source reference from resolving.

Related Objects

  • CSP_REQUIREMENT_LINES — the parent table; join on CSP_REQ_LINE_DETAILS.REQUIREMENT_LINE_ID = CSP_REQUIREMENT_LINES.REQUIREMENT_LINE_ID.
  • CSP_REQUIREMENT_HEADERS — reached transitively through the parent requirement line for header-level reporting.
  • CSP_REQUIREMENTS-family views and workbench UI — consume the detail rows for sourcing display and processing.
  • Inventory and Order Management tables — the polymorphic SOURCE_TYPE/SOURCE_ID pair points into the appropriate upstream entity depending on source classification.
  • CSP_REQ_LINE_DETAILS_PK — the primary-key constraint enforcing uniqueness of REQ_LINE_DETAIL_ID.