Search Results print_attributes




Overview

APPS.ECE_FLATFILE_PVT is a private PL/SQL package within the Oracle E-Business Suite E-Commerce Gateway (ECE) module. It provides the internal engine that converts Oracle EBS interface table data into EDI flat-file output for outbound transactions. The package name reflects its role: it prepares and writes flat-file records that are subsequently transmitted to trading partners through the ECE communication layer. It is classified as a PVT (private) API, meaning it is not intended as a public integration point; it is invoked by higher-level ECE packages rather than by external application code. The ETRM documentation indicates that 28 other packages reference ECE_FLATFILE_PVT, confirming its position as a shared low-level utility within the ECE outbound processing stack. The package operates against both 12.1.1 and 12.2.2 environments, and its source header dates to 2005, reflecting its long-standing stability across releases.

Key Procedures and Functions

The documented 16 procedures and functions address three concerns: attribute discovery, layout/mapping resolution, and output generation.

Tables Accessed

The package reads configuration and mapping metadata from ECE_INTERFACE_COLUMNS, ECE_INTERFACE_TABLES, and ECE_MAPPINGS. These define which interface columns exist, how they relate to base tables, and how values are converted. Resolved output is written to ECE_OUTPUT and ECE_OUTPUT_LINES_S. The package also references DBMS_SQL and DBMS_UTILITY for dynamic SQL execution and PLITBLM for index-by table handling.

Usage Notes

ECE_FLATFILE_PVT is invoked internally when outbound EDI transactions are generated — typically from the ECE outbound concurrent programs or from the higher-level packages that orchestrate transaction extraction. Because INIT_TABLE and its companion procedures rely on package-global state (such as t_tran_attribute_tbl and the G_ constants), callers must respect the intended sequencing: attributes are gathered, tables initialized, mappings resolved, values assigned, and finally output written. Custom code should not call this package directly; extensions should use the supported public ECE APIs. Debugging typically involves enabling the PRINT_ATTRIBUTES diagnostic output to inspect the attribute values driving record layout.