Activities

In the target company, you can pull master data from the source company. When you have done so, depending on the status of the master record, data steward actions can be required in the source company:

When you have decided to not make the requested changes to a master record, mark the change request as Cancelled.

You can change a master record after it is released. To do so, cancel the release of the master record. As a result, the status of the record is changed to Cancelled.

You can again edit, approve, and release a cancelled master record.

In the target company, a change can be required for a master data record. To inform the source company of the required change, create a master record change request.

With MDM studio you can manage master data. For a master data record, you can edit the:

As a data steward in the source company, you can monitor the errors that occurred when master data was sent to the target company.

You can monitor master data errors on the Master data management - Operation workspace, on the Master data errors tab. This tab shows the same data as the Master data inbox in the target company. However, here only the master data records are shown for which an error occurred when sent.

The error can for example be a data error, an error in the message, or an error in the message run.

To investigate the master data error, you can follow the steps to:

• Monitor the master data inbox.
• Monitor the master data staging journal, if staging is applicable.

When a source company releases a master record, it is added to the Master data inbox of the target company.

When a source company releases a master record, it is added to the Master data inbox of the target company.

If you use staging in your master data process, master records are imported into the staging journal by the ‘Data to staging’ message. You can monitor the master record staging journals in the target company.
Each time a ‘Data to staging’ message is run, all related master records (with status Released) are imported into the staging journal. For each message run and target company combination, a journal is added to the MDM staging journal. Each processed master record results in a line in the relevant journal. For each line, all the fields, as defined in the document, are shown with the related values.

Staging journal validations

The master records in the staging journal can be validated according to the applicable staging journal validation setup. If the applicable validation rules are:

• Met, the staging journal line is automatically approved. Depending on the master data entity setup, the approved lines are processed automatically by the 'Data from staging' message or you must manually run this message.
• Not met, an error or warning is given. Before the line can be processed further, review the errors and warnings, and take appropriate actions.

If you use data comparison, you can also apply a staging journal validation. This validation defines what happens with journal lines with data differences. If you manually generate a data comparison, make sure the data comparison is done before you manually apply staging journal validations.

To apply a staging validation, in Connectivity studio, in the Staging display options, for the desired record, set up a validation with the BisValidationMdmDifference validation class. The Exception behavior and Type settings of the validation setup define what happens if differences are found. For more information, refer to Set up staging validations. 

If you use staging in your master data process, master records are imported into the staging journal by the ‘Data to staging’ message. You can monitor the master record staging journals in the target company.
Each time a ‘Data to staging’ message is run, all related master records (with status Released) are imported into the staging journal. For each message run and target company combination, a journal is added to the MDM staging journal. Each processed master record results in a line in the relevant journal. For each line, all the fields, as defined in the document, are shown with the related values.

Staging journal validations

The master records in the staging journal can be validated according to the applicable staging journal validation setup. If the applicable validation rules are:

• Met, the staging journal line is automatically approved. Depending on the master data entity setup, the approved lines are processed automatically by the 'Data from staging' message or you must manually run this message.
• Not met, an error or warning is given. Before the line can be processed further, review the errors and warnings, and take appropriate actions.

If you use data comparison, you can also apply a staging journal validation. This validation defines what happens with journal lines with data differences. If you manually generate a data comparison, make sure the data comparison is done before you manually apply staging journal validations.

To apply a staging validation, in Connectivity studio, in the Staging display options, for the desired record, set up a validation with the BisValidationMdmDifference validation class. The Exception behavior and Type settings of the validation setup define what happens if differences are found. For more information, refer to Set up staging validations. 

In the target company, as a data steward, you can pull master data from the source company.

In the target company, as a data steward, you can use a dynamic button to pull master data from the source company.

From which pages you can use the dynamic button is defined by the dynamic button setup.

You can release approved master records.
If you release a master record, it is added to the Master data inbox of the target company.

You cannot change a released master record.

You can release approved master records.
If you release a master record, it is added to the Master data inbox of the target company.

You cannot change a released master record.

In the target company, to any D365 FO page, you can add a dynamic button to pull master data from the source company.

As a result, to the Action Pane of the D365 FO page, the Master data management tab is added with the dynamic button. The dynamic button opens a page showing the available records. Which page is opened, is defined in the Dynamic menu form setup of the applicable master data entity.

For example, to the Sales orders (SalesTable) page, you can add a dynamic button to pull customer accounts to the current company.

In the target company, to any D365 FO page, you can add a dynamic button to pull master data from the source company.

As a result, to the Action Pane of the D365 FO page, the Master data management tab is added with the dynamic button. The dynamic button opens a page showing the available records. Which page is opened, is defined in the Dynamic menu form setup of the applicable master data entity.

For example, to the Sales orders (SalesTable) page, you can add a dynamic button to pull customer accounts to the current company.

Use a master data entity to define:

To send data form a staging journal to a target company, you need two connectors, two documents, and a message.
For the 'Data from staging' message, you can re-use the connectors and documents that are used for the 'Data to staging' message. 
Make sure you use the:

• Source connector and document of the ‘Data to staging’ message as target connector and document on the ‘Data from staging’ message.
• Target connector and document of the ‘Data to staging’ message as source connector and document on the ‘Data from staging’ message.

To send data from a source company to a staging journal, you need two connectors, two documents, and a message. 

To set up these components for MDM studio, some specific setup is required:

For more information on setting up connectors, documents, and messages, refer to Connectivity studio.

To send data directly from a source company to a target company, you need two connectors, two documents and a message.

To set up these components for MDM studio, some specific setup is required:

To send data from a source company to an external application or location, you need two connectors, two documents, and a message. 
To set up these components for MDM studio, some specific setup is required:

For more information on setting up connectors, documents, and messages, refer to Connectivity studio.

In MDM studio, you can use the Create MDM message wizard to create the message for an internal direct master data setup. With an internal direct master data setup, you send data from the source (master data) company directly to the target company.

With the wizard, you create the:

• Documents that are used in the MDM message.
• MDM message.

In MDM studio, you can use the Create MDM message wizard to create the messages for an internal staging master data setup. With an internal staging master data setup, you send data from your source company to a staging journal. The target company triggers the message to send the data from the staging journal to the target company.

With the wizard, you create the:

• Documents that are used in the MDM messages.
• MDM message to send data from the source company to the staging journal (data to staging message).
• MDM message to send data from the staging journal to the target company (data from staging message).

For each standard company, define the data stewards. 

A data steward is a user in D365 FO who can send and release master data for the sending company and can receive the data for the target company.