Skip to main content
Share / Export

PO Vendor Materials

Company Tracker action: implementation-setup-po-vendor-materials Milestone: Purchase Order / Module Setup (milestone_id=11, core_milestone_id=2) Order: 5 Estimated duration: 0.5–1 hours Typical owner: Purchasing / Controller

Purpose​

Map internal material IDs to each vendor’s material ID (and optional vendor unit cost) so POs show the vendor’s code and pricing.

Prerequisites​

  • Internal material / catalog IDs exist for items that need a vendor cross-reference.
  • Vendor list of their material codes (and vendor unit costs when they differ from standard).

Vista configuration article​

See the detailed Vista guide:

Configuring PO Vendor Materials

Field meanings and form steps live there. Do not restate them on this page.

Implementation guidance​

  • Vendor material ID: cross-reference so if internally the item is material 1000 but the vendor calls it ABCD, the PO can show the vendor’s code (not only the internal code).
  • Unit cost: optional override when the vendor’s unit cost differs from the standard internal unit cost — use the vendor-specific cost on the PO.
  • Decide / load: which vendors/items need cross-refs at go-live (often high-volume or mis-matched catalogs); load those maps. Skip/hide if the client never prints vendor part numbers or vendor-specific costs.
  • Accept means Purchasing confirms a sample PO shows the vendor material ID / cost as expected.

Tips and gotchas​

  • Solves “our ID vs their ID” on the PO document.
  • Vendor unit cost is for when standard cost is wrong for that vendor — do not load every item unless needed.
  • Not a substitute for IN item master setup.

Done when​

  • Either: vendor materials N/A / hidden, or
  • Go-live vendor↔internal maps (and needed vendor costs) are loaded and accepted.