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:
- VENDOR_ID — surrogate primary key (index PO_VEND_MST_PK), used by all foreign-key references.
- CO_CODE and VENDOR_NO — the composite business key defined by index PO_VEND_MSTI1; these two columns uniquely identify a vendor within a company.
- VENDOR_NAME, REMIT_NAME, ALTVEND_NO, VENDSORT_NO — descriptive and alternate identifiers; index PO_VEND_MSTI2 provides a secondary lookup path over VENDOR_NO, VENDSORT_NO, VENDOR_NAME, and control flags.
- ADDR_ID and MAILADDR_ID — foreign keys to SY_ADDR_MST, holding the primary and mailing addresses.
- DEFAULT_CURRENCY — references GL_CURR_MST; governs the vendor's default transaction currency.
- TERMS_CODE and FRTBILL_MTHD — payment terms and freight billing method, referencing OP_TERM_MST and OP_FRGT_MTH.
- VEND_CLASS, VENDGL_CLASS, VENDTRADE_CLASS — vendor classification codes used for reporting, GL mapping, and trade categorization.
- APPROVED_IND, INACTIVE_IND, DELETE_MARK — lifecycle and status-control flags.
- TEXT_CODE — link to PO_TEXT_HDR for standard notes.
- ATTRIBUTE1 through ATTRIBUTE30 and ATTRIBUTE_CATEGORY — the standard Oracle EBS descriptive flexfield columns.
- Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID.
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.
-
Vendor master.
-
Customer master.
-
View: OP_CUST_MSTI2_VW1 12.1.1
Customer Master table view.
APPS.OP_CUST_MSTI2_VW1·↳ FND_PROFILE·↳ OP_CUST_MST·Explore GML module →
-
View: OP_CUST_MSTI2_VW1 12.2.2
Customer Master table view.
APPS.OP_CUST_MSTI2_VW1·↳ FND_PROFILE·↳ OP_CUST_MST·Explore GML module →
-
View: OP_CUST_MST_V 12.1.1
View of op_cust_mst for OPM OF customers
APPS.OP_CUST_MST_V·↳ FND_PROFILE·↳ GL_PLCY_MST·↳ HZ_CUST_ACCOUNTS·Explore GML module →
-
View: PO_VEND_MSTI2_VW1 12.1.1
View on vendor master table.
-
View: PO_VEND_MSTI2_VW1 12.2.2
View on vendor master table.
-
Table: PO_VEND_MST_INT 12.2.2
This table is not used in 11i.
-
View: OPM_CUSTOMERS 12.2.2
Used for OPM customer synchronization
APPS.OPM_CUSTOMERS·↳ FND_PROFILE·↳ GL_PLCY_MST·↳ GMF_AR_CUSTOMER·Explore GMF module →
-
View: OPM_CUSTOMERS 12.1.1
Used for OPM customer synchronization
APPS.OPM_CUSTOMERS·↳ FND_PROFILE·↳ GL_PLCY_MST·↳ GMF_AR_CUSTOMER·Explore GMF module →
-
View: OP_CUST_MST_V 12.2.2
View of op_cust_mst for OPM OF customers
APPS.OP_CUST_MST_V·↳ FND_PROFILE·↳ GL_PLCY_MST·↳ HZ_CUST_ACCOUNTS·Explore GML module →
-
Vendor master.
-
Table: OP_CUST_MST_INT 12.2.2
Customer Interface table for data transferred from Oracle Receivables into the OPM customer master.
-
Table: PO_VEND_MST_INT 12.1.1
This table is not used in 11i.
-
Customer master.
-
Table: OP_CUST_MST_INT 12.1.1
Customer Interface table for data transferred from Oracle Receivables into the OPM customer master.
-
VIEW: GML.PO_VEND_MST# 12.2.2
-
VIEW: GML.PO_VEND_MST_INT# 12.2.2
-
VIEW: GML.OP_CUST_MST_OPM# 12.2.2
-
VIEW: GML.OP_CUST_MST_INT# 12.2.2
-
VIEW: APPS.OP_CUST_MSTI2_VW1 12.2.2
-
VIEW: APPS.OP_CUST_MSTI2_VW1 12.1.1
-
VIEW: GML.PO_VEND_MST# 12.2.2
-
VIEW: APPS.PO_VEND_MSTI2_VW1 12.1.1
-
VIEW: APPS.PO_VEND_MSTI2_VW1 12.2.2
-
VIEW: GML.OP_CUST_MST_OPM# 12.2.2
-
VIEW: APPS.PO_VEND_MSTI2_VW1 12.1.1
-
VIEW: APPS.PO_VEND_MSTI2_VW1 12.2.2
-
VIEW: GML.PO_VEND_MST_INT# 12.2.2
-
VIEW: APPS.OP_CUST_MSTI2_VW1 12.2.2
-
VIEW: APPS.OP_CUST_MSTI2_VW1 12.1.1
-
VIEW: GML.OP_CUST_MST_INT# 12.2.2
-
VIEW: APPS.OPM_CUSTOMERS 12.2.2
-
TABLE: GML.PO_VEND_MST_INT 12.2.2
-
TABLE: GML.PO_VEND_MST_INT 12.1.1
-
VIEW: APPS.OPM_CUSTOMERS 12.1.1
-
TABLE: GML.PO_VEND_MST 12.1.1
-
TABLE: GML.PO_VEND_MST 12.2.2
-
VIEW: APPS.OPM_CUSTOMERS 12.2.2
-
VIEW: APPS.OPM_CUSTOMERS 12.1.1
-
TABLE: GML.OP_CUST_MST_INT 12.2.2
-
TABLE: GML.OP_CUST_MST_INT 12.1.1
-
VIEW: APPS.OP_CUST_MST_V 12.2.2
-
VIEW: APPS.OP_CUST_MST_V 12.1.1
-
TABLE: GML.OP_CUST_MST_OPM 12.2.2
-
TABLE: GML.OP_CUST_MST_OPM 12.1.1