Search Results ec_xml_processor_out_generic

Overview

EC_XML_UTILS is a utility package in the Oracle E-Business Suite E-Commerce Gateway (EC) module, owned by APPS and classified as an OTHER API. Its primary business function is to support the generation and consumption of XML messages exchanged between Oracle EBS and external trading partners, as well as between EBS and other internal systems requiring structured data interchange. The package provides the runtime plumbing for building value-object (VO) definitions, serializing transactional data into XML documents, and parsing inbound XML back into structured records for further processing by E-Commerce Gateway mapping and interface logic.

The package operates with AUTHID CURRENT_USER, meaning its procedures execute under the privileges of the invoking schema rather than the definer. This design is significant because the package is intended to be called dynamically by generic XML processing routines that may run under different application contexts. The user search term "ec_xml_processor_out_generic" corresponds directly to one of the package's documented procedures, EC_XML_PROCESSOR_OUT_GENERIC, which serves as the outbound counterpart to the inbound generic processor.

Key Procedures and Functions

• CREATE_TOPLEVEL_VO — Constructs a top-level value object definition from supplied naming, select, from, where, and order-by clauses, along with a list of attributes to hide. It returns product, error, parameter, and error-string outputs indicating success or failure of the VO creation.
• CREATE_CHILD_VO — Builds a child value object linked to a parent data object, accepting bind information for parent and child attribute aliases and child attribute columns. This enables hierarchical XML structures where child elements are nested under their parent.
• CREATE_VO_TREE — Assembles the complete value-object tree from the top-level and child VOs previously defined, forming the structural template that governs the shape of the resulting XML document.
• PRODUCE_XML — Serializes the populated value-object tree into an XML file on the file system, using the supplied file name. This is the core outbound generation routine.
• CONSUME_XML — Reads an inbound XML file and parses its contents into the value-object structures for downstream processing by the E-Commerce Gateway interface tables.
• EC_XML_PROCESSOR_OUT_GENERIC — A generic driver procedure that orchestrates the outbound XML flow by invoking the appropriate VO creation and produce steps for a given output run. It abstracts the outbound processing so multiple transaction types can reuse the same logic.
• EC_XML_PROCESSOR_IN_GENERIC — The inbound mirror of the generic outbound processor, orchestrating the consume-and-map steps for inbound XML messages.

Tables Accessed

• ECE_EXTERNAL_LEVELS — Stores level definitions for external (trading partner) data structures, used to determine the hierarchical levels present in an XML message.
• ECE_INTERFACE_COLUMNS — Defines the columns of E-Commerce Gateway interface tables, referenced to map VO attributes to physical interface columns.
• ECE_MAPPINGS — Holds the mapping definitions between EBS application data and external trading partner formats, essential for translating between VO attributes and XML elements.
• ECE_OUTPUT_RUNS_S — The sequence for output run identifiers, used when recording or retrieving outbound XML generation runs.
• DUAL — Used for single-row lookups and initialization within PL/SQL logic.

Usage Notes

EC_XML_UTILS is typically invoked indirectly rather than called directly by end users. It is referenced by eight other packages, indicating it functions as a shared utility layer within the E-Commerce Gateway XML processing stack. Outbound XML generation is commonly triggered by concurrent programs that process outbound interface data for a trading partner, invoking EC_XML_PROCESSOR_OUT_GENERIC to drive the generic outbound flow. Inbound XML consumption is likewise triggered by concurrent programs or inbound processing routines that call EC_XML_PROCESSOR_IN_GENERIC.

Because the package uses file-system based XML input and output (via file-name parameters), directory paths must be accessible to the database server processes executing the concurrent requests. Custom extensions should not modify this package; instead, they should call the generic processor procedures or implement supplementary VO definitions through the documented create procedures. Given its AUTHID CURRENT_USER qualifier, administrators should ensure that invoking schemas hold the necessary object privileges and directory access.