Plex and JAGGAER integration

What moves between them

Purchase orders and suppliers flow from Plex into JAGGAER on a polling schedule aligned with manufacturing demand cycles. Plex purchase order releases, GL accounts, and supplier information are read and mapped to JAGGAER contract items and vendor records so procurement teams have manufacturing context for each PO. Invoice data flows from Plex into JAGGAER for reconciliation against received goods. The sync runs on a configurable interval to capture changes without overwhelming either API.

How ml-connector handles it

ml-connector stores OAuth2 client credentials for both systems encrypted and refreshes bearer tokens as needed on each API call. Because Plex offers polling only, ml-connector polls the Plex REST API on a configurable interval, filtering by modified_date to capture new and changed purchase orders, suppliers, and invoices. For each Plex purchase order, ml-connector maps the supplier ID and GL account to matching JAGGAER vendor and contract records, handling mismatches with an alert so procurement can resolve the vendor mapping. JAGGAER rate limits are not publicly documented, so ml-connector uses exponential backoff on HTTP 429 responses. Every record carries an audit trail and a unique external reference so duplicate detection works across retries. Plex company code (PCN) is required for SOAP calls when legacy datasources are used.

A real-world example

A mid-sized automotive supplier runs Plex ERP for manufacturing operations and inventory across three plants, and uses JAGGAER to manage supplier contracts and source parts from Tier 1 and Tier 2 suppliers. Before the integration, procurement planners manually reviewed Plex purchase order reports and entered them into JAGGAER by hand or via email, losing visibility into which orders were tied to actual production demand. Supplier quality and delivery history in JAGGAER could not be linked to the orders in Plex. With Plex and JAGGAER connected, each manufacturing purchase order appears in JAGGAER within minutes, procurement teams see the GL account and cost center context from Plex, and supplier performance metrics in JAGGAER are now tied to the orders that drove them.

What you can do

• •Sync Plex purchase orders and releases into JAGGAER so procurement teams see manufacturing demand in real time.
• •Map Plex suppliers and GL accounts to JAGGAER vendor and contract records, maintaining referential integrity across both systems.
• •Pull Plex invoice data and push it into JAGGAER for invoice-to-PO matching and reconciliation.
• •Authenticate both systems via OAuth2 client credentials, with automatic token refresh on each request.
• •Poll Plex on a configurable schedule with exponential backoff and a full audit trail on every record.

Questions

Which direction do purchase orders flow between Plex and JAGGAER?

Purchase orders flow from Plex into JAGGAER. Plex is the source of manufacturing demand, and JAGGAER manages the procurement and supplier contracts against that demand. Invoices can flow in the same direction for reconciliation, but JAGGAER does not push order confirmations back to Plex.

How does ml-connector handle the fact that Plex has no webhooks?

ml-connector polls the Plex REST API on a configurable interval, filtering by modified_date to capture new and changed purchase orders, suppliers, and invoices. The polling schedule can be aligned with manufacturing demand cycles, typically every 5-15 minutes for real-time visibility without overwhelming the API.

What happens if a Plex supplier or GL account does not exist in JAGGAER?

ml-connector checks for matching vendor and contract records in JAGGAER before syncing the PO. If a supplier or GL account is missing, ml-connector logs an alert so procurement can resolve the mapping. The record is held pending the fix and retried automatically.