Search Results iby_pay_service_requests_u2

Overview

IBY.IBY_PAY_SERVICE_REQUESTS is the central transactional table in the Oracle Payments (IBY) schema that stores payment process requests submitted by source products such as Payables, Receivables, and Payroll. A payment process request (PPR) represents a logical grouping of documents payable that a calling application transmits to Oracle Payments for payment service processing, including payment creation, formatting, and instruction generation. Each row in this table corresponds to a single Payment Process Request as presented on the Payment Process Requests page in the E-Business Suite user interface.

The object is owned by the IBY schema, is registered under FND Design Data as IBY.IBY_PAY_SERVICE_REQUESTS, carries a VALID status, and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. In Oracle EBS 12.1.1 and 12.2.2 the documented physical schema contains 39 columns. Based on the mined foreign key topology, the table exhibits a satellite-leaning Data Vault classification — it holds descriptive and state-bearing attributes about a payment request and hangs off the calling application's identifier rather than acting as a pure hub or junction. Modeling this object as a satellite keyed to the calling application and the source request code is therefore a reasonable design suggestion.

Key Information Stored

The surrogate primary key is PAYMENT_SERVICE_REQUEST_ID, a system-generated NUMBER(15) that uniquely identifies each payment process request and is enforced by the unique index IBY_PAY_SERVICE_REQUESTS_U1. The second unique index, IBY_PAY_SERVICE_REQUESTS_U2, covers the business-key pair CALLING_APP_ID and CALL_APP_PAY_SERVICE_REQ_CODE, establishing the natural source-product identity of the request. CALLING_APP_ID is the numeric identifier of the source product, while CALL_APP_PAY_SERVICE_REQ_CODE is a VARCHAR2(255) holding the source product's own request identifier — stored as a string because source identifiers may be alphanumeric.

PAYMENT_SERVICE_REQUEST_STATUS is a VARCHAR2(30) populated from the IBY_REQUEST_STATUSES lookup and can hold values such as PAYMENTS_CREATED. PROCESS_TYPE describes how documents payable are built into payments and payments into payment instructions. Financial and control attributes include INTERNAL_BANK_ACCOUNT_ID, PAYMENT_PROFILE_ID, MAXIMUM_PAYMENT_AMOUNT, MINIMUM_PAYMENT_AMOUNT, ALLOW_ZERO_PAYMENTS_FLAG, DOCUMENT_REJECTION_LEVEL_CODE, PAYMENT_REJECTION_LEVEL_CODE, REQUIRE_PROP_PMTS_REVIEW_FLAG, and CREATE_PMT_INSTRUCTIONS_FLAG. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) plus ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 provide audit and extensibility support.

Common Use Cases and Queries

Typical reporting scenarios include tracking PPR status by source application, reconciling requests against their generated payments and instructions, and auditing rejected or reviewed submissions. The following pattern joins the request to its documents payable:

• SELECT p.PAYMENT_SERVICE_REQUEST_ID, p.CALLING_APP_ID, p.CALL_APP_PAY_SERVICE_REQ_CODE, p.PAYMENT_SERVICE_REQUEST_STATUS, d.DOCUMENT_PAYABLE_ID FROM IBY_PAY_SERVICE_REQUESTS p, IBY_DOCUMENTS_PAYABLE_H d WHERE p.PAYMENT_SERVICE_REQUEST_ID = d.PAYMENT_SERVICE_REQUEST_ID;
• Filter by status using the IBY_REQUEST_STATUSES lookup, for example WHERE PAYMENT_SERVICE_REQUEST_STATUS = 'PAYMENTS_CREATED', to identify completed runs.
• Join to IBY_ACCT_PMT_PROFILES_B on PAYMENT_PROFILE_ID to report the payment profile configuration used for each request.
• Join to CE_BANK_ACCOUNTS on INTERNAL_BANK_ACCOUNT_ID to expose the disbursement bank account.

Because the U2 unique index covers CALLING_APP_ID and CALL_APP_PAY_SERVICE_REQ_CODE, source systems commonly query by that pair to locate a specific submitted request.

Related Objects

The table participates in several documented foreign key relationships. IBY_DOCUMENTS_PAYABLE_H, IBY_PAY_INSTRUCTIONS_ALL, and IBY_HOOK_PAYMENTS_T each reference IBY_PAY_SERVICE_REQUESTS through PAYMENT_SERVICE_REQUEST_ID, supporting the documents-payable, payment-instruction, and hook payment flows respectively. In the reverse direction, IBY_PAY_SERVICE_REQUESTS references CE_BANK_ACCOUNTS via INTERNAL_BANK_ACCOUNT_ID and IBY_ACCT_PMT_PROFILES_B via PAYMENT_PROFILE_ID. Reporting objects and concurrent programs that consume payment process requests typically traverse these relationships, and the IBY_REQUEST_STATUSES lookup supplies the valid values for PAYMENT_SERVICE_REQUEST_STATUS.