Results for “iby_gen_docs_payable”

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

Overview

The IBY_GEN_DOCS_PAYABLE table resides in the IBY schema and forms part of the Oracle Payments (IBY) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the payable-side documents submitted to the payment engine for processing — typically invoices, credit memos, and other source documents originating from Payables, Payroll, or other calling applications that require disbursement. Each row represents a single document payable instruction captured during the payment instruction build process, carrying the monetary, banking, party, and remittance attributes needed to generate a payment.

In Data Vault modeling terms, the heuristic classification supplied by the ETRM metadata identifies this object as standalone. This is a modeling suggestion: the table behaves largely as a transaction-oriented record with its own atomic keys, rather than a pure hub, link, or satellite. Because the table carries both business attributes and foreign-key references to legal entities and payment profiles, it can practically be modeled as a satellite attached to a document hub, with the legal entity and payment profile references acting as links.

Key Information Stored

With 84 documented columns, the table is broad. The most operationally significant columns include:

• PAYMENT_FUNCTION — identifies the payment function context for the document.
• PAYMENT_DATE and DOCUMENT_DATE — the scheduled payment date versus the originating document date.
• DOCUMENT_TYPE, DOCUMENT_AMOUNT, and DOCUMENT_CURRENCY_CODE — the source document's identity and value.
• PAYMENT_AMOUNT and PAYMENT_CURRENCY_CODE — the amount actually payable after conversion.
• BENEFICIARY_PARTY, PAYEE_PARTY_ID, PARTY_SITE_ID, and SUPPLIER_SITE_ID — the payee identification chain.
• LEGAL_ENTITY_ID and ORG_ID — the legal entity and operating unit that own the payment.
• PAYMENT_PROFILE_ID — the payment profile governing disbursement behavior.
• CALLING_APP_ID and CALLING_APP_DOC_UNIQUE_REF1–5 — the surrogate-to-source linkage identifying the calling application and its document references.
• DOCUMENT_SEQUENCE_ID and DOCUMENT_SEQUENCE_VALUE — payment document sequencing for legal numbering.
• ATTRIBUTE1–15 and ATTRIBUTE_CATEGORY — the DFF extension columns.

The metadata does not document a named single-column surrogate primary key for this table; identity is instead strongly implied by the combination of calling application references (CALLING_APP_ID plus CALLING_APP_DOC_UNIQUE_REF1–5) and sequence values, which serve as business-key candidates. Two documented foreign keys anchor the table: LEGAL_ENTITY_ID to FV_LEGAL_ENTITIES and PAYMENT_PROFILE_ID to IBY_ACCT_PMT_PROFILES_B. Standard audit columns (CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, OBJECT_VERSION_NUMBER) are also present.

Common Use Cases and Queries

Typical reporting scenarios include reconciling documents selected into a payment instruction, validating payment amounts by currency, and auditing document sequencing. A representative query joining the legal entity FK:

SELECT p.CALLING_APP_DOC_REF_NUMBER, p.DOCUMENT_AMOUNT, p.PAYMENT_AMOUNT, le.NAME
FROM IBY.IBY_GEN_DOCS_PAYABLE p, FV.FV_LEGAL_ENTITIES le
WHERE p.LEGAL_ENTITY_ID = le.LEGAL_ENTITY_ID;

Grouping by payment profile to analyze disbursement volume is a second common pattern, joining PAYMENT_PROFILE_ID to IBY_ACCT_PMT_PROFILES_B. Filtering on PAYMENT_DATE supports cash forecasting and due-date analysis.

Related Objects

• FV_LEGAL_ENTITIES — joined on LEGAL_ENTITY_ID.
• IBY_ACCT_PMT_PROFILES_B — joined on PAYMENT_PROFILE_ID.
• IBY_PAYMENTS — the generated payment records associated with these payable documents.
• IBY_PAY_INSTRUCTIONS_ALL — the payment instruction headers governing document grouping.
• IBY_DOCS_PAYABLE_ALL — the transactional document-payable detail layer.
• IBY_PAY_SERVICE_REQUESTS — the service request records tied to payment actions.
• AP_INVOICES_ALL and AP_CHECKS_ALL — upstream Payables sources and downstream disbursement records.
• IBY_DELIVERY_OPTIONS_B — delivery channel configuration referenced by DELIVERY_CHANNEL_CODE and PAYMENT_FORMAT_CODE.