I have talked about the Dispute management usage and the creation of dispute case in Part 1 of this series. This document talks about the configuration steps that need to be completed to start usage of dispute management
Configuration Steps for starting the Dispute Management
The setting of dispute management is a simple process and can be done quickly. The below process flow broadly defines the steps to set up Dispute Management in a system:
Create RMS ID
The term RMS stands for Record Management System. The RMS ID controls the visibility of the various elements for a dispute case and the element types which can be used. Generally, the below RMS ID are defined depending on the Applications used in the SAP System:
1. UDM_DISPUTE – This RMS ID is used in integration with AR component of the Financials
2. UDM_FICA_DISPUTE – This RMS ID is used in integration with Contract Accounting Payables and Receivables
We can change the values here.
Create Element Type
The element type are defined in this step.
A new element type can be created or modified. There are three tabs, Properties, Connection Parameter value and Classification
Create Attribute Profile
The attribute profile allows to define the attributes which can be used on a dispute case. All these parameters are defined in an attribute profile. The system also provides the flexibility to set up the maintenance and display properties for each of the attribute. The standard attribute profile is FIN_DISP.
Now select the Attribute Profile and select the Attribute Group
In the above attribute profile, you can see the various attributes which are available. You can add your own attributes as well and set the maintenance and display usage of each of the attribute. There are three steps involved in defining an attribute. They are:
a. Attribute Profile
b. Attribute Priority
c. Escalation Reason
The steps for attribute profile are already listed above. The path for defining attribute priority are as under:
The path for defining the escalation reason are as under:
After the creation of the escalation reason, the same is assigned to an attribute profile. There is also a functionality to include custom attributes as well. The customer include CI_UDMCASEATTR00 in Table UDMCASEATTR00 can be used for attributes from AR.
Case Search Profile
A case search profile allows to search for a dispute case. Defining a case profile allows to define the layout for case search, fields for selection screen and fields which can be modified. FIN_LOC is the most common case search profile. For a case search profile to be used, it is assigned to a case type. Once the case search profile is assigned to a case type, the parameters of a case search profile flow into a dispute case, based on the case type used.
There are two config steps:
1. Selection Fields
2. Modifiable Fields
Depending on the business requirements, the selection and modifiable fields can be decided for a case search profile.
The function profile defines what kind of functions or activities can be performed for a dispute case. The configuration menu for Function profile is as under:
The function profile is assigned to a specific case type. Once the dispute case is created, the allowed functions are called up depending on the case type used for creation of Dispute Case. The function profile FIN_DISP is the most common function profile which is used for Dispute Management Configuration.You can also define your own functions and than call them through an implementation of BADI, SCMG_CASE_FCODE_ S.
The next step in the configuration for Dispute Management is to create the text id. The Text Id are grouped together in a text profile. The text profile is in turn assigned to the Case Type. The text id define a heading for a note which defines its purpose and use.
I would continue with the configuration steps in the final document in this series.