Logistics doesn’t have a transaction problem. It has a visibility problem, and Oracle Forms is exactly the wrong architecture for fixing it. A 1,200-truck operator we worked with runs warehouse operations and fleet dispatch on 94 Forms screens built between 2004 and 2009. Drivers still call dispatchers on the phone to give ETAs. Dispatchers still type those ETAs into Forms. Allocation logic works. Inventory reconciles. But nobody in the company can see where a shipment is right now.
What modern logistics dashboards need
Supply chain customers consistently ask for the same four capabilities, and Forms can deliver none of them: real-time fleet tracking with ETA and fuel data refreshed every 30 seconds, warehouse heatmaps over inventory density and dock utilization, an end-to-end order fulfillment pipeline with SLA alerts, and carrier scorecards that drive automated routing to the best performer.
The integration problem
Modern logistics requires the ERP to talk to a dozen external systems: GPS providers like Samsara and Geotab, e-commerce platforms like Shopify, EDI partners for automated POs, and IoT sensors for temperature and motion in the warehouse. Forms has no native API surface. Every one of those integrations today is a custom middleware project with its own maintenance burden and failure modes.
The DEX approach
After migration, the new TypeScript application exposes REST APIs that any external service can call. GPS data feeds the fleet dashboard directly. E-commerce orders flow into the fulfillment pipeline without a nightly batch. IoT sensor readings trigger inventory alerts in real time.
Business logic that governs warehouse allocation, carrier selection, and order prioritization is preserved exactly as it ran in Forms. Our migration engine extracts it from the original PL/SQL deterministically, so the rules don’t drift in translation. Dispatchers stop typing ETAs because the system already knows them.