Results for “payment_instruction_status”

50+ results




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

Overview

IBY_PAY_INSTRUCTIONS_ALL is the central transactional table in the Oracle Payments (IBY) module of Oracle E-Business Suite, storing payment instructions generated by the payments engine. Each row represents a discrete instruction to disburse funds — a grouping of one or more payments to be processed through a specific payment method, payment profile, internal bank account, and payment service request. The table is owned by the IBY schema and is documented as VALID in both EBS 12.1.1 and 12.2.2, containing 57 columns in the 12.2.2 physical schema.

The _ALL suffix indicates that the table is partitioned by operating unit (ORG_ID), a standard multi-org construct in EBS. Rows are created during payment processing runs, updated as the instruction moves through transmission, acknowledgement, and completion stages, and referenced thereafter by downstream payment, treasury, and withholding modules. Under a heuristic Data Vault classification — inferred from its foreign key footprint and its position as a referenced parent — IBY_PAY_INSTRUCTIONS_ALL leans toward a satellite role, describing the state and attributes of a payment instruction hub keyed by PAYMENT_INSTRUCTION_ID, with a small number of descriptive links to profiles, service requests, and bank accounts.

Key Information Stored

The surrogate primary key is PAYMENT_INSTRUCTION_ID, enforced by the IBY_PAY_INSTRUCTIONS_ALL_PK constraint and mirrored by the unique index IBY_PAY_INSTRUCTIONS_ALL_U1. Several columns govern processing state and timing:

Common Use Cases and Queries

Typical reporting focuses on instruction status, timing, and reconciliation against disbursed payments. A common pattern joins the instruction to AP_CHECKS_ALL by PAYMENT_INSTRUCTION_ID to reconcile checks to their parent instruction:

  • Payment run monitoring: filter by PROCESS_TYPE, PAYMENT_INSTRUCTION_STATUS, and PAYMENT_DATE to track in-flight instructions.
  • Settlement reporting: join to AP_CHECKS_ALL and CE_PAYMENT_DOCUMENTS on PAYMENT_INSTRUCTION_ID to verify cash clearing.
  • Bank file auditing: use BANK_ASSIGNED_REF_CODE, TRANSMISSION_DATE, and PAYMENT_SERVICE_REQUEST_ID to trace files sent to payment systems.
  • Audit extraction: select audit columns and ATTRIBUTE1 through ATTRIBUTE15 for customer-specific tracking.

Related Objects

IBY_PAY_INSTRUCTIONS_ALL sits at the junction of payments, treasury, and withholding: