Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
AP-MD-PRO (Application Component) Central Part of Product Master⤷
COM_PRODUCT_CUST (Package) Product Master Customizing - General
IMG Activity
| ID | COM_PRODUCT_MAPLOG | Assign Logical Systems |
| Transaction Code | S_AEC_66000480 | (empty) |
| Created on | 20010306 | |
| Customizing Attributes | COM_PRODUCT_MAPLOG | Assign Logical Systems |
| Customizing Activity | COM_PRODUCT_MAPLOG | Assign Logical Systems |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | COM_PRODUCT_MAPLOG |
In order to transport categories and hierarchies from one system to another, you need to map the logical systems involved.
In this activity, you specify the logical systems of the source and target systems you are using.
Example
You want to transport categories from your test system <SYSTEM_TEST> to your production system <SYSTEM_PROD>.
Case 1
You have created the categories in your test system. They therefore have the logical system <SYSTEM_TEST>. So that the categories can also be changed once they have been transported into the production system, the categories must have the logical system <SYSTEM_PROD> in the target system.
Maintain the following entry:
Source <SYSTEM_TEST>
Target <SYSTEM_PROD>
The logical system of the categories will be changed from <SYSTEM_TEST> to <SYSTEM_PROD>.
Case 2
You have replicated categories from your backend/MDC system R3_TEST to your test system <SYSTEM_TEST>. The categories therefore have the logical system R3_TEST.
If your production system is also connected to this backend system, the logical system must not be changed during the transport.
Maintain the following entry:
Source R3_TEST
Target R3_TEST
Case 3
You have replicated categories from your backend/MDC system R3_TEST to your test system <SYSTEM_TEST>. The categories therefore have the logical system R3_TEST.
Your production system is connected to the backend/MDC system R3_PROD. This backend system is a copy of the system R3_TEST, that is, it has identical data.
Maintain the following entry:
Source R3_TEST
Target R3_PROD
During the transport, the logical system of the categories is changed from R3_TEST to R3_PROD. You can then download the categories from your backend/MDC system R3_PROD to your production system <SYSTEM_PROD>.
Case 4
You have replicated categories from your backend system R3_TEST to your test system <SYSTEM_TEST>. The production system <SYSTEM_PROD> is connected to the backend/MDC system R3_PROD. This backend/MDC system has different data than the backend/MDC system R3_TEST.
Therefore, do not transport the hierarchy containing the categories from R3_TEST. You can set up the categories in the production system by replicating the categories from the ERP/MDC System.
Specifics in EBP
If you have several backend systems connected to both your test system <SYSTEM_TEST> and your production system <SYSTEM_PROD>, make an entry in the table for each backend system (either as in case 2 or case 3, depending on whether the production system is connected to a backend system other than the test system).
Note
Generally more than one of these cases applies. For example, you have created categories in the system (case 1) and have also at the same time replicated categories from the ERP/MDC System (case 2 or 3). Then make several entries in the table. There must be an entry in the table for each logical system for which there are categories in your test system.
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | COM_PRODUCT_MAPLOG | 0 | A4C0000261 | Central Part of Product Master |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| COMV_LOGSYS_MAP | V - View | SM30 |
History
| Last changed by/on | SAP | 20040309 |
| SAP Release Created in | 30A |
