Results for “iby_payment_adapter_pub”

50+ results




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

Overview

IBY_PAYMENT_ADAPTER_PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite. It operates within the Payments module of Oracle iPayment (IBY), which provides the shared payment infrastructure used across Oracle Payables, Oracle Receivables, and other EBS product families. The package functions as an adapter layer that translates inbound payment processing requests—originated by external payment systems, bank communication interfaces, or BPEL-based authorization workflows—into the internal calls required by the IBY funds capture and disbursement engine.

The "PUB" suffix in the package name indicates an Oracle-classified public API, meaning it is intended for supported invocation by other application modules, rather than serving as a purely internal private routine. Its dependency on FND_API confirms that it observes the standard Oracle Application Object Library API conventions, including the use of standardized return status and message handling. In EBS 12.1.1 and 12.2.2, this package is a component of the broader funds capture processing chain that governs credit card authorizations, settlements, refunds, voids, and batch operations executed against payment instruments.

Key Procedures and Functions

The documented package exposes eighteen procedures and functions that map to discrete payment processing operations. The principal entry points include:

  • ORAPMTREQ — Submits a payment request or authorization against a payment instrument.
  • ORAPMTMOD — Modifies a previously submitted payment transaction.
  • ORAPMTCANC — Cancels a pending payment or authorization request.
  • ORAPMTREVERSE — Reverses a completed payment transaction.
  • ORAPMTQRYTRXN and ORAPMTINQ — Query transaction details and inquiry information.
  • ORAPMTCAPTURE and ORACCBATCHCAPTURE — Perform capture operations at the individual transaction and settlement batch levels respectively.
  • ORAPMTVOID — Voids an authorization or transaction.
  • ORAPMTCREDIT — Issues a credit against a previously captured payment.
  • ORAPMTCLOSEBATCH and ORAPMTQUERYBATCH — Close and query settlement batches.
  • ORAPMTRETURN — Handles returned or rejected payment responses.
  • ORARISKEVAL — Invokes risk evaluation processing for a payment transaction.
  • IS_RISKINFO_REC_MISSING — Determines whether required risk information records are absent.
  • ORASECUREEXTENSION — Supports secure extension handling for payment-related data.

Together these routines cover the standard lifecycle of a funds capture transaction: request, authorization, modification, capture, settlement, inquiry, void, reversal, credit, and return.

Tables Accessed

The package interacts with core IBY transaction tables through APPS synonyms:

  • IBY_FNDCPT_TX_EXTENSIONS — Stores extended attribute data associated with funds capture transactions, used to persist adapter-specific or payment-system-specific fields.
  • IBY_TRXN_SUMMARIES_ALL — Holds transaction summary records that consolidate payment processing outcomes for reporting and reconciliation.

It additionally relies on technical infrastructure objects including DBMS_OUTPUT, PLITBLM, UTL_HTTP, and UTL_TCP. The UTL_HTTP and UTL_TCP dependencies indicate that the adapter communicates with external payment processors or gateways over network protocols, while PLITBLM provides PL/SQL table handling utilities.

Usage Notes

IBY_PAYMENT_ADAPTER_PUB is typically invoked indirectly rather than called directly by end users. It is referenced by six other packages, notably AR_PMT_PROCESS_WRAPPER and AR_CC_REFUNDS in Oracle Receivables, IBY_BPEL_EBSR121PAYMENTAUTH for BPEL-based payment authorization, IBY_FNDCPT_TRXN_PUB, and IBY_NETUTILS_PVT. This reference pattern confirms its role as a downstream adapter receiving calls from higher-level processing packages and concurrent programs.

Administrators and developers should treat this package as an internal integration point. Customizations that call it directly should follow FND_API error-handling conventions, and any changes to caller packages in Receivables or iPayment must account for the adapter contract. Because external network calls are involved, monitoring and timeout handling deserve particular attention in production environments.