Dispute management- SAP
Dispute management- SAP
Public
Warning
This document has been generated from SAP Help Portal and is an incomplete version of the official SAP product documentation.
The information included in custom documentation may not reflect the arrangement of topics in SAP Help Portal, and may be
missing important aspects and/or correlations to other topics. For this reason, it is not for production use.
This is custom documentation. For more information, please visit SAP Help Portal. 1
2/5/25, 10:02 PM
SAP Dispute Management allows agents to handle dispute cases with adequate information, following an optimized workflow.
SAP Dispute Management is based on the case management process of SAP, and a dispute case can be work-flowed through a
business for resolution.
The aim of SAP Dispute Management is to provide agents with an FI integrated tool to efficiently solve disputes with customers
involving all stakeholders in an automated way.
This page is created to help you to find quick and adequate answers to your questions related to SAP Dispute Management.
Useful Links
A Dispute Case is created and then can be work-flowed through a business for resolution.
Links can be made to 3rd party information, business rules can be applied so certain dispute types are automatically credit'ed, or
moved to certain users for resolution.
The core reporting occurs in BI, however it integrates very well with SAP Collections Management and SAP Biller Direct.
The aim of the module is to record the dispute in a single system to allow all business users to have access to the same
information and work together to resolve the dispute as quickly as possible to improve cash flow, and reduce the DSO.
Workflow is a key part of controlling the dispute management process. Disputes will be created and then passed out to different
business users for approval or more information. The key to this process is ensuring that workflow is used at the correct time in
the process.
The main transaction code in Dispute Management is UDM_DISPUTE, which leads to the following screen:
This is custom documentation. For more information, please visit SAP Help Portal. 2
2/5/25, 10:02 PM
Find Dispute Case: This provides you with several options to filter the existing dispute cases and find the one you are looking
for
My Dispute Cases: This shows a list of the dispute cases in which the user is the processor of the dispute case
And, under Record and Case Record Management, you can go to the Modeler for Case Records in SAP Dispute Management,
where you can create your own Case Records model, to add different documents to your dispute cases. SAP recommends that, in
case a custom model is created, this new model is based on a standard model.
The available fields, and these being optional or required, as other options, can be customized in SPRO, SAP Reference IMG,
Financial Supply Chain Management, Dispute Management, Dispute Case Processing, Case Types, attribute profile. Here you can
modify the case types and its names, case records management models, attribute profile, function profile, status profile, text
profile, RMS_ID, element types, interval number ranges, the process and the action profile.
In SPRO, under Financial Supply Chain Management, Dispute Management, Dispute Case Processing, Attribute Profile and Create
Attribute Profile, you can modify the mentioned available fields, which can also be divided in several attribute groups, and be set as
required, invisible, or, among other option, configure a dropdown with the available options.
This is custom documentation. For more information, please visit SAP Help Portal. 4
2/5/25, 10:02 PM
ANST Replicate a transaction or program and get a trace with all the Note 1818192. Available as of release 740 SAP Basis
ABAP objects used/executed during the replication. Once the Component and included in Support Package in
Automated Note
trace is generated, you have the options to: releases 700, 701, 702, 731
Search Tool
1) Search for SAP Notes.
2) Problematic Custom Coding.
3) Missing Customizing Entries.
4) List of ABAP objects to start debugging.
PANKS A new button has been added to the Performance Assistant in Note 2096401. Released with note 2020356 and
order to enable context sensitive SAP Notes and KBAs search. included in Support Package in releases 700, 701,
702, 710, 711, 730, 731, 740 of SAP Basis
Component.
Debugging with a Can´t enter /h at a pop up. 'Generate a Short Cut' , (Type: Available In R/3
shortcut 'System Command', Command: '/h', Location 'Desktop').
Drag and drop the icon from your desktop to the pop up.
RKSE16N_CD When entries in tables are changed using SE16N, the system Available In R/3
writes change documents. Report RKSE16N_CD helps to
This is custom documentation. For more information, please visit SAP Help Portal. 5
2/5/25, 10:02 PM
know if some entry was manually changed in a table.
SE91 Where used list for a message number helps to display the Available In R/3
"suspicious" code to start root cause analysis when
debugging isn´t possible.
[PAT03] This table contents the date when a system was upgraded to Available In R/3
some support package. SE16, table PAT03, enter SAPKH* for
field 'PATCH', execute, display field 'IMPLE_DATE'.
How we search Best search strategy for notes and KBAs KBA 2172375
[VIDEO]
Check the Guided Answers Tool of SAP Collection Management to find quick answers.
This is custom documentation. For more information, please visit SAP Help Portal. 6