Oracle PeopleSoft and UPS integration

What moves between them

Shipment creation flows from Oracle PeopleSoft into UPS. Purchase orders and requisitions in Oracle PeopleSoft are mapped to UPS shipments, with line items, dimensions, weights, and addresses extracted from Oracle PeopleSoft vendor and item master records and sent to UPS via the shipment creation endpoint. Tracking status flows back into Oracle PeopleSoft via UPS Track Alert subscriptions, which push delivery events every 14 days. ml-connector also polls Quantum View periodically to catch tracking updates in case Track Alert subscriptions lapse.

How ml-connector handles it

ml-connector stores OAuth2 credentials for both systems encrypted. On the Oracle PeopleSoft side, it accepts HTTP Basic Auth or OAuth2 bearer token and polls purchase orders and requisitions using date-range filters to avoid missing records. For each new shipment request, ml-connector extracts the ship-from and ship-to addresses, dimensions, and weight from Oracle PeopleSoft entity references and sends the shipment to UPS. UPS OAuth2 tokens are refreshed when they expire (every 4 hours), and ml-connector respects the 250 token request daily limit by reusing tokens across multiple shipment calls. UPS Track Alert subscriptions are renewed before expiry to ensure tracking updates continue flowing back into Oracle PeopleSoft. Address validation happens in UPS before shipment creation to catch mismatches. Every shipment and tracking update carries a full audit trail so failed calls can be replayed.

A real-world example

A distribution company uses Oracle PeopleSoft to manage purchase orders from suppliers and ship products to customers. Before the integration, the logistics team created shipments in UPS manually by copying addresses and weights from Oracle PeopleSoft purchase orders, then manually updated Oracle PeopleSoft with delivery status when packages arrived. With Oracle PeopleSoft and UPS connected, each new purchase order in Oracle PeopleSoft automatically creates a shipment in UPS with the correct addresses, weight, and dimensions. Tracking updates flow back into Oracle PeopleSoft as they happen, so the logistics team can see delivery status without switching between systems. The manual keying step is eliminated and shipments ship faster.

What you can do

• •Create UPS shipments from Oracle PeopleSoft purchase orders and requisitions, with addresses, dimensions, and weights from vendor and item master records.
• •Map Oracle PeopleSoft line items to UPS packages and validate addresses in UPS before shipment creation.
• •Receive UPS Track Alert push notifications and Quantum View polling data and update Oracle PeopleSoft with delivery status and tracking events.
• •Authenticate Oracle PeopleSoft with HTTP Basic Auth or OAuth2 bearer token, and UPS with OAuth2 client credentials, managing token refresh and subscription renewal.
• •Poll Oracle PeopleSoft on a schedule with date-range filters to catch new shipment requests, and maintain a full audit trail on every shipment and tracking update.

Questions

Which direction does data move between Oracle PeopleSoft and UPS?

Shipment creation flows from Oracle PeopleSoft into UPS. Purchase orders and requisitions in Oracle PeopleSoft are mapped to UPS shipments. Tracking status flows back from UPS into Oracle PeopleSoft via UPS Track Alert subscriptions and Quantum View polling so your team can see delivery status without switching systems.

How does the integration handle Oracle PeopleSoft's lack of webhooks and self-hosted architecture?

ml-connector polls Oracle PeopleSoft using date-range filters to read new purchase orders and requisitions on a schedule. Because each Oracle PeopleSoft customer has a unique hostname and port, ml-connector accepts the full base URL for each customer's instance. Polling ensures no shipment requests are missed even if a webhook subscription cannot be configured.

What happens if a UPS Track Alert subscription expires or a shipment address is invalid?

UPS Track Alert subscriptions expire after 14 days and must be renewed. ml-connector renews subscriptions before expiry to prevent tracking updates from stopping. Before creating a shipment, ml-connector validates the address in UPS. If validation fails, the shipment is not created and an alert is logged for manual review.