Search Results process_xmlgt_inbwf

Overview

APPS.OZF_PRE_PROCESS_PVT is a private (PVT) PL/SQL package within the Oracle E-Business Suite Trade Management (formerly Oracle Sales and Marketing/Resale) module. Its principal responsibility is the pre-processing, validation, defaulting, and mapping of resale-related data staged in the Open Sales Order / resale integration interface tables before that data is promoted to the base Trade Management tables. In EBS 12.1.1 and 12.2.2 the package operates as the transformation and cleansing layer that sits between inbound WebADI spreadsheets, XML Gateway (XMLGT) messages, and the resale batch processing engine.

The package defines a comprehensive set of PL/SQL collection types — including number_table, varchar2_table (a table of VARCHAR2(5000) indexed by BINARY_INTEGER), and date_table — together with record types such as party_rec_type, party_site_rec_type, party_cntct_rec_type, and resale_line_int_rec_type. These structures allow the bulk manipulation of resale lines and their associated party, site, and contact data in a single pass, which is essential for performance when large batch volumes are imported.

Key Procedures and Functions

The documented API surface consists of 37 procedures and functions. Representative entries include:

• WEBADI_IMPORT — consumes data originating from WebADI uploads and stages it for subsequent processing.
• PROCESS_XMLGT_INBWF — processes inbound XML Gateway messages routed through the workflow.
• RESALE_PRE_PROCESS — the top-level orchestration routine that drives the overall pre-processing flow.
• BATCH_UPDATE, BATCH_FETCH, VALIDATE_BATCH, BATCH_DEFAULTING — the batch-level handlers responsible for retrieval, update, validation, and application of default values to resale batches.
• LINES_UPDATE, LINES_PROCESS, LINES_BULK_UPDATE, LINE_DEFAULTING, LINE_VALIDATIONS — the line-level equivalents, with bulk variants for high-volume processing.
• CODE_ID_MAPPING, UOM_CODE_MAPPING, PARTY_MAPPING — translate external codes and identifiers into internal Oracle IDs.
• LINE_PARTY_VALIDATIONS and PRODUCT_VALIDATIONS — validate party and inventory item data associated with each line.
• LINE_CURRENCY_PRICE_DERIVATION and CURRENCY_PRICE_DERIVATION — derive currency and pricing attributes for resale lines.
• AGREEMENT_DEFAULT — applies agreement-derived defaulting values.

Tables Accessed

The package reads and writes a tightly related set of interface and base tables:

• OZF_RESALE_BATCHES_ALL and OZF_RESALE_LINES_INT_ALL — the primary resale batch and interface line tables that are validated, defaulted, and updated.
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES — customer account and site information used during party and site validation.
• HZ_PARTIES, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_LOCATIONS — Trading Community Architecture party, site, and address data.
• HZ_MATCHED_CONTACTS_GT, HZ_MATCHED_PARTIES_GT, HZ_MATCHED_PARTY_SITES_GT — global temporary tables holding matched party, site, and contact candidates produced during the matching process.
• MTL_SYSTEM_ITEMS — inventory item validation for resale products.
• OZF_REQUEST_HEADERS_ALL_B — request header data supporting the resale flow.

All of these are accessed through APPS synonyms, confirming that the package runs with the standard APPS schema privileges and is not intended for direct customer invocation.

Usage Notes

Because OZF_PRE_PROCESS_PVT is classified as a private package, Oracle does not document it as a public integration point, and it is referenced by only two other packages within the ETRM codebase. It is typically invoked indirectly — either from the WebADI import handler, from the XML Gateway inbound workflow, or from the higher-level resale batch concurrent programs that call RESALE_PRE_PROCESS. Customizations should not call the PVT package directly; instead, customers should use the documented public APIs or the standard concurrent programs. Any reliance on the varchar2_table or other collection types defined here should be treated as version-specific, since private package signatures are subject to change between EBS releases such as 12.1.1 and 12.2.2.