Ansicht
Dokumentation

CRMVC_ARD_CONTEXT_D - Assign Reason Codes for Transaction Types and Context

CRMVC_ARD_CONTEXT_D - Assign Reason Codes for Transaction Types and Context

Addresses (Business Address Services)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity you can define default dispute reasons for each transaction type and context. The settings that you make here only refer to the configuration of the Web Client UI configuration.

The context defines the environment in which a dispute is generated or edited. A dispute can be generated directly from the Dispute Management application. It can also be generated or edited from the bill or BDR display or the FI-CA documents display. The context is predefined by SAP and has the following features:

  • Context key 1000: Create or edit a dispute from Dispute Management
  • Context key 2000: Create or edit a dispute from the bill or BDR display
  • Context key 3000: Create or edit a dispute from an FI-CA document.

You can define transaction types for which you want to record dispute reasons within the selected context. All transaction types that you maintained in the Customizing activity for admissible transaction types in Dispute Management are available for selection under Customer Relationship Management → Cross-Industry Functions → Dispute Management and Adjustment Requests → Settings for Dispute Management → Define Profiles, Admissible Transaction Types and Linkages.

A transaction type can only be used once within each context. However, it can be used in more than one context. A transaction type can be defined as a standard transaction type for the default selection in the dropdown box in the Web Client UI. If no default setting is made, you can make your own entry in the dropdown box.

You can enter dispute reasons for each transaction type and context. You can select reasons from those recorded in the C2 catalog. You can enter your own dispute reasons by adding them to the C2 catalog.

You can make these settings in Customizing under Customer Relationship Management → Cross-Industry Functions → Dispute Management and Adjustment Requests → Settings for Dispute Management → Assign Reason Codes for Transaction Types and Context.

You can define a standard dispute reason as a default entry in the dropdown box in the Web Client UI. If no default entry is made, you can make your own entry in the dropdown box.

You have defined the admissible transaction types for Dispute Management.

Note that you define the admissible transaction types for a specific profile. If you have not assigned the corresponding profile, for which you have defined the transaction type, to your role, the transaction types defined in this profile are not available on the UI for entry or editing in Dispute Management, even if they have been maintained correctly in this Customizing activity.

SAP supplies the "DEFAULT" profile.

  1. Select the context required.
  2. Define the transaction types that are to be displayed on the UI for the respective context and define any default transaction type required.
  3. Define the dispute reasons to be displayed on the UI for the respective transaction type selected and any default reason required.
Context Transaction Type Dispute Reason
1000 CMDC 0001
1000 CMDC 0002
1000 CM0C 0001
2000 CMDC 0013
2000 CMDC 0014

In the following example Customizing settings, you can select the transaction types CMDC and CM0C if the dispute is created directly from Dispute Management. However, you can only select the dispute reasons 0001 and 0002 for the transaction type CMDC. If the transaction type CM0C is selected to create the dispute, you can only use dispute reason 0001.

If the dispute is created from the bill or BDR display, you can only use transaction type CMDC and the dispute reasons 0013 and 0014.






Fill RESBD Structure from EBP Component Structure   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 4698 Date: 20240523 Time: 170410     sap01-206 ( 83 ms )