Results for “fax_no”

50+ results




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

Overview

PO_VEND_MST is the vendor master table owned by the GML schema (Process Manufacturing Logistics) in Oracle EBS 12.1.1 and 12.2.2. It stores the authoritative vendor and supplier records used throughout Oracle Process Manufacturing and its adjacent purchasing, receiving, quality, and financial modules. Each row represents a single vendor entity, identified internally by a surrogate VENDOR_ID but externally by the combination of company (CO_CODE) and vendor number (VENDOR_NO). Because supply, procurement, receiving, invoicing, and quality-testing transactions all ultimately point back to a vendor, this table functions as a foundational reference object rather than a transactional one.

Under the heuristic Data Vault classification mined from the foreign-key topology, PO_VEND_MST is best modeled as a hub: it defines business keys and their associated descriptive context, and it is referenced by a large number of downstream detail tables. Analysts building a Data Vault representation should treat it as the vendor hub, with its derived descriptive fields potentially split into one or more satellites.

Key Information Stored

The table contains 82 documented columns. The most operationally significant are:

Common Use Cases and Queries

Typical usage includes vendor listing and validation reports, procurement spend analysis, receiving and return reconciliation, and quality specification lookups. A standard pattern joins PO_VEND_MST to PO_ORDR_HDR on VENDOR_ID to report purchase orders by vendor:

SELECT v.VENDOR_NO, v.VENDOR_NAME, h.ORDER_NUMBER, h.ORDER_DATE
FROM   GML.PO_VEND_MST v, GML.PO_ORDR_HDR h
WHERE  v.VENDOR_ID = h.PAYVEND_ID
  AND  v.CO_CODE   = :co_code
  AND  v.INACTIVE_IND = 'N';

Because vendors may be referenced as pay vendors or ship vendors, joins must use the correct FK column (PAYVEND_ID vs. SHIPVEND_ID). Queries should filter on ACTIVE flags and honor DELETE_MARK. For application-tier access, the corresponding Oracle EBS Forms and concurrent programs (e.g., vendor validation, receiving programs) use this table's primary key internally, so direct DML should be confined to supported APIs and imports.

Related Objects

PO_VEND_MST is central to a dense web of foreign keys. Significant related objects include:

  • PO_ORDR_HDR / PO_ORDR_DTL — purchase orders reference the vendor via PAYVEND_ID and SHIPVEND_ID.
  • PO_RECV_HDR and PO_RECV_DTL — receiving records reference vendors for both payment and shipment.
  • PO_RTRN_HDR — returns reference vendors through RETURN_VENDOR_ID.
  • PO_VNIT_MST — vendor item master links items to vendors via VENDOR_ID.
  • PO_VEND_ASC — vendor association table linking associated vendors.
  • SY_ADDR_MST, SY_ORGN_MST — addresses and organization units.
  • GL_CURR_MST, OP_TERM_MST, OP_FRGT_MTH — currency, terms, and freight method reference data.
  • QC_SPEC_MST, QC_SMPL_MST, QC_RSLT_MST — quality specifications, samples, and results all reference VENDOR_ID.

Together these relationships confirm PO_VEND_MST's role as the canonical vendor hub within the Process Manufacturing Logistics data model.