Central common data

Depending on the required functionality, and in addition to the tables mentioned in the previous section, several other common tables must be or can be shared. These tables are described in this section.

R05000 Central First Free Numbers (KT)

Table set R05000 contains all tables that must be shared to achieve central first free numbering. In a central first free number scenario, the definition and registration of first free numbers are handled centrally and apply to all companies (logistic and financial).

Using Central First Free Numbering, the customer can generate unique IDs of all objects such as items, business partners, orders, and contracts across all its companies.

Central First Free Numbers is required for sharing of all objects such as items or purchase contracts across companies. By selecting different number groups per company, sequential numbering of for example sales orders per company can still be achieved.

R05100 Central Departments (KT)

This table set contains all the tables that must be shared to have central departments. Central departments will achieve central numbering of the departments, but it is also required for several other requirements as central employees and the sharing of the financial business partner roles.

Although shared departments are visible in all companies, they are linked to an operational company and they can also only be linked to transactional data into that operational company. For example, if a sales office is linked to operational company 100, you cannot create a sales order in logistic company 200 for this sales office. Moreover, each department must be entered in its operational company, so if a sales office is entered in company 100, company 100 will be the operational company of this department and sales orders for this department can only be created and maintained in this company.

R05200 Central Calendar Setup (KT)

This table set contains the basic data needed to generate calendars. By sharing these tables, common definitions and working times across companies can be achieved, but the calendars can differ per company.

R05300 Central Actual Calendars (KT)

All calendar management (operational calendar data) is shared, which means that the calendars are available in all companies. Still in each company different calendars can be used.

R05400 Central Warehouses (KT)

This table set contains all the tables that must be shared to have central warehouses.

Although shared warehouses are visible in all companies, they are linked to an operational company and they can also only be linked to transactional data into that operational company. For example, if a warehouse is linked to operational company 100, you cannot create a warehouse order in logistic company 200 for this warehouse. Moreover, each warehouse needs to be entered in its operational company, so if a warehouse is entered in company 100, company 100 will be the operational company of this warehouse and warehouse orders for this warehouse can only be created and maintained in this company.

R05500 Central Items (KT)

This table set includes the tables that must be shared to maintain items centrally. When items are shared, the date-effective supply sources of the items must also be shared among the companies involved.

However, if you require different supply sources for individual companies, you must not share the date-effective supply sources. Supply sources are defined in the Default Supply Source field in the Items (tcibd0501m000) session. Date-effective sources are defined using the Source by Date option in the Items (tcibd0501m000) session.

Note: 
  • If the referenced tables are also shared, the Business Partner tables are shared as well. This is because of the reference from the manufacturer to the buy-from business partner. Sharing the Business Partner tables because of centralized items can be avoided by not using manufacturers for items or by not using business partners for manufacturers.
  • When using the Table Sharing Modeler, this can be achieved by 'Accepting' this reference between the manufacturer and the buy-from business partner in the Table Sharing Exceptions (tltsm2100m000) session. All other references to the business partner are removed.
  • In case of project items, the project table (tcmcs052) must be shared as well.
  • When items are shared and the Project package is used, the Project Resources (R55300) table set needs to be shared between the logistic companies.
  • If Export Licenses are implemented in the Project Pegging Parameters, either the Bill of Material must be shared or the Detect Export Licensed Item Structure (tcibd0208m000) session must run in the production company.
  • If table tcibd001 is shared and tcibd010 is not, deleting a date-effective supply source for an individual company can cause date-effective supply sources present for other companies to be ignored. This is because the Date-Effective Item Sources check box in the Items (tcibd0501m000) session is cleared for all companies if the supply source is deleted in one company. Therefore, once created, a date effective item source should not be deleted.

Date-effective supply source ignored

Item X with default supply source Job Shop is shared among companies 100, 200, and 300.

In company 200, the default supply source is replaced with date-effective supply source Purchase.

In company 300, it is replaced with date-effective supply source Subcontract. Next, date-effective supply source Subcontract is removed in company 300. This causes the Date-Effective Item Sources check box in the Items (tcibd0501m000) session to be cleared for all companies.

This has no consequences for companies 100 and 300, but for company 200, the default supply source Job Shop is activated and the date-effective supply source Purchase is ignored.

R05600 Central Business Partners (KT)

This table set contains all tables that must be shared to have central Business Partners. This table set also contains all business partner roles, but it is also possible to share only a subset of the roles.

Note: 
  • In the buy-from role, a purchase office can be specified and in the sold-to role, a sales office can be specified. This purchase and sales office are the departments as specified in TD and these departments cannot be shared. These departments are used to default the office on a sales or a purchase order. If the department cannot be used in the current logistic company, it is considered to be blank on the BP role and the defaulting logic continues.
  • Some financial business partner roles (Invoice-from and Invoice-to) include soft references to financial tables. Data from these tables is retrieved taking into account the correct financial company. As a result, there is no need to share these tables to a purely logistic company. You can accept these messages in the Table Sharing Exceptions (tltsm2100m000) session.

R05700 Central Credit Limit Check (KT)

This table set contains the tables which must be shared to have a central credit limit check across companies.

R05800 Central Tax Setup (KT)

In order to have a central tax setup, tables from this table set must be shared. This table set includes the following:

  • Central Tax handling: To support central tax handling, the tax handling table (tctax038) must be shared. Still the tax handling needs to be specified per financial company, so the main advantage of having the tax handling centrally is that the tax handling can be maintained and viewed from a single company.
  • Central Tax Test: By having a central Tax Test setup, a central set of tax tests is available for all companies.
  • Central Tax Exception Modeling: The Tax Exception Modeling tables must be shared between the companies of the company set for which these exceptions are valid.
  • Central Income Tax & Social Contribution: By sharing the tables for Income Tax and Social Contribution, the master data can be maintained and set up from a single company.
  • Central Intrastat and ESL: The Intrastat records are logged in the logistic company. Intrastat is reported by financial company. In order to achieve this (without having to combine separate reports, the Intrastat tables must be shared between the logistic companies, related to one financial company. If the ESL tables are shared from one company, ESL can be reported for all companies between which these tables are shared.
Note: 

The tables related to the tax provider (Tax Provider Parameters – tctax600, Product Category – tctax601, Product Category Tax matrix – tctax602 and GEO Codes by Address Data – tctax605) can be shared only between financial companies using the same tax provider with the same tax provider setup.

R05900 Central Terms & Conditions

Multiple companies (logistic companies as well as financial companies) can share the Terms and Conditions. However, it is not required that all these companies share the Terms and Conditions.

If you share the Terms and Conditions table, you must also share all referenced tables, except for the departments and the warehouses. LN always retrieves departments and warehouses by using the operational company.

Because you can set up terms and conditions by warehouse (or group of warehouses) and departments, you can specify that certain terms and conditions are only valid for a specified part of the organization.

R06000 Central Landed Costs Set-up (KT)

If the tables of this table set are shared, the landed costs can be set up and maintained in one company, but also used in the other companies.

R06100 Central Material Pricing Master Data

If material prices need to be the same between different companies, the tables from this table set must be shared.

R06200 Central Material Pricing Content

In the material pricing functionality, prices depend on the content of a specific material (for example, copper) in an end product. Therefore, based on the bill of material of the end product, the quantity of this material in the end product will be determined and stored. These amounts can also be shared between different companies. To do so, the tables of this table set must be shared.

In addition, the Bills-of-Materials must be the same in all (logistic) companies. Therefore, the tables from table set R30000: Central Bills-of-Material must be shared between these companies.

Note: 

Ctr. Material Pricing Material Content is supported only if the following concepts are not used in any of the logistic companies involved:

  • Assembly Control
  • Product Configurator (PCF)
  • PCM Configurator Integration

R06300 Central Document Management Master Data

These tables must be shared for a central setup of Document Output Management master data.

R06400 Ctr Global Trade Master Data

These tables must be shared for a central setup of master data for global trade.

R06500 Ctr Global Trade Licenses

These tables must be shared to use central global trade licenses.

R06600 Ctr Letter of Credit

LN supports the use of letters of credit in sales or purchase transactions between departments in different logistic companies. For this purpose, you must share the tables of this table set among the logistic companies involved.

R06700 Central Bank Guarantees

A bank guarantee can be used by departments in different logistic companies. To support a central bank guarantee, the tables of this table set must be shared between the logistic companies.

R06800 Central Embargoes and Boycotts

To support the setup and the use of embargoes and boycotts across logistic companies, the tables of this table set can be shared among the logistic companies. To use this functionality, the tables from table set R06400 must also be shared.

R06900 Central Classification Schemes

Usually, classification schemes are almost identical across countries. To support central management of classification schemes, the tables of this table set must be shared.

R09900 Maximum Sharing Common Data (KT)

This table set contains all tables from the Common Data package that can be shared. Tables that are not included in this table set cannot be shared.

Note: 
  • Project Table (tcmcs052): The common project table (tcmcs052), which includes the PCS projects and the TP projects can be shared, but one project can only be managed in one company.
  • Labor Rates by Business Partner and Project (tccpl092): If the Project field is used, sharing of this table is not allowed.
  • Limits of Income Tax and Social Contribution (tctax017): You can share the tctax017 table only between financial companies that have the same tax IDs and local currencies, because the values of the withholding tax are valid only for a particular tax ID. The tctax017 table stores the limits and actual values for the withholding tax.
  • If Effectivity Units (tcuef002) are shared, no cost price per effectivity unit can be specified. Effectivity units have several references to logistic tables, for example, to sourcing strategies. Because unit effectivity is a purely logistic concept, which is not used in Financials, there is no need to share these logistic tables to a purely financial company. Moreover, this is not possible, because these logistic tables are not present in a financial company. The user can accept these messages in the Table Sharing Exceptions (tltsm2100m000) session.
  • Item Ordering (tcibd200) can be shared only when sites are active.

Relations between table sets

tr_graph_central_common_data_relations.png