Results for “instance_type_code”

50+ results




Overview
Explore in AI Chat

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

Overview

The AMS_PARTY_INSTANCE_V view is a Marketing (AMS) module data source view owned by the APPS schema in Oracle E-Business Suite. It exposes Install Base item instance records joined to their associated trading parties, and is described in the ETRM metadata as a "data source view for install base." Views in the AMS data source layer are used to feed Oracle Marketing's customer and install base analytics, list generation, and segmentation functions, and are also frequently accessed by reporting and integration routines that must reconcile installed product ownership at the customer level.

Because the view returns one row per instance/party pairing and filters to the latest update of each instance/party combination, consumers can rely on it to obtain a current-state view of installed assets without writing the deduplication logic themselves. The view is exposed in EBS 12.1.1 and 12.2.2 with an identical column list, making it portable across both releases.

Underlying Base Objects

The view is defined over three referenced base objects (all exposed as APPS synonyms):

  • CSI_ITEM_INSTANCES (CII) — the Install Base instance master, supplying instance identifiers, item and organization references, serial number, quantity, unit of measure, type code, and lifecycle dates.
  • CSI_I_PARTIES (CIP) — the instance-to-party relationship table, linking an instance to the parties playing a role on it.
  • HZ_PARTIES (PARTIES) — the Trading Community Architecture party master, validating that the associated party exists.

The view joins CII.INSTANCE_ID = CIP.INSTANCE_ID and CIP.PARTY_ID = PARTIES.PARTY_ID, with the constraint CIP.PARTY_SOURCE_TABLE = 'HZ_PARTIES' to restrict relationships to TCA parties. A correlated subquery on CSI_ITEM_INSTANCES.LAST_UPDATE_DATE retains only the most recently updated instance/party row, preventing duplicate party rows per instance.

Key Columns

  • INSTANCE_ID — unique Install Base instance identifier; primary join key to CSI tables.
  • INSTANCE_NUMBER — user-facing instance number.
  • INVENTORY_ITEM_ID — the inventory item of the installed product.
  • INV_MASTER_ORGANIZATION_ID — owning inventory master organization.
  • SERIAL_NUMBER — serialized asset identifier where applicable.
  • QUANTITY / UNIT_OF_MEASURE — installed quantity and its UOM.
  • INSTANCE_TYPE_CODE — the value the user searched for; classifies the instance record (for example, whether it represents an installed base instance or another CSI instance category). This column drives filtering and grouping in most queries against this view.
  • ACTIVE_START_DATE / ACTIVE_END_DATE — effective period of the instance.
  • INSTALL_DATE — date the asset was installed.
  • PO_ORDER_LINE_ID — originating purchase order line, where the install was PO-driven.
  • PARTY_ID — TCA party (customer) attributed to the instance.

Common Use Cases and Queries

Typical scenarios include retrieving all installed products for a given customer (PARTY_ID), segmenting customers by INSTANCE_TYPE_CODE, and building install base counts by inventory item.

  • Instances for a specific customer, filtered by type:
    SELECT instance_id, instance_number, inventory_item_id, serial_number, install_date FROM ams_party_instance_v WHERE party_id = :p_party_id AND instance_type_code = :p_type;
  • Instance type distribution:
    SELECT instance_type_code, COUNT(*) FROM ams_party_instance_v GROUP BY instance_type_code;
  • Items owned by a party for marketing segmentation joins on PARTY_ID.

Because the view already deduplicates to the latest update, it is safe for direct joining to HZ_CUST_ACCOUNTS or AMS list tables without additional DISTINCT logic.