Results for “delete_mark”

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

Overview

OP_GNRC_ITM_VW2 is a database view owned by the APPS schema within Oracle E-Business Suite, documented under the GML - Process Manufacturing Logistics product family. Its stated purpose in the ETRM metadata is a "View on customer/generic item table." In practice, the view provides a denormalized, report-friendly projection that resolves the numeric generic item identifier stored on the customer/generic item mapping table into the human-readable item number maintained on the master item table. This makes the view particularly useful where a generic item identifier alone would be meaningless to end users, report authors, or integration consumers.

The view is relevant to both Oracle EBS 12.1.1 and 12.2.2, since the underlying GML tables and the IC_ITEM_MST master item table retain the same core structure across these releases. The object carries a VALID status in the APPS schema, indicating it is a supported, compiled database object rather than an orphaned artifact. A defining characteristic of this view is that it is filtered to customers identified by CUST_ID = 0 and to generic records where GENERIC_ID is not zero, so it effectively returns only the "generic" subset of the customer/generic item mapping rather than the full mapping population.

Underlying Base Objects

The ETRM 12.2.2 metadata documents two referenced base objects, both exposed through synonyms: IC_ITEM_MST and OP_GNRC_ITM. The view definition joins these two tables on ITEM_ID:

• OP_GNRC_ITM — the customer/generic item table. In this join it is aliased G and provides the generic item identifier (GENERIC_ITEM), the customer identifier (CUST_ID), the item identifier (ITEM_ID), the generic identifier (GENERIC_ID), and the deletion flag (DELETE_MARK).
• IC_ITEM_MST — the Inventory item master table, aliased I. It supplies the descriptive item number (ITEM_NO) that corresponds to the ITEM_ID in OP_GNRC_ITM.

Because both base objects are accessed through APPS synonyms, the view is portable across environments where the underlying physical tables may reside in different schemas. The join condition G.ITEM_ID = I.ITEM_ID is the mechanism that links the generic mapping record to its master item description.

Key Columns

The view exposes three columns:

• GENERIC_ITEM — the generic item identifier drawn from OP_GNRC_ITM. This is the numeric key that classifies the item under a generic grouping.
• ITEM_NO — the item number sourced from IC_ITEM_MST. This is the user-facing, meaningful identifier for the item, and it is the principal value of the view since it transforms a numeric reference into an intelligible item name.
• DELETE_MARK — the soft-delete indicator from OP_GNRC_ITM. A non-zero value conventionally represents a logically deleted record, allowing consumers to filter out obsolete mappings without physically removing them.

Consumers should note that the view does not itself filter on DELETE_MARK; records marked for deletion are returned, and filtering is left to the query author.

Common Use Cases and Queries

The view is typically used in GML process manufacturing reporting, where generic item classifications must be presented alongside readable item numbers. A representative query lists all active generic item mappings:

• SELECT generic_item, item_no FROM apps.op_gnrc_itm_vw2 WHERE delete_mark = 0 ORDER BY item_no;
• SELECT generic_item, COUNT(*) FROM apps.op_gnrc_itm_vw2 WHERE delete_mark = 0 GROUP BY generic_item; — summarizes how many items map to each generic classification.
• SELECT v.item_no FROM apps.op_gnrc_itm_vw2 v WHERE v.generic_item = :generic_id AND v.delete_mark = 0; — resolves a specific generic item to its associated item numbers.

Because the view restricts results to CUST_ID = 0 and GENERIC_ID <> 0, it is best suited to the standard generic-item scenario. When customer-specific mappings or all generic identifiers are required, the base tables OP_GNRC_ITM and IC_ITEM_MST should be queried directly, as the view intentionally narrows the result set.