Search Results calling_app_document_unique_id

Overview

The view APPS.IBY_EXT_FD_DOC_1_0_V is a public interface view published by the Oracle Payments (IBY) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes payment document data in the flat, denormalized structure defined by the Oracle Payments ISO 20022 / external file delivery format known as DOC_1_0. The view acts as the read interface through which external payment formats, extract generators, and integration programs retrieve the payment and payable document records that must be rendered into a payment instruction file.

The DOC_1_0 payload represents a single payment document line — the payable, the payment, and the formatting instructions associated with the transmission of funds. Applications and interfaces query this view by CALLING_APP_DOC_REF_NUMBER and process the returned rows to build outbound bank files or to reconcile payment instructions. The view is therefore central to payment file generation, payment formatting, and remittance advice production in EBS.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over three referenced objects:

• IBY_EXT_FD_DOC_1_0_VT — the underlying view (the "_VT" suffix indicates a view text/template layer) from which all columns are selected. The public view is essentially a projection and ordering of this base view.
• IBY_FD_EXTRACT_GEN_PVT — the extract generation package that populates the data consumed by the _VT view at runtime.
• FND_GLOBAL — the standard EBS package used to resolve session context such as USER_ID, RESP_ID, and ORG_ID; the view inherits this context for access and data filtering.

The view is defined with a deterministic ordering clause: ORDER BY CALLING_APP_DOC_REF_NUMBER, ensuring a stable, predictable sequence when consumers read multiple document lines.

Key Columns

The view exposes approximately 80 columns. The most significant groupings are:

• Identifiers: PAYMENT_ID, DOCUMENT_PAYABLE_ID, PAYMENT_SERVICE_REQUEST_ID, CALLING_APP_ID, CALLING_APP_DOCUMENT_UNIQUE_ID, CALLING_APP_DOC_REF_NUMBER, CALLING_APP_DOC_UNIQUE_REF1 through REF5.
• Bank/remittance identification: BANK_ASSIGNED_REF_CODE, UNIQUE_REMITTANCE_IDENTIFIER, URI_CHECK_DIGIT.
• Document classification: DOC_CATEGORY, DOC_SEQUENCE_NAME, DOC_SEQUENCE_VALUE, PO_NUMBER, DOCUMENT_TYPE, DOCUMENT_TYPE_MEANING.
• Status: DOCUMENT_STATUS and its decode column DOCUMENT_STATUS_MEANING — the human-readable meaning used when reporting or displaying payment document state. This is the value most commonly searched for by users inspecting payment document processing.
• Amounts and currency: DOCUMENT_AMOUNT, DOCUMENT_CURRENCY_CODE, PAYMENT_AMOUNT, PAYMENT_CURRENCY_CODE, AMOUNT_WITHHELD, PAYMENT_CURR_DISCOUNT_TAKEN, DOCUMENT_CURR_CHARGE_AMOUNT, DOCUMENT_CURRENCY_TAX_AMOUNT.
• Formatting and delivery: DELIVERY_CHANNEL_CODE / DELIVERY_CHANNEL_MEANING, DELIVERY_CHANNEL_FORMAT_VALUE, SETTLEMENT_PRIORITY / SETTLEMENT_PRIORITY_MEANING, PAYMENT_REASON_CODE / PAYMENT_REASON_MEANING, REMITTANCE_MESSAGE1..3, FORMATTING_PAYMENT_ID, EMPLOYEE_PAYMENT_FLAG, EXCLUSIVE_PAYMENT_FLAG.
• Dating: DOCUMENT_DATE, DOCUMENT_CREATION_DATE, PAYMENT_DUE_DATE, DISCOUNT_DATE.
• Flexfields: GLOBAL_ATTRIBUTE_CATEGORY and GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE20.

Common Use Cases and Queries

The view is typically used to inspect payment document content before or after extraction, to verify status and amounts, and to build ad hoc reports on payment instructions.

SELECT CALLING_APP_DOC_REF_NUMBER,
       PAYMENT_ID,
       DOCUMENT_PAYABLE_ID,
       DOCUMENT_STATUS,
       DOCUMENT_STATUS_MEANING,
       DOCUMENT_AMOUNT,
       DOCUMENT_CURRENCY_CODE,
       PAYMENT_DUE_DATE,
       DELIVERY_CHANNEL_MEANING
  FROM APPS.IBY_EXT_FD_DOC_1_0_V
 WHERE DOCUMENT_STATUS_MEANING = 'Paid'
 ORDER BY CALLING_APP_DOC_REF_NUMBER;

A second common pattern is to locate a document by its payables reference:

SELECT PAYMENT_ID, DOCUMENT_PAYABLE_ID, DOCUMENT_TYPE_MEANING,
       DOCUMENT_AMOUNT, DOCUMENT_STATUS_MEANING
  FROM APPS.IBY_EXT_FD_DOC_1_0_V
 WHERE CALLING_APP_DOC_REF_NUMBER = :p_ref_number;

Because the view is ordered and flat, it is also frequently joined to IBY_PAYMENTS_ALL or IBY_DOCS_PAYABLE_ALL to reconcile generated extract lines against their source payment and payable records, and it is queried by formatting programs to resolve amounts, currencies, and remittance messages immediately prior to payment file transmission.