Search Results ece_poo_header_s

Overview

APPS.ECE_POO_TRANSACTION is a VALID PL/SQL package body in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases that supports the outbound processing of Purchasing Order (PO) data within the e-Commerce Gateway (ECE) / EDI framework. Its principal role is to extract purchase order information from the EBS base tables and interface tables, transform that data into the flat-file format expected by an external trading partner or EDI translator, and write the resulting output to the ECE output tables and physical file. The package derives its name from the "POO" (Purchase Order Outbound) transaction family, and it works alongside sibling objects such as ECE_POO_HEADER_S, ECE_POO_LINE_S, and ECE_POO_SHIPMENT_S, which hold header, line, and shipment-level staging data respectively.

The package is classified as an OTHER API type and exposes eleven documented programs that collectively cover extraction, population, output writing, and attachment handling. Because it is not referenced by any other database object, ECE_POO_TRANSACTION is effectively a top-level driver invoked by the ECE concurrent processing framework.

Key Procedures and Functions

• EXTRACT_POO_OUTBOUND — primary driver that orchestrates the end-to-end extraction of purchase order data for outbound transmission.
• POPULATE_POO_TRX — builds the transaction records that represent a purchase order for output.
• UPDATE_PO — updates the purchase order records, typically to reflect processing status after extraction.
• POPULATE_DISTRIBUTION_INFO — gathers PO distribution information for inclusion in the outbound transaction.
• PUT_DATA_TO_OUTPUT_TABLE — writes the assembled PO transaction data into the ECE output table.
• PUT_DISTDATA_TO_OUT_TBL — writes distribution-related data to the output table.
• POPULATE_TEXT_ATTACHMENT — retrieves and prepares text attachments associated with the purchase order.
• POPULATE_TEXT_ATT_DETAIL — populates the detail rows of text attachments.
• PUT_ATT_TO_OUTPUT_TABLE — writes attachment header data to the output table.
• PUT_ATT_DETAIL_TO_OUTPUT_TABLE — writes attachment detail data to the output table.
• WRITE_TO_FILE — emits the assembled output rows to the flat file using UTL_FILE.

Tables Accessed

The package reads and writes a broad set of ECE and Purchasing base tables. Among the ECE objects it references are ECE_POO_HEADER_S, ECE_POO_LINE_S, and ECE_POO_SHIPMENT_S, which supply header, line, and shipment data; ECE_PO_DISTRIBUTIONS and ECE_PO_PROJECT_INFO_S for distribution and project information; ECE_ATTACHMENT_HEADERS and ECE_ATTACHMENT_DETAILS for attachments; and ECE_OUTPUT, ECE_OUTPUT_RUNS_S, ECE_MAPPINGS, and ECE_INTERFACE_TABLES for output staging, run tracking, and mapping. Purchasing base tables such as PO_HEADERS, PO_LINE_LOCATIONS, PO_RELEASES, PO_HEADERS_ARCHIVE, and PO_RELEASES_ARCHIVE supply the authoritative PO data. Reference data comes from MTL_UNITS_OF_MEASURE, FINANCIALS_SYSTEM_PARAMETERS, and PA_PROJECTS_EXPEND_V. The package also uses UTL_FILE for physical file output and standard utilities such as FND_GLOBAL, FND_PROFILE, EC_DEBUG, and EC_CODE_CONVERSION_PVT.

Usage Notes

ECE_POO_TRANSACTION is invoked as part of the Oracle e-Commerce Gateway outbound purchase order process. In a typical deployment it is executed indirectly through the ECE concurrent program used to generate EDI 850 (or equivalent) purchase order documents, rather than being called directly by user code. The package may also be called from custom code in controlled integration scenarios where an application needs to regenerate outbound PO output. Because the package is owned by APPS and depends on FND_GLOBAL and FND_PROFILE for runtime context, it must be invoked within an EBS session with valid application context. The user search term "ece_poo_line_s" corresponds to one of the staging tables referenced here (ECE_POO_LINE_S), indicating the package is frequently investigated when troubleshooting PO line-level outbound data.