---
entityname: Change Package
alias: user-guide-create-change-package
description: "Create and manage a Change Package by defining deployment settings and adding Master Data contents"
---
# Create Change Package

:lock: ChangePackage.**Create**

## Overview

This operation is used to create a **Change Package**, which groups Master Data changes that can be published to the **Global Data Orchestrator** and deployed to other Customer Environments.

## Setup

No specific setup is required other than to meet the preconditions of the transaction.

## Preconditions

* You must have an active Critical Manufacturing MES license that includes the **Global Data Orchestrator** module.
* A Local Customer Environment ID must be configured.
* You must have access to a Customer Portal account.

## Sequence of Steps

{% include-markdown 'includes/pages/info_creating_versioned_entities.md' %}

### Step 1: Log in to the Customer Portal

1. Authenticate in Customer Portal with your credentials.

    !!! warning
        You must be signed in to the Customer Portal to select a Master Data Deployment Plan.

### Step 2: Change Set

{% include-markdown 'includes/pages/step_one_versioned_entities.md' %}

### Step 3: General Data

1. Provide a name for the **Change Package**.
2. If you are creating a new entity or revision, provide a name for the revision or it will be automatically generated for you. For more information on revision naming, see [Revision Naming](../../../general/revisions#Naming/).

    !!! note
        Change Packages do not support new versions. Use revisions to update an existing Change Package.

3. Optionally, provide a description of the **Change Package**.
4. Select the type of **Change Package**. The list of possible values is taken from the [[changepackagetype-lt]] lookup table.
5. Optionally, associate it with a Data Group.
6. Select a Master Data Deployment Plan.

    !!! info
        The Master Data Deployment Plan defines the Customer Environments to which the package contents are deployed. For more information, see the [Global Data Orchestrator](https://portal.criticalmanufacturing.com/Help/global-data-orchestrator/) documentation.

7. Select a Publication Mode:

    * **Automatic** - when the **Change Package** is set effective, the system approves it and calls the Publish operation automatically.
    * **Manual** - when the **Change Package** is set effective, the system approves it, but it must be published later by using the Publish operation.

8. Optionally, edit the Release Notes.
9. Select **Create** to complete the operation.

![Screenshot showing the "Create" button in the context of entering general data for a new object.](images/create_change_package_wizard.png)

After the **Change Package** is created, the system sets its initial system state to `Draft`, associates it with the current Local Customer Environment and MES version, and sets the item count to zero until contents are added to the package.

A Change Package must contain at least one item to be approved or published. For more information on adding contents to the **Change Package**, see [[user-guide-manage-change-package-items]].

![Screenshot showing the Change Package created.](images/change_package_01.png)