Search Results ece_advo_x

Overview

APPS.ECE_ADVO_X is a stub package body within the Oracle E-Business Suite ECE (e-Commerce Gateway / Electronic Commerce Exchange) module. It belongs to the family of "extension" packages generated to support the Advanced Outbound (ADVO) processing path of the e-Commerce Gateway, which converts outbound interface data into flat-file EDI or other interchange formats. The package defines named hooks that allow customers or integrators to inject custom PL/SQL logic into the outbound document generation flow without modifying Oracle-owned code. In the 12.1.1 and 12.2.2 releases the body ships as a placeholder: both documented procedures contain only a NULL; statement, meaning no functional extension is performed by default. The presence of the package guarantees that the e-Commerce Gateway framework can call a stable, pre-declared entry point even when no customer customization exists.

Key Procedures and Functions

The ETRM metadata documents two procedures, both taking an l_fkey (foreign key to the interface data) and an l_plsql_tbl collection of type ece_flatfile_pvt.Interface_tbl_type. Parameter lists are reproduced here only as documented; no additional parameters are implied.

• populate_extension_headers — Intended as a user-exit hook invoked during header-level processing of the outbound document. Because the shipped body is NULL, it performs no default work. Customers enable customization by replacing or extending the stub so that header extension columns are populated before the flat-file header record is written.
• populate_extension_details — The analogous hook for detail-level (line) processing. It is called when detail extension attributes must be computed or supplied. As delivered, it also contains only NULL;.

Tables Accessed

The documented metadata lists no direct table references via APPS synonyms for this package. This is consistent with its stub nature: the delivered body performs no DML or query. Any data access occurs only after a customer implements the procedures, at which point custom statements would typically target the extension columns or staging tables associated with the e-Commerce Gateway outbound interface. The l_plsql_tbl parameter, typed as ece_flatfile_pvt.Interface_tbl_type, indicates that header and detail data is passed in memory through a PL/SQL collection rather than being read directly by the package.

Usage Notes

ECE_ADVO_X is referenced by one other package, which is the caller that drives the Advanced Outbound generation sequence. It is not normally invoked directly from Oracle Forms or a standalone concurrent program; instead it is dispatched by the e-Commerce Gateway runtime during outbound document creation. Typical invocation is therefore implicit, triggered when the customer runs the outbound interface concurrent program for a configured transaction type. Because the delivered procedures are empty, the only practical use is as a customization point: a developer copies the body into a customer-owned package or modifies it following Oracle extension conventions, then registers or recompiles it in APPS. All callers should preserve the documented signatures so that the framework invocation continues to resolve.