Results for “invbv_customer_items”

32 results




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

Overview

The APPS.INVBV_CUSTOMER_ITEMS view is a read-only reporting object that belongs to the Oracle Inventory (INV) product family. It exposes customer item definitions maintained in Oracle Inventory alongside the customer identification and address information associated with each definition. In Oracle EBS Release 12.1.1 and 12.2.2, customer items are a core construct for conducting business with specific trading partners: they allow a manufacturer or supplier to map its own internal inventory items to the numbering conventions and descriptions used by a particular customer. The MTL_CUSTOMER_ITEMS entity stores that cross-reference, while the view joins it to the Oracle Receivables party and site model so that reporting users can retrieve customer names and addresses without constructing the multi-table join themselves.

The view is documented in ETRM as retrofitted, indicating that its definition was adapted during the R12 upgrade cycle, most notably to incorporate the HZ (Trading Community Architecture) party and location tables that replaced the earlier customer tables. Because the view includes the WITH READ ONLY clause, it cannot be used as the basis for DML; it is intended strictly for queries, reports, and integrations that require a flattened, human-readable presentation of customer item master data. The description column searched by users, CUSTOMER_ITEM_DESC, is exposed directly, which makes the view a convenient anchor for reporting on customer-specific item descriptions.

Underlying Base Objects

The view text references a single base table, MTL_CUSTOMER_ITEMS, joined to several HZ and AR objects. MTL_CUSTOMER_ITEMS supplies the customer item number, description, tolerances, planning flags, and the various container and commodity references. HZ_CUST_ACCOUNTS provides the customer account identifier, while HZ_PARTIES supplies PARTY_NAME, which the view exposes as the customer name. Address details are drawn from HZ_LOCATIONS, filtered through HZ_PARTY_SITES and HZ_CUST_ACCT_SITES_ALL so that only sites belonging to the relevant account are returned, with organization identifiers aligned through HZ_LOC_ASSIGNMENTS. AR_LOOKUPS is joined with an outer join on the customer category code and the ADDRESS_CATEGORY lookup type, yielding the MEANING column that translates stored codes into user-facing values.

The documented referenced objects are AR_LOOKUPS (VIEW), HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_LOCATIONS, HZ_LOC_ASSIGNMENTS, HZ_PARTIES, HZ_PARTY_SITES, and MTL_CUSTOMER_ITEMS, all resolved in the APPS schema. The address subquery is joined using an outer join to the customer item record, so customer items without an associated address still appear in the result set.

Key Columns

Common Use Cases and Queries

The most frequent use of this view is to report on customer item cross-references and their descriptive text, particularly where a customer requests reconciliation of their item descriptions against the supplier's records. A typical query filters on the description column:

  • SELECT customer_name, customer_item_name, customer_item_desc FROM apps.invbv_customer_items WHERE UPPER(customer_item_desc) LIKE '%BRACKET%';
  • SELECT customer_name, customer_item_name FROM apps.invbv_customer_items WHERE inactive_flag = 'N';
  • SELECT customer_name, country, customer_item_name FROM apps.invbv_customer_items ORDER BY customer_name;

Additional scenarios include extracting active customer item catalogs for EDI or order management integration, validating address data assigned to customer items, and auditing planning tolerance values across a customer base. Because the view performs the HZ joins internally and applies the outer join to addresses, consumers should not assume ADDRESS_ID is always populated; report logic should tolerate null address values for customer items defined without a site.