Search Results import_data_purge

Overview

APPS.FUN_OPEN_INTERFACE_PKG is an Oracle EBS Financials package belonging to the Open Interface import framework for the Funds (FUN) module — the subsystem that tracks open interface transactions between external or feeder systems and the Funds final transaction tables. Its primary business purpose is to convert validated rows staged in the FUN_INTERFACE_* interface tables into records in the destination Funds tables, and to subsequently cleanse accepted rows from the interface staging area. In practice, this package represents the server-side engine behind the Funds Open Interface concurrent program: it accepts a source and group identifier, validates the staged data against control totals, lookup values, and party (HZ) references, and on success performs the final insert into the destination tables while optionally recording rejected rows for correction and resubmission. The package is owned by APPS and is classified as OTHER, meaning it is not an officially published public API; nonetheless it is widely referenced from Oracle forms, concurrent programs, and legacy customization code that automate Funds interface loads. Because the package header is dated 2006 (revision 120.4), the same source has been carried forward with minimal change through 12.1.1 and 12.2.2, so behavior is materially identical across the two releases.

Key Procedures and Functions

• MAIN — The primary driver procedure. It validates interface table data and, on success, inserts the validated rows into the FUN final destination tables. It accepts a source, a group identifier, and control flags for import-as-sent behavior, rejected-only processing, and debug output, returning an error buffer and a completion return code to the caller. This is the entry point typically invoked by the Funds Open Interface concurrent program.
• PURGE_INTERFACE_TABLE — The procedure the user searched for. It purges accepted records from the interface tables, taking a source and group identifier to scope the delete against the correct interface batch. It is the standard mechanism for removing successfully processed rows without affecting rejected rows retained for correction and resubmission.
• IMPORT_DATA_PURGE — Documented in the 12.2.2 metadata as a third procedure. Consistent with the naming of the other two, it covers the import-and-purge cycle, coupling the load of interface data with the removal of the rows consumed so that the staging tables do not grow unbounded across successive runs.

No additional parameter metadata is documented beyond the header excerpt, so callers should inspect the deployed package specification for exact signatures prior to invoking these procedures directly.

Tables Accessed

• FUN_INTERFACE_HEADERS, FUN_INTERFACE_DIST_LINES, FUN_INTERFACE_BATCHDISTS, FUN_INTERFACE_BATCHES, FUN_INTERFACE_CONTROLS — the staged Funds interface data, distributions, batch associations, and control totals that are validated and then consumed by MAIN or removed by PURGE_INTERFACE_TABLE.
• FUN_INTERFACE_REJECTIONS — staging area for rows that fail validation, retained for correction and resubmission.
• FUN_TRX_HEADERS — the final destination table to which validated transactions are inserted.
• FND_LOOKUP_VALUES, FUN_SYSTEM_OPTIONS — reference and configuration data used during validation.
• FND_USER, FND_GRANTS, FND_OBJECT_INSTANCE_SETS — security, responsibility, and data-access validation.
• HZ_PARTIES, HZ_ORG_CONTACTS, HZ_ORG_CONTACT_ROLES — party and contact validation against the Trading Community Architecture model.

Usage Notes

Invocation is normally indirect: the Funds Open Interface concurrent program calls MAIN to validate and load a submitted group, and a purge step (or PURGE_INTERFACE_TABLE/IMPORT_DATA_PURGE called from PL/SQL) removes accepted rows afterward. Because the package is not a published public API, direct calls from custom code should be treated as unsupported and tested carefully; the source and group must always match the batch being processed, and p_rejected_only should be used to re-process rejected rows without reloading already-accepted data. The package is referenced by no other package, so it is a consumer rather than a provider of APIs.