Dear IFS R&D Team,
We are currently using IFS APP10 Transport Order solution to manage goods movements between onshore and offshore sites. As we plan to move to IFS Cloud next year, we are evaluating the Shipment Order solution (25R2).
During this evaluation, we identified several gaps in IFS Cloud compared to the APP10 Transport Order functionality. We would appreciate your advice on available workarounds and whether these gaps are planned to be addressed in future releases.
1. Movements within the same site
In APP10, Transport Orders support bulk movement of parts (including project materials) between onshore–onshore or offshore–offshore locations.
In IFS Cloud, this is not supported via Shipment Orders, and Move Inventory Part is not suitable for bulk moves.
-
Can Transport Tasks be used instead?
-
Do Transport Tasks support replication? (We have not set up replication yet.)
2. Movements between different companies
In APP10, Transport Orders allowed us to move parts from the project company (onshore) to the operations company (offshore). In Cloud, this is not supported in Shipment Orders, and we were told to use Distribution Orders.
Problems with Distribution Orders:
-
Replication is not supported
-
They require setting up basic data (like inter-site flow) each time, which is not efficient.
-
One Distribution Order is created per part
Is Distribution Order the long-term solution for moving parts between companies? Will replication be supported in the future?
3. Loading process is not efficient
In APP10, loading was done in one window (Load Part / Load No Part tabs). In Cloud, users must go through several windows:
-
Move into Stock (Inventory Part Receipts)
-
Receipt (Non-Inventory/No Part Receipts)
-
Inventory Part In Stock
Other issues:
-
No option to load parts directly from Shipment Order. Users must remember order numbers.
-
Deleting loaded items requires entering a cancellation reason, which adds steps.
Given that oil & gas shipments often include both inventory and no parts, we would appreciate a more centralized and efficient loading process. Are there current ways to make this easier?
4. Missing details for No Part lines
We often use No Part lines and need to enter:
-
Weight
-
Notes (to print on Transport Order)
-
Cost (used in fiscal note)
These fields are missing in Cloud.
5. Shipment automation
Even when shipments are created without stops, the process stops at the Pick List Creation step. Users must run it manually. Full automation would help.
6. Fiscal note creation
In APP10, we configured the system to automatically create the fiscal note when a transport order is executed. Could you explain how fiscal notes are generated in Cloud, so we can avoid relying on this configuration?
7. Handling discrepancies after arrival
Packages are opened only after reaching offshore, so we often find differences between shipped and received quantities. In APP10, we could revert arrivals and adjust Transport Order lines. In Cloud, shipment quantities cannot be corrected after arrival. We ask for this function in future releases.
8. No history log
Shipment Orders and Shipments do not provide a history log. This is important for auditing and troubleshooting, especially for replication issues.
In APP10, Transport Orders covered all goods movements. In Cloud, we must use different solutions, some without replication support. The user experience is also less smooth.
We would like to know how IFS plans to improve these areas, especially for the Oil & Gas industry, in future releases.
Kind regards,
Madusha Abeywickrama
