Results for “ams_instance_party_b2c_v”

24 results




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

Overview

The AMS_INSTANCE_PARTY_B2C_V view resides in the APPS schema and is owned by Oracle Marketing (AMS). It exposes Business-to-Consumer (B2C) party relationships for Install Base records, presenting a flattened, reporting-ready projection of installed instances joined to the parties that own or relate to them. Functionally, it is a consumer-facing companion to the broader Install Base views: where CSI_INSTANCE_DETAILS_V provides the master set of instance attributes, AMS_INSTANCE_PARTY_B2C_V narrows the perspective to those instances relevant to consumer party relationships, making it suitable for marketing segmentation, installed-base analytics, and outbound campaign targeting.

Within Oracle EBS 12.1.1 and 12.2.2, the view is documented as VALID and is referenced by Marketing analytics that require both the physical instance context (serial number, item, organization, location) and the owning party context. It shields consuming reports and integrations from the multi-table joins across CSI and HZ that would otherwise be required, so it is frequently reused by custom reports, OBIEE/BI Publisher extracts, and integration layers that synchronize installed-base party data with external CRM or data-warehouse systems.

Underlying Base Objects

The documented view metadata lists four referenced objects:

  • CSI_INSTANCE_DETAILS_V (VIEW) — The primary source of instance-level attributes. The view text selects from an alias CID, which resolves to this object, supplying instance number, item, revision, serial number, quantity, status, condition, location, and transaction-reference columns.
  • CSI_II_RELATIONSHIPS (SYNONYM) — The Install Base item-instance relationship structure, used to link instances to related objects and parties.
  • CSI_I_PARTIES (SYNONYM) — The Install Base parties association, which binds an instance to a party role (for example, customer or merchant). The CUSTOMER_VIEW_FLAG and MERCHANT_VIEW_FLAG columns in the view text derive from this relationship layer, which is what distinguishes the "B2C" perspective.
  • HZ_PARTIES (SYNONYM) — The TCA party master, providing the consumer/customer identity that the instance is associated with.

The combination of CSI_I_PARTIES and HZ_PARTIES with CSI_INSTANCE_DETAILS_V is what produces a party-centric Install Base view rather than a purely asset-centric one.

Key Columns

Common Use Cases and Queries

Typical scenarios include consumer installed-base reporting, marketing campaign target lists, warranty and entitlement analysis, and integration extracts into CRM or BI platforms. Because the view combines instance detail with party association, a frequent query pattern filters by the party visibility flag:

  • Listing all instances visible to consumers for a given customer, joined back to HZ_PARTIES for contact details.
  • Extracting serial numbers, items, and install dates for warranty or service-contract eligibility checks.
  • Identifying sellable instances by SELLABLE_FLAG and INSTANCE_STATUS_ID for upgrade or cross-sell campaigns.
  • Reconciling instances against source order, RMA, or project references using the LAST_OE_* and PA_* columns.

A representative query:

SELECT instance_number, serial_number, inventory_item_id, status_name, install_date
FROM apps.ams_instance_party_b2c_v
WHERE customer_view_flag = 'Y'
AND instance_status_id IS NOT NULL;

Note: while the object name references "party," the view text excerpt above exposes instance attributes; the party linkage is achieved through the CSI_I_PARTIES and HZ_PARTIES join layer documented in the metadata. Queries requiring party name or contact data should join or rely on that association accordingly.