Oracle PeopleSoft and FedEx integration

What moves between them

The main flow runs from Oracle PeopleSoft into FedEx. Purchase order and shipment data from PeopleSoft are polled on a schedule and sent to FedEx to create outbound shipment labels, request rate quotes, and manage freight LTL shipments. Tracking data flows back from FedEx into PeopleSoft so receiving staff can monitor in-transit packages and confirm receipt. Address and vendor data are aligned in both directions to ensure shipment labels match PeopleSoft's master vendor and customer records.

How ml-connector handles it

ml-connector stores PeopleSoft credentials encrypted and connects to each customer's unique hostname using HTTP Basic Auth or OAuth2 Bearer token, depending on the PeopleTools version. It polls purchase orders and requisitions from the PeopleSoft REST endpoints at a frequency you control, typically daily or on-demand after order entry. For FedEx, ml-connector caches the OAuth2 Bearer token for the full 1-hour TTL to stay well below the 3 tokens per second limit, and it batches tracking queries to stay under FedEx's rate limit of 1,400 transactions per 10 seconds. When a PeopleSoft shipment is ready, ml-connector calls the FedEx Ship API with the address, weight, and service type from PeopleSoft, receives the tracking number and label, and stores it back in PeopleSoft's requisition or receiving record. If FedEx returns a rate limit (429) or 403 due to token rate-limit exhaustion, ml-connector backs off and retries. Every shipment and tracking poll carries a full audit trail, and failed calls can be replayed after credentials or configuration are fixed.

A real-world example

A mid-sized manufacturing company runs Oracle PeopleSoft on-premise for procurement and inventory. They ship goods to customers and receive material from suppliers daily. Before the integration, the procurement team entered purchase orders into PeopleSoft, printed them, then manually created shipments in the FedEx portal, typed addresses and weights, and paid for postage. Receiving staff asked customers for tracking numbers via email or phone and typed them into PeopleSoft by hand. With Oracle PeopleSoft and FedEx connected, purchase orders and shipments from PeopleSoft automatically create FedEx labels with the correct address and weight, FedEx tracking numbers flow back into receiving records, and the procurement team and warehouse staff see real-time shipment status without switching systems or re-keying data.

What you can do

• •Create FedEx shipment labels directly from Oracle PeopleSoft purchase orders and requisitions, with address and weight data mapped automatically.
• •Sync FedEx tracking events and delivery status back into PeopleSoft receiving and shipment records so warehouse staff see in-transit status in the ERP.
• •Support both outbound shipments and inbound freight by integrating FedEx LTL and standard shipping into PeopleSoft procurement workflows.
• •Authenticate Oracle PeopleSoft with HTTP Basic Auth or OAuth2 at the customer's unique hostname, and FedEx with OAuth2 client credentials and token caching.
• •Handle FedEx rate limits and token exhaustion with exponential backoff, and provide a full audit trail and replay for every shipment and tracking request.

Questions

How does ml-connector handle Oracle PeopleSoft's self-hosted architecture and unique hostname?

Oracle PeopleSoft runs on each customer's own servers with a unique hostname, port, and node name. ml-connector accepts the full PeopleSoft URL per customer and authenticates with HTTP Basic Auth (OPRID and password) or OAuth2 Bearer token, depending on the PeopleTools version. There is no shared API base URL or Oracle-managed sandbox, so testing must use the customer's own dev or test environment via Cloud Manager.

What tracking data flows from FedEx back into Oracle PeopleSoft?

ml-connector polls the FedEx Track API for in-transit location, delivery status, and event history on tracking numbers from PeopleSoft shipments. Tracking events are written back into PeopleSoft's receiving or shipment records so warehouse staff can see real-time status in the ERP. FedEx also offers a paid Advanced Integrated Visibility webhook service for push notifications, which ml-connector can consume if enabled on the customer's FedEx account.

How does ml-connector manage FedEx's rate limits and token caching?

FedEx limits OAuth2 token requests to 3 per second, and exceeding that triggers a 403 for 10 minutes. ml-connector caches the Bearer token for the full 1-hour TTL to stay well below that limit. API calls themselves are limited to 1,400 transactions per 10 seconds; ml-connector batches Track API requests (up to 30 tracking numbers per call) and implements exponential backoff if the rate limit is exceeded, so shipment syncs never overwhelm FedEx or cause prolonged outages.