Search Results iby_ext_fd_doc_1_0_v




Overview
Explore in AI Chat

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.

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

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.