When the Oracle EBS Accounts Payable team reports that a payment batch is stuck, that a Format Payments request failed, or that an EFT transmission file was never generated, the root cause is almost never where the error message points. The Oracle Payments engine — built on the IBY module and integrated with CE bank account configuration, AP payment documents, and the FND concurrent manager — has more than a dozen distinct failure points between the point where an invoice is selected for payment and the point where a check is cut or an electronic file is transmitted. Each failure point has a different owner, a different resolution path, and a different impact on the payment cycle timeline.
The most common presentation is a payment batch that shows a status of FORMATTING or CONFIRMING in the Payment Batches screen and simply does not advance. The concurrent request for the Format Payments program has either completed with an error, is waiting in the queue behind a long-running job, or completed successfully but wrote an empty file because the payment process profile was misconfigured. In each case the visible symptom — batch stuck — is identical, but the resolution is completely different. Submitting Format Payments again without diagnosing the root cause produces a second failed batch and compounds the problem.
EFT payment failures introduce an additional layer. The IBY payment process profile must specify a valid disbursement bank account, a correctly configured transmission protocol, and a payment method rule that maps the supplier's bank account to the correct payment format. If any of these elements is missing or incorrectly sequenced, the transmission file either fails to generate or generates with zero records. The supplier does not receive payment. The payment batch shows as confirmed in Oracle while the supplier's bank receives nothing. This creates an accounts payable liability that is invisible to Oracle's own reconciliation reports until a bank statement is imported and the discrepancy surfaces.
AP-02 runs a structured investigation of the complete payment processing chain — from payment batch header status through concurrent request state, bank account assignment, payment process profile completeness, IBY document status, and transmission configuration. It identifies exactly where the chain broke, states the root cause, and provides the resolution path. For direct-fixable conditions — a batch stuck in FORMATTING due to a completed-with-error concurrent request — it generates the resubmission with the correct parameters. For setup issues — a missing bank account use, an inactive payment document — it identifies the exact Oracle Forms navigation path.
