Results for “ece_poco_headers_v”

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

Overview

ECE_POCO_HEADERS_V is a private view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the EC (e-Commerce Gateway) product and is registered with the display name "Purchase Order Change Header View" under the business entity PO_PU. Its documented purpose is to extract header-level information for the outbound Purchase Order Change transaction, X12 860 / ORDCHG. In practice the view acts as a staging query that the e-Commerce Gateway concurrent programs use to assemble a flat, EDI-oriented result set; each row represents one purchase order header destined for translation and transmission to a trading partner.

Although the object is associated with the PO product lifecycle metadata, the underlying DDL draws from both Oracle Purchasing and Oracle Payables objects. This dual sourcing reflects the fact that the row combines purchasing document attributes with trading-partner profile values maintained in the gateway and payment tables.

Underlying Base Objects

The documented referenced base objects span several schemas exposed through APPS synonyms and views. The Purchasing side includes PO_HEADERS, PO_RELEASES, PO_LINE_LOCATIONS and their archive counterparts PO_HEADERS_ARCHIVE and PO_RELEASES_ARCHIVE, together with PO_VENDORS, PO_VENDOR_CONTACTS and PO_VENDOR_SITES. The trading-partner and outbound-configuration side includes ECE_TP_HEADERS, ECE_TP_DETAILS and the location code reference used for TP_LOCATION_CODE_EXT.

Payment and consolidation attributes are drawn from AP_TERMS, FINANCIALS_SYSTEM_PARAMETERS, FND_CURRENCIES_VL, and the internal FND_GLOBAL and HR_GENERAL packages. Supplier location and telephone details come from HR_LOCATIONS, HR_LOCATIONS_ALL, HR_LOCATIONS_ALL_TL, PER_ADDRESSES, PER_ALL_PEOPLE_F and PER_PHONES. Notably, the metadata also lists AP_CARDS, AP_CARD_PROFILES, AP_CARD_PROGRAMS, AP_CARD_SUPPLIERS and IBY_CREDITCARD among the referenced objects — these are the payment-instrument tables commonly associated with the search term "ap_card_profiles." Where the view text joins these depends on the full DDL, but their inclusion indicates that procurement card and credit card attributes can be surfaced for the trading partner when the change document requires payment references. In most implementations the header extract is driven primarily by PO_HEADERS, with the AP and IBY objects referenced for partner-specific payment profiling.

Key Columns

The projection begins with fixed and partner-derived identifiers. COMMUNICATION_METHOD is hard-coded to 'EDI'; DOCUMENT_ID is 'POCO'; TEST_FLAG and TRANSLATOR_CODE are taken from ECE_TP_DETAILS, and TP_DESCRIPTION, TP_REFERENCE_EXT1, TP_REFERENCE_EXT2 and the fifteen TP header ATTRIBUTE columns come from ECE_TP_HEADERS. TRANSACTION_DATE is SYSDATE and DOCUMENT_TYPE and DOCUMENT_CODE map to TYPE_LOOKUP_CODE and SEGMENT1.

Purchasing document attributes follow: PO_NUMBER (SEGMENT1), CREATION_DATE, REVISION_NUM, REVISED_DATE formatted as DD-MON-RR HH24:MI, COMMENTS, PO_TYPE, PAYMENT_TERMS, CURRENCY_CODE, CURRENCY_RATE, SHIP_VIA, FOB_CODE and FREIGHT_TERMS. Release-related placeholders POR_RELEASE_ID, POR_RELEASE_NUM and POR_RELEASE_DATE are defaulted to 0 / NULL, confirming that this header extract is oriented to the standard change transaction rather than a release change. TP location reference data is exposed through TP_LOCATION_CODE_EXT, and the document-level and trading-partner attribute categories are preserved so that user-defined flexfields survive the extract.

Common Use Cases and Queries

Typical uses include validating outbound 860 content, debugging a specific trading partner's change document, and reconciling gateway output back to the purchasing document. A practical query filters by PO number and partner:

• SELECT PO_NUMBER, REVISION_NUM, REVISED_DATE, DOCUMENT_TYPE, CURRENCY_CODE, TP_DESCRIPTION FROM ECE_POCO_HEADERS_V WHERE TP_DESCRIPTION = :partner AND PO_NUMBER = :po;
• SELECT DOCUMENT_ID, TRANSLATOR_CODE, TEST_FLAG, TRANSACTION_DATE FROM ECE_POCO_HEADERS_V WHERE TEST_FLAG = 'Y';
• SELECT PO_TYPE, PAYMENT_TERMS, SHIP_VIA, FOB_CODE, FREIGHT_TERMS FROM ECE_POCO_HEADERS_V WHERE PO_NUMBER = :po;

Because the view depends on ECE_TP_DETAILS and ECE_TP_HEADERS, rows are only returned for trading partners configured with an active outbound Purchase Order Change transaction. Reviewing the joining of the AP_CARD_PROFILES family of objects through the full DDL is advisable where credit card or procurement card attributes are required in the change extract.