Results for “iby_fd_docs_payable_v”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The IBY_FD_DOCS_PAYABLE_V view is a reporting and integration object within the Oracle Payments (IBY) module of Oracle E-Business Suite, available in both release 12.1.1 and 12.2.2. It presents payable document information as consumed by the Funds Disbursement (FD) layer of Oracle Payments, exposing the attributes required to build, validate, format, and transmit payment instructions to a payment system or financial institution. The view derives its name from the "FD" abbreviation for Funds Disbursement and from the payable documents it surfaces, and it is owned by the APPS schema with a status of VALID in the ETRM repository. Its principal role is to provide a denormalized, query-friendly projection of the payment document repository so that reports, extracts, and interfacing programs can retrieve payment-relevant document data without navigating the full base table structure directly.
Underlying Base Objects
According to the documented ETRM metadata for 12.2.2, the view is defined over the base object IBY_DOCS_PAYABLE_ALL, which is referenced through a synonym. IBY_DOCS_PAYABLE_ALL is the central transactional repository in Oracle Payments for payable documents — the records that represent individual payment instructions together with their payee, amount, currency, and processing status information. The view text shows an unqualified reference to the alias IBY_DOCS, which resolves to the IBY_DOCS_PAYABLE_ALL synonym. Because the view is a projection of a single base table, it does not introduce joins or aggregations; it functions as a column subset and rename layer over the underlying documents table, preserving row-for-row correspondence with the base object. The ALL designation in the base object name signals multi-organization visibility, meaning the view returns documents across the operating units accessible to the querying responsibility.
Key Columns
The view exposes a broad set of columns that span document identification, payment processing, and formatting concerns. Principal columns include DOCUMENT_PAYABLE_ID, the primary document identifier, and PAYMENT_ID and FORMATTING_PAYMENT_ID, which link the document to its payment and formatting contexts. Monetary attributes include DOCUMENT_AMOUNT, PAYMENT_AMOUNT, AMOUNT_WITHHELD, PAYMENT_CURR_DISCOUNT_TAKEN, DOCUMENT_CURRENCY_TAX_AMOUNT, and DOCUMENT_CURR_CHARGE_AMOUNT, alongside currency codes at both document and payment level (DOCUMENT_CURRENCY_CODE, PAYMENT_CURRENCY_CODE).
- Status and type: DOCUMENT_STATUS, DOCUMENT_TYPE, DOCUMENT_CATEGORY_CODE, and PAY_PROC_TRXN_TYPE_CODE describe the document's nature and processing state.
- Payment routing: PAYMENT_METHOD_CODE, PAYMENT_FUNCTION, PAYMENT_FORMAT_CODE, DELIVERY_CHANNEL_CODE, and PAYMENT_SERVICE_REQUEST_ID drive how the instruction is executed.
- Party and location: PAYEE_PARTY_ID, EXT_PAYEE_ID, PARTY_SITE_ID, SUPPLIER_SITE_ID, REMIT_TO_LOCATION_ID, and LEGAL_ENTITY_ID identify the payee and remittance destination.
- Dates: PAYMENT_DATE, DOCUMENT_DATE, PAYMENT_DUE_DATE, DISCOUNT_DATE, and ANTICIPATED_VALUE_DATE support scheduling and cash management.
- Calling application references: CALLING_APP_ID, CALLING_APP_DOC_REF_NUMBER, and the CALLING_APP_DOC_UNIQUE_REF1 through REF5 columns correlate the payment document back to its source application record.
- Remittance and bank data: REMITTANCE_MESSAGE1 through MESSAGE3, PAYMENT_REASON_CODE, PAYMENT_REASON_COMMENTS, BANK_ASSIGNED_REF_CODE, and PO_NUMBER carry the narrative and reference content transmitted with the payment.
- Internal control columns: ORG_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER.
Common Use Cases and Queries
The view is typically queried when investigating payment document content, reconciling payment batches, or building extracts for reconciliation and audit reporting. A frequent pattern filters documents by calling application and status to isolate in-flight or completed instructions.
A representative query retrieving key payment attributes for a given payee is:
SELECT document_payable_id, payment_id, document_amount, payment_currency_code, document_status, payment_date, calling_app_doc_ref_number FROM apps.iby_fd_docs_payable_v WHERE payee_party_id = :p_party_id AND document_status = 'CREATED';
Another common pattern aggregates amounts by currency and payment method for a specific operating unit, joining to lookup or payment method views as needed. Because the view is defined over IBY_DOCS_PAYABLE_ALL, it inherits multi-org security, so users should restrict queries by ORG_ID or rely on the operating unit context of the responsibility to avoid returning data from units they are not authorized to view. Developers integrating with Oracle Payments frequently use this view to retrieve CALLING_APP_ID and the unique reference columns in order to reconcile documents created through the payment service request interface.
-
View: IBY_FD_DOCS_PAYABLE_V 12.1.1
APPS.IBY_FD_DOCS_PAYABLE_V·↳ IBY_DOCS_PAYABLE_ALL·Explore IBY module →
-
View: IBY_FD_DOCS_PAYABLE_V 12.2.2
APPS.IBY_FD_DOCS_PAYABLE_V·↳ IBY_DOCS_PAYABLE_ALL·Explore IBY module →
-
Available cashflow payments/receipts for reconciliation or clearing
APPS.CE_260_CF_TRANSACTIONS_V·↳ CE_BANK_ACCTS_GT_V·↳ CE_BANK_BRANCHES_V·↳ CE_CASHFLOWS·Explore CE module →
-
Available cashflow payments/receipts for reconciliation or clearing
APPS.CE_260_CF_TRANSACTIONS_V·↳ CE_BANK_ACCTS_GT_V·↳ CE_BANK_BRANCHES_V·↳ CE_CASHFLOWS·Explore CE module →
-
View: CE_260_CF_REVERSAL_V 12.1.1
AR receipts for reversing or unclearing
APPS.CE_260_CF_REVERSAL_V·↳ CE_BANK_ACCTS_GT_V·↳ CE_BANK_BRANCHES_V·↳ CE_CASHFLOWS·Explore CE module →
-
View: CE_260_CF_REVERSAL_V 12.2.2
AR receipts for reversing or unclearing
APPS.CE_260_CF_REVERSAL_V·↳ CE_BANK_ACCTS_GT_V·↳ CE_BANK_BRANCHES_V·↳ CE_CASHFLOWS·Explore CE module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
View: CE_260_CF_RECONCILED_V 12.1.1
Reconciled cashflow receipts and payments for unreconciling
APPS.CE_260_CF_RECONCILED_V·↳ CE_BANK_ACCTS_GT_V·↳ CE_CASHFLOWS·↳ CE_CASHFLOW_ACCT_H·Explore CE module →