Service

Get Involved. Join the Conversation.

Topic

    Aparajit Malli
    Data Migration of Work Orders (Engagement Cloud -...Answered
    Topic posted August 27, 2019 by Aparajit MalliBlue Ribbon: 750+ Points, tagged Integration, Service Request Management 
    37 Views, 3 Comments
    Title:
    Data Migration of Work Orders (Engagement Cloud - Service)
    Summary:
    Data Migration of Work Orders (Engagement Cloud - Service)
    Content:

    Data Migration of Work Orders (Engagement Cloud - Service)

     

    Hi,

      We have about 150,000 work order records that need to be migrated from legacy on-premise application to Oracle Engagement Cloud (Service).

     

    Based on my analysis, the file-based migration is not available for Work Order. (REST API is available but not suitable for such large volume - 150,000).

     

    Does anyone know if this in the road-map? 20A or 20B?

     

    Thanks,

    Aparajit

    Version:
    19A

    Best Comment

    Jeff McCrory

    Hey Aparajit,

    You are correct, currently the only way to migrate the work orders would be to use our REST API but you would need to make sure you don't have the integrations in Oracle Integration Cloud (OIC) active to avoid all of those creating corresponding Field Service Cloud activities. My recommendation would be to break those down into smaller batches and not try to send all 150,000 through the REST Service at one time. We do have this functionality on the road-map for the second half of 2020 and plan to add in functionality so by default the imported work orders are filtered out of SOA and not sent to OIC. Please reach out to me if you have additional questions.

    Thanks,

    Jeff 

    Comment

     

    • Jeff McCrory

      Hey Aparajit,

      You are correct, currently the only way to migrate the work orders would be to use our REST API but you would need to make sure you don't have the integrations in Oracle Integration Cloud (OIC) active to avoid all of those creating corresponding Field Service Cloud activities. My recommendation would be to break those down into smaller batches and not try to send all 150,000 through the REST Service at one time. We do have this functionality on the road-map for the second half of 2020 and plan to add in functionality so by default the imported work orders are filtered out of SOA and not sent to OIC. Please reach out to me if you have additional questions.

      Thanks,

      Jeff 

    • Fritz Cooper

      Hey Aparajit,

      Jeff is correct in his above recommendations.  There are limits to processing capacity.  Cycle time for record processing, just as in manufacturing capacity planning, will always be your principle constraint. It is wise to consult with your client about work order criticality.  Here the process is "manufacturing" work orders with correct attributes and without Field Service activities, as Jeff wisely notes above. The client will assist in determining work order conversion priority, by category / type to process, and in what order.  Customer consultation in these conversion efforts, regardless of API capability to process in one batch, is central to satisfaction.

      With best regards,

      Fritz A. Cooper

    • Aparajit Malli

      Thank you Fritz & Jeff!