Ansicht
Dokumentation

CRMVC_CMDC_MAP - Define ERP Dispute Case Integration

General Data in Customer Master   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

In this Customizing activity, you define ERP dispute case integration by mapping Dispute Management to the CRM back-end system.

1. Set the Remote Function Call (RFC) destination.

2. Map the Case Type (back-end system) to the Transaction Type (CRM system). The Case Type is unique.

3. Assign the Note ID to the Transaction Type.

4. The Code Group Profile for Subject Profile and the Code Groups profile are only displayed in the Define ERP Dispute Case Integration view cluster. Maintain subject profiles in Customizing under Customer Relationship Management → Transactions → Settings for Complaints → Settings for Subjects.

5. Map the CRM Reason for Case code to the FI-CA: Internal Reason code in the back-end system.

6. Assign the Reason for Case code and the FI-CA: Internal Reason code to the Subjectcode.

7. Map the back-end Priority code to the CRM Priority code and check the Description.

8. If you want to replicate escalation reasons to the ERP system, enable the escalation reasons to be replicated based on the dispute profile being used. By default, escalation reasons are not transferred to ERP.

9. If you have enabled the replication of escalation reasons in the previous step, assign the escalation reasons maintained in CRM to the escalation reasons in ERP by entering catalog, code group and code as well as the corresponding escalation reason code from ERP. A reason in CRM is represented by the combination of catalog, code group, and code (also called subject code). The ERP escalation reason is 2 digits long; the subject code in CRM is 4 digits long.

Fill RESBD Structure from EBP Component Structure   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 2466 Date: 20240523 Time: 161338     sap01-206 ( 49 ms )