Results for “po_vgld_cls”

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

Overview

PO_VGLD_CLS is a GML (Process Manufacturing Logistics) setup table that stores vendor GL (General Ledger) class definitions. In Oracle EBS 12.1.1 and 12.2.2, it is owned by the GML schema and holds the master list of vendor GL classes, which are used to categorize vendors for accounting and GL account determination purposes. Vendor GL classes act as a grouping mechanism that drives default accounting rules and account mapping for vendor transactions, particularly in the Process Manufacturing (OPM) financials integration.

Based on the mined foreign key relationships, the table is heuristic-classified as hub-leaning in Data Vault terms. This suggests modeling PO_VGLD_CLS as a hub entity, since its primary key, VENDGL_CLASS, is a business identifier referenced by other tables via foreign keys rather than a transactional or descriptive attribute set. That classification is a modeling suggestion; the table also carries descriptive and audit attributes typical of a satellite.

Key Information Stored

The table contains ten documented columns. The most important are:

• VENDGL_CLASS — The primary key (PO_VGLD_CLS_PK) and business-key candidate. It uniquely identifies each vendor GL class and is the column referenced by dependent tables.
• VENDGL_CLASS_DESC — The descriptive name or text label for the vendor GL class, used for display and reporting.
• TEXT_CODE — A foreign key to PO_TEXT_HDR, linking the GL class to a text/note header for extended descriptive content.
• TRANS_CNT — A transaction count or control column, typically used for concurrency or processing reference.
• DELETE_MARK — The soft-delete flag indicating whether the class is logically active or removed.

Standard EBS audit columns are also present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The surrogate primary key is PO_VGLD_CLS_PK, built on the VENDGL_CLASS business key, which the metadata documents as the sole unique index and business-key candidate.

Common Use Cases and Queries

Typical uses include validating vendor GL class setup, driving GL account mapping defaults, and reporting on vendor classification. A common lookup retrieves active classes:

SELECT vgld_class, vgld_class_desc
FROM   gml.po_vgld_cls
WHERE  delete_mark = 0
ORDER  BY vgld_class;

To review which vendors belong to a class, join against PO_VEND_MST:

SELECT v.vendor_name, v.vendgl_class
FROM   gml.po_vend_mst v
WHERE  v.vendgl_class = :p_class;

To inspect associated GL account mapping, join GL_ACCT_MAP on VENDGL_CLASS. Reporting scenarios include setup audits, GL class usage analysis, and validating that every mapped class has a corresponding account rule.

Related Objects

• GL_ACCT_MAP — references PO_VGLD_CLS.VENDGL_CLASS via GL_ACCT_MAP.VENDGL_CLASS; defines GL account mappings per class.
• PO_VEND_MST — references PO_VGLD_CLS.VENDGL_CLASS via PO_VEND_MST.VENDGL_CLASS; the vendor master storing vendor-to-class assignment.
• PO_TEXT_HDR — referenced by PO_VGLD_CLS.TEXT_CODE; supplies extended text for the class.

These three tables constitute the documented dependency neighborhood for PO_VGLD_CLS in the GML schema.