Master Data Management System
app for Microsoft Dynamics 365 Business Central

Synchronization and exchanging master data across multiple Dynamics 365 Business Central tenants and databases

Many multi-subsidiary companies face daily problems with data structure and communication between subsidiaries, as well as individual users. By default, companies in Dynamics 365 Business Central (and also previously in Microsoft Dynamics NAV) manage their data on their own. This implies data inconsistency if there is no tool used for data synchronization. The data inconsistency has business drawbacks in many operational areas. The lack of standardized data management triggers problems with monitoring subsidiary performance as well as applying uniform pricing and distribution policies. Processes get more and more inefficient.

 

Master Data Management System is an app for Microsoft Dynamics 365 Business Central designed for multinational organizations that use this system. Sooner or later, such organizations are confronted with challenges regarding data consistency in their companies. From the group’s perspective, it is recommended to standardize critical data categories (e.g. items) in all companies instead of permitting inconsistencies at a local level. This approach can be extended with new sets of features to meet growing demands of users and markets during the digital transformation.

What problems can be solved with Master Data Management System?

  • Standardized data in group of companies

    With the Master Data Management System app, standardized Chart of Accounts, customers and vendors,...

    Standardized data in group of companies

    With the Master Data Management System app, standardized Chart of Accounts, customers and vendors, inventory numbering, pricing, BOMs etc., can be implemented for the entire group of companies.

  • Data consolidation and reporting

    Data standardization supports consolidated reporting for the entire group of companies, eliminating the need...

    Data consolidation and reporting

    Data standardization supports consolidated reporting for the entire group of companies, eliminating the need to monitor each company individually. Data from subsidiaries are sent to the headquarters in a standardized format.

  • Faster deployment of new companies in the group

    By using predefined data and global templates new companies in the group might be...

    Faster deployment of new companies in the group

    By using predefined data and global templates new companies in the group might be deployed much faster and more effectively.

  • Effective communication

    Data standardization and electronic data exchange support efficient communication between units within the group.

    Effective communication

    Data standardization and electronic data exchange support efficient communication between units within the group.

  • Centralized data management

    Data maintenance is managed in a central database which ensures data consistency across the...

    Centralized data management

    Data maintenance is managed in a central database which ensures data consistency across the whole groups and streamlines data management.

  • Integration with external systems

    Thanks to data consistency within the group, integration with external solutions is much simpler...

    Integration with external systems

    Thanks to data consistency within the group, integration with external solutions is much simpler and helps reduce maintenance and operational costs.

  • z

    Functionality of Master Data Management System

  • The concept of Master Data Management System

    The concept of Master Data Management System

    As an extension of Microsoft Dynamics 365 Business Central, Master Data Management System allows users to configure sets of data within the Master Company (i.e. central company in a group) and replicate this data to the local companies (Receivers) that use Business Central in order to ensure data consistency within the corporate group.

    Users are allowed to set up any number of Receivers, which are target companies, to which data is replicated. The structure of replicated data can be set up as data sets. Users can use any number of created data sets and set them up to be replicated to a particular Receiver, by using the replication card. Replication can be either Full or Incremental. While processing Incremental replication, only data changed during the last replication will be exported.

    The app is particularly useful when a company wants to create and maintain certain Dynamics 365 Business Central cards (e.g. items, BOMs, vendors) in one company – called “Master” company – and afterwards synchronize the data to all of the subsidiaries (“Receiver” companies).

     

  • Replication – Master Company and Receiver Companies

    Replication – Master Company and Receiver Companies

    In Master Data Management System, data exchange is always performed from the Master Company to Receiver Companies. A Master Company is a company where all data considered global is stored. Receiver Companies are the companies to which data is sent.

    Depending on the type of Dynamics 365 Business Central (Dynamics NAV) installation in the organization, data exchange is managed within one database, or within multiple databases, or within databases located at multiple SQL servers or in the scenarios using corporate ERP systems such as SAP, Oracle, etc.

    It is possible to synchronize data across the companies on different Business Central or NAV versions. Master Data Management System also supports the scenario with some Business Central companies installed on-premises whereas the others are in SaaS.

  • Single database (both on-premises and on-cloud)

    Single database (both on-premises and on-cloud)

    An example of data synchronization using Master Data Management System in an organization with a single Dynamics 365 Business Central (or Dynamics NAV) database/tenant.

  • Multiple production environments (SaaS)

    Multiple production environments (SaaS)

    With the SaaS version, it is no longer needed to keep separate countries in different databases because of the location of a company/subsidiary, or to keep them on separate data centers
    because of the bandwidth. Therefore, it is recommended for such organization to simply create different production environments within the same tenant (one production environment
    for each country). This approach simplifies the architecture.

    Master Data Management System can be used to synchronize data across the companies. Obviously, if you decide to keep different companies on different tenants, data synchronization will be also possible.

  • Multiple databases (for on-premises)

    Multiple databases (for on-premises)

    An example of data synchronization using Master Data Management System in an organization with multiple databases on the SQL server.

     

  • Multiple data centers (for on-premises)

    Multiple data centers (for on-premises)

    An example of data synchronization using Master Data Management System, during which Dynamics 365 Business Central (Dynamics NAV) data bases are synchronized on servers located in different data centers (usually because of insufficient bandwidth). The primary assumption of the Master Data Management System architecture is that some of the subsidiaries in the organization use their own Dynamics 365 Business Central installations deployed on different servers.

  • Regionalization

    Regionalization

    The other variant of the Master Data Management System installation is an organization with subsidiaries with uniform master data. However, this data can be different depending on the region in which a subsidiary operates. In such cases, a layer is created between the main Master Company and all the Receivers. Regional companies become Receivers for the main Master Company in the group, but at the same time they are Master Companies for the subsidiaries in their respective regions. The above diagram represents the overview of such regionalization in the on-premises environment. However, this approach can also be applied to SaaS – one or more production environments have to be used to maintain the “proxy”, regional companies.

  • Corporate ERP system (e.g. SAP)

    Corporate ERP system (e.g. SAP)

    An example of data synchronization using Master Data Management System in an organization where Dynamics 365 Business Central (Dynamics NAV) is used by subsidiaries in the group and another ERP system e.g. SAP is used as a corporate system. In such a case, SAP can be a source of data for the Master Company (as shown in the diagram), but there are other scenarios. In such scenarios, Master Data Management System is a source of data both for SAP and Dynamics 365 Business Central, or data is sent directly from SAP to Receiver Companies, and part of typical Dynamics 365 Business Central data is still maintained in the Master Company. In the last example, a separate Master Company is required for Dynamics 365 Business Central, because of the differences between the SAP and Dynamics 365 Business Central data structures. Therefore, it is necessary to maintain e.g. accounting groups, dimensions and charts of accounts in the Master Company. Please note that integration with SAP is not part of the standard Master Data Management System functionality.

  • Data sets

    Data sets

    The data set contains information about the structure of data to be replicated. The user can set up which tables and which fields should be included in a data set. It is possible to add fields and tables, both from Business Central and other extensions or applications. In the replication process, data sets are linked to a selected Receiver and the scope of data to be replicated is set up.

    On the data set level, the user can also manage local blocking rules by enabling the fields allowing for local insertions, deletions or modifications. It will prevent users from the modifications of the global (common) records in the receiver (local) companies.

  • Replication types

    Replication types

    When starting the replication process, the user decides which data should be synchronized with which recipient.

    Manual / Automatic

    In manual replication, the user can run replication manually, from the Replication Card or the Replication List pages. It is also possible to set up replication to be run automatically by using the Dynamics 365 Business Central (Dynamics NAV) Job Queue Entries.

    Full / Incremental

    Full replication loops through all the records from the Data Set, including filters set up on a selected replication line (if any). If no filters have been set up, all records will be exported each time replication is run. Incremental replication includes only data that has been recently modified (since the dates set in Last Run Date and Time on the replication card).

    Record subscription

    After enabling the record-level replication feature, the user can decide to which receiver the record should be replicated. Subscriptions can be created per record or in batch via the matrix from the record list or card. Record-level replication is available “out of the box” for: items, customers, vendors, resources, contacts and G/L accounts. However, it can be easily implemented for other master data. The advantage of the record-level functionality is that the record will not be synchronized until the configuration is finished and the record is subscribed. This eliminates the risk of synchronizing the master data that has not been configured completely.

     

     

  • Communication Methods

    Communication Methods

    Data can be synchronized via a web service published on the receiver’s side with authorization using the MS Entra Application. This method is not only recommended but also required for data exchange between different environments. For companies within the same environment, a simpler database-based communication method can be used, allowing for data synchronization without the need to configure web service communication.

  • Advanced features of Master Data Management System

    Advanced features of Master Data Management System

    Group Receivers

    When using the Group Receivers feature, it is possible to process one replication for multiple receivers simultaneously.

    Binary Data replication

    Binary data refers to the content of the Blob, Media, and MediaSet fields that store files such as images or other types of media. The application allows for the synchronization of such fields.

    Transformations

    The transformation functionality allows for the conversion of global values of replicated fields according to established rules. This enables exception handling for certain local companies.

    Translations

    Certain tables, such as an Item, an Item Variant or Payment Terms, can have their values translated in the Business Central base application. The translation functionality allows, for example, to maintain Item descriptions in English at master company, while locally in receiver company in local language.

    Deleting Records

    It is possible to delete records in the Master Company. For records that have been replicated, the system will automatically issue a webservice call to all receiving companies that haveever received this particular record, and will attempt to delete the record. If the process is completed successfully, the records will be deleted from the Master Company. We provide also the MDMS Records Management tool which enables the deletion of records only from the selected receiver company.

    Local Template Setup
    MDMS local template setup is used to apply the configuration template automatically after record synchronization is run. The configuration template is applied only once when a new record is created in a receiver company. You can also define the conditions under which the configuration template will be applied to the record.

    Master Data Management System Extensibility
    The application is extensible. The app can be easily extended or integrated with external systems using multiple available publishers.

  • z

    The concept of Master Data Management System

    As an extension of Microsoft Dynamics 365 Business Central, Master...

    More

    The concept of Master Data Management System

    As an extension of Microsoft Dynamics 365 Business Central, Master Data Management System allows users to configure sets of data within the Master Company (i.e. central company in a group) and replicate this data to the local companies (Receivers) that use Business Central in order to ensure data consistency within the corporate group.

    Users are allowed to set up any number of Receivers, which are target companies, to which data is replicated. The structure of replicated data can be set up as data sets. Users can use any number of created data sets and set them up to be replicated to a particular Receiver, by using the replication card. Replication can be either Full or Incremental. While processing Incremental replication, only data changed during the last replication will be exported.

    The app is particularly useful when a company wants to create and maintain certain Dynamics 365 Business Central cards (e.g. items, BOMs, vendors) in one company – called “Master” company – and afterwards synchronize the data to all of the subsidiaries (“Receiver” companies).

     

    Replication – Master Company and Receiver Companies

    In Master Data Management System, data exchange is always performed...

    More

    Replication – Master Company and Receiver Companies

    In Master Data Management System, data exchange is always performed from the Master Company to Receiver Companies. A Master Company is a company where all data considered global is stored. Receiver Companies are the companies to which data is sent.

    Depending on the type of Dynamics 365 Business Central (Dynamics NAV) installation in the organization, data exchange is managed within one database, or within multiple databases, or within databases located at multiple SQL servers or in the scenarios using corporate ERP systems such as SAP, Oracle, etc.

    It is possible to synchronize data across the companies on different Business Central or NAV versions. Master Data Management System also supports the scenario with some Business Central companies installed on-premises whereas the others are in SaaS.

    Single database (both on-premises and on-cloud)

    An example of data synchronization using Master Data Management System...

    More

    Single database (both on-premises and on-cloud)

    An example of data synchronization using Master Data Management System in an organization with a single Dynamics 365 Business Central (or Dynamics NAV) database/tenant.

    Multiple production environments (SaaS)

    With the SaaS version, it is no longer needed to...

    More

    Multiple production environments (SaaS)

    With the SaaS version, it is no longer needed to keep separate countries in different databases because of the location of a company/subsidiary, or to keep them on separate data centers
    because of the bandwidth. Therefore, it is recommended for such organization to simply create different production environments within the same tenant (one production environment
    for each country). This approach simplifies the architecture.

    Master Data Management System can be used to synchronize data across the companies. Obviously, if you decide to keep different companies on different tenants, data synchronization will be also possible.

    Multiple databases (for on-premises)

    An example of data synchronization using Master Data Management System...

    More

    Multiple databases (for on-premises)

    An example of data synchronization using Master Data Management System in an organization with multiple databases on the SQL server.

     

    Multiple data centers (for on-premises)

    An example of data synchronization using Master Data Management System,...

    More

    Multiple data centers (for on-premises)

    An example of data synchronization using Master Data Management System, during which Dynamics 365 Business Central (Dynamics NAV) data bases are synchronized on servers located in different data centers (usually because of insufficient bandwidth). The primary assumption of the Master Data Management System architecture is that some of the subsidiaries in the organization use their own Dynamics 365 Business Central installations deployed on different servers.

    Regionalization

    The other variant of the Master Data Management System installation...

    More

    Regionalization

    The other variant of the Master Data Management System installation is an organization with subsidiaries with uniform master data. However, this data can be different depending on the region in which a subsidiary operates. In such cases, a layer is created between the main Master Company and all the Receivers. Regional companies become Receivers for the main Master Company in the group, but at the same time they are Master Companies for the subsidiaries in their respective regions. The above diagram represents the overview of such regionalization in the on-premises environment. However, this approach can also be applied to SaaS – one or more production environments have to be used to maintain the “proxy”, regional companies.

    Corporate ERP system (e.g. SAP)

    An example of data synchronization using Master Data Management System...

    More

    Corporate ERP system (e.g. SAP)

    An example of data synchronization using Master Data Management System in an organization where Dynamics 365 Business Central (Dynamics NAV) is used by subsidiaries in the group and another ERP system e.g. SAP is used as a corporate system. In such a case, SAP can be a source of data for the Master Company (as shown in the diagram), but there are other scenarios. In such scenarios, Master Data Management System is a source of data both for SAP and Dynamics 365 Business Central, or data is sent directly from SAP to Receiver Companies, and part of typical Dynamics 365 Business Central data is still maintained in the Master Company. In the last example, a separate Master Company is required for Dynamics 365 Business Central, because of the differences between the SAP and Dynamics 365 Business Central data structures. Therefore, it is necessary to maintain e.g. accounting groups, dimensions and charts of accounts in the Master Company. Please note that integration with SAP is not part of the standard Master Data Management System functionality.

    Data sets

    The data set contains information about the structure of data...

    More

    Data sets

    The data set contains information about the structure of data to be replicated. The user can set up which tables and which fields should be included in a data set. It is possible to add fields and tables, both from Business Central and other extensions or applications. In the replication process, data sets are linked to a selected Receiver and the scope of data to be replicated is set up.

    On the data set level, the user can also manage local blocking rules by enabling the fields allowing for local insertions, deletions or modifications. It will prevent users from the modifications of the global (common) records in the receiver (local) companies.

    Replication types

    When starting the replication process, the user decides which data...

    More

    Replication types

    When starting the replication process, the user decides which data should be synchronized with which recipient.

    Manual / Automatic

    In manual replication, the user can run replication manually, from the Replication Card or the Replication List pages. It is also possible to set up replication to be run automatically by using the Dynamics 365 Business Central (Dynamics NAV) Job Queue Entries.

    Full / Incremental

    Full replication loops through all the records from the Data Set, including filters set up on a selected replication line (if any). If no filters have been set up, all records will be exported each time replication is run. Incremental replication includes only data that has been recently modified (since the dates set in Last Run Date and Time on the replication card).

    Record subscription

    After enabling the record-level replication feature, the user can decide to which receiver the record should be replicated. Subscriptions can be created per record or in batch via the matrix from the record list or card. Record-level replication is available “out of the box” for: items, customers, vendors, resources, contacts and G/L accounts. However, it can be easily implemented for other master data. The advantage of the record-level functionality is that the record will not be synchronized until the configuration is finished and the record is subscribed. This eliminates the risk of synchronizing the master data that has not been configured completely.

     

     

    Master Data Management System

    Communication Methods

    Data can be synchronized via a web service published on...

    More

    Communication Methods

    Data can be synchronized via a web service published on the receiver’s side with authorization using the MS Entra Application. This method is not only recommended but also required for data exchange between different environments. For companies within the same environment, a simpler database-based communication method can be used, allowing for data synchronization without the need to configure web service communication.

    Advanced features of Master Data Management System

    Group Receivers

    When using the Group Receivers feature, it is...

    More

    Advanced features of Master Data Management System

    Group Receivers

    When using the Group Receivers feature, it is possible to process one replication for multiple receivers simultaneously.

    Binary Data replication

    Binary data refers to the content of the Blob, Media, and MediaSet fields that store files such as images or other types of media. The application allows for the synchronization of such fields.

    Transformations

    The transformation functionality allows for the conversion of global values of replicated fields according to established rules. This enables exception handling for certain local companies.

    Translations

    Certain tables, such as an Item, an Item Variant or Payment Terms, can have their values translated in the Business Central base application. The translation functionality allows, for example, to maintain Item descriptions in English at master company, while locally in receiver company in local language.

    Deleting Records

    It is possible to delete records in the Master Company. For records that have been replicated, the system will automatically issue a webservice call to all receiving companies that haveever received this particular record, and will attempt to delete the record. If the process is completed successfully, the records will be deleted from the Master Company. We provide also the MDMS Records Management tool which enables the deletion of records only from the selected receiver company.

    Local Template Setup
    MDMS local template setup is used to apply the configuration template automatically after record synchronization is run. The configuration template is applied only once when a new record is created in a receiver company. You can also define the conditions under which the configuration template will be applied to the record.

    Master Data Management System Extensibility
    The application is extensible. The app can be easily extended or integrated with external systems using multiple available publishers.

    Price list

    Subscription

    online

    on-premises

    Per User

    6

    / month

    Unlimited

    600

    / month

    Perpetual license

    on-premises

    Per User

    140

    +EP

    Unlimited

    14000

    +EP

    • Per User – the fee is calculated on the basis of the number of Dynamics 365 Business Central full users
    • EP – in the case of the Perpetual License, the prices should be increased by an annual fee or the Enhancement Plan (EP)
    • Unlimited – the fee does not depend on the number of Business Central users
    • The license fee is calculated for each Dynamics 365 Business Central tenant separately
    • The above prices do not include VAT

    Ask me about the application

    Master Data Management System

    Product specialist

    Przemysław Kniat

    Sales Department Manager

    Contact me

    Reviews of Master Data Management System

  • DLF is world largest seed company. We use IT.integro's Master Data Management System to handle three areas of master data. The first one is a supply chain, handling items, production BOMs, packaging materials and so forth. Second area is financial data to run and standardize our chart of accounts to secure the transparency across the group. And thirdly we are using it to handle our contacts, meaning our vendors and customers to secure we don't have duplicates across the group. The system has a good, comprehensive functionality and it fits our needs very well.

  • Having common master data, thanks to Master Data Management System, speeds up the implementation of new companies in the group and secures unity of data when it comes to reporting and analysis.

  • Looking at Master Data Management System, mostly we use it for central item management. Central item management in the broadest sense of the word, not only the item data but also related data like Prices, Discounts, Unit of measures, Languages, etc. Our customers are happy with the software that IT.integro delivers because it does what has to be done. It's easy to implement and has also a good prize for the functionality, which is delivered.

  • We chose IT.integro because of their solution that is available globally. They also are a professional partner to work with and a good sparring partner in case we have customers that don’t fit to the standard solution. A strength of the Microsoft platform lies in combining market leading apps to create the ecosystem that fits the customer’s purpose best. In our case an ecosystem that combines Drink-IT, Master Data Management System and Advanced Intercompany of IT.integro and potentially other apps.

  • We chose Master Data Management System because it gives our customers control over a central master data company within our solution tegossuite – the leading enterprise software for the recycling industry - to maintain and keep data consistent. The data is entered in a controlled and managed way throughout our customers’ companies. It simplifies and speeds up the data management and influences greatly on reliable evaluations and reports company-wide.

  • Thanks to Master Data Management System, we managed to standardize data between the databases maintained in two different data centers (in Europe and North America), ensuring the high quality of the data at the same time. This way, the exchange of inter-company documents became much more effective. With standardized and harmonized data, we are also able to streamline report creation in our BI tools.

  • The Global Integration Apps from IT.integro are highly ranked by Fellowmind consultants. Mainly for the high quality, rich functionality and that they are user-friendly.

  • Master Data Management System, powered by IT.integro, was developed to facilitate central control of all master data related to financial transactions, customers, vendors, items and system settings. The system has helped Kleen-Tex to effectively administer our master data and keep it consistent between the databases. Due to the high volume of intercompany transactions, we have, this has helped a lot in streamlining the documents between systems. We are happy to comment on those features after we have time to test them and use them in a productive setting.

  • Master Data Management System from IT.integro helps to speed up the implementation time of new companies. We implemented a company in Ireland in seven days because we were able to replicate master data. Also, in general we see a reduced implementation time because we easily can transfer our master data to new companies. Generally, we see our implementation projects being sped up because we don't need to spend time on master data in each of the implementations.

  • We decided to implement Microsoft Dynamics NAV integrated with LS Retail because the existing ERP system limited the growth of our business – it worked only locally and lacked scaling capabilities. We were looking for a global solution – the one that was unified and could be used by all company locations. The solution that would provide secure and instant access to a coherent database and reliable analytical tools. To achieve the desired effect, Master Data Management System – a module supporting the management of central data was implemented. The new tool allows more effective monitoring of business activities carried out in individual subsidiaries and seamless data synchronization.

  • Check out our other apps

    Discover solutions that support business growth and automate processes. Take advantage of modern IT tools tailored to your company's needs!

    Cash Desk Management

    Cash Desk Management

    Improved cash operations, transactions and reporting

    1. Applications for trading companies

    2. Author applications

    Polish Localization

    Polish Localization

    Comply with Polish taxation and invoicing requirements

    1. Applications for Polish companies

    2. Author applications

    Advanced Cost Allocations

    Advanced Cost Allocations

    Parallel Posting, Manufacturing Cost Allocation and Calculation

    1. Author applications

    2. Production applications

    Electronic Banking

    Electronic Banking

    Electronic banking in ERP system: Integration with local banks in multiple countries

    1. Applications for capital groups

    2. Applications for Polish companies

    3. Author applications

    HR & Payroll Manager

    HR & Payroll Manager

    HR and payroll services in the ERP system

    1. Applications for Polish companies

    2. Author applications

    3. HR and payroll applications

    Intercompany Insights

    Intercompany Insights

    Insight into inventory availability and customer balance overviews across companies within the group

    1. Applications for capital groups

    2. Applications for trading companies

    3. Author applications

    Advanced Product Configurator

    Advanced Product Configurator

    Products customization for trading and manufacturing companies

    1. Applications for trading companies

    2. Author applications

    3. Production applications

    Advanced Intercompany

    Advanced Intercompany

    Managing and tracking intercompany transactions in real-time

    1. Applications for capital groups

    2. Author applications

    Bonsues & Accruals

    Bonuses & Accruals

    Retrospective bonuses and rebates with real-time accruals posting

    1. Applications for trading companies

    2. Author applications

    Fiscalization

    Fiscalization

    Fiscalization in the ERP system: fiscal documents in compliance with local requirements

    1. Applications for Polish companies

    2. Author applications

    Przemysław Kniat

    Sales Department Manager

    Opiekun produktu

    Zapytaj mnie o aplikację Master Data Management System