Search Results item




The PO_VENDOR_ITEMS_MST (PO_VNIT_MST) table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical repository for vendor item information within the Purchasing module. This table stores master data that links supplier-provided items with internal inventory items, facilitating procurement processes, supplier collaboration, and purchase order management. Below is a detailed technical and functional analysis of this table.

Table Overview

PO_VNIT_MST serves as the foundation for vendor item master data, enabling organizations to maintain a centralized record of items supplied by vendors. It acts as a cross-reference between internal item identifiers (e.g., INVENTORY_ITEM_ID and ORGANIZATION_ID) and vendor-specific item details (e.g., VENDOR_PRODUCT_NUM). This linkage is essential for automating procurement workflows, reducing manual data entry, and ensuring accuracy in purchase orders.

Key Columns and Relationships

  • VENDOR_ID: Foreign key to PO_VENDORS, identifying the supplier.
  • VENDOR_SITE_ID: Foreign key to PO_VENDOR_SITES_ALL, specifying the supplier location.
  • INVENTORY_ITEM_ID and ORGANIZATION_ID: Foreign keys to MTL_SYSTEM_ITEMS_B, linking to internal inventory items.
  • VENDOR_PRODUCT_NUM: Vendor’s unique identifier for the item (e.g., SKU or part number).
  • PRIMARY_UOM_CODE: Unit of measure (UOM) for the item, referencing MTL_UNITS_OF_MEASURE.
  • USER_ITEM_DESCRIPTION: Optional user-defined description overriding the default item description.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY: Standard Oracle audit columns.

Functional Significance

  1. Procurement Efficiency: Enables auto-population of item details in purchase orders, reducing errors.
  2. Supplier Collaboration: Facilitates electronic data interchange (EDI) by mapping vendor-specific identifiers to internal items.
  3. Price Negotiation: Supports vendor-specific pricing agreements stored in related tables like PO_VENDOR_ITEM_PRICES.
  4. Approval Workflows: Integrates with approval hierarchies by associating items with approved suppliers.

Integration Points

  • Inventory Management: Synchronizes with MTL_SYSTEM_ITEMS_B to ensure item consistency.
  • Purchasing Documents: Linked to PO_HEADERS_ALL and PO_LINES_ALL for PO generation.
  • Supplier Portal: Exposes vendor item data for self-service updates via Oracle iSupplier Portal.

Technical Considerations

  • Indexes: Key indexes include PO_VENDOR_ITEMS_MST_N1 (VENDOR_ID, VENDOR_SITE_ID) and PO_VENDOR_ITEMS_MST_U1 (unique constraint on VENDOR_ID, VENDOR_SITE_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID).
  • APIs: Custom integrations should use Oracle’s PL/SQL APIs (e.g., PO_VENDOR_ITEMS_PKG) to avoid direct DML.
  • Data Volume: Large implementations may require partitioning strategies for performance optimization.

Common Use Cases

  • Item Master Maintenance: Adding or updating vendor item cross-references via Oracle Forms or web ADI.
  • Reporting: Generating supplier performance reports by joining with PO_VENDORS and PO_VENDOR_SITES_ALL.
  • Data Migration: Legacy system data loads during implementations require careful mapping of vendor item attributes.

Conclusion

PO_VNIT_MST is a cornerstone table in Oracle EBS Purchasing, bridging internal inventory systems with supplier data. Its design supports scalability, auditability, and integration with broader supply chain processes. Proper utilization of this table enhances procurement accuracy, streamlines supplier interactions, and ensures data integrity across the procure-to-pay lifecycle.