Results for “tp_layer_id”

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

Overview

VEA_PACKAGES is a table in the VEA (Automotive) product schema of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It functions as a registry of packages that have been registered with the trading partner architecture repository. In practical terms, the table records which PL/SQL packages, and their associated specification and body files, are exposed to and consumed by the ETRM trading partner layer, so that the runtime infrastructure can resolve, version, and invoke those packages consistently across participating trading partners.

The object carries the status VALID and is owned by the VEA schema. Based on heuristic analysis of its foreign key structure, VEA_PACKAGES is classified as satellite-leaning in a Data Vault model. This classification is a modeling suggestion rather than a prescribed design; it reflects the fact that the table primarily carries descriptive attributes tied to a package identifier and one parent reference, rather than acting as a central hub or many-to-many link.

Key Information Stored

The table contains twenty-two documented columns. The most significant are summarized below.

• PACKAGE_ID — Surrogate identifier for the package record. Together with LAYER_PROVIDER_CODE it forms the composite primary key PK_VEA_PACKAGES and the unique index VEA_PACKAGES_U1.
• LAYER_PROVIDER_CODE — Code identifying the trading partner layer provider; part of the primary key and the foreign key to VEA_TP_LAYERS.
• NAME — The registered package name. With APPLICATION_SHORT_NAME and CLIENT_SERVER_FLAG it forms the business-key unique index VEA_PACKAGES_U2.
• APPLICATION_SHORT_NAME — Short name of the owning application, used to disambiguate packages with identical names.
• CLIENT_SERVER_FLAG — Indicates whether the package is intended for client-server execution.
• TP_LAYER_ID — Reference to the trading partner layer to which the package belongs.
• TPA_FLAG and GENERATE_FLAG — Control flags governing trading partner architecture inclusion and generation behavior.
• SPECIFICATION_FILENAME and BODY_FILENAME — File references for the package specification and body used during registration or generation.
• LABEL, VERSION_NUMBER, and DESCRIPTION — Descriptive and versioning attributes for the registered package.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE support auditing and concurrent program traceability.

Common Use Cases and Queries

Typical uses include auditing which packages are registered for a trading partner layer, verifying version and filename metadata before deployment, and tracing packages to their owning application. A query listing packages by layer might read:

SELECT p.PACKAGE_ID, p.NAME, p.APPLICATION_SHORT_NAME, p.VERSION_NUMBER
FROM VEA.VEA_PACKAGES p, VEA.VEA_TP_LAYERS l
WHERE p.LAYER_PROVIDER_CODE = l.LAYER_PROVIDER_CODE
AND p.TPA_FLAG = 'Y';

Reporting scenarios include reconciliation of registered packages against VEA_PROGRAM_UNITS, identification of packages pending generation (GENERATE_FLAG), and impact analysis when a layer provider is retired. Because the table is small and reference-oriented, queries are generally inexpensive and suitable for operational dashboards.

Related Objects

• VEA_TP_LAYERS — Parent table; joined on LAYER_PROVIDER_CODE.
• VEA_PROGRAM_UNITS — Child table referencing VEA_PACKAGES through LAYER_PROVIDER_CODE and PACKAGE_ID.
• PK_VEA_PACKAGES / VEA_PACKAGES_U1 — Primary key and unique index on LAYER_PROVIDER_CODE and PACKAGE_ID.
• VEA_PACKAGES_U2 — Business-key unique index on APPLICATION_SHORT_NAME, CLIENT_SERVER_FLAG, and NAME.
• FND_APPLICATION — Consulted to resolve APPLICATION_SHORT_NAME to an application identifier.