Cross-Company Data Sharing

With Update 1 for RTW there is new feature available which users in multicompany environements will like. It is called cross-compnay data sharing whatever we expect it hears good in case of shared data across differeent legal entities.

Furthermore Microsoft delivers supported data packages to implement data sharing for not customized packages. For the moment there are two packages available at the shared asset library at LCS within the data packages area.

Finanial data sharing template contains the following entities including the sub-tables:

  • Asset posting profiles
  • Ledger Journal Names
  • Payment Days
  • Payment Schedules
  • Payment Terms
  • Tax Exempt Codes

Supply Chain data sharing template contains the following entities including the sub-tables:

  • Barcode Setup
  • Buyer Group
  • Charges Group
  • Commissions
  • Destination Code
  • Non conformance Type
  • Order Entry Deadline Group
  • Order Origin Code
  • Order Pool
  • Production Group
  • Production Pool
  • Purchase Pool
  • Reason for Delivery
  • Supplementary Item Group
  • Terms of Delivery
  • Work time calendar

Of course you have to take care that all companies use same processes, setup and configuration regarding these process master data.


Use cross-company data sharing for the following business scenarios:

  • Sharing of simple reference and group data in a single deployment
  • Sharing among companies that have very similar configurations
  • Sharing scenarios that have been explicitly tested by Microsoft

Don’t use cross-company data sharing in following scenarios:

  • Franchising solutions, where thousands of records are shared across thousands of companies.
  • Sharing of transactional records for reporting or management purposes, such as consolidations
  • Sharing across deployments
  • Complex scenarios, such as replication of subtype/supertype tables or tables that have date effectivity rules
  • Master data management

A short introduction how to use you can see here

There are also some limitations you should know and you shouldn’t pass over:

  • It can’t be used to share transactional data between companies
  • Only reference and group data can be shared
  • It supports replication of fewer than one million total records per job. (This total is calculated as the number of shared records × the number of shared companies.)
  • Only one level of child relationships is exposed. To protect data consistency, replication doesn’t occur if another level is required.










Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.