Results for “vendgl_class”

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

Overview

The GMF_XLA_RCV_VENDOR_V view is a Process Manufacturing Financials (GMF) reporting and integration object owned by the APPS schema. It acts as a bridge between Oracle's receiving subledger and the Subledger Accounting (XLA) engine used to generate accounting entries. Specifically, this view joins receiving transactions, purchase order headers, vendor site information, and GMF receiving accounting transaction records to present a consolidated, denormalized view of vendor-related receiving accounting data.

The view exposes the receiving transaction identifier as RCV_TRANSACTION_ID, which is central to tracing a physical receipt from the receiving open interface through to its eventual accounting event. Because the view surfaces this column alongside the accounting transaction ID and vendor identifiers, it supports reconciliation between operational receiving activity and the corresponding journal entries posted by Subledger Accounting.

Within Oracle EBS 12.1.1 and 12.2.2, this object is typically consumed by GMF accounting extraction programs, custom reconciliation reports, and diagnostic queries that need to link a receipt to its vendor site and accounting event without navigating the underlying normalized tables.

Underlying Base Objects

The view is defined over a mix of synonyms, views, and a package. The documented referenced base objects are:

• PO_VENDOR_SITES_ALL (VIEW) — supplies VENDOR_SITE_ID (aliased as VENDOR_ID) and ATTRIBUTE1 (aliased as VENDGL_CLASS), the vendor GL classification.
• RCV_TRANSACTIONS (SYNONYM) — the core receiving transaction table, providing TRANSACTION_ID as RCV_TRANSACTION_ID and VENDOR_SITE_ID.
• PO_HEADERS_ALL (SYNONYM) — the purchase order headers, joined via PO_HEADER_ID.
• GMF_RCV_ACCOUNTING_TXNS (SYNONYM) — the GMF accounting transaction staging table, providing ACCOUNTING_TXN_ID as GRAT_ACCOUNTING_TXN_ID and EVENT_SOURCE_ID.
• FND_GLOBAL (PACKAGE) — the standard EBS package used for session context such as organization and user identity.

The join logic uses an NVL on the vendor site: VS.VENDOR_SITE_ID = NVL(RT.VENDOR_SITE_ID, POH.VENDOR_SITE_ID), meaning the receipt-level vendor site is preferred, falling back to the PO header's vendor site. This reflects the reality that a receipt line may or may not carry its own vendor site reference.

Key Columns

• VENDOR_ID — Derived from PO_VENDOR_SITES_ALL.VENDOR_SITE_ID; identifies the vendor site associated with the receipt or PO.
• VENDGL_CLASS — Mapped from the vendor site's ATTRIBUTE1; the vendor GL classification used for account derivation.
• GRAT_ACCOUNTING_TXN_ID — The accounting transaction identifier from GMF_RCV_ACCOUNTING_TXNS, linking the receipt to its Subledger Accounting event.
• RCV_TRANSACTION_ID — The receiving transaction identifier from RCV_TRANSACTIONS.TRANSACTION_ID, the operational key that ties the view to receipt activity.

Common Use Cases and Queries

A primary use case is reconciling a specific receipt to its accounting event. A query filtering on the receiving transaction ID returns the accounting transaction and vendor context:

• SELECT RCV_TRANSACTION_ID, GRAT_ACCOUNTING_TXN_ID, VENDOR_ID, VENDGL_CLASS FROM APPS.GMF_XLA_RCV_VENDOR_V WHERE RCV_TRANSACTION_ID = :p_transaction_id;

For batch reconciliation of accounting events to receipts, joining on the accounting transaction ID supports validating that every XLA event has a matching receipt.

Additional scenarios include vendor-level analysis of receiving accounting volume by GL class, and diagnostic investigation when a receipt fails to create an accounting entry, by comparing the view's population against expected receipt counts.