Introduction

Master data replication means a function for creating and maintaining similar master data sets for the Financial Accounting in multiple organizations that are closely connected. With this function, master data can be maintained across organizations. Based on specification of a maintaining organization, where the master data are created and changed, identical or modified records with the same keys can be transferred to one or more dependent organizations.

The replication of master data can only be carried out for organizations in which the function is activated. These organizations can be used as the maintenance or dependent organization in a replication relationship for master data maintenance (e.g. for maintenance of object accounts).

By setting up replication relationships, you determine which data objects should be transferred from which maintaining organization to which dependent organizations. The replication relationships for a data object must always be linear, i.e. a maintaining organization cannot receive data of the same data object from another organization and a dependent organization cannot itself transfer data to other organizations.

For each master data object in a replication relationship, the replication behavior is defined, by which the attribute behavior for each data field is preset for the replication.

You use the attribute behavior to control the changeability of the data fields in the dependent organizations. Data fields that should always be transferred are protected during master data maintenance in dependent organizations and cannot be changed. The attribute behavior of each individual data field can be adjusted individually for each organization.

The master data replication of individual records always takes place when saving a record in the corresponding master data application. If, for example, a new object account is created or an object account is changed in the maintaining organization, the same is followed automatically in the dependent organizations. If the records of a data object in total (e.g., all object accounts) from the maintaining organizations are to be transferred to the dependent organizations, this is performed with the Execute replication action which is available in the replication applications.

The Cockpit: Replication data application displays the records that could not be taken over in the dependent organization, for example, due to missing external keys (e.g., classifications for object account replications).

This article provides an overview of the settings and processes for replicating data.

Definition of terms

Replication

In the Financial Accounting, replication means, e.g., automatic copying of master data between organizations that have to use shared master data (e.g., corporate master data). The copy ensures that, for example, an object account has the same meaning within a group of connected companies.

Attribute behavior

The attribute describes a data field. The attribute behavior determines the behavior of a data field, e.g., in case of replication. This way, it can be specified for a data field whether its content should be taken over in the course of replication from the maintaining organization to the dependent organizations.

Setting

In order to be able to use the functions of the master data replication, settings must be made in the following applications.

Customizing

For each organization that is to be involved in a replication, the Master data replication function under the Comarch Financials Enterprise menu must be activated in the Customizing application.

Applications

This chapter lists the applications that you use to configure replication data and replicate master data.

Master data replication

In this application you define the replication relationships between the maintaining and the dependent organization. Here you assign the dependent organization for the replication of the master data to a maintenance organization and specify which data objects should be replicated (transferred) from the maintenance organization.

You also specify the replication behavior for the data objects and determine whether replicated data records may be deleted in the dependent organization.

In addition, you have the option of individually adapting the preset attribute behavior of each individual data field.

You can use the application’s actions to create a new configuration, delete an existing configuration or replicate the master data.

A description of the application you will find in the Master Data Replication article.

Cockpit: Replication data

If the replication of a record cannot be performed, for example, due to a missing external key (e.g., classifications) in the dependent organization, this record will be labelled with an error status. The Cockpit: Replication data application is used for displaying and correcting such erroneous records.

In order to obtain correct master data in the dependent organizations, the records displayed here must be corrected. First, error messages should be checked. You can display the error messages for every entry with the Display errors detailed search. You can use the Zoom view to have them displayed separately.

The incorrect data can be corrected directly in the master data application of the dependent organization. Double click in a row in order to open the corresponding application with the incorrect record to be edited. After the data have been saved and the cockpit display has been updated, the error status and the corrected entry will be removed from the display.

A description of the application you will find in the Cockpit: Replication Data article.

Master data applications

For all master data that are involved in a replication relation, the master data replication of individual records always takes place when saving the record in the master data application. If, for example, a new object account is created or an object account is changed in an organization that is defined as the maintaining organization of a replication relation, the same is followed automatically in the dependent organizations, as far as the Object accounts data object is a part of this replication relation. In the dependent organizations as such, no new object accounts can be created then. Here, it is only possible to create the replicated data of the object account if the setting of the attribute behavior allows.