Results for “vend_class”

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

Overview

PO_VEND_CLS is the vendor class definition table within the Oracle E-Business Suite Process Manufacturing Logistics (GML) product family. It stores the master list of vendor classifications — the discrete category codes used to group suppliers for reporting, approval routing, procurement analysis, and defaulting purposes across process manufacturing operations. The table is owned by the GML schema, is documented as VALID and available in both Oracle EBS 12.1.1 and 12.2.2, and contains ten documented columns in the ETRM 12.2.2 physical schema.

From a Data Vault modeling perspective, the mined relationship structure classifies PO_VEND_CLS as satellite-leaning. This heuristic suggests that the table behaves primarily as a descriptive attribute repository attached to a business concept rather than as an independent hub. The single-column primary key PO_VEND_CLS_PK, defined on VEND_CLASS, functions as the business key, while the remaining columns carry descriptive and auditing attributes. The table does not reference the vendor master directly; instead, PO_VEND_MST references PO_VEND_CLS through the VEND_CLASS foreign key column, meaning vendor class assignment is enforced from the vendor master side. PO_VEND_CLS also carries a foreign key from TEXT_CODE to PO_TEXT_HDR, allowing a text header to be associated with a vendor class definition.

Key Information Stored

The columns documented for this table fall into three groups: classification data, descriptive data, and standard Oracle audit and concurrency columns.

• VEND_CLASS — The primary key and business-key candidate (unique index PO_VEND_CLS_PK). This is the class code assigned to vendors and referenced by PO_VEND_MST.VEND_CLASS.
• VEND_CLASS_DESC — The descriptive name or label associated with the class code, used for display and reporting.
• TEXT_CODE — Foreign key referencing PO_TEXT_HDR, linking the vendor class to a reusable text block for additional notes or instructions.
• TRANS_CNT — Transaction counter used for Oracle concurrency and version control.
• DELETE_MARK — Soft-delete indicator; rows are logically deactivated rather than physically removed.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle audit and session tracking columns.

The distinction between the surrogate primary key and business-key candidate is nominal here: because PO_VEND_CLS_PK is itself defined on VEND_CLASS, the two coincide. VEND_CLASS is therefore both the unique identifier and the natural business key presented to users.

Common Use Cases and Queries

Typical usage centers on validation, lookup, and reporting. A common validation query resolves a vendor class description before insertion into PO_VEND_MST:

• SELECT VEND_CLASS, VEND_CLASS_DESC FROM GML.PO_VEND_CLS WHERE DELETE_MARK = 0; — standard lookup list for forms and integrations.
• SELECT v.VENDOR_NAME, m.VEND_CLASS, c.VEND_CLASS_DESC FROM PO_VEND_MST m, PO_VEND_CLS c WHERE m.VEND_CLASS = c.VEND_CLASS AND c.DELETE_MARK = 0; — vendor counts grouped by class for spend or supplier segmentation reporting.
• Joining TEXT_CODE to PO_TEXT_HDR to retrieve class-level notes during vendor maintenance or approval workflows.
• Feeding class-based defaulting rules into purchasing and planning reports in Process Manufacturing Logistics.

Because PO_VEND_MST enforces the foreign key, any vendor class used in vendor setup must exist as an active row in PO_VEND_CLS with DELETE_MARK set to 0. This makes the table a critical reference for data migration and interface validation, particularly when loading vendor records from legacy systems.

Related Objects

The documented relationships identify the primary dependent and referenced objects:

• PO_VEND_MST — The vendor master table; references PO_VEND_CLS via VEND_CLASS. This is the principal consumer of vendor class definitions and the object most often joined to PO_VEND_CLS.
• PO_TEXT_HDR — Text header table; referenced by PO_VEND_CLS.TEXT_CODE. Provides additional text storage associated with a class.
• PO_VEND_CLS_PK — The primary key constraint enforcing uniqueness of VEND_CLASS.

In practice, vendor class is exposed through purchasing and supplier inquiry forms and concurrent programs that draw on PO_VEND_MST, making PO_VEND_CLS an indirect participant in supplier reporting, approval hierarchies, and procurement analytics in both Oracle EBS 12.1.1 and 12.2.2.