Results for “commodity_code_id”

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

Overview

VEH_MTL_COMMODITY_CODES is an Automotive-specific inventory table belonging to the VEH – Automotive Integration Kit, a module that is documented as obsolete in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The table stores commodity code information required by CARaS (the automotive industry data-exchange standard, historically associated with AIAG and the OEM shipping/receiving process). Its purpose is to hold inventory commodity code definitions that would otherwise be represented generically in Oracle Inventory, so that the automotive integration layer can map EBS inventory items to externally exchanged commodity classifications.

The ETRM metadata states that the table is not implemented in this database, a status consistent with the full Automotive Integration Kit being obsolete within the supported 12.1.1 / 12.2.2 code lines. The heuristic Data Vault classification mined from the foreign-key structure is standalone. As a modeling suggestion, this implies the table behaves as an independent reference set: because no parent links were detected, a Data Vault implementation would likely treat it as a hub-like reference entity rather than as a link or satellite dependent on other automotive exchange tables. Any such modeling should be validated against the actual deployment, since the object may simply be absent.

Key Information Stored

The documented metadata identifies the following structural elements rather than a full column list:

• COMMODITY_CODE_ID – the single documented column. It serves as the surrogate primary key and is the object of the user's search term.
• VEH_COMMODITY_CODES_PK – the primary key constraint defined on COMMODITY_CODE_ID, enforcing uniqueness of the surrogate identifier.

No business-key unique indexes, alternate keys, or descriptive columns (for example commodity code name, description, or external CARaS code values) are documented in the ETRM excerpt. Because the metadata provides only a primary key and no unique business index, COMMODITY_CODE_ID must be treated as a pure surrogate key rather than as a natural or business-key candidate. Practice in similar VEH reference tables suggests that additional attributes would have carried the automobile-industry code value, an effective date range, and an enabled flag, but these are not confirmed by the supplied metadata and should not be relied upon. Implementers should confirm the current column inventory directly through ALL_TAB_COLUMNS before using the table in any integration or conversion script.

Common Use Cases and Queries

Because the table is documented as not implemented, the primary practical use case is impact analysis and discovery: confirming whether an historical or customized EBS instance ever contained the object, and identifying dependent objects before an upgrade or migration. A typical discovery query is:

• SELECT * FROM all_tables WHERE table_name = 'VEH_MTL_COMMODITY_CODES'; to verify existence in the current database.
• SELECT * FROM all_tab_columns WHERE table_name = 'VEH_MTL_COMMODITY_CODES' ORDER BY column_id; to obtain the authoritative column list.
• SELECT * FROM all_constraints WHERE table_name = 'VEH_MTL_COMMODITY_CODES'; to confirm VEH_COMMODITY_CODES_PK and any undocumented constraints.

Where the table does exist—most likely in a legacy 11i or early 12.1 automotive-integration footprint—reporting scenarios would resolve COMMODITY_CODE_ID against dependent automotive exchange tables to produce commodity-level shipping, receiving, or EDI (DELFOR, DELJIT, DESADV) reconciliation reports. Reconciliation queries would join on the surrogate key to the foreign-key columns of any child tables present in that instance.

Related Objects

The supplied metadata documents only the primary key constraint VEH_COMMODITY_CODES_PK and explicitly classifies the object as standalone with no mined foreign-key relationships. Consequently, no dependent tables, views, or public APIs can be asserted from the documented facts alone. In a functioning Automotive Integration Kit instance, related objects would conventionally include the CARaS staging and interface tables that reference automotive inventory and commodity data, together with Oracle Inventory base tables such as MTL_SYSTEM_ITEMS_B, MTL_ITEM_CATEGORIES, and MTL_CATEGORIES, which hold the generic item and category structures that automotive commodity codes supplement. Any join between VEH_MTL_COMMODITY_CODES and those Inventory tables would have to be established through undocumented columns and should be verified against the actual deployment. Given the obsolete status of the VEH module, implementers should treat this object as a deprecated reference artefact and validate all relationships empirically before relying on it in production code.