Results for “vea_tp_layers”

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

Overview

VEA_TP_LAYERS is a transactional configuration table in the Oracle EBS Automotive (VEA) product module. It stores "trading partner layers," which represent the organizational or commercial layers through which trading partners such as dealers, distributors, or OEM entities are classified and modeled. In EBS automotive flows, these layers act as a controlling dimension for how transactions, packages, and licensing rules are validated and applied between trading partners. The table resides in the VEA schema and is flagged as VALID in the documented environment.

From a modeling perspective, the mined metadata classifies this object as hub-leaning in a Data Vault heuristic. This suggests treating VEA_TP_LAYERS as a hub entity whose business key is a composite of the layer provider and the trading partner layer, with the surrounding descriptive columns behaving as satellite attributes. The primary key PK_VEA_TP_LAYERS (LAYER_PROVIDER_CODE, TP_LAYER_ID) reinforces this hub interpretation, as the key pairs a provider context with a layer identity.

Key Information Stored

The table is documented with 14 columns. The most significant are described below.

• TP_LAYER_ID — Surrogate identifier for the trading partner layer. Combined with LAYER_PROVIDER_CODE, it forms part of the primary key.
• LAYER_PROVIDER_CODE — Code identifying the provider of the layer. This is a leading component of the primary key and the unique index.
• NAME — Descriptive name of the layer. Together with LAYER_PROVIDER_CODE it forms the unique index UK1_VEA_TP_LAYERS, making (LAYER_PROVIDER_CODE, NAME) a strong business-key candidate.
• DESCRIPTION — Free-text description of the layer's purpose.
• ACTIVE_FLAG — Indicates whether the layer is currently active and eligible for use.
• CREATED_BY / CREATION_DATE — Standard audit columns recording who created the record and when.
• LAST_UPDATED_BY / LAST_UPDATE_DATE — Audit columns tracking the most recent change and its author.
• LAST_UPDATE_LOGIN — Login context associated with the last update.
• REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATE_DATE — Concurrent program context columns recording the program that last touched the row.

The surrogate primary key is (LAYER_PROVIDER_CODE, TP_LAYER_ID), while the unique index UK1_VEA_TP_LAYERS on (LAYER_PROVIDER_CODE, NAME) provides the natural business key.

Common Use Cases and Queries

Typical usage includes validating that a layer provider has an active trading partner layer before processing automotive transactions, driving package and license rules, and producing layer configuration reports.

List active layers for a provider:

• SELECT tp_layer_id, name, description FROM vea.vea_tp_layers WHERE layer_provider_code = :provider AND active_flag = 'Y';

Resolve a layer by its business key through the unique index:

• SELECT tp_layer_id FROM vea.vea_tp_layers WHERE layer_provider_code = :provider AND name = :name;

Reporting queries frequently join to VEA_PACKAGES and VEA_LAYER_LICENSES to summarize which packages and licenses depend on each layer, supporting impact analysis when a layer is deactivated.

Related Objects

The following objects reference or depend on VEA_TP_LAYERS, based on documented foreign key relationships.

• VEA_LAYER_LICENSES — References this table via LAYER_PROVIDER_CODE and TP_LAYER_ID, linking licenses to their trading partner layer.
• VEA_PACKAGES — References this table via LAYER_PROVIDER_CODE and TP_LAYER_ID, associating packages with their layer.

These dependents make VEA_TP_LAYERS a referenced parent. Changes to layer identity or provider codes cascade in meaning to both licensing and package configuration, so updates should account for dependent rows.