Search Results instance_description

Overview

AMS_DS_INSTALL_BASE_V is a Marketing (AMS) schema view owned by APPS that consolidates installed-base item instance data for use by Oracle Marketing and downstream reporting or integration processes. It joins customer item instances from the CSI (Customer Support/Installed Base) tables to item master attributes and to the originating order line in Order Management, producing a single denormalized row per installed instance enriched with descriptive, order, and status information. The view is a foundational data source for installed-base analytics, customer/product ownership reporting, and marketing segmentation, since it exposes both the physical instance details and the commercial context (order number, line, shipment date) under which the product was acquired. In Oracle EBS 12.1.1 and 12.2.2 the object is documented as a VALID view under the APPS schema, referenced by Marketing responsibilities and any custom extract or BI query that requires an installed-base perspective.

Underlying Base Objects

The documented ETRM metadata lists the following referenced objects: CSI_INSTANCE_STATUSES, CSI_ITEM_INSTANCES, CSI_LOOKUPS, HZ_LOCATIONS, MTL_DEFAULT_CATEGORY_SETS, MTL_ITEM_CATEGORIES, MTL_SYSTEM_ITEMS_KFV, OE_ORDER_HEADERS_ALL, and OE_ORDER_LINES_ALL. The primary driver is CSI_ITEM_INSTANCES (aliased CII), which supplies the core instance columns including INSTANCE_ID, INSTANCE_NUMBER, INVENTORY_ITEM_ID, QUANTITY, and the LAST_OE_ORDER_LINE_ID foreign key. MTL_SYSTEM_ITEMS_KFV (MSI) provides the item description, item type, control codes, and concatenated segment values. OE_ORDER_HEADERS_ALL (LOOH) and OE_ORDER_LINES_ALL (LOOL) supply the last order context, joined through the instance’s order-line reference. The remaining objects (CSI_INSTANCE_STATUSES, CSI_LOOKUPS, HZ_LOCATIONS, and the MTL category tables) resolve status meanings, location details, and item categorization used to enrich or filter the result set.

Key Columns

• INSTANCE_ID / INSTANCE_NUMBER: Unique identifier and user-facing number of the installed-base instance.
• INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, DESCRIPTION: Item identity and the concatenated item key flexfield value.
• LAST_OE_ORDER_LINE_ID: Foreign key to the originating OE_ORDER_LINES_ALL row; the column most commonly searched by users seeking order-line linkage.
• LAST_HEADER_ID, LAST_ORDER_NUMBER, LAST_ORDERED_DATE: Header-level order context for the last order associated with the instance.
• LAST_LINE_ID, LAST_LINE_NUMBER, LAST_CUST_PO_NUMBER: Line-level order detail, including the customer PO reference.
• SHIPPED_DATE: Derived via NVL(ACTUAL_SHIPMENT_DATE, FULFILLMENT_DATE), indicating actual or expected shipment.
• INSTALL_DATE, RETURN_BY_DATE, ACTUAL_RETURN_DATE: Lifecycle dates for installation and return of the instance.
• INSTANCE_STATUS_ID, LOCATION_TYPE_CODE, LOCATION_ID, INV_ORGANIZATION_ID: Status, location, and inventory organization context.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT: Descriptive flexfield columns for customer-specific extensions.

Common Use Cases and Queries

Typical uses include installed-base extracts for marketing campaigns, reconciliation between customer instances and sales orders, and ownership/warranty reporting. A frequent query pattern locates an instance via its originating order line:

• SELECT instance_number, last_order_number, last_line_number, shipped_date FROM ams_ds_install_base_v WHERE last_oe_order_line_id = :line_id;
• SELECT instance_number, concatenated_segments, last_order_number, install_date FROM ams_ds_install_base_v WHERE inventory_item_id = :item_id;
• SELECT last_order_number, last_cust_po_number, instance_number FROM ams_ds_install_base_v WHERE install_date BETWEEN :from_date AND :to_date;

Because the view is a simple join and not a base table, no DML is permitted; consumers should query it read-only and, where performance is critical, filter on INSTANCE_ID, INVENTORY_ITEM_ID, or LAST_OE_ORDER_LINE_ID to leverage the underlying CSI and OE indexes.