Results for “ams_instance_party_b2b_v”

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

Overview

AMS_INSTANCE_PARTY_B2B_V is a business-to-business (B2B) reporting view owned by the APPS schema within the AMS (Marketing) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to provide "Business to Business Views for Install Base," presenting installed base instance data joined to the trading parties (customers, merchants, and related organizations) that participate in B2B relationships. The view is documented as VALID and is classified explicitly as a VIEW object, meaning it holds no data of its own; it derives all rows from underlying Install Base and party entities at query time.

Structurally, the view projects a wide column list beginning with instance-identification attributes (INSTANCE_ID, INSTANCE_NUMBER, EXTERNAL_REFERENCE) and continuing through inventory, serial, lot, status, project, and order-origin attributes sourced from the CSI instance detail construct, followed by concatenated key flexfield segments and descriptive columns. It also exposes relationship-oriented identifiers such as LINE_TYPE_ID, LINE_NUMBER, and CUST_PO_NUMBER, which support party-role reporting. The presence of both "current" attributes (for example, WIP_JOB_ID) and "last" attributes (for example, LAST_WIP_JOB_ID) is a defining characteristic of this view, enabling traceability across the instance lifecycle. Users searching for "last_wip_job_id" will find it exposed here as LAST_WIP_JOB_ID, distinct from the current WIP_JOB_ID column.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects:

• CSI_II_RELATIONSHIPS (SYNONYM) — the item-instance relationship table that links instances to related entities and party roles.
• CSI_INSTANCE_DETAILS_V (VIEW) — the primary instance detail view supplying the CID-prefixed columns (INSTANCE_ID, INSTANCE_NUMBER, inventory attributes, status, project, and order-origin fields).
• CSI_I_PARTIES (SYNONYM) — the item-instance party assignment entity that associates instances with HZ party records.
• HZ_PARTIES (SYNONYM) — the Trading Community Architecture registry of parties, supplying the party identity behind the B2B relationship.

The view text shows a SELECT list aliased entirely with the prefix "CID," indicating the instance-detail view is the driving dataset, with the party and relationship objects joined to enrich each instance row with B2B party context. Because the base objects are reached through APPS synonyms, the view resolves consistently in both 12.1.1 and 12.2.2 environments where the CSI and HZ schemas are installed.

Key Columns

• INSTANCE_ID / INSTANCE_NUMBER — the surrogate and user-facing identifiers of the installed base instance; INSTANCE_ID is the primary join key to other CSI objects.
• INVENTORY_ITEM_ID / INVENTORY_REVISION / SERIAL_NUMBER / LOT_NUMBER — item and tracking attributes identifying the specific tracked configuration.
• WIP_JOB_ID and LAST_WIP_JOB_ID — the current and most recent Work in Process job associated with the instance. LAST_WIP_JOB_ID is retained after the instance moves on, providing historical traceability to the job that last touched it.
• LAST_OE_ORDER_LINE_ID / LAST_OE_RMA_LINE_ID / LAST_PO_PO_LINE_ID / LAST_OE_AGREEMENT_ID — the most recent order, RMA, purchasing, and agreement line associations, paralleling the "last" semantics of LAST_WIP_JOB_ID.
• ACCOUNTING_CLASS_CODE / INSTANCE_STATUS_ID / STATUS_CODE / STATUS_NAME — accounting classification and current status of the instance.
• CUSTOMER_VIEW_FLAG / MERCHANT_VIEW_FLAG / SELLABLE_FLAG — flags governing the B2B visibility of the instance to customer and merchant parties.
• CONCATENATED_SEGMENTS / PADDED_CONCATENATED_SEGMENTS / ORGANIZATION_NAME / UNIT_OF_MEASURE_NAME — descriptive and flexfield-derived display values.
• INSTALL_DATE / RETURN_BY_DATE / ACTUAL_RETURN_DATE / ACTIVE_START_DATE / ACTIVE_END_DATE — lifecycle dates supporting warranty, return, and active-period reporting.

Common Use Cases and Queries

Typical uses include installed base reporting by customer party, B2B merchant visibility analysis, and traceability of instances back to their last manufacturing, order, or purchasing transaction.

To locate instances by their last WIP job:

• SELECT instance_id, instance_number, serial_number, wip_job_id, last_wip_job_id, wip_entity_name FROM apps.ams_instance_party_b2b_v WHERE last_wip_job_id IS NOT NULL;

To retrieve B2B-visible instances for a specific customer item:

• SELECT instance_number, serial_number, status_name, install_date, cust_po_number, order_number FROM apps.ams_instance_party_b2b_v WHERE inventory_item_id = :item_id AND customer_view_flag = 'Y';

Because the view joins party and relationship objects, queries should filter on INSTANCE_ID or item identifiers rather than assuming a single row per instance where multiple party relationships exist.