Search Results customer_category_code




Overview
Explore in AI Chat

Overview

INVFV_CUSTOMER_ITEMS is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Inventory (INV) module. It consolidates customer item definition data with customer, address, commodity, organization, and inventory item attributes, presenting a denormalized result set suitable for inquiry, reporting, and integration scenarios. The view is particularly relevant to users searching on the customer_item_number attribute, since that column appears twice in the projection — once from the primary customer item record (CUIT1) and once from a related customer item record (CUIT2). This dual exposure supports both direct lookups of a customer's part number and cross-reference queries that compare a customer item to its related model or master definition. In ETRM 12.2.2 the object is documented as VALID under the INV product, confirming its continued availability across the 12.1.1 and 12.2.2 code lines.

Underlying Base Objects

The view is defined over a mixture of MTL, HZ, and AR objects, joined to resolve customer, site, and item context. The documented base objects are: MTL_CUSTOMER_ITEMS (the central table holding customer item definitions), MTL_SYSTEM_ITEMS (joined twice, as SY1 and SY2), MTL_PARAMETERS, MTL_COMMODITY_CODES, HR_ALL_ORGANIZATION_UNITS, HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_LOCATIONS, HZ_LOC_ASSIGNMENTS, HZ_PARTY_SITES, and AR_LOOKUPS. The HZ location tables are combined in an inline subquery that resolves address and site information through HZ_LOC_ASSIGNMENTS, HZ_LOCATIONS, HZ_CUST_ACCT_SITES_ALL, and HZ_PARTY_SITES, matching on PARTY_SITE_ID, LOCATION_ID, and an NVL-normalized ORG_ID. MTL_PARAMETERS supplies the inventory organization context (ORGANIZATION_CODE via HR_ALL_ORGANIZATION_UNITS), while AR_LOOKUPS resolves the item definition level meaning. The joins therefore bridge customer master data (HZ_PARTIES, HZ_CUST_ACCOUNTS) to customer item definitions (MTL_CUSTOMER_ITEMS) and to the internal inventory items they reference (MTL_SYSTEM_ITEMS).

Key Columns

Common Use Cases and Queries

Typical uses include retrieving all customer item definitions for a given customer, mapping a customer part number to an internal inventory item, and validating addresses and tolerances for demand planning. Because the view already joins HZ and MTL data, it removes the need for ad hoc joins in reports and interfaces.

Sample query by customer item number:

  • SELECT customer_item_number, party_name, organization_code, customer_item_desc, customer_category_code FROM apps.invfv_customer_items WHERE customer_item_number = :p_item_number;
  • SELECT c.customer_item_number, c.party_name, c.commodity_code, c.address_id FROM apps.invfv_customer_items c WHERE c.customer_id = :p_customer_id ORDER BY c.customer_item_number;
  • SELECT customer_item_number, party_name, country, city, demand_tolerance_positive FROM apps.invfv_customer_items WHERE party_name LIKE :p_party_name;

These queries support customer item cross-reference maintenance, order-entry validation of customer part numbers, and demand planning extracts where tolerance and fill percentage data are required alongside the customer's item number.