Change Package Scenarios#
The scenarios in this tutorial show how a source Customer Environment running MES version 12.0 distributes Master Data through the Global Data Orchestrator to destination Customer Environments with matching or different MES versions. They also demonstrate how approval and deployment settings can vary by destination.
Learning Path#
- Same-Version Deployment - distribute a BOM and its dependencies between two Customer Environments running version 12.0, by completing the full Change Package flow and manually initiating the deployment.
- Cross-Version Deployment - use a new Master Data Deployment Plan to distribute the same Master Data changes to version 12.0 and version 11.3 destinations, with Manual Approval required for the version 11.3 destination.
- Role-Based Approval and Deployment - extend the multi-destination plan with a third destination where the same role is configured as both the Approval Role and Deployment Role, requiring manual action.