Search Results invoice_interface_status_code

Overview

AMS_OE_ORDER_LINES_V is a reporting view registered under the Oracle Marketing (AMS) product family that exposes order line data drawn from the Order Management transaction schema. In Oracle E-Business Suite 12.1.1 and 12.2.2, the view functions as a denormalized read interface over the order line entity, joining line-level attributes from the order line table to descriptive item attributes. Its principal role is to support Marketing and Trade Management reporting, promotions and demand analysis where order line detail — including the demand bucket classification — must be presented without requiring the calling application to reconstruct the Order Management join logic.

The ETRM metadata records the view as "Not implemented in this database," indicating that the object definition is delivered as part of the AMS schema but may not be instantiated in every environment, depending on whether the Marketing modules are licensed and installed. Consumers must therefore verify object existence and validity before referencing the view in custom reports.

Underlying Base Objects

The view text selects from an order line source aliased as OL and an item master source aliased as IT. The OL alias resolves to the Order Management order lines entity, whose canonical base table is OE_ORDER_LINES_ALL, while the IT alias resolves to an inventory item definition supplying SEGMENT1 and DESCRIPTION. The documented metadata lists no referenced base objects, so the underlying tables must be confirmed by inspecting ALL_DEPENDENCIES and the view DDL in the target instance. Because the view is defined over the transactional order line table, it inherits that table's multi-org structure; SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, and DELIVER_TO_ORG_ID are exposed directly and should be constrained in any query.

Key Columns

The view projects a broad set of line attributes. Among the most significant are:

• DEMAND_BUCKET_TYPE_CODE — classifies the line's demand according to the bucket type used in ATP, scheduling, and demand planning. This is the column most frequently searched by report authors.
• LINE_ID, HEADER_ID, LINE_NUMBER — the primary line key, its parent order reference, and the user-visible line sequence.
• ORDERED_ITEM, INVENTORY_ITEM_ID, ITEM_NAME, ITEM_DESCRIPTION — the ordered item identifier and descriptive attributes sourced from the item master.
• ORDERED_QUANTITY, SHIPPED_QUANTITY, CANCELLED_QUANTITY, FULFILLED_QUANTITY, PRICING_QUANTITY — quantity metrics supporting fulfillment and demand analysis.
• REQUEST_DATE, PROMISE_DATE, SCHEDULE_SHIP_DATE — scheduling dates used for demand bucketing and lead-time computation.
• DEMAND_CLASS_CODE, SHIPMENT_PRIORITY_CODE, SHIPPING_METHOD_CODE, FREIGHT_TERMS_CODE — fulfillment and classification attributes.
• UNIT_SELLING_PRICE, UNIT_LIST_PRICE, TAX_CODE, TAX_RATE, TAX_VALUE — pricing and tax attributes.
• CONFIGURATION_ID, COMPONENT_SEQUENCE_ID, COMPONENT_CODE, OPTION_NUMBER, OPTION_FLAG — configuration and model structure indicators for configured items.

Common Use Cases and Queries

The view is typically used to report order line demand by bucket, to reconcile fulfillment quantities, and to drive marketing or trade promotion analysis tied to specific sold-to customers and items. A representative query filtered on the demand bucket type is shown below.

• Demand reporting by bucket: SELECT header_id, line_id, ordered_item, demand_bucket_type_code, ordered_quantity, schedule_ship_date FROM ams_oe_order_lines_v WHERE demand_bucket_type_code = 'MDS' ORDER BY schedule_ship_date;
• Fulfillment variance: SELECT line_id, ordered_item, ordered_quantity, shipped_quantity, fulfilled_quantity FROM ams_oe_order_lines_v WHERE ordered_quantity > fulfilled_quantity;
• Customer and item join: SELECT v.cust_po_number, v.item_name, v.demand_bucket_type_code FROM ams_oe_order_lines_v v WHERE v.sold_to_org_id = :p_customer_id;

Because the view is uninvoiced against documented base objects in the metadata, developers should confirm its validity in each environment and prefer indexing and filtering on LINE_ID, HEADER_ID, and the org ID columns to limit the scan footprint against the underlying order line table.