Results for “co_code”

50+ results




Overview
Explore in AI Chat

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

Overview

PO_VEND_MST_V1 is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GML (Process Manufacturing Logistics) product family. As its name and the ETRM description indicate, it is a view on the vendor master table and presents a deliberately minimal, de-normalized projection of supplier data. Rather than exposing the full vendor record, the view surfaces only two columns — VENDOR_NO and CO_CODE — restricted to records that have not been marked for deletion. The "V1" suffix denotes that this is an Oracle-supplied, versioned interface object, signaling that its structure is intended to remain stable for downstream consumers.

Its role in EBS reporting and integration is that of a lightweight supplier reference list. Because it filters on DELETE_MARK = 0, it automatically excludes soft-deleted suppliers, sparing report authors and interface developers from having to replicate that predicate. It is commonly consulted in process manufacturing environments where a compact vendor-number-to-company-code mapping is required. The object carries a VALID status in the 12.2.2 metadata, confirming it is compiled and available in a standard installation. The search term "vendor_no" maps directly to the view's primary exposed column, reflecting the most common reason users locate this object.

Underlying Base Objects

The documented base object is PO_VEND_MST, referenced as a synonym in the 12.2.2 metadata. The view text supplied by ETRM is concise:

  • SELECT DISTINCT VENDOR_NO, CO_CODE FROM PO_VEND_MST WHERE DELETE_MARK = 0

This reveals three defining characteristics. First, the projection is limited to exactly two columns from the underlying vendor master. Second, the DISTINCT keyword collapses duplicate rows, meaning the view returns unique VENDOR_NO / CO_CODE combinations rather than one row per vendor record. Third, the WHERE clause enforces a soft-delete filter: rows with a non-zero DELETE_MARK are suppressed. As a read-only view it carries no DML capability; it cannot be used to insert, update, or delete vendor data. Any change to the base vendor master is reflected automatically when the view is queried.

Because PO_VEND_MST is presented as a synonym, the view resolves to the physical vendor master table through that synonym at runtime. In GML installations, this structure supports the process manufacturing vendor model, which may differ from the standard Oracle Payables supplier tables (AP_SUPPLIERS, PO_VENDORS).

Key Columns

  • VENDOR_NO — The vendor number, the primary identifier exposed by the view and the column that matches the user's "vendor_no" search. It is the human-facing supplier key used across transactions, reports, and interfaces.
  • CO_CODE — The company code, indicating the operating company or legal entity context to which the vendor number belongs. Because the DISTINCT clause operates over both columns, a single vendor number can legitimately appear multiple times when it is associated with more than one company code.

No descriptive attributes — such as vendor name, status, or address — are exposed. Consumers requiring those fields must join back to the base vendor master or to other supplier views.

Common Use Cases and Queries

Typical uses include populating supplier value lists in process manufacturing reports, validating vendor numbers during data migration or interface loads, and producing a deduplicated vendor/company mapping for reconciliation.

  • Listing all active vendors: SELECT vendor_no, co_code FROM apps.po_vend_mst_v1 ORDER BY vendor_no;
  • Checking whether a specific vendor number exists: SELECT vendor_no, co_code FROM apps.po_vend_mst_v1 WHERE vendor_no = :p_vendor_no;
  • Filtering by company: SELECT vendor_no FROM apps.po_vend_mst_v1 WHERE co_code = :p_co_code;
  • Counting active vendors: SELECT COUNT(*) FROM apps.po_vend_mst_v1;

Because the view is read-only and filtered, it is safe for query-only integration and reporting. Where richer supplier detail is required, join VENDOR_NO to the underlying vendor master tables.