Results for “ece_poo_headers_v”

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

Overview

ECE_POO_HEADERS_V is a private view owned by the APPS schema in Oracle E-Business Suite, defined within the e-Commerce Gateway (EC) product. Its purpose is to extract header-level information for the outbound Purchase Order transaction, identified by the document identifier POO and the EDI standard transaction set 850 (ORDERS). The view is catalogued with the display name "Purchase Order Header View," an active lifecycle status, and a business entity classification.

Within the e-Commerce Gateway architecture, this view functions as one of the extraction sources that feed the outbound PO interface tables and, subsequently, the generated EDI flat file transmitted to trading partners. Because the view assembles buyer-side and trading-partner-side attributes into a single row per purchase order header, it enables a query to resolve the communication method, translator configuration, trading partner details, and purchasing attributes in one pass, without requiring the report developer to join the underlying ECE_TP_HEADERS, ECE_TP_DETAILS, and PO_HEADERS tables manually.

Underlying Base Objects

The documented referenced base objects span several schemas exposed to APPS through synonyms and views. Purchasing data originates from PO_HEADERS and PO_HEADERS_ARCHIVE, with PO_RELEASES and PO_RELEASES_ARCHIVE supporting the release-level columns. Trading partner configuration is drawn from ECE_TP_HEADERS and ECE_TP_DETAILS. Supplier and supplier site information comes from PO_VENDORS, PO_VENDOR_SITES, and PO_VENDOR_CONTACTS, while payment terms are resolved through AP_TERMS. Currency attributes are sourced from FND_CURRENCIES_VL, addresses and contacts from HR_LOCATIONS, HR_LOCATIONS_ALL, HR_LOCATIONS_ALL_TL, PER_ADDRESSES, PER_ALL_PEOPLE_F, and PER_PHONES, and financials defaults from FINANCIALS_SYSTEM_PARAMETERS. The AP_CARDS, AP_CARD_PROFILES, AP_CARD_PROGRAMS, AP_CARD_SUPPLIERS, and IBY_CREDITCARD objects support procurement card scenarios. FND_GLOBAL and HR_GENERAL are referenced as packages for session and organizational context.

Key Columns

The column list follows the EDI 850 header segment layout. COMMUNICATION_METHOD is hard-coded to 'EDI', and DOCUMENT_ID to 'POO'. DOCUMENT_TYPE carries PH.TYPE_LOOKUP_CODE, while DOCUMENT_CODE and PO_NUMBER both expose PH.SEGMENT1. Trading partner fields include TRANSLATOR_CODE, TP_LOCATION_CODE_EXT, TP_DESCRIPTION, TP_REFERENCE_EXT1, and TP_REFERENCE_EXT2, sourced from ECE_TP_HEADERS and ECE_TP_DETAILS, along with the fifteen attribute columns from each of those tables. TEST_FLAG indicates whether the transaction is a test. TRANSACTION_DATE returns SYSDATE. Purchasing columns include PO_TYPE, REVISION_NUM, REVISED_DATE, COMMENTS, SHIP_VIA, FOB_CODE, FREIGHT_TERMS, CANCEL_FLAG, PAYMENT_TERMS, CURRENCY_CODE, and CURRENCY_RATE. The columns POR_RELEASE_ID, POR_RELEASE_NUM, and POR_RELEASE_DATE are defined as literal placeholders (0, 0, and TO_DATE(NULL)) so that the header-level extraction remains structurally compatible with release-level extraction, which is the reason a search for "por_release_date" surfaces this view. In ECE_POO_HEADERS_V the release date is therefore always null and must not be treated as populated header data.

Common Use Cases and Queries

Typical uses include verifying that a purchase order will be extracted with the correct trading partner and translator settings, and diagnosing why a PO was excluded from an outbound 850 run. A representative query retrieves header information for a specific PO number:

• SELECT po_number, tp_description, translator_code, tp_location_code_ext, currency_code, payment_terms, revision_num, transaction_date FROM apps.ece_poo_headers_v WHERE po_number = :p_po_number;

To inspect placeholder release columns and confirm they carry no data:

• SELECT po_number, por_release_id, por_release_num, por_release_date FROM apps.ece_poo_headers_v WHERE rownum <= 25;

To isolate test versus production extractions:

• SELECT po_number, test_flag, cancellation_flag FROM apps.ece_poo_headers_v WHERE test_flag = 'Y';

Because the view is marked private, it is intended for internal e-Commerce Gateway processing rather than general reporting; nevertheless, it is commonly referenced in diagnostic queries. Queries should always be schema-qualified as APPS.ECE_POO_HEADERS_V and filtered by PO_NUMBER or trading partner to avoid full scans across the header population.