Hierarchy
SAP_AP (Software Component) SAP Application Platform⤷
AP-PRC-PR (Application Component) Pricing⤷
PRICING_CUSTOMIZING_C (Package) Customizing for Pricing
IMG Activity
| ID | CRM_PRI_PFLEGSYST | Determine System for Maintenance |
| Transaction Code | S_A2C_40000181 | (empty) |
| Created on | 20001017 | |
| Customizing Attributes | CRM_PRI_PFLEGSYST | Determine System for Maintenance |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | CRM_PRI_PFLEGSYST |
Condition records can be maintained in the R/3 or CRM System. You can determine which system is used. To do this, maintain the table MNTCNT in the R/3 System using the transaction SM30 as follows:
- No entry means that everything is maintained in the R/3 System.
- If you enter a condition type/table, this is maintained in the CRM System. Usage and application as well as the logical CRM System should be entered. Maintenance in R/3 is not possible.
- Condition types that only exist in the CRM System need not be entered. However, they can be maintained in the CRM System.
Your entries can be replicated in the CRM System during the Customizing download in the table /SAPCND/T681M for display.
Changes in the current system are possible but they are critical. You must note the following:
- Before changing the table MNTCNT, the data in the CRM and R/3 Systems must be consistent.
- When maintaining the table MNTCNT (or making changes in the table /SAPCND/T681M by exchange), you cannot implement condition maintenance.
- There is currently no general exchange of condition master data from CRM into the R/3 System.
- When moving maintenance from CRM into R/3, note: At the start of an initial master data download from R/3 into CRM, all entries in the target table in CRM are deleted if they can be maintained in the Customizing setting in R/3. This means records that don't exist in R/3 can go missing.
If there is an entry for the condition type in the table MNTCNT, the condition records are not taken into account in the condition record download (Example: You maintain the condition records for the condition type PR00 and table xxx in CRM and make an entry in table MNTCNT. Then when you download the condition records from the R/3 System into the CRM System, there are no data records for condition type PR00, table xxx).
The whole process for controlling maintenance using the table MNTCNT in the R/3 System is activated during the first object download for the object class CONDCUSTOMIZING.
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 | CRM_PRI_PFLEGSYST | 0 | PFC0000020 | Pricing |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20010503 |
| SAP Release Created in | 20C |
