Results for “calling_app_doc_ref_number”

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

Overview

IBY_EXT_FD_DOC_1_0_V is a seeded, VALID view owned by the APPS schema within the Oracle Payments (IBY) product family. Its name follows Oracle Payments' external extract interface convention: the EXT segment identifies it as a public interface object, FD denotes the Funds Disbursement/Document extract area, and the 1_0 suffix indicates a versioned interface contract expected to remain stable across patch levels. The view exposes payment document content in a denormalized, presentation-ready form for external consumers — primarily bank-format extract generation, XML/EFT outbound file production, and custom reporting on payable documents.

Its principal role is to decouple downstream consumers from the normalization of the underlying payment schema. Rather than joining IBY_DOCS_PAYABLE_ALL to lookup, sequence, delivery channel, and payment reason tables directly, external programs, BI Publisher extracts, and reporting layers select from this single flattened source.

Underlying Base Objects

Per the documented ETRM metadata, the view resolves against four categories of base objects.

• IBY_DOCS_PAYABLE_ALL — aliased as DOC; the driving table and the source of nearly every column in the view. It holds the payable document header data such as payment ID, document amounts, currencies, status, and remittance attributes.
• FND_DOCUMENT_SEQUENCES (FND_DOC_SEQ) — outer-joined on DOCUMENT_SEQUENCE_ID to supply the human-readable sequence name accompanying the numeric document sequence value.
• IBY_DELIVERY_CHANNELS_VL — outer-joined on DELIVERY_CHANNEL_CODE to expose the channel meaning and its format value used by extract format engines.
• IBY_PAYMENT_REASONS_VL — outer-joined on PAYMENT_REASON_CODE to provide the translated reason meaning and format value.
• FND_LOOKUPS — joined repeatedly (aliased DOCUMENT_STATUS_LOOKUP, DOCUMENT_TYPE_LOOKUP, SETTLEMENT_PRIORITY_LOOKUP, BANK_CHARGE_BEARER_LOOKUP) to translate coded values into MEANING text.

The documented ETRM base object list additionally records FND_GLOBAL (package), IBY_EXT_FD_DOC_1_0_VT (view), and IBY_FD_EXTRACT_GEN_PVT (package), reflecting the operational runtime path — the extract generation package invokes the view (directly or through its _VT translation variant), and FND_GLOBAL supplies session context such as ORG_ID and language for the multilingual lookup columns.

Key Columns

• PAYMENT_ID, DOCUMENT_PAYABLE_ID, PAYMENT_SERVICE_REQUEST_ID — primary joins back to the payment and document entities.
• CALLING_APP_ID, CALLING_APP_DOC_UNIQUE_REF1..5, CALLING_APP_DOC_REF_NUMBER — the calling application and its external document keys.
• DOCUMENT_SEQUENCE_VALUE, NAME — the assigned payment document number and its sequence name.
• DOCUMENT_STATUS, MEANING — coded status plus translated lookup meaning.
• DOCUMENT_AMOUNT, PAYMENT_AMOUNT, DOCUMENT_CURRENCY_CODE, PAYMENT_CURRENCY_CODE — monetary figures and currencies.
• PO_NUMBER, UNIQUE_REMITTANCE_IDENTIFIER, URI_CHECK_DIGIT, BANK_ASSIGNED_REF_CODE — key remittance and reconciliation identifiers.
• DELIVERY_CHANNEL_CODE, FORMAT_VALUE, MEANING — the extract channel and its format driver.
• REMITTANCE_MESSAGE1..3, PAYMENT_REASON_CODE, MEANING — remittance narrative and reason data.

Common Use Cases and Queries

Typical scenarios include extracting payable documents for a payment format, reconciling document status, and auditing remittance identifiers. A representative query follows.

SELECT v.PAYMENT_ID,
       v.DOCUMENT_PAYABLE_ID,
       v.PO_NUMBER,
       v.DOCUMENT_SEQUENCE_VALUE,
       v.DOCUMENT_STATUS_MEANING,
       v.DOCUMENT_AMOUNT,
       v.DOCUMENT_CURRENCY_CODE,
       v.UNIQUE_REMITTANCE_IDENTIFIER
  FROM APPS.IBY_EXT_FD_DOC_1_0_V v
 WHERE v.DELIVERY_CHANNEL_CODE = :p_channel
   AND v.DOCUMENT_STATUS = 'READY_FOR_EXTRACT';

Because the view is a versioned external contract, organizations should treat its column list as stable and avoid replacing it with custom joins unless the seeded interface cannot satisfy a requirement.