Results for “vea_release_details”

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

Overview

VEA_RELEASE_DETAILS is a table in the VEA (Automotive) product schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its ETRM metadata description reads simply "Not currently used," which indicates that the object is retained for schema stability and possibly for backward compatibility with earlier releases or patch-line artifacts in the Automotive vertical. It is a technical/metadata-style repository rather than a transactional business table: the columns describe release identifiers, layer provider codes, file artifacts, and bug/fix references, which are characteristic of an internal patch or release tracking structure rather than day-to-day automotive processing.

The documented relation is physical only (a base table), with a composite primary key named PK_VEA_RELEASE_DETAILS. The heuristic Data Vault classification mined from the FK structure is "standalone." In Data Vault modeling terms, this suggests treating the object as a standalone satellite-like structure keyed by its natural business key, since no foreign-key dependencies were detected. A hub would normally be created for the release identifier and layer-provider combination if integration into a Data Vault warehouse were pursued, but the metadata supports the standalone interpretation.

Key Information Stored

The table contains 19 documented columns, of which the most significant are the composite key components and the descriptive attributes:

• RELEASE_ID – Identifier for the release to which the detail row belongs; a leading component of the primary key and unique index.
• LAYER_PROVIDER_CODE – Code identifying the layer provider, another key component.
• APPLICATION_SHORT_NAME – Short name of the EBS application (for example, a product abbreviation such as VEA), the third key component.
• FILE_NAME – Name of the file associated with the release; the fourth key component and the column that makes each row distinguishable.
• VERSION_NUMBER – Version of the tracked release artifact.
• FILE_PATH – Location of the file within the deployment or patch structure.
• TP_LAYER_ID – Identifier for the third-party or technology-provider layer.
• DESCRIPTION – Free-text description of the release detail.
• ARU_NUMBER – Application-related update (ARU) reference number.
• BUG_NUMBER – Reference to the associated bug or defect.
• CREATED_BY, CREATION_DATE – Standard WHO-column audit attributes recording creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Audit columns for the most recent change.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE – Standard concurrent-program context columns indicating the request that last touched the row.

The surrogate primary key is defined as PK_VEA_RELEASE_DETAILS over (FILE_NAME, LAYER_PROVIDER_CODE, RELEASE_ID, APPLICATION_SHORT_NAME). A separate unique index, VEA_RELEASE_DETAILS_U1, covers the same business columns in a different order (LAYER_PROVIDER_CODE, RELEASE_ID, APPLICATION_SHORT_NAME, FILE_NAME), confirming the natural business key of the table. The absence of separate ID columns means the business key effectively serves as the surrogate key.

Common Use Cases and Queries

Because the object is documented as "Not currently used," practical usage is limited. Reporting and investigation scenarios typically involve inspecting release lineage, locating a file by release, or verifying whether a specific bug or ARU is associated with a release. A representative query follows:

• Retrieve all files for a given release and provider:
  SELECT file_name, version_number, file_path, bug_number, aru_number FROM vea.vea_release_details WHERE release_id = :release_id AND layer_provider_code = :provider AND application_short_name = :app ORDER BY file_name;
• Look up details by bug number:
  SELECT release_id, application_short_name, file_name FROM vea.vea_release_details WHERE bug_number = :bug_number;
• Audit recent changes driven by concurrent programs:
  SELECT request_id, program_id, last_update_date, last_updated_by FROM vea.vea_release_details WHERE last_update_date >= :cutoff;

Joins to concurrent program tables (FND_CONCURRENT_REQUESTS) on REQUEST_ID allow tracing of the process that loaded or updated the detail rows. In practice, DBA or support teams inspect this table during upgrade validation or when diagnosing a stray release artifact.

Related Objects

The metadata records no foreign-key relationships, so related objects are inferred from the semantics of the columns and the standard EBS patterns present:

• FND_CONCURRENT_REQUESTS – join on REQUEST_ID to identify the concurrent request that last modified a row.
• FND_APPLICATION – join on APPLICATION_SHORT_NAME to resolve the application identity.
• FND_CONCURRENT_PROGRAMS – join on PROGRAM_APPLICATION_ID and PROGRAM_ID for program context.
• FND_USER – join on CREATED_BY and LAST_UPDATED_BY for user attribution.
• VEA_RELEASES (or an equivalent release header table) – expected parent of RELEASE_ID.
• VEA_LAYER_PROVIDERS (or equivalent) – expected parent of LAYER_PROVIDER_CODE and TP_LAYER_ID.

No incoming foreign keys were detected, confirming the standalone classification. The primary key constraint PK_VEA_RELEASE_DETAILS and the unique index VEA_RELEASE_DETAILS_U1 are the principal dependent objects that reference this table.