Results for “css_def_def_sources_b”

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

Overview

CSS_DEF_DEF_SOURCES_B is a base table in the Oracle E-Business Suite CSS (Support) module, which is designated as obsolete in the ETRM metadata for releases 12.1.1 and 12.2.2. The table models the relationship between a defect record and the source files (and their versions) that are associated with that defect. As the description states, "A Defect may have multiple Source Files and Source File versions associated with it. This table stores the Source file name and version." This is a classic one-to-many detail structure: a single defect in CSS_DEF_DEFECTS_B can be linked to many rows in CSS_DEF_DEF_SOURCES_B, each representing an individual source file and its version.

From a Data Vault modeling perspective, the metadata's heuristic classification marks this object as satellite-leaning. This is consistent with its structure: it hangs off a parent business entity (the defect, a hub) and records descriptive, historical-detail attributes — file names and versions — that describe the defect's associated source artifacts rather than defining a new core business key. It functions as an attributive satellite to the defect hub, though its identifying surrogate key (DEF_SOURCE_ID) gives it independent row identity.

Key Information Stored

The table's columns are not exhaustively enumerated in the ETRM excerpt, but the documented keys and foreign keys identify the most important fields. The surrogate primary key is DEF_SOURCE_ID, enforced by the constraint CSS_DEF_DEF_SOURCES_B_PK. This is the technical row identifier and should not be treated as a business key.

The principal foreign key is DEFECT_ID, which references CSS_DEF_DEFECTS_B. This column is the join back to the parent defect and is the primary business-meaningful relationship column; it is the strongest business-key candidate for relating a source file to its defect. Beyond these documented key columns, and consistent with the table's stated purpose, the table stores the source file name and the source file version associated with each defect. Additional descriptive attributes may exist but are not documented in the provided metadata. Note that the metadata states "Not implemented in this database," indicating the table is not physically present in the reference database where the ETRM data was mined.

Common Use Cases and Queries

Because the object is obsolete, most practical interest in CSS_DEF_DEF_SOURCES_B is oriented toward historical data extraction, legacy migrations, or auditing rather than active transactional use. Typical reporting scenarios include listing all source files tied to a given defect, tracing which file versions were in play for a defect, and counting source files per defect for workload or complexity metrics.

A representative query joining the detail table back to its parent defect would take the pattern:

• SELECT src.DEF_SOURCE_ID, src.DEFECT_ID, src.SOURCE_FILE_NAME, src.SOURCE_FILE_VERSION FROM CSS_DEF_DEF_SOURCES_B src, CSS_DEF_DEFECTS_B def WHERE src.DEFECT_ID = def.DEFECT_ID AND src.DEFECT_ID = :defect_id;
• Aggregate reporting: SELECT DEFECT_ID, COUNT(*) source_file_count FROM CSS_DEF_DEF_SOURCES_B GROUP BY DEFECT_ID;
• Migration extract filtering to a target set of defects using the DEFECT_ID foreign key as the driver.

Consumers should first confirm the table's existence in the target environment, since the ETRM metadata records it as not implemented in the mined database.

Related Objects

The most significant related object is the parent defect table, CSS_DEF_DEFECTS_B, joined via CSS_DEF_DEF_SOURCES_B.DEFECT_ID = CSS_DEF_DEFECTS_B.DEFECT_ID. This is the only foreign-key relationship documented in the provided metadata and is therefore the primary dependency. Any dependent views, concurrent programs, or forms in the CSS Support module that display defect source files would reference this table through that same DEFECT_ID linkage. Because the metadata does not document additional foreign keys, reverse-dependency objects are not enumerated here; integrators should mine the data dictionary for any views or packages referencing CSS_DEF_DEF_SOURCES_B directly.