mediumFreight Orders
1. You are designing a side-by-side transportation planning solution where embedded TM handles order management but freight cost calculation logic is run externally during a phased migration. Which APIs and integration patterns support this cutover approach?
Use released OData/API endpoints for freight order and freight booking exposure so the external planning component can read TM data without direct table access, and push calculated freight costs back via API rather than direct BAPI calls where possible. During cutover, run both systems in parallel with a defined cutoff for freight cost ownership, using API-based synchronization to avoid duplicate postings, and decommission the external calculation once embedded TM logic is validated.