Search Results vendor_attribute1




Overview
Explore in AI Chat

Overview

IBY_PYO_PAYMENT_GT is an Oracle EBS Applications (APPS) schema table belonging to the IBY — Payments product family. The "GT" suffix denotes a global temporary table used by Oracle Payments during payment instruction building and formatting. It acts as a transient staging area that holds the denormalized data set required to produce payment documents (checks, EFT/ACH files, wire transmissions) for a single payment process request. The table is populated at run time by the payment formatting programs and is scoped, in practice, to the processing session, so its contents are short-lived and cannot be treated as a permanent transactional record.

From a heuristic Data Vault modeling perspective, the object classifies as a standalone structure. It does not behave as a pure hub, link, or satellite; it is a wide, denormalized staging/landing area that aggregates attributes originating from multiple upstream entities (supplier, supplier site, bank, bank account, and payment instruction) into a single flattened projection. It should therefore be modeled as a transient staging or snapshot construct rather than as a conformed dimensional source.

Key Information Stored

The documented physical schema for 12.2.2 contains 264 columns. Only the most significant are highlighted below; the remainder are descriptive address, attribute, and context fields.

The surrogate/technical key is not enumerated among the documented columns; the joinable business identifiers are PAYMENT_INSTRUCTION_ID and SELECTED_CHECK_ID, which carry the documented foreign key constraints.

Common Use Cases and Queries

Because IBY_PYO_PAYMENT_GT is a session-scoped staging table, its primary uses are debugging and reconciliation of payment formatting output, verification of bank and supplier data propagated onto a payment document, and confirming that flexfield attributes were correctly defaulted.

A typical diagnostic pattern joins the staging rows back to the payment instruction to confirm the instruction under construction:

  • SELECT g.check_number, g.check_amount, g.currency_code, g.vendor_name FROM iby_pyo_payment_gt g WHERE g.payment_instruction_id = :instruction_id;
  • Correlate to source: join PAYMENT_INSTRUCTION_ID to IBY_PAY_INSTRUCTIONS_ALL and SELECTED_CHECK_ID to AP_SELECTED_INVOICE_CHECKS_ALL to trace a formatted payment back to selected invoices.
  • Bank data validation: query BANK_ACCOUNT_NUM, BANK_NUM, IBAN_NUMBER, and BK_EFT_SWIFT_CODE to confirm routing information rendered onto EFT/ACH outputs.
  • Extensibility audit: SELECT DISTINCT ABA_GLOBAL_ATTRIBUTE_CATEGORY, ABA_GLOBAL_ATTRIBUTE1 FROM iby_pyo_payment_gt to verify bank flexfield values reached the document.

Reporting use cases include pre-format data review and troubleshooting of payment process requests where output is missing or malformed.

Related Objects