Results for “iby_pyo_invoice_gt”

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

Overview

IBY_PYO_INVOICE_GT is an APPS-owned table within the Oracle E-Business Suite Payments (IBY) module. The suffix _GT identifies it as a Global Temporary Table used by the Payment Process (PYO) to stage invoice-level payment instruction data during a payment run. When the Payment Process Request (PPR) builds a payment batch, individual invoice records selected for payment are inserted into this staging structure so that downstream programs — payment formatting, remittance advice generation, and bank file creation — can operate on them. The table holds no permanent business data; its contents are transient and typically scoped to the session or transaction that populated them.

From a data modeling perspective, the heuristic classification supplied in the ETRM metadata is standalone, meaning the table does not participate in a formal hub-and-link Data Vault structure. A modeling suggestion would be to treat it as a satellite-like staging artifact: it carries descriptive attributes about invoices and payment instructions consolidated for one processing pass, rather than acting as a reusable business key hub or a many-to-many link between entities. The single documented foreign key to IBY_PAY_INSTRUCTIONS_ALL is instructive: a small fragment of its rows reference a persistent instruction key, while the majority of its columns are descriptive payload populated only during processing.

Key Information Stored

The table contains 81 documented columns spanning payment identifiers, invoice attributes, and extensibility fields. The most operationally significant columns are:

• PAYMENT_ID — Surrogate identifier for the payment being built; the primary correlation key between staged invoices and the eventual payment record.
• PAYMENT_INSTRUCTION_ID — Foreign key to IBY_PAY_INSTRUCTIONS_ALL, linking a staged row to the persistent payment instruction definition.
• INVOICE_NUM, INVOICE_DATE, INVOICE_DESCRIPTION — Business attributes describing the invoice being paid.
• VENDOR_NUM, VENDOR_ID, VENDOR_SITE_ID — Supplier identification, resolved from the invoice source.
• CUSTOMER_NUM — Populated for refund or third-party payment flows where the payee is a customer rather than a supplier.
• INVOICE_AMOUNT, PROPOSED_PAYMENT_AMOUNT, DISCOUNT_AMOUNT, AMOUNT_WITHHELD — Financial measures representing the invoice value, the amount selected for this payment, early-payment discount taken, and any portion withheld.
• PAYMENT_METHOD_CODE, PAYMENT_MEAN, PAYMENT_CHANNEL, DELIVERY_CHANNEL_CODE — The instrument and channel by which the payment will be remitted.
• BANK_ACCOUNT_ID, VENDOR_BANK_ACCOUNT_ID, EXTERNAL_BANK_ACCOUNT_ID — Disbursement and payee bank account references.
• CHECK_NUMBER, PAYMENT_REFERENCE_NUMBER, DOCUMENT_SEQUENCE_ID, DOCUMENT_SEQUENCE_VALUE — Instrument-specific numbering and document sequencing data.
• REMITTANCE_MESSAGE1–3, UNIQUE_REMITTANCE_IDENTIFIER, URI_CHECK_DIGIT — Remittance advice content and identifiers used in bank file generation.
• ATTRIBUTE1–15 and INV_GLOBAL_ATTRIBUTE1–20 — Descriptive flexfield and global descriptive flexfield segments carried forward from the invoice.
• CALLING_APP_ID and CALLING_APP_DOC_UNIQUE_REF1–5 — The calling application identifier and up to five document reference values, allowing external systems to reconcile created payments back to source documents.

No surrogate primary key or unique index is documented in the ETRM metadata; the table functions as an anonymous staging area rather than a keyed master record.

Common Use Cases and Queries

The principal use case is diagnostic: during or immediately after a payment run, a query against this table reveals precisely which invoices were selected, what amounts were proposed, and which bank accounts will be credited. A representative pattern is:

• Filtering staged rows for a specific payment run — SELECT payment_id, invoice_num, vendor_num, proposed_payment_amount, payment_method_code FROM iby_pyo_invoice_gt WHERE payment_id = :p_payment_id;
• Aggregating proposed amounts against invoice amounts to detect partial payments or discounts taken — SELECT payment_id, SUM(invoice_amount) invoice_total, SUM(proposed_payment_amount) payable_total, SUM(discount_amount) discount_total FROM iby_pyo_invoice_gt GROUP BY payment_id;
• Joining to the payment instruction to confirm the instruction context — SELECT gt.invoice_num, instr.payment_instruction_id FROM iby_pyo_invoice_gt gt, iby_pay_instructions_all instr WHERE gt.payment_instruction_id = instr.payment_instruction_id;
• Reporting on remittance message content ahead of bank file transmission by inspecting REMITTANCE_MESSAGE1–3 and UNIQUE_REMITTANCE_IDENTIFIER.

Extraction or reconciliation queries against this table must run in the context of an active payment process; because it is a global temporary table, rows disappear at session or transaction end, and querying it from an unrelated session typically returns no data.

Related Objects

• IBY_PAY_INSTRUCTIONS_ALL — The only documented foreign key target, joined via PAYMENT_INSTRUCTION_ID. Holds the persistent instruction header that a staged invoice group belongs to.
• IBY_PAYMENTS_ALL — The persistent payment record ultimately produced from the staged rows, correlated through PAYMENT_ID.
• IBY_PAYMENT_TRANSACTIONS — Detail transaction lines that reference the payment and invoice, providing a permanent counterpart to this transient staging table.
• IBY_REMIT_ADVICE / IBY_REMIT_ADVICE_DOCS — Remittance advice structures populated from the remittance message and URI columns staged here.
• IBY_DISBURSEMENT_SETUPS / IBY_EXTERNAL_PAYEES_ALL — Sources for bank account and delivery channel values carried into the staged rows.
• AP_INVOICES_ALL / AP_INVOICE_PAYMENTS_ALL — Payables source tables whose invoice details are staged into this structure during a payment run.
• IBY_FD_PAYMENT_FORMATS / IBY_FD_DOCUMENTS — Payment formatting objects that consume rows from the staging table to construct bank files.

These relationships confirm the table's role as a transient integration point between Payables invoice selection, the Payments engine, and downstream payment formatting and remittance delivery.