About Exporting Routes

Using the ERP Export REST Service, you can export a route from a Plant Applications environment. The export's response is used by the ERP Scheduler REST Service, located on another server, to import the same route defintion into another environment.

The response of the export is a formatted JSON file with the following sections:
  • exportMetaData.modelProperties
  • exportMetaData.sourceProperties
  • segmentDefinition
The import service will leverage the source names and IDs to replace IDs with the destination IDs, and create a valid route aligned to the destination server's data.

This is the fastest and most convenient way to move a route from a source system to a target system.

Note:
  • Imported routes can have a status of draft, released or archived only. Routes pending approval cannot be imported as the supporting workflow to complete the approval is not imported with the route.
  • To successfully import a route, all entities of the route must exist in the destination system. This includes:
    • Departments, lines and units
    • BOM formulations
    • Materials
    • Labor codes
    • Machine and people plans
    • Property definitions (exact GUID’s required in destination environment)
    • Documents
    • Data Entry Plan (to successfully import a data entry plan, variables must exist in the destination system)
  • Upon import, the BOM formulation must exist in the destination, but the BOM formulation items of the destination are not validated to exactly match the BOM formulation items of the source. The route will be imported based on the BOM items explicitly defined in the route versus the BOM items of the destination BOM formulation
  • Upon import, documents will reference the CouchDB URL of the destination Plant Applications configuration. Imported route documents are not validated on import. It is assumed the destination and source couchDB’s have replicated the required document. Replicating the documents ensures the document ID is maintained between CouchDB servers.