Search Results put_distdata_to_out_tbl

Overview

APPS.ECE_POO_TRANSACTION is an Oracle E-Business Suite package that supports the outbound exchange of Purchasing Order (POO) transaction data through Oracle's e-Commerce Gateway (ECE) architecture. The package is responsible for extracting purchase order header, line, shipment, and distribution information from the EBS Purchasing schema and writing that data into the ECE output tables used by the EDI / XML Gateway outbound processor. The package is declared with AUTHID CURRENT_USER, which means it executes with the privileges of the invoking user and therefore relies on the APPS synonym layer for all cross-schema references.

In 12.1.1 and 12.2.2 the package sits within the outbound transaction flow that converts native EBS purchasing documents into flat-file or interface-format records for external trading partners. The naming convention "POO" refers to the Purchase Order Outbound transaction, and the package is one of the modular transaction handlers coordinated by the e-Commerce Gateway output program.

Key Procedures and Functions

The package exposes eleven documented procedures. The ETRM metadata does not publish parameter lists for each, so the descriptions below are limited to documented purpose and cross-referenced behavior.

• EXTRACT_POO_OUTBOUND — Top-level driver for producing the POO outbound extract. Its parameters are documented in the source header and include output path, output filename, PO number range, creation date range, PC type, vendor name, vendor site code, and a debug mode flag defaulting to 0.
• POPULATE_POO_TRX — Populates the POO transaction staging structures. Its source-declared parameters cover communication method, transaction type, output width, transaction date, run ID, four interface table names, creation date range, supplier name and site, document type, and PO number range.
• PUT_DATA_TO_OUTPUT_TABLE — Writes assembled transaction records into the ECE_OUTPUT structure.
• UPDATE_PO — Updates purchase order state associated with the extract run.
• POPULATE_DISTRIBUTION_INFO — Populates PO distribution interface data. Per Bug 1891291, this procedure was renamed from populate_project_info to reflect that it operates on the distribution interface table rather than the project interface table. This is the procedure associated with the search term "populate_project_info".
• PUT_DISTDATA_TO_OUT_TBL — Writes distribution data rows to the output table; renamed from put_project_data_to_output_tbl in the same bug fix.
• POPULATE_TEXT_ATTACHMENT and POPULATE_TEXT_ATT_DETAIL — Load purchase order text attachments and their detail lines for inclusion in the outbound message.
• PUT_ATT_TO_OUTPUT_TABLE and PUT_ATT_DETAIL_TO_OUTPUT_TABLE — Write attachment and attachment-detail rows to the output table.
• WRITE_TO_FILE — Produces the physical output file on the database server using UTL_FILE.

Package-level constants G_MAX_ATT_SEG_SIZE (900) and G_DEFAULT_ATT_SEG_SIZE (400) govern attachment segment sizing.

Tables Accessed

• ECE_POO_HEADER_S, ECE_POO_LINE_S, ECE_POO_SHIPMENT_S — Source views of purchase order header, line, and shipment data.
• ECE_PO_DISTRIBUTIONS and ECE_PO_PROJECT_INFO_S — Distribution and project-charge reference data; the latter is directly relevant to the historical populate_project_info name.
• ECE_OUTPUT, ECE_OUTPUT_RUNS_S — Destination tables and run registry for the generated output.
• ECE_ATTACHMENT_HEADERS, ECE_ATTACHMENT_DETAILS, ECE_ATTACHMENT_DETAILS_S — Text attachment source data.
• ECE_INTERFACE_TABLES, ECE_MAPPINGS — Interface table definitions and mapping rules.
• FINANCIALS_SYSTEM_PARAMETERS, MTL_UNITS_OF_MEASURE — Configuration and UOM reference data.
• UTL_FILE — Oracle-supplied file I/O package used by WRITE_TO_FILE.

Usage Notes

ECE_POO_TRANSACTION is normally invoked from the e-Commerce Gateway outbound concurrent programs rather than directly by end users. In 12.1.1 and 12.2.2 it is referenced by one other package and is called as part of the POO output workflow driven by EXTRACT_POO_OUTBOUND. Sites customizing the extract should extend the package body rather than the specification, apply the documented bug fixes (notably 1891291 and 1854866) when backporting, and note that populate_project_info no longer exists under that name — custom code calling it must be repointed to populate_distribution_info. Output files are written to a server directory accessible to the database process, and the debug mode parameter provides diagnostic tracing during troubleshooting.