Common migration scenarios and tools
The following are two scenarios, and recommendations for which integration pattern to use.
Scenario 1
An energy company has field workers who schedule installation jobs for heaters. This company uses finance and operations apps for the back office and third-party software as a service (SaaS) to schedule appointments. When field workers schedule appointments, they must look up inventory availability to make sure that installation parts are available for the job.
The real-time data required:
- Peak data volume is 1,000 records per hour
- Frequency is Ad hoc.
This scenario can be implemented by using a custom service integration pattern.
In finance and operations, have a developer create a custom service to calculate the physical on-hand inventory for a given item.
In the scheduling application, make a real-time call to a custom service endpoint, through either SOAP or REST, to retrieve inventory information for the selected item.
Scenario 2
A company receives a large volume of sales orders from a front-end system that runs on-premises. Periodically, these orders must be sent to finance and operations for processing and management.
The real-time data is not required. Peak data volume is 20,000 records per hour and the Frequency is One time every five minutes.
This scenario is best implemented by using a batch data APIs integration pattern.
Determine all the entities that are required for the integration, and make sure that data management is enabled for the entities.
Finance and operations apps integration tools
Finance and operations apps offer tools for data migration, such as:
- Data management workspace
- Office integration
- Excel workbook designer
To learn more about API technology for finance and operations apps, see the Integrate finance and operations apps with Microsoft Azure, and Implement the Data management package API for finance and operations apps modules.