Search Results veh_mtl_commodity_codes

Overview

The VEH_MTL_COMMODITY_CODES table is a data object within the now-obsolete Automotive Integration Kit (VEH) for Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. Its primary role was to store automotive-specific commodity code information required for integration with CARaS (Customer Acceptance and Release System), a system used in automotive manufacturing for managing supplier part validation and shipping authorization. This table served as an extension to standard inventory functionality, capturing industry-specific attributes necessary for supply chain communication and compliance within the automotive sector. As the product module is marked obsolete, this table is typically not present in standard EBS implementations unless the specific automotive kit was historically installed.

Key Information Stored

Based on the provided ETRM metadata, the table's structure centers on a primary key identifier. The most critical column is COMMODITY_CODE_ID, which uniquely identifies each automotive commodity code record. While the full column list is not detailed in the excerpt, a table of this nature in an automotive context would typically store data such as a unique commodity code, descriptions, classification hierarchies, and potentially flags linking it to specific Original Equipment Manufacturer (OEM) standards or part categorization systems used for supplier communication. The primary purpose was to map internal inventory items to the precise commodity codes mandated by automotive customers for labeling, shipping, and electronic data interchange (EDI) transactions.

Common Use Cases and Queries

The primary use case involved associating inventory items with automotive customer-specific commodity codes for generating advanced shipping notices (ASNs) and other EDI documents like 830 schedules and 862 call-offs. A typical query would retrieve the commodity code for a given item to populate outbound transaction data. For example, a report or interface program might execute a SQL pattern joining this table to inventory master data. However, as the metadata explicitly states "Not implemented in this database," these use cases are theoretical for a standard instance. Sample SQL would be contingent on discovering related tables via the documented primary key relationship.

Related Objects

The primary documented relationship for this table is its own primary key constraint, VEH_COMMODITY_CODES_PK, defined on the COMMODITY_CODE_ID column. This indicates that COMMODITY_CODE_ID is the unique identifier for records in this table and would be the referenced column in any foreign key relationships from other tables within the obsolete VEH module. Potential related objects, though not specified in the excerpt, could include tables storing item-customer combinations or EDI transaction staging tables that would hold the COMMODITY_CODE_ID as a foreign key to retrieve the specific code for transmission. Without the VEH module installed, no standard EBS tables reference this object.