Specific configuration object and object set details

This topic outlines a few specific actions that are performed during a Configuration Data Management run for some of the configuration data object sets of the APP-III-A and APP-III-B export definitions.

For extended details, please refer to the spreadsheet attached in KB article 2271146. This spreadsheet is updated for each additional release.

  • Configuration object set Common – Number Groups (tc0045)

    In configuration object Common - First Free Number Groups (tcmcs051), the In Use check box is cleared for new number groups after the import. This is to avoid any blocking issues during manual assignment of these number groups.

    If you import any parameter or configuration data that refer such a number group, the DAL software automatically selects this check box.

    New first free numbers obtain the default value 1 after the import. If another value is required for any number group, you can manually specify the required value in the Number Group (tcmcs0651m000) session in the destination environment.

  • Configuration object set: Common - Companies (tc0060)

    • The following logic applies to both configuration objects in this set:

      • For a standard import from scratch, in which tcemm170 and tccom000 rows do not exist, the rows are created during the import.
      • For tcemm170 rows that are present in the destination environment, the update is skipped during the import.
      • tccom000 rows that are present in the destination environment are updated unless functional errors occur. If errors occur, the update is skipped, and the errors are listed in a report.

    • Common – Implemented Software Components (tccom000)

      If a representative is not yet defined as an employee in the destination company, this field is not filled during the import.

      To fill the fields that were initially not filled, configuration object set: Common - Employee References Retrieval (tc0930rr) is included. This configuration object set is processed after the export or import of the employee data.

  • Configuration object set Common - Company Dependent Parameters (tc0070)

    An automatically triggered Initialize Parameters command is included. This command is similar to the initialization command performed through the Initialize Parameters (tcmcs0295m000) session.

    For BOD parameters that are initialized during the Configuration Data Management run, the Prevent BOD Publishing check box will be selected in the BOD Parameters (tcbod0100m000) session.

  • Configuration object set: Common – Item Classifications (tc0120)

    • Common – Manufacturers (tcmcs060)

      If a referenced buy-from business partner does not yet exist in the destination company, the field is not filled during the import.

      To fill the fields that were initially not filled, configuration object set: Common – Business Partner References Retrieval (tc0960rr) is included. This configuration object set is processed after the export or import of the business partner data.

  • Configuration object set Common – Registration Master Data (tc0160)

    Registrations by enterprise unit are skipped during the import if the enterprise unit does not yet exist in the destination company. This applies to these configuration objects:

    • Common - Registrations by Financial Company (tctax222)
    • Common - Expected Registrations (tctax223)

    To create the missing rows, configuration object set Common - Enterprise Unit References Retrieval (tc0910rr) is included. This configuration object set is processed after the export or import of the enterprise units.

  • Configuration object set: Common – Tax Codes by Country (tc0190)

    • Common - Tax Codes and Rates by Country (tcmcs036)

      If the collection office does not yet exist in the destination company, the Collection Office field is not filled, the Settlement Tax Code is cleared, and the Pay Tax value will be set to Periodically during the import.

      To fill the fields that were initially not filled, configuration object set: Common – Business Partner References Retrieval (tc0960rr) is included.

  • Configuration object set: Common – Enterprise Structure (tc0210)

    • Common – Internal Planning Clusters (tcemm135)

      Only internal planning clusters are included. External planning clusters, including the mandatory references to specific business partner roles, are included in configuration object set: Common – External Sites (tc0650). This configuration object set is processed after the export or import of the business partner data.

    • Common – Enterprise Units (tcemm030)

      If the default purchase office does not yet exist in the destination company, the purchase office is not inserted during the import. The same applies to the default calculation office.

      To fill the fields that were initially not filled, configuration object set: Common - Department References Retrieval (tc0920rr) is included. This configuration object set is processed after the export or import of the departments.

    • Common – Internal Sites (tcemm050)

      Only internal sites, that refer to internal planning clusters, are included. If the default warehouse does not yet exist in the destination company, the field is not filled during the import.

      To fill the fields that were initially cleared, configuration object set: Common - Warehouse References Retrieval (tc0940rr) is included. This configuration object set is processed after the export or import of the warehouses.

      External sites are included in configuration object set: Common – External Sites (tc0650). This configuration object set is processed in export definition APP-III-B, after the export or import of the business partner data.

  • Configuration object set: Common – Departments and their Classifications (tc0220)

    • The configuration objects of this configuration object set include the department data of the Common package and some, but not all department data of the Order Management, Manufacturing, and Service packages.

      This means that some of the data needed for a full setup of departments is unavailable in this configuration object set.

      For example, department settings by site are unavailable in this configuration object set.

      Consequently, mandatory department data from Order Management, Manufacturing, or Service that does not exist in the target environment is left empty after the import of this configuration object set. To allow for the import of incomplete data, the checks for the presence of this data are bypassed during the import.

      The resulting incomplete master data setup for departments allows for use in Common, but not for full operational use.

      Configuration objects for the department settings by site and other department data that is currently unavailable are being developed and will be provided for in a future release.

    • If a department's manager is not yet defined as an employee in the destination company, the Manager field in the Departments (tcmcs0565m000) session is not filled during the import.

      To fill the fields that were initially not filled, configuration object set: Common - Employee References Retrieval (tc0930rr) is included. This configuration object set is processed after the export or import of the employees.

    • The same applies to any referenced and not yet existing warehouses and departments. These references are filled in configuration object sets Common - Warehouse References Retrieval (tc0940rr), and Common - Department References Retrieval (tc0920rr), respectively. For information about the specific referenced fields, please refer to the spreadsheet in KB 2271146.

    • Specific import logic applies to these departments:

    • The import of a production department that exists in the destination company is skipped if the referenced calculation office does not yet exist in the destination company.

      To perform the import and subsequent update, configuration object set: Common - Department References Retrieval (tc0920rr) is included. This configuration object set is processed after the export or import of the departments.

    • During the import of work centers, referenced Manufacturing based classifications are not filled if they do not exist in the destination company.

    • The import of a subcontracting work center is skipped if the subcontractor does not yet exist in the destination company. To import the work centers that were initially skipped, configuration object set: Common – Business Partner References Retrieval (tc0960rr) is included. This configuration object set is processed after the export or import of the business partner data.

    • The export and import of service departments include their locations.

  • Configuration object set: Common – Internal Business Partners (tc0250)

    This configuration object set supports the preliminary initialization of internal business partners. Business partner roles are not included in the export and import.

    The complete internal business partner synchronization is part of configuration object set: Common – Business Partners and Related Data (tc0600), which is included in export definition APP-III-B.

    If the primary contact does not yet exist yet in the destination company, the Primary Contact field is not filled during the import. To fill the fields that were initially not filled, configuration object set: Common – Contact References Retrieval (tc0950rr) is included. This configuration object set is processed after the export or import of the contact data.

    If the parent business partner does not yet exist in the destination company, the Parent Business Partner field is not filled during the import. The same applies to the business partner texts. They are included in the Common – Business Partners and Related Data (tc0600) configuration object set mentioned earlier.

  • Configuration object set: Common – Internal Warehouses (tc0260)

    • The export and import include internal warehouses, which refer to internal clusters and internal sites. External warehouses are included in configuration object set: Warehousing - Warehouses (wh0080). This configuration object set is processed in export definition APP-III-B, after the export or import of the business partner data.

    • The configuration objects of this configuration object set include warehousing data of the Common package and some, but not all data of the Warehousing package.

      The complete warehouse export and import is included in configuration object set: Warehousing - Warehouses (wh0080), see above. Configuration object set: Warehousing - Warehouses (wh0080) is part of export definition APP III-B.

    • During the import of configuration object set: Common – Internal Warehouses tc0260, referenced Warehousing based classifications are not filled if they do not exist in the destination company. If multiple classifications exist for warehouses, this may result in multiple notifications in the import report.

    • The same applies to any referenced, not yet existing warehouses and business partners. To fill the warehouse fields that are not filled during the initial import, configuration object set: Common - Warehouse References Retrieval (tc0940rr) is included.

      To fill the business partner fields that were initially not filled, configuration object set: Common – Business Partner References Retrieval (tc0960rr) is included. Please refer to the spreadsheet in KB 2271146 for a list of the referenced fields.

  • Configuration object set: Common – Item Defaults (tc0280)

    • Planning – Item Planning Defaults (cprpd101)

      If the family item does not yet exist in the destination company, the family item is not filled during the import, and the other two family fields are left blank or given a default value, respectively. The family fields will be included in a future release, in which the Enterprise Planning configuration objects will become available.

  • Configuration object set: Common – Items (tc5000)

    In the APP-III-A export definition, only the item base data (table tcibd001) is included. The item data of the item subentities such as Item - Purchase, Item - Sales, and Item - Warehousing will be included in a future release.

  • Configuration object set: Business Partners and Related Data (tc0600)

    For each exported business partner and business partner role, the business partner contact data is exported as well. The contact data is included in the import.

    To fill the business partner and bank account fields that were initially not filled, configuration object set: Common – Business Partner References Retrieval (tc0960rr) is included.

    • Common – Buy-from Business Partners (tccom120)

      If any of the referenced business partner fields, such as the entry fields for prices/discounts, ship-from, or invoice-from data do not yet exist in the destination company, these fields are not filled during the initial import.

      If the purchase order type does not yet exist in the destination company, the relevant field is not filled during the import. The same applies to the document set.

      If the services trade value does not yet exist in the destination company, the buy-from role row is skipped, which is entered in the report.

    • Common – Invoice-from Business Partners (tccom122)

      If the pay-to business partner does not yet exist in the destination company, this field is not filled during the initial import.

    • Common – Pay-to Business Partners (tccom124)

      If any of the referenced bank accounts, such as the bank account and the VAT bank account, do not yet exist in the destination company, these fields are not filled during the initial import.

    • Common – Sold-to Business Partners (tccom110)

      If any of the referenced business partner fields, such as the entry fields for prices/discounts, ship-to, or invoice-to data do not yet exist in the destination company, these fields are not filled during the initial import.

      If the response type does not yet exist in the destination company, the relevant field is not filled during the import.

    • Common – Invoice-to Business Partners (tccom112)

      If the pay-by business partner does not yet exist in the destination company, the relevant field is not filled during the initial import.

    • Common – Pay-by Business Partners (tccom114)

      If the referenced bank account does not yet exist in the destination company, the relevant field is not filled during the initial import.

  • Configuration object set: Common - Contacts (tc061)

    • Common – Contacts (tccom140)

      If any of the referenced contacts, such as the reports-to and the assistant do not yet exist in the destination company, these fields are not filled during the initial import. To fill the fields that were initially not filled, configuration object set: Common - Contact References Retrieval (tc0950rr) is included.

  • Configuration object set: Order Management – Sales Master Data (td0120)

    • Order Management – Sales Order Types (tdsls094).

      If the referenced warehousing order type does not yet exist in the destination company, this field is not filled during the initial import. To fill the fields that were initially not filled, configuration object set: Order Management - Sales Master Data - References Retrieval (td0951rr) is included.

  • Configuration object set: Financials – Basic Master Data (tf0010)

    • Financials - Years and Periods (tfgld005)

      Years that are already present in the destination company are skipped during the import.

  • Configuration object set: Financials - Ledger Account Related Master Data (tf0070)

    • Financials - Transaction Templates (tfgld012)

      The target company validation is bypassed during the import.

  • Configuration object set: Financials - Tax Related Master Data (tf0110)

    • Financials - Posting Data for Multiple Tax Codes (tfgld070)

      Tax codes by country for which posting data exist in the destination company are skipped during the import.

  • Configuration object set: Financials - Bank Master Data (tf0150)

    • Financials - Bank Branches (tfcmg011)

      If the referenced bank guarantee costs set does not exist in the destination company, the field is not filled during import.

      If the referenced business partner does not yet exist in the destination company, the field is not filled during import. To fill the business partner fields that were initially not filled, configuration object set: Common – Business Partner References Retrieval (tc0960rr) is included.

  • Configuration object set: Warehousing - Parameters (wh0010)

    • Warehousing – Inventory Handling Parameters (whinh000)

      If any of the referenced priority definition or cross-dock restriction definition fields do not yet exist in the destination company, these fields are not filled during the import. To fill the fields that were initially not filled, configuration object set: Warehousing - Inventory Handling Parameters - References Retrieval (wh0910rr) is included.

  • Configuration object set: Warehousing – Cross-docking (wh0060)

    • Warehousing – Priority Definitions (whinh620)

      If the referenced field value does not yet exist in the destination company, the field value is not filled during the import. To fill the fields that were initially not filled, configuration object set: Warehousing - Planning Priority Rules - References Retrieval (wh0920rr) is included.

    • Warehousing – Cross-dock Restriction Definitions (whinh650)

      If the referenced warehousing order type does not yet exist in the destination company, this field is not filled during the import. To fill the fields that were initially not filled, configuration object set: Warehousing Cross-dock Restriction Rules - References Retrieval (wh0930rr) is included.