Search Results po_vend_msti1




Overview
Explore in AI Chat

Overview

The PO_VEND_MST table is the central vendor master data repository within the GML (Process Manufacturing Logistics) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the system of record for all supplier entities, storing comprehensive information required for procurement, accounts payable, and logistics operations. Its role is foundational, as vendor data from this table integrates with core purchasing, receiving, and financial processes, enabling transaction processing, payment management, and supply chain analytics. The table's design supports multi-organization structures through its CO_CODE column and maintains data integrity through defined primary and foreign key relationships.

Key Information Stored

The table's structure is defined by several key columns that uniquely identify and describe a vendor. The primary identifier is VENDOR_ID, which serves as the system-generated primary key (PO_VEND_MST_PK). Business-facing identifiers include VENDOR_NO (vendor number) and VENDOR_NAME. The table enforces business uniqueness through two additional primary keys: one on the combination of CO_CODE and VENDOR_NO (PO_VEND_MSTI1), and another on VENDOR_NO, VENDSORT_NO, VENDOR_NAME, CO_CODE, INACTIVE_IND, and DELETE_MARK (PO_VEND_MSTI2). Critical descriptive and control columns include CO_CODE (company/organization), INACTIVE_IND, DELETE_MARK for soft-delete functionality, ADDR_ID and MAILADDR_ID linking to the SY_ADDR_MST table for addresses, and various classification codes (VEND_CLASS, VENDGL_CLASS, VENDTRADE_CLASS). It also stores transactional defaults like DEFAULT_CURRENCY, TERMS_CODE, and FRTBILL_MTHD (freight billing method).

Common Use Cases and Queries

This table is central to numerous operational and reporting activities. Common use cases include vendor lookup for purchase order creation, validation of vendor status during goods receipt, and supplier performance reporting. A typical query involves joining with address and organization tables to generate a comprehensive vendor list for a specific operating unit. For example, to retrieve active vendors with their primary address, one might use:

  • SELECT v.VENDOR_NO, v.VENDOR_NAME, a.ADDRESS_LINE1, a.CITY FROM GML.PO_VEND_MST v JOIN APPS.SY_ADDR_MST a ON v.ADDR_ID = a.ADDR_ID WHERE v.CO_CODE = :p_org_id AND v.INACTIVE_IND = 'N' AND v.DELETE_MARK = 0;

Another common pattern is validating a vendor's existence and status before creating a purchase order header, ensuring the PAYVEND_ID or SHIPVEND_ID references a valid, active record in PO_VEND_MST.

Related Objects

PO_VEND_MST has extensive relationships, acting as a parent table for numerous transactional and setup entities. Key documented foreign key relationships include: