Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
SD-MD-CM (Application Component) Conditions⤷
CND_EXCHANGE_GENERAL (Package) Exchange Conditions General
IMG Activity
| ID | R3CRMDATAUS | Data Exchange Conditions |
| Transaction Code | S_AXA_22000019 | (empty) |
| Created on | 20021114 | |
| Customizing Attributes | R3CRMDATAUS | Data Exchange Conditions |
| Customizing Activity | R3CRMDATAUS | Data Exchange Conditions |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | R3CRMDATAUS |
Use
Determine System for Maintenance
Condition records can be maintained in the ERP or CRM system; you can decide which to use. In this activity you determine the maintenance system as follows:
- No entry means that everything is maintained in the ERP system.
- If you enter a condition type or condition table, it will be maintained in the CRM system. The use, application, and the logical system of the CRM system also needs to be specified. Maintenance in the ERP system is not possible.
- You do not need to enter condition types that only exist in the CRM system. They can be maintained in the CRM system in any case.
- In the CRM system your entries will be replicated by the Customizing download in table /SAPCND/T681M for display.
Changes in the running system are possible but are critical. You should note the following:
- Before you make changes to table MNTCNT you must ensure that the data in the CRM system is consistent with the data in the ERP system.
- Condition maintenance cannot be carried out while table MNTCNT is being maintained (or whilst changes are being made to table /SAPCND/T681M by exchange)
When shifting maintenance from CRM to ERP, you should note the following: At the beginning of an initial master data download from the ERP system into the CRM system, all entries in the target table of the CRM system, which according to the settings in Customizing can be maintained in the ERP system, will be deleted. This means that records that do no exist in the ERP system could be lost.
If there is an entry for a condition type in table MNTCNT, the condition records for it will not be taken into account in the download of condition records (Example: You want to maintain the condition records for the condition type PR00 and table xxx in the CRM system and so you make an entry in table MNTCNT. This means that in the download of condition records from the ERP system to the CRM system, there are no data records for the condition type PR00, table xxx).
The entire controlling of maintenance using table MNTCNT in the ERP system is activated by the first initial download of an object from object class CONDCUSTOMIZING.
Requirements
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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 | R3CRMDATAUS | 0 | AXA0000014 | CRM Content |
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 |
| MNTCNT | S - Table (with text table) | SM30 |
History
| Last changed by/on | SAP | 20021114 |
| SAP Release Created in | 2003_1_470 |
