Results for “transaction_reason_code”

50+ results




Overview
Explore in AI Chat

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

Overview

ECE_POO_LINES_V is a private, active view owned by the APPS schema that extracts purchase order line detail for the outbound Purchase Order (850/ORDERS) transaction processed by the e-Commerce Gateway (product EC). Its ETRM display name is "Purchase Order Line View," and it is registered under the BUSINESS_ENTITY PO_PUR category with PO as the associated product. The view functions as the line-level staging and extraction layer that the e-Commerce Gateway reads when assembling an 850 outbound document for transmission to a trading partner.

Because the view publishes purchase agreement line fields — notably COMMITTED_AMOUNT, QUANTITY_COMMITTED, UNIT_PRICE, LIST_PRICE_PER_UNIT, MARKET_PRICE, and NOT_TO_EXCEED_PRICE — it is also frequently consulted by reporting and reconciliation queries that need a denormalized, header-and-line-joined picture of blanket and contract purchase orders without navigating PO_LINES_ALL directly. In Oracle EBS 12.1.1 and 12.2.2 the object remains defined and valid; its column list is stable across both releases.

Underlying Base Objects

Per the documented 12.2.2 metadata, the view is defined over the following base objects (all referenced through APPS synonyms): FINANCIALS_SYSTEM_PARAMETERS, MTL_SYSTEM_ITEMS_B, PO_HAZARD_CLASSES_B, PO_HAZARD_CLASSES_TL, PO_HEADERS_ALL, PO_LINES, PO_LINES_ALL, PO_LINE_LOCATIONS, PO_LINE_TYPES, PO_RELEASES, PO_UN_NUMBERS_B, and PO_UN_NUMBERS_TL.

  • PO_LINES_ALL supplies the core line attributes, including quantity, unit price, commitment and pricing columns, attributes 1–15, and cancellation fields.
  • PO_HEADERS_ALL is joined multiple times: one alias provides the PO number (SEGMENT1) and another supplies the vendor quote number.
  • PO_LINE_LOCATIONS and PO_LINE_TYPES contribute shipment/schedule and order type lookup context.
  • PO_RELEASES supports release-level extraction against blanket agreements.
  • PO_HAZARD_CLASSES_B/TL and PO_UN_NUMBERS_B/TL supply hazardous material classification and UN number descriptions.
  • MTL_SYSTEM_ITEMS_B provides item-level descriptive flexfield attributes, aliased with the LP_ prefix.
  • FINANCIALS_SYSTEM_PARAMETERS is referenced for operating unit and set-of-books context.

Key Columns

Common Use Cases and Queries

The primary use case is outbound 850 extraction, where the e-Commerce Gateway selects lines for a given purchase order. Secondary uses include commitment reporting against blanket agreements and reconciliation of committed versus ordered value.

Retrieve committed values for a purchase order:

  • SELECT po_number, line_num, item_description, quantity_committed, committed_amount FROM apps.ece_poo_lines_v WHERE po_number = :p_po_number ORDER BY line_num;

Identify lines with a material commitment on blanket or contract orders:

  • SELECT po_number, line_num, committed_amount, unit_price FROM apps.ece_poo_lines_v WHERE committed_amount IS NOT NULL AND committed_amount > 0 AND order_type_lookup_code IN ('BLANKET','CONTRACT') ORDER BY committed_amount DESC;

Join to PO_HEADERS_ALL for supplier and date context:

  • SELECT v.po_number, v.line_num, v.committed_amount, h.vendor_id, h.currency_code FROM apps.ece_poo_lines_v v, apps.po_headers_all h WHERE v.po_number = h.segment1 AND h.org_id = :p_org_id;

Because ECE_POO_LINES_V is marked private in the ETRM repository, it should be treated as an internal e-Commerce Gateway object rather than a supported public interface; custom integrations should be validated after upgrades between 12.1.1 and 12.2.2.