Results for “recall_from_external_agency”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IEX_OPEN_INTERFACE_PUB is a public PL/SQL package in the APPS schema that provides the integration layer for Oracle E-Business Suite's open interface and credit bureau reporting functionality. It belongs to the Oracle Advanced Collections (IEX) application family and serves as the published API through which both internal EBS modules and external systems submit, process, and reconcile open-interface records. In Oracle EBS 12.1.1 and 12.2.2, the package acts as a controlled gateway, abstracting the underlying tables and private packages so that callers do not manipulate base tables directly.

The package's responsibilities span two related domains: logging and completing credit bureau report requests, and managing open-interface transfers associated with external agencies, including recall, review, and notification workflows. It depends on several sibling APIs, including IEX_IOH_PVT, OKC_API, OKL_OIN_PVT, and OKL_OPEN_INT_PUB, and is itself referenced by IEX_CO_WF, IEX_OPI_PVT, OKL_CO_WF, and recursively by IEX_OPEN_INTERFACE_PUB. This dependency graph confirms its role as a shared service invoked from workflow and other public entry points.

Key Procedures and Functions

The documented API exposes eleven procedures, grouped by purpose:

• REPORT_ALL_CREDIT_BUREAU — Initiates reporting of open items to credit bureaus.
• INSERT_PENDING — Stages new open-interface records in a pending state for later processing.
• PROCESS_PENDING — Processes the staged pending records, moving them into completed status or error handling.
• COMPLETE_REPORT_CB — Marks a credit bureau report request as complete after successful submission.
• COMPLETE_TRANSFER — Finalizes an open-interface transfer, confirming that the record has been transferred successfully.
• RECALL_TRANSFER — Recalls a previously submitted transfer, reversing or cancelling it.
• REVIEW_TRANSFER — Places a transfer into review, allowing examination before it is finalized or recalled.
• NOTIFY_CUSTOMER — Sends a notification to the customer regarding reporting or transfer activity.
• NOTIFY_RECALL_EXTERNAL_AGENCY — Notifies an external agency that a recall has been initiated.
• NOTIFY_EXTERNAL_AGENCY — Notifies an external agency about transfer activity.
• RECALL_FROM_EXTERNAL_AGENCY — Recalls a record that was previously transmitted to an external agency.

The pattern is a staged lifecycle: records are inserted as pending, processed, then progressed through complete, review, or recall states, with notifications emitted at the relevant transitions. Parameter details are not documented in the available metadata.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• IEX_OPEN_INT_HST — History table for open-interface records, retaining prior states and processing outcomes.
• OKL_OPEN_INT — The primary open-interface table holding current records to be processed, updated, or recalled.
• HZ_PARTIES — Provides party data, such as the customers or agencies involved in reporting and notification.
• HZ_CONTACT_POINTS — Supplies contact information used when generating notifications to customers or agencies.
• JTF_AMV_ITEMS_B — The message/attribute repository, used to build the content of outbound notifications.

These tables support the full cycle: staging (OKL_OPEN_INT, IEX_OPEN_INT_HST), party resolution (HZ_PARTIES, HZ_CONTACT_POINTS), and notification generation (JTF_AMV_ITEMS_B).

Usage Notes

IEX_OPEN_INTERFACE_PUB is typically invoked from Oracle Advanced Collections workflow processes, concurrent programs, and custom integrations rather than from a single base form. The references from IEX_CO_WF and OKL_CO_WF indicate workflow-driven invocation for completion and notification steps, while IEX_OPI_PVT suggests orchestration from the open-item processing logic.

Custom code should call these procedures rather than inserting directly into OKL_OPEN_INT or IEX_OPEN_INT_HST, because the package enforces status transitions and emits the required notifications. Because the API is classified as PUB, it is intended for supported customer and integration use, though callers should supply correct identifiers and honor the pending-then-process sequencing when staging records. In 12.2.2 the package remains valid and structurally equivalent to its 12.1.1 counterpart, preserving upgrade compatibility for existing integrations.