SAP FSCM Dispute Management Configuration Guide
SAP FSCM Dispute Management Configuration Guide
Dispute Management
Configuration Guide
1 of 38
7/7/2022
Dispute Management: Configuration Guide
Contents
1 Dispute Management............................................................................................................... 4
2 Purpose................................................................................................................................... 4
3 Preparation.............................................................................................................................. 4
3.1 Prerequisites.................................................................................................................. 4
3.2 Check - Reason Codes................................................................................................. 4
4 Customizing............................................................................................................................. 5
4.1 Make settings in Accounting.......................................................................................... 5
5 Customizing in the Application component – Dispute Management........................................5
Dispute Management – Customizing areas.................................................................................5
5.1 Create RMS ID.............................................................................................................. 5
5.2 Element type and Case Record Model..........................................................................7
5.2.1 Create Element type.................................................................................................. 7
5.2.2 Create and Process Case Record Model..................................................................8
5.2.3 Create Element type for Case Record.....................................................................19
5.2.4 Assign Logical System to Element Types for SAP Business Objects......................22
5.3 Attribute Profile............................................................................................................ 22
5.3.1 Create Attribute Profile............................................................................................22
5.3.2 Create Alternative Input Help for Attributes.............................................................24
5.4 Case Search................................................................................................................ 24
5.5 Function Profile............................................................................................................ 24
5.5.1 Customer-Specific Functions...................................................................................24
5.5.2 Create Function Profile............................................................................................24
5.6 Text Profile.................................................................................................................. 26
5.6.1 Configure Text IDs.................................................................................................. 26
5.6.2 Create Text Profile.................................................................................................. 26
5.7 Status Management.................................................................................................... 27
5.7.1 Create Status Profile...............................................................................................27
5.8 Number ranges............................................................................................................ 28
5.9 Case Types................................................................................................................. 29
5.9.1 Define Case Types.................................................................................................. 29
5.9.2 Preliminary Check................................................................................................... 31
5.9.3 Create values for Attribute Category.......................................................................32
2 of 38
7/7/2022
Dispute Management: Configuration Guide
3 of 38
7/7/2022
Dispute Management: Configuration Guide
1 Dispute Management
Dispute Management application enables to resolve customer disputes over receivables more
effectively. Fully integrated with other SAP financial management applications, Dispute
Management application can help to improve the tracking and processing of short payments,
streamline accounts receivable processes, and enhance customer relationships.
Dispute Management is a part of SAP Financial Supply Chain Management (SAP FSCM)
applications. As one of the new key functional areas of mySAP ERP, SAP FSCM optimizes the
financial and information flows within a company and between business partners. It helps
companies to reduce sales days outstanding, to save time and costs and improve customer
relationship management. It enables cross-department dispute resolution and streamlines the
entire dispute management process.
2 Purpose
This configuration guide summarises the configuration activities relating to Dispute Management.
3 Preparation
3.1 Prerequisites
Organizational Structure
Financial Accounting Application is active
Legend:
Check box C -> Charge off difference
Check box D -> Relevant to dispute management
4 of 38
7/7/2022
Dispute Management: Configuration Guide
4 Customizing
Notes Guidelines
To use SAP Dispute Management, customizing has to be carried out in two different SAP
Components namely (I) Accounts Receivable Accounting (FI-AR) or Contract Accounts
Receivable and Payable ( if FI-CA application is used) and (II) in Financial Supply Chain
Management Dispute Management.
Note: Before the customizing in the application component ‘Process Integration with Accounts
Receivable accounting’ is commenced, the customizing tasks within the SAP Dispute
Management component must have been completed. Only after this the activation has to be done
in process integration area.
IMG nodes for DM
In this IMG activity RMS (Records Management Systems) ID has to be defined. In Dispute
Management RMS ID is used to control the visibility of element types and elements.
The standard delivery contains the following RMS ID’s:
UDM_DISPUTE -> this has to be used if the application component Accounts Receivable
Accounting (FI –AR) is used.
UDM_FICA_DISPUTE -> this has to be used if the application component Contracts
Accounts Receivable and payable (FI – CA) is used.
Activity:
Use RMS ID -> S_AREA_CMG.
6 of 38
7/7/2022
Dispute Management: Configuration Guide
7 of 38
7/7/2022
Dispute Management: Configuration Guide
The case record model identifies the types of objects that can be related to a case - financial
documents, customer or vendor master data, etc. It also has a logical structure that groups the
objects. SAP recommends copying the standard SAP-delivered model and then changing it to
meet customer needs instead of creating a case model from scratch.
The user has to carry out following Steps:
1. To access the Activity “Create a Case Record Model”, use the Transaction Code SCASE.
2. Note: The prerequisite for this Activity is completion of Activity -> Create RMS ID. So to check
whether the required RMS ID is available and the work area has been set to the required
RMS ID, the user has to select the button Change RMS and check whether the value shown
is “UDM_DISPUTE”.
8 of 38
7/7/2022
Dispute Management: Configuration Guide
4. In the Hierarchical view expand the node “Record and Case Record Models”.
5. Then select the node “Modeler for Case Records in Dispute Management”. Then do a right-
click on this and from the listed options click/select the option Find.
9 of 38
7/7/2022
Dispute Management: Configuration Guide
8. Standard Case Record Models and other case record models (if any) will be listed.
9. From the list select the entry with the short description “Dispute Management – with the
unique ID: UDM_ DISPUTE”: This is the SAP-delivered entry.
10 of 38
7/7/2022
Dispute Management: Configuration Guide
11. The standard case model “Dispute Management – with the unique ID: UDM_ DISPUTE” is
now listed in the display area in the lower left section of the screen.
12. Select the model, and from the menu, select Model -> Save as Local File.
11 of 38
7/7/2022
Dispute Management: Configuration Guide
13. In the popup window give the file name ‘model download’ and click on ‘Save’ button.
14. The standard model ‘Dispute management’ with the unique ID UDM_DISPUTE will get saved
to the local file.
12 of 38
7/7/2022
Dispute Management: Configuration Guide
15. Return back to the Hierarchical view and select the node “Record and Case Record Models”
and right-click on the node “Modeler for Case Records in Dispute Management” and select
the option ‘Create’.
16. In the toolbar menu of the Modeler select Model Load local file.
13 of 38
7/7/2022
Dispute Management: Configuration Guide
18. The model data stored in the local file will be uploaded now.
14 of 38
7/7/2022
Dispute Management: Configuration Guide
20. In the toolbar menu of the Modeler select the option Attributes for Record Model. This is the
button on the right side of the Save button. On the screen Change Attributes the first row is
for entering the Short description.
15 of 38
7/7/2022
Dispute Management: Configuration Guide
22. Once the short description is entered, then the next row is for ‘Generation of Unique ID’. We
can either assign our own value for “Unique ID” or click the “Generate Unique Identifier”
button so that the system can generate a “Unique ID”.
16 of 38
7/7/2022
Dispute Management: Configuration Guide
23. Once the Unique ID is generated then click on the button Continue (Enter).
24. In the toolbar of the Modeler, select the Save button (the one with the disc) and select “Save”.
The status as displayed in the Modeler will be displayed green (Status ‘Saved’).
25. The model Z_DISPUTE_MODEL is saved now and this can be used for further activities.
26. To display the model created now use the same procedures (Steps 5 to 9) and select the
model Z_DISPUTE_MODEL.
17 of 38
7/7/2022
Dispute Management: Configuration Guide
29. The model can be renamed using the same functionality of Change Attribute. Using this
original description Z_DISPUTE_MODEL has been changed to
Z_DISPUTE_UNDERPAYMENT as shown in the figure below.
18 of 38
7/7/2022
Dispute Management: Configuration Guide
In this activity user has to define one or more element types for the case records. There are
standard element types delivered by SAP namely UDM_SPS_CASE_RECORD, which has to be
used if the relevant application component is FI- AR -> Accounts Receivable Accounting or
UDM_FICA_SPS_CASE_RECORD, has to be used if the relevant Application component is FI-
CA -> Contract Accounts Receivable and Payable. As these two element types are standard
deliveries they cannot be used directly. The user has to create their own element types for case
records by using these standard element types as copy template.
To create their own element types for case records, the user has to carry out following
Steps:
1. Set the work area.
19 of 38
7/7/2022
Dispute Management: Configuration Guide
2. In the screen display of data relating to Registry: Customizing mode scroll down to reach the
standard deliveries relating to Case Record and select the node
SCMG_SP_CASE_RECORD.
3. Expand the node details and the user can see the standard deliveries one each for Customer
(UDM) and Vendor (UKM).
20 of 38
7/7/2022
Dispute Management: Configuration Guide
5. Select the function Copy to copy the standard element type to a user defined Element Type
for case record.
6. In the pop-up window change the Element type ID to one that starts with Z and also provide
the description for the Element type. By default the standard ID and its description will be
displayed.
7. Now the user can see that the new element type Z_UDM_SPS_CASE_RECORD has been
created.
21 of 38
7/7/2022
Dispute Management: Configuration Guide
9. Check the Connection Parameter Values and reset the required parameters.
5.2.4 Assign Logical System to Element Types for SAP Business Objects
22 of 38
7/7/2022
Dispute Management: Configuration Guide
3. The standard Attribute Profile which is relevant for Dispute Case Management is FIN_DISP.
4. This can be copied to create a user defined Attribute Profile and while doing the copy
operation the entire data content can be copied.
5. Now the new Attribute Profile has been created.
6. Select the option Assign Attribute to do the required modifications based on the User
requirement as the data is a copy from the standard Attribute Profile.
7. Note: This is an important activity. From the figure shown above it will be clear that the
Attribute Profile controls the display of the case record and the screen display when a case is
created from SAP Easy Access menu.
23 of 38
7/7/2022
Dispute Management: Configuration Guide
8. Note: The options relating to maintenance of Groups, Rows, Columns along with the control
feature for data entry as shown in the figure above has to be maintained based on the user
requirement for the Display of Case Record.
9. Once the required changes have been made the Attribute Profile ZFIN_DIS can be saved.
4. Same as Attribute Profile, the standard Function Profile has to be copied into user defined
profile.
24 of 38
7/7/2022
Dispute Management: Configuration Guide
5. For the newly created Function Profile ZFIN_DISP when the user selects the feature Allowed
Functions following values will be displayed.
6. For the newly created Function Profile ZFIN_DISP when the user selects the feature Allowed
Case components the following parameters will be displayed and based on requirement the
values can be maintained.
25 of 38
7/7/2022
Dispute Management: Configuration Guide
7. Note: The case type wherein this newly created Function Profile has been assigned will
provide the corresponding functions and display the relevant case components.
4. Same as other earlier Profiles, the standard Text Profile has to be copied into user defined
profile.
5. The values for the newly created Text Profile ZFIN_DIS are shown in the figure below.
26 of 38
7/7/2022
Dispute Management: Configuration Guide
27 of 38
7/7/2022
Dispute Management: Configuration Guide
4. Same as other earlier Profiles, the standard Status Profile has to be copied into user defined
profile.
5. The values for the newly created Status Profile ZFIN_DIS are shown in the figure below.
In this activity the user has to Define/Check availability of Number Range Interval for Case.
28 of 38
7/7/2022
Dispute Management: Configuration Guide
In this activity the user has to create a Case Type. For this the following steps have to be
followed:
1. When the transaction is selected system will list the details of the available Case types in the
system.
2. To have their own Case Type, user has to define a new one and for this the user has to
Select the New Entries push button and the screen will be displayed as shown below.
3. The user has to provide a name and for example for defining the Case Type relating to Under
Payments the name Z_UP can be given.
4. Then the values for each of the rows have to be defined.
5. RMS ID has to be set to UDM_DISPUTE.
6. Next, Element Type ID(Record) has to be defined and user has to select the Z element type
created earlier Z_UDM_SPS_CASE_RECORD and
7. Element Type ID(Case) has to be selected and user can select UDM_SPS_CASE.
8. Then Case record Model has to be defined and user has to select the Z Model created earlier
SRM_MOD02 FE391ADB50F3174B9482F9D8A9901DD7.
9. For all other fields though the standard values can be selected the best practice is to have the
user defined values.
10. In this document, intially standard values have been assigned to the case type as shown
below and were later replaced with user defined values.
29 of 38
7/7/2022
Dispute Management: Configuration Guide
11. The values for newly created profiles can be updated now in the new case type Z_UP and the
updated details are shown below
12. Now the user can Save the entries and the new Case type Z_UP for Underpayment is now
ready for further processing.
30 of 38
7/7/2022
Dispute Management: Configuration Guide
1. Execute the transaction and select the create function and choose the Underpayment Case
Type.
2. The user can see the Header data displayed as per the system set up.
31 of 38
7/7/2022
Dispute Management: Configuration Guide
32 of 38
7/7/2022
Dispute Management: Configuration Guide
33 of 38
7/7/2022
Dispute Management: Configuration Guide
34 of 38
7/7/2022
Dispute Management: Configuration Guide
35 of 38
7/7/2022
Dispute Management: Configuration Guide
36 of 38
7/7/2022
Dispute Management: Configuration Guide
37 of 38
7/7/2022
Dispute Management: Configuration Guide
38 of 38
7/7/2022