Results for “ast_ls_deliverables_v”

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

Overview

AST_LS_DELIVERABLES_V is a TeleSales (AST) module view that exposes deliverable records available for fulfillment within Oracle E-Business Suite. In the context of the Oracle Advanced Telecommunications (formerly TeleSales) product, a deliverable represents a tangible or intangible item — a physical product, a brochure, a service entitlement, or an electronic document — that can be offered to a customer through a campaign or telesales interaction. The view consolidates deliverable header attributes from the AMS deliverables layer with inventory item master details and campaign associations, producing a denormalized, reporting-ready result set.

In both Oracle EBS 12.1.1 and 12.2.2, this view functions as a read-only integration and reporting surface rather than a transactional entity. The ETRM metadata records this object as "Not implemented in this database," meaning the view definition is shipped with the AST product but is not necessarily present in every environment unless the relevant product schema is installed and compiled. When present, it supports downstream reporting, order capture, and fulfillment eligibility checks.

Underlying Base Objects

Although the ETRM metadata documents no referenced base objects at the table level, the view text itself reveals three primary sources:

• AMS_P_DELIVERABLES_V (aliased DLH) — the driving source, supplying deliverable identifier, name, description, availability dates, user status, non-inventory quantities, and the DFF attribute columns.
• MTL_SYSTEM_ITEMS_VL (aliased ITM) — the inventory item master, joined on INVENTORY_ITEM_ID and ORGANIZATION_ID to retrieve item number, description, and unit-of-measure data. The outer-join (+) syntax indicates the item join is optional.
• AST_CAMPAIGNS_VL (aliased CMP) — the campaign definition view, joined via CMP_DELIVERABLE_ID to DELIVERABLE_ID to expose campaign name and source code.

The view applies filters restricting output to active deliverables (ACTIVE_FLAG = 'Y'), those fulfillable either physically or electronically, and those whose availability window brackets the current system date using TRUNC(SYSDATE).

Key Columns

The column list spans deliverable, item, and campaign domains. Deliverable identity columns include DELIVERABLE_ID, DELIVERABLE_NAME, and DESCRIPTION. Temporal control is provided by ACTUAL_AVAIL_FROM_DATE and ACTUAL_AVAIL_TO_DATE, which gate visibility of the row. Status columns USER_STATUS_ID and USER_STATUS reflect the workflow state assigned to the deliverable.

Quantity columns — NON_INV_QUANTITY_ON_HAND, NON_INV_QUANTITY_ON_ORDER, and NON_INV_QUANTITY_ON_RESERVE — support non-inventory availability tracking. Inventory linkage columns INVENTORY_ITEM_ID, INVENTORY_ITEM_ORG_ID, ITEM_NUMBER (CONCATENATED_SEGMENTS), ITEM_DESCRIPTION, PRIMARY_UOM_CODE, PRIMARY_UNIT_OF_MEASURE, and CHARGEBACK_UOM connect the deliverable to item master data. Campaign context is supplied through CAMPAIGN_ID, CAMPAIGN_NAME, and SOURCE_CODE. The fifteen ATTRIBUTE columns plus ATTRIBUTE_CATEGORY expose descriptive flexfield content for extensibility.

Common Use Cases and Queries

Typical applications include telesales availability reporting, campaign-to-deliverable mapping, and integration feeds into order capture or fulfillment systems.

A straightforward listing of active deliverables with their campaign and item context:

• SELECT DELIVERABLE_ID, DELIVERABLE_NAME, ITEM_NUMBER, PRIMARY_UOM_CODE, CAMPAIGN_NAME, USER_STATUS FROM AST_LS_DELIVERABLES_V ORDER BY DELIVERABLE_NAME;

To identify deliverables tied to a specific campaign and item organization:

• SELECT DELIVERABLE_ID, DELIVERABLE_NAME, ITEM_NUMBER, NON_INV_QUANTITY_ON_HAND, NON_INV_QUANTITY_ON_RESERVE FROM AST_LS_DELIVERABLES_V WHERE CAMPAIGN_ID = :p_campaign_id AND INVENTORY_ITEM_ORG_ID = :p_org_id;

To audit flexible attribute usage across deliverables:

• SELECT DELIVERABLE_NAME, ATTRIBUTE_CATEGORY, ATTRIBUTE1, ATTRIBUTE2, ATTRIBUTE3 FROM AST_LS_DELIVERABLES_V WHERE ATTRIBUTE_CATEGORY IS NOT NULL;

Because the view enforces active-flag, fulfillment-capability, and date-window predicates internally, callers do not need to repeat those conditions. Reports should nonetheless be mindful that the view reflects only the current point in time due to its TRUNC(SYSDATE) comparison.