Search Results splc_code

Overview

PO_VEND_MSTI2_VW1 is a read-only database view owned by the APPS schema in Oracle E-Business Suite, validated and present in both release 12.1.1 and 12.2.2. It belongs to the Process Manufacturing Logistics (GML) product family and is documented as a "view on vendor master table." Functionally, it presents a projection of supplier header information sourced from the legacy Process Manufacturing vendor master, exposing a deliberately flat structure suitable for reporting, interfaces, and integration programs that need supplier attributes without joining the broader Oracle Payables (AP) supplier model.

The view is especially relevant to consumers searching for the MAILADDR_ID attribute, which it exposes directly alongside the primary ADDR_ID. This allows callers to retrieve the mailing address identifier associated with a supplier record in a single, stable query against the GML supplier data, rather than navigating the multi-table relationship between supplier headers, supplier sites, and address records in the standard AP tables. Because it is a simple, single-source projection, it carries no procedural logic, no filters on INACTIVE_IND or DELETE_MARK, and no business-rule transformation; all filtering and interpretation remain the responsibility of the calling application.

Underlying Base Objects

Per the ETRM metadata for 12.2.2, the view is defined over a single referenced base object: the synonym PO_VEND_MST. The view is a straightforward SELECT of an explicit column list from that synonym, with no joins, unions, or aggregation. Every column in the view carries the same name as the corresponding column in the source, and no column aliases or expressions are applied.

Because the sole dependency is a synonym rather than a physical table, the view is loosely coupled to the underlying storage; the synonym resolves to the GML vendor master object in the Process Manufacturing schema. This dependency structure means the view inherits the partitioning, indexing, and security characteristics of the base object, and it remains valid only while the source columns it enumerates are present. Deployments that migrate supplier data to the standard Oracle Payables model (AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, and related address tables) will find that PO_VEND_MSTI2_VW1 continues to reflect the GML master rather than the AP supplier model.

Key Columns

The view exposes the full vendor master column set, including the following high-value attributes:

• VENDOR_ID — Primary identifier of the supplier record; the principal join key to other GML and AP objects.
• VENDOR_NO and ALTVEND_NO — Supplier number and any alternate vendor number used for cross-reference.
• VENDOR_NAME — Supplier name as held in the vendor master.
• ADDR_ID — Identifier of the supplier's primary address record.
• MAILADDR_ID — Identifier of the supplier's mailing address, the attribute that most frequently drives searches against this view.
• REMIT_NAME — Remit-to name used on payment documents.
• PHONE_NO, FAX_NO, TELEX_NO — Contact communication attributes.
• DEFAULT_CURRENCY and CHANGE_CURRENCY — Default transaction currency and currency-change indicator.
• TERMS_CODE and TERMS_VARY — Payment terms and the terms-variance flag.
• APPROVED_IND, INACTIVE_IND, SHIP_IND, PAYMENT_IND, TAXABLE_IND, INFORM_GOVT — Status and control flags governing purchasing, payment, shipping, tax, and government reporting behavior.
• VEND_CLASS, VENDTRADE_CLASS, VENDGL_CLASS — Supplier classification values for reporting and accounting derivation.
• CREDIT_LIMIT, MIN_PURCHASE, BUS_AMOUNT — Commercial limits and business volume attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — The descriptor flexfield used for client-specific supplier attributes.
• DELETE_MARK and TRANS_CNT — Deletion flag and transaction counter maintained by the GML data model.

Common Use Cases and Queries

The most common use is resolving mailing address information for a supplier, particularly where integration code expects the GML vendor master rather than the AP supplier model. A typical lookup by vendor number is:

• SELECT vendor_id, vendor_no, vendor_name, addr_id, mailaddr_id FROM apps.po_vend_msti2_vw1 WHERE vendor_no = :p_vendor_no;
• SELECT vendor_id, vendor_name, mailaddr_id FROM apps.po_vend_msti2_vw1 WHERE mailaddr_id = :p_mailaddr_id;
• SELECT vendor_no, vendor_name, default_currency, terms_code, credit_limit FROM apps.po_vend_msti2_vw1 WHERE approved_ind = 'Y' AND NVL(inactive_ind, 'N') = 'N';

Because the view applies no filtering, queries intended for active supplier reporting should explicitly test INACTIVE_IND, APPROVED_IND, and DELETE_MARK. When MAILADDR_ID is populated, it should be joined to the appropriate address table to obtain street, city, and postal details; when it is null, consumers should fall back to ADDR_ID. Performance is equivalent to querying the base synonym directly, so predicates on VENDOR_ID, VENDOR_NO, or MAILADDR_ID benefit from whichever indexes exist on the underlying GML vendor master object.