Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
AP-MD-PRO (Application Component) Central Part of Product Master⤷
COM_HIERARCHY_CUST (Package) Product Master Customizing - Hierarchy and categories
Basic Data
| Data Element | COMT_MATKL_MULTI_SYS |
| Short Description | Create Material Groups as Categories per Backend System |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | COM_BOOLEAN | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Mult.Bknds |
| Medium | 15 | Multiple Bcknds |
| Long | 40 | Create Material Groups per Backend Syst. |
| Heading | 60 | Create Material Groups as Categories per Backend System |
Documentation
Definition
When material groups are downloaded from several back-end systems, this indicator determines whether the material groups from the various systems are merged in the CRM/EBP system or whether the material groups are created separately for each system.
Use
The indicator is used as follows when material groups are downloaded from R/3:
- Indicator is set:
When material groups are downloaded from the ERP system the hierarchy R3MATCLASS is created with the following categories below the root category:
- Category R3MATLCASS + <logical ERP system>
All categories replicated from the ERP system are created below this category. - Category R3MATLCASS + <CRM logical system>
All categories created locally in the CRM System are inserted below this category. - If a download is performed from a second ERP system, a second category R3MATLCASS + <second logical ERP system> is created, below which all categories from this back-end system are created.
A new category will be created if it has already been replicated from the first ERP system and is then replicated from the second ERP system. This means there can be more than one category within the hierarchy R3MATCLASS with the same category ID but originating from a different system. To identify a category in the CRM/EBP System, the logical system is required in addition to the category ID.
This setting is recommended when the back-end systems connected are not synchronized and have different material groups.
- Indicator is not set (standard setting):
The logical system (origin) of the category is not taken into account during the download. A category ID can only occur once in the hierarchy R3MATCLASS.
For example, the material group 01 is replicated from the ERP system R3SYS1 with the following descriptions:
- German description: "Autos"
- English description: "Cars"
The category 01 is created in the CRM/EBP System in the hierarchy R3MATCLASS with these texts. Another category called 01 cannot be created in the CRM/EBP System.
A download is then performed from a second ERP system R3SYS2. The material group 01 also exists in this system and has the following descriptions:
- French description: "Automobile"
- English description: "Cars"
Another category is not created in the CRM/EBP System. Instead, the category 01 from the system R3SYS1 which already exists is overwritten with the data from material group 01 from the system R3SYS2 and the descriptions are merged.
The following texts then exist for category 01:
Categories which were only replicated from the system R3SYS1 and do not exist in R3SYS2 are not changed by the second download (nor deleted).
The indicator should not be set if only one ERP system is connected or all ERP systems connected have identical Customizing (the same material groups).
If the indicator is not set, material groups can be replicated from one back-end system, but products from several back-end systems. The products are then assigned to a material group category, irrespective of the logical system of the product concerned.
Dependencies
If you deactivate CRM in an EBP System (Customizing transaction Deactivate/Reactivate CRM-Specific Data in Enterprise Buyer System), this indicator will be set.
If you have already replicated material groups from an ERP system, the indicator can be changed as follows:
- If the hierarchy was created as under 1, you can only reset the indicator with report COM_HIERARCHY_CHANGE_MULTI_SYS. This will also delete the categories "R3MATCLASS + <logical system>". However, this report can only be executed successfully if there are no duplicate category IDs in the hierarchy.
- If the hierarchy was created as described under 2, you can set the indicator whenever required and the download will then be handled as described under 1.
Example
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in | 400 |
