Results for “consign_ind”

4 results




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

Overview

IC_WHSE_MST_VW is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the GMI (Process Manufacturing Inventory) product family. Its documented description identifies it as a "View for pre migration UI mapping of warehouse," indicating that it was constructed to present warehouse master data in the shape required by the legacy or pre-migration user interface prior to the migration of Process Manufacturing warehouses into the discrete inventory organization model. The view carries a VALID status in both release 12.1.1 and 12.2.2 and serves as a compatibility and reporting layer rather than a transactional object.

Consumers of this view — custom reports, conversion programs, integration interfaces, and reconciliation scripts — obtain a consolidated warehouse record that blends native warehouse attributes from IC_WHSE_MST with costing warehouse attributes and the associated Oracle organization identifier. Because the view is read-only and joins several base objects, it is typically used for inquiry, extraction, and validation rather than for DML operations.

Underlying Base Objects

The documented metadata lists three referenced base objects, each accessed through a synonym: CM_WHSE_ASC, IC_WHSE_MST, and SY_ORGN_MST. The view definition joins them as follows:

  • IC_WHSE_MST is the driving table, aliased W, supplying warehouse code, name, organization code, tax location, staging indicators, and audit columns.
  • CM_WHSE_ASC is joined with an outer join on WHSE_CODE (C.WHSE_CODE (+) = W.WHSE_CODE), contributing COST_WHSE_CODE where a costing association exists.
  • SY_ORGN_MST is joined on ORGN_CODE (S.ORGN_CODE = W.ORGN_CODE), contributing the Oracle ORGANIZATION_ID.

The outer join to the costing table means that warehouses lacking a costing association still appear in the result set, with COST_WHSE_CODE null. The inner-style join on organization code requires that a matching organization master record exist for the row to be returned.

Key Columns

Common Use Cases and Queries

The view is commonly used to resolve TAXLOC_CODE for a given warehouse, to determine whether a warehouse has been migrated (MIGRATED_IND), and to reconcile costing warehouse mappings. A typical lookup by tax location code:

SELECT whse_code, whse_name, org_code, taxloc_code
FROM   apps.ic_whse_mst_vw
WHERE  taxloc_code = :p_taxloc_code
AND    NVL(delete_mark, 0) = 0;

Identifying unmigrated warehouses with their inventory organization:

SELECT v.whse_code, v.orgn_code, v.mtl_organization_id, v.organization_id
FROM   apps.ic_whse_mst_vw v
WHERE  NVL(v.migrated_ind, 'N') = 'N'
ORDER  BY v.whse_code;

Listing costing associations, preserving warehouses without one via the outer join:

SELECT whse_code, whse_name, cost_whse_code
FROM   apps.ic_whse_mst_vw
WHERE  cost_whse_code IS NULL;

Because the view exposes legacy identifiers alongside migrated organization values, it is well suited to pre-migration validation queries and post-migration reconciliation reports in both 12.1.1 and 12.2.2 environments.