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:
- PAYMENT_INSTRUCTION_STATUS — current lifecycle state of the instruction (e.g., created, formatted, transmitted, acknowledged, completed).
- PAYMENTS_COMPLETE_CODE — flag indicating whether all payments on the instruction have settled.
- PROCESS_TYPE and PAYMENT_FUNCTION — classify the payment run (e.g., payment, refund) and the business function invoked.
- PAYMENT_METHOD_CODE and PAYMENT_CURRENCY_CODE — drive formatting and settlement behavior.
- PAYMENT_PROFILE_ID (FK to IBY_ACCT_PMT_PROFILES_B), PAYMENT_SERVICE_REQUEST_ID (FK to IBY_PAY_SERVICE_REQUESTS), and PAYMENT_REASON_CODE (FK to IBY_PAYMENT_REASONS_B) — link the instruction to its configured processing context.
- INTERNAL_BANK_ACCOUNT_ID (FK to CE_BANK_ACCOUNTS) and LEGAL_ENTITY_ID (FK to FV_LEGAL_ENTITIES) — identify the disbursing bank account and owning legal entity.
- PAYMENT_DATE, TRANSMISSION_DATE, and ACKNOWLEDGEMENT_DATE — key reporting timestamps.
- PAYMENT_COUNT — number of payments consolidated into the instruction.
- ORG_ID and ORG_TYPE — operating unit partition key and entity type.
- REQUEST_ID — the concurrent request that created the instruction.
- Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER.
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:
- AP_CHECKS_ALL — references PAYMENT_INSTRUCTION_ID; each check is attached to one instruction.
- IBY_TRXN_DOCUMENTS — payment/remittance documents per instruction.
- IBY_PAY_INSTRUCTIONS_H — history/audit version of the instruction.
- IBY_ACCT_PMT_PROFILES_B, IBY_PAY_SERVICE_REQUESTS, IBY_PAYMENT_REASONS_B, CE_BANK_ACCOUNTS, FV_LEGAL_ENTITIES — parent reference tables.
- FV_SUMMARY_CONSOLIDATE_ALL, FV_TP_TS_AMT_DATA, FV_VOIDED_CHECKS, FV_TREASURY_CONFIRMATIONS_ALL — treasury settlement and voiding.
- JL_AR_AP_AWT_CERTIF_ALL — withholding certificate linkage.
- CE_PAYMENT_DOCUMENTS — bank statement reconciliation linkage.
-
"This table contains records of the payment instructions. Instructions are created based on the Payment Process Request options. Data is inserted in to the table IBY_PAY_INSTRUCTIONS_AL after payment instruction creation, based on the opt
-
IBY_PAY_INSTRUCTIONS_H stores historical snapshots of payment instructions. This table contains denormalized versions of payment instructions from specific points in time, including when the payment instruction was submitted to a payment sy
-
View: IBY_EXT_FD_INS_1_0_V 12.2.2
APPS.IBY_EXT_FD_INS_1_0_V·↳ CE_LOOKUPS·↳ CE_PAYMENT_DOCUMENTS·↳ CE_SECURITY_PROFILES_GT·Explore IBY module →
-
APPS.IBY_PAY_INSTRUCTIONS_SEC_V·↳ CE_SECURITY_PROFILES_V·↳ FND_ACCESS_CONTROL_UTIL·↳ FND_GLOBAL·Explore IBY module →
-
APPS.IBY_PAY_INSTRUCTIONS_SEC_V·↳ CE_SECURITY_PROFILES_V·↳ FND_ACCESS_CONTROL_UTIL·↳ FND_GLOBAL·Explore IBY module →
-
View: IBY_EXT_FD_INS_1_0_V 12.1.1
APPS.IBY_EXT_FD_INS_1_0_V·↳ CE_LOOKUPS·↳ CE_PAYMENT_DOCUMENTS·↳ CE_SECURITY_PROFILES_GT·Explore IBY module →