Search Results arp_process_boe




Overview
Explore in AI Chat

Overview

ARP_PROCESS_BOE is a PL/SQL package in the APPS schema that supports the processing of Bank of Entry (BOE) receipts within Oracle Receivables. Bank of Entry is the Japanese banking instrument used to settle customer obligations; in Oracle E-Business Suite the receipt method associated with BOE transactions drives automatic batch creation, remittance formatting, and receipt application. ARP_PROCESS_BOE provides the underlying programmatic logic that groups qualifying receipts into automatic and remittance batches, initiates the concurrent requests used to format those batches, and maintains the membership of receipts and transactions within a batch.

The package is registered as VALID in the ETRM metadata for both 12.1.1 and 12.2.2 and is classified under the generic API category (OTHER). It is a utility package rather than a public user-facing API, and it is referenced by only one other package in the documented dependency set: ARP_RW_BATCHES_PKG, Oracle's automatic receipt and remittance batch creation package. This tight coupling reflects its role as a supporting routine invoked during batch build and formatting cycles.

Key Procedures and Functions

The documented package exposes six procedures and functions. Names and purposes are as follows:

  • ADD_OR_RM_REMIT_REC_TO_BATCH — Adds a receipt to, or removes a receipt from, a remittance batch. This routine maintains remittance batch membership for receipts selected for BOE remittance processing.
  • CREATE_REMIT_BATCH_CONC_REQ — Submits the concurrent request that creates a remittance batch from the receipts currently staged for remittance processing.
  • APP_FMT_AUTO_BATCH_CONC_REQ — Submits the concurrent request that applies formatting to an automatic batch, producing the formatted output required by the BOE process.
  • APP_FMT_REMIT_BATCH_CONC_REQ — Submits the concurrent request that applies formatting to a remittance batch.
  • CREATE_AUTO_BATCH_CONC_REQ — Submits the concurrent request that creates an automatic batch from eligible receipts.
  • ADD_OR_RM_TXN_FROM_AUTO_BATCH — Adds a transaction to, or removes a transaction from, an automatic batch, maintaining the transaction-level contents of the batch during build or adjustment.

No parameter lists are documented in the ETRM metadata; callers should reference the package specification in a supported instance rather than assuming signatures.

Tables Accessed

The package operates across the core Receivables and Trading Community tables that define receipt, batch, and customer context. AR_BATCHES, AR_CASH_RECEIPTS, and AR_CASH_RECEIPT_HISTORY supply batch definitions, receipt records, and receipt status history. AR_PAYMENT_SCHEDULES and RA_CUSTOMER_TRX provide the transaction and installment detail against which receipts are applied, while AR_RECEIVABLE_APPLICATIONS stores the resulting application records. AR_CONS_INV supports consolidated billing and invoice context.

Customer and site information is drawn from HZ_PARTIES, HZ_CUST_ACCOUNTS, and HZ_CUST_SITE_USES. Receipt method configuration is read from AR_RECEIPT_METHODS, and system-level defaults such as the BOE-related profile options and batch numbering come from AR_SYSTEM_PARAMETERS. The metadata also lists AP_PAYMENT_PROGRAMS and IBY_FNDCPT_TX_EXTENSIONS, indicating interaction with payment program definitions and IBY funds capture transaction extensions used in receipt instrument processing.

Usage Notes

ARP_PROCESS_BOE is not intended for direct invocation by end users. It is invoked indirectly through the Receivables automatic receipt and remittance batch processes, primarily via ARP_RW_BATCHES_PKG, which is the only documented dependent package. In standard deployments it executes as part of the concurrent programs that create and format automatic and remittance batches for BOE receipt methods, and it may be reached from Receipts workbench batch maintenance when receipts are added to or removed from an existing batch.

Customizations should avoid reimplementing this logic. Because batch formatting and concurrent request submission are tightly coupled to Oracle's batch framework, extensions should call ARP_RW_BATCHES_PKG or the standard concurrent programs rather than ARP_PROCESS_BOE directly. Any code that does reference the package must be validated against the 12.1.1 and 12.2.2 package specifications, as ETRM documents only object metadata and not the callable interface.