Results for “doc_category_code”

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

Overview

IBY_DOCS_PAYABLE_GT is a global temporary table (denoted by the _GT suffix) owned by the IBY schema within Oracle EBS Payments. It serves as a transient staging structure for Oracle Payments (IBY) payable document processing. Unlike the persistent IBY_DOCS_PAYABLE_ALL table, which stores the definitive record of payable documents, IBY_DOCS_PAYABLE_GT holds working-set rows scoped to a single session or transaction during payment build, formatting, and instruction generation. Its role is procedural: it carries document-level attributes into the payment engine so that formatting programs and payment instruction build routines can consolidate, group, and serialize payable records without committing intermediate state to the permanent schema.

The ETRM Data Vault classification for this object is standalone, indicating that the FK heuristic did not identify it as a conventional hub, link, or satellite. Modelers can interpret this as guidance that the table behaves as a session-scoped staging satellite rather than a durable Data Vault construct; its data typically maps to a satellite keyed on the persistent payable document identifier held in IBY_DOCS_PAYABLE_ALL.

Key Information Stored

The documented physical schema contains 81 columns. The most significant are:

• DOCUMENT_PAYABLE_ID — Foreign key to IBY_DOCS_PAYABLE_ALL; the primary business-key candidate linking the staging row to its persistent document. This is the surrogate key of the parent, not a new key generated in the GT.
• CALLING_APP_ID and CALLING_APP_DOC_UNIQUE_REF1–5 — Identify the source application and its unique document references, enabling cross-application reconciliation (AP, AR, GL, Treasury).
• CALLING_APP_DOC_REF_NUMBER — Human-readable source document reference, commonly the invoice or payment number.
• PAYMENT_AMOUNT, DOCUMENT_AMOUNT, PAYMENT_CURR_DISCOUNT_TAKEN, AMOUNT_WITHHELD, BANK_CHARGE_AMOUNT — Monetary figures governing the payable and the resulting payment instruction.
• DOCUMENT_CURRENCY_CODE and PAYMENT_CURRENCY_CODE — Distinguish the document currency from the payment currency for cross-currency settlement.
• PAYMENT_METHOD_CODE, PAYMENT_FORMAT_CODE, PAYMENT_FUNCTION, PROCESS_TYPE — Drive routing, formatting, and disbursement behaviour.
• PAYMENT_PROFILE_ID (→ IBY_ACCT_PMT_PROFILES_B), LEGAL_ENTITY_ID (→ FV_LEGAL_ENTITIES), and DOC_SEQUENCE_ID (→ FND_DOCUMENT_SEQUENCES) — Configure the payment profile, legal entity context, and document sequencing.
• PAYEE_PARTY_ID, PAYEE_PARTY_SITE_ID, SUPPLIER_SITE_ID, REMIT_TO_LOCATION_ID — Party and remittance routing attributes.
• PAYMENT_GROUPING_NUMBER, SETTLEMENT_PRIORITY, PAYMENT_DUE_DATE — Inputs to grouping logic that consolidates documents into a single payment.
• OBJECT_VERSION_NUMBER and the audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — Standard EBS concurrency and audit tracking; note their presence confirms that rows may be updated within a session.

Common Use Cases and Queries

The table is used almost exclusively by Oracle Payments internal concurrent programs during payment instruction build and formatting. Typical investigative queries suppress duplicates and restrict to the current session because the table is global temporary:

• Reconcile a staged payable against its persistent parent: SELECT g.* FROM iby.iby_docs_payable_gt g WHERE g.document_payable_id = :id joined to IBY_DOCS_PAYABLE_ALL.
• Report grouped payments: aggregate PAYMENT_AMOUNT by PAYMENT_GROUPING_NUMBER, PAYMENT_METHOD_CODE, and PAYMENT_CURRENCY_CODE.
• Diagnose missing payments by comparing expected source documents (via CALLING_APP_DOC_UNIQUE_REF1–5) to rows present in the GT.
• Validate document sequencing outcomes using DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE.

Related Objects

• IBY_DOCS_PAYABLE_ALL — the persistent parent, joined on DOCUMENT_PAYABLE_ID.
• IBY_ACCT_PMT_PROFILES_B — payment profile configuration, joined on PAYMENT_PROFILE_ID.
• FV_LEGAL_ENTITIES — legal entity context, joined on LEGAL_ENTITY_ID.
• FND_DOCUMENT_SEQUENCES — sequence assignment, joined on DOC_SEQUENCE_ID.
• IBY_PAY_SERVICE_REQUESTS and IBY_PAY_INSTRUCTIONS_ALL — downstream payment instruction and service request objects that consume staged rows.
• IBY_FD_PAYMENT_FORMAT_APIS — formatting routines that read GT rows to produce output.