Search Results veh_mtl_customer_item_pk

Overview

The VEH_MTL_CUSTOMER_ITEMS table is a data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, specifically architected for the now-obsolete Automotive Integration Kit (VEH). Its primary role was to store automotive-specific metadata related to customer items within the Inventory module, serving as an extension to standard Oracle Inventory functionality. This data was explicitly required to support CARaS (Customer Acceptance and Release System), a common automotive industry process for managing part approval and release between suppliers and original equipment manufacturers (OEMs). The table's design facilitates the association of customer-specific item information with internal inventory items and organizations, enabling the traceability and compliance reporting critical in automotive supply chains.

Key Information Stored

Based on the provided ETRM metadata, the table's structure is defined to enforce unique automotive customer item records through its primary key. The key columns are:

• CUSTOMER_ITEM_ID: Likely a foreign key linking to the standard customer item definition, possibly referencing MTL_CUSTOMER_ITEMS or a similar base table.
• ORGANIZATION_ID: Identifies the specific inventory organization to which this automotive customer item data is scoped, ensuring data isolation by operating unit.
• TP_GROUP_ID: A critical identifier directly referenced in the user's search. This column would store a key for a "Trading Partner Group," which is a common automotive concept for classifying customers (OEMs) based on shared business rules, release schedules, or communication standards (e.g., EDIFACT, ODETTE).

The combination of these three columns forms the primary key (VEH_MTL_CUSTOMER_ITEM_PK), guaranteeing uniqueness for a customer item within a given organization and trading partner group context.

Common Use Cases and Queries

This table supported specialized automotive processes. A primary use case was generating reports for CARaS, detailing which customer items, for specific trading partner groups, were active within an organization. A typical query would join this table to standard Inventory and Trading Partner master data to extract release information. For example, to find all automotive customer items for a specific TP_GROUP_ID:

• SELECT vci.* FROM VEH_MTL_CUSTOMER_ITEMS vci WHERE vci.TP_GROUP_ID = <group_id> AND vci.ORGANIZATION_ID = <org_id>;

Another common scenario involved integration with external CARaS systems, where this table acted as a source for data extracts containing the TP_GROUP_ID and related item identifiers, enabling automated customer release management.

Related Objects

The ETRM documentation explicitly states this table is "Not implemented in this database," indicating it may be a reference definition only in many installations. However, its logical relationships can be inferred from the primary key structure. It has a direct foreign key relationship with the base MTL_CUSTOMER_ITEMS table via the CUSTOMER_ITEM_ID column. It is also intrinsically linked to ORG_ORGANIZATION_DEFINITIONS via the ORGANIZATION_ID column. The TP_GROUP_ID would typically join to a trading partner group master table, which may be part of the obsolete VEH schema or a common trading partner setup. The table itself was central to the obsolete Automotive Integration Kit and was likely referenced by VEH-specific forms, concurrent programs, and CARaS interface programs.