Oracle Fusion Cloud ERP and UPS integration

What moves between them

Purchase orders flow from Oracle Fusion to UPS. When a new purchase order is created in Oracle Fusion with a designated UPS carrier code and supplier, ml-connector polls Oracle Fusion for that order, extracts the ship-to address and line item quantities, and creates a corresponding shipment in UPS. Tracking events then flow back from UPS into Oracle Fusion, either via Track Alert push webhooks (renewed automatically every 14 days) or via polling Quantum View Feed, so procurement staff can see shipment status without switching systems.

How ml-connector handles it

ml-connector stores OAuth credentials for both systems encrypted and refreshes tokens transparently when either system returns a 401. It polls Oracle Fusion every 5 to 15 minutes for new purchase orders with CreationDate > last_poll_time, using OData filters to avoid re-reading the same orders. For each order flagged for UPS shipment (via a custom field or supplier code), ml-connector extracts the bill-to and ship-to addresses and calls UPS Rating and Create Shipment endpoints to generate a label. It maps the Oracle Fusion supplier name and cost center to the UPS merchant ID and account number per customer, storing the UPS tracking number back to Oracle Fusion as a custom field or note. UPS Track Alert subscriptions are registered for the generated tracking numbers and renewed internally 24 hours before expiry so notification webhooks never stop. If address validation fails or a shipment fails to create, ml-connector logs the error, marks the purchase order with a status flag, and retries on the next polling cycle.

A real-world example

A mid-market supplier distributes industrial components to dozens of customers. Purchase orders flow into Oracle Fusion from a web portal, and the supply team ships them via UPS. Before the integration, staff manually looked up each UPS tracking number after shipping and pasted it into notes in Oracle Fusion, and customers called in asking where their orders were because the tracking was invisible inside Oracle Fusion. With Oracle Fusion and UPS connected, each shipment is created automatically in UPS when the order is ready, the tracking number flows back into Oracle Fusion in seconds, and customers can track their deliveries from the customer portal without waiting for manual updates.

What you can do

• •Create UPS shipments automatically from Oracle Fusion purchase orders, including carrier selection and cost center mapping.
• •Retrieve UPS tracking events and delivery status back into Oracle Fusion so procurement and customers have real-time visibility.
• •Authenticate both systems independently with OAuth 2.0 and refresh tokens automatically when they expire.
• •Manage UPS Track Alert webhook subscriptions and renew them automatically within the 14-day expiry window.
• •Validate addresses, handle shipment failures, and retry on the next polling cycle with full audit logging.

Questions

How does ml-connector decide when a purchase order in Oracle Fusion should trigger a UPS shipment?

ml-connector monitors Oracle Fusion for new purchase orders with a designated carrier code or supplier flag indicating UPS. When it detects such an order during polling, it extracts the ship-to address, quantities, and cost center, then calls the UPS Rating and Create Shipment APIs to generate a label and tracking number, which is written back into Oracle Fusion as a custom field or note.

What happens when a UPS Track Alert subscription expires?

UPS Track Alert subscriptions expire after 14 days and must be renewed. ml-connector tracks the expiry time for each subscription and renews it automatically 24 hours before expiration, so tracking event push notifications never stop flowing. If a renewal fails, ml-connector falls back to polling Quantum View Feed to ensure no tracking events are missed.

Does ml-connector handle address validation and shipment creation failures?

Yes. If UPS Address Validation rejects an address, ml-connector logs the error and flags the Oracle Fusion purchase order with a status indicating the address needs correction. If shipment creation fails due to weight, dimensions, or service restrictions, ml-connector retries on the next polling cycle. All errors are recorded in the audit trail so you can diagnose and correct the root cause.