Search Results gr_whse_default




Overview
Explore in AI Chat

Overview

APPS.GR_ALL_ITEMS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, owned by the APPS schema and documented within the ETRM (E-Business Suite Technical Reference Manual) repository. It presents a consolidated list of item codes and descriptions drawn from inventory master data and multilingual reference data. The view is a core component of the Oracle Process Manufacturing (OPM) / Oracle Quality / GR (goods receipt) family of objects, where "GR" objects typically support goods receipt, item validation, and label-related processing.

Functionally, the view answers the question: "Which items are available for selection in a GR-related context, presented with a single user-facing code and description?" It combines inventory items from a specific warehouse organization with a set of multilingual name translations, producing a unique, ordered list of ITEM_CODE / DESCRIPTION pairs. Because the view filters on the GR_WHSE_DEFAULT profile option and excludes items already present in GR_ITEM_GENERAL, it serves as a "candidate item" or "available item" lookup rather than a complete inventory listing.

For a user searching on "item_code", the view is directly relevant: ITEM_CODE is the first column projected, and it is the primary join key used by downstream forms, concurrent programs, and label/report templates.

Underlying Base Objects

The view is defined over the following documented base objects:

  • MTL_SYSTEM_ITEMS (synonym) — the inventory item master, providing SEGMENT1 (the item code), DESCRIPTION, ENABLED_FLAG, and ORGANIZATION_ID.
  • HR_ALL_ORGANIZATION_UNITS (synonym) — the organization definition, used to resolve ORGANIZATION_ID to an organization name and to constrain results to the default GR warehouse.
  • GR_ITEM_GENERAL (synonym) — the GR item general table, used in a NOT IN subquery to exclude items already registered in the GR item master.
  • GR_MULTILINGUAL_NAME_TL (synonym) — the multilingual name translation table, contributing translated item codes and descriptions where LABEL_CODE = '11007'.
  • FND_PROFILE (package) — invoked as FND_PROFILE.VALUE('GR_WHSE_DEFAULT') and USERENV('LANG') to supply the default warehouse and the current session language.

The view is a UNION of two branches, ordered by column 1 (ITEM_CODE). The first branch joins MTL_SYSTEM_ITEMS to HR_ALL_ORGANIZATION_UNITS and applies the enabled-flag and exclusion filters. The second branch draws translated names from GR_MULTILINGUAL_NAME_TL, unioning them into the same two-column result shape.

Key Columns

  • ITEM_CODE — the item identifier. In the inventory branch this is MTL_SYSTEM_ITEMS.SEGMENT1; in the translation branch it is GR_MULTILINGUAL_NAME_TL.ITEM_CODE. This is the column matched by searches such as "item_code".
  • DESCRIPTION — the human-readable item description. The inventory branch uses MTL_SYSTEM_ITEMS.DESCRIPTION; the translation branch uses GR_MULTILINGUAL_NAME_TL.NAME_DESCRIPTION.

Both columns are exposed under their alias names. The view intentionally limits its projection to these two fields, keeping it lightweight for LOV (List of Values) and lookup scenarios.

Common Use Cases and Queries

Typical scenarios include populating an item LOV in a GR or label form, validating that an item code is available for GR registration, and generating multilingual item lists for user-facing reports. A representative query is:

  • SELECT ITEM_CODE, DESCRIPTION FROM APPS.GR_ALL_ITEMS_V WHERE ITEM_CODE LIKE :p_item_code ORDER BY ITEM_CODE;
  • SELECT ITEM_CODE, DESCRIPTION FROM APPS.GR_ALL_ITEMS_V WHERE UPPER(DESCRIPTION) LIKE '%'||UPPER(:p_desc)||'%';
  • SELECT COUNT(*) FROM APPS.GR_ALL_ITEMS_V; — to gauge the candidate set for the current warehouse.

Because the result set depends on the GR_WHSE_DEFAULT profile value and the session language, integrations should set the profile option and language context before querying, and should not assume the view returns the full inventory master. Items already defined in GR_ITEM_GENERAL are deliberately excluded, so the view is best understood as a "not-yet-registered, enabled, warehouse-specific item" lookup.