Dispute Management – Automatic Document Changes from Dispute Case
Dispute case in SAP system is a central repository which provides access to the necessary information to responsible person involved with resolving the dispute. There are different attributes in a dispute case which includes reason for the dispute, the dispute priority, dispute processor, dispute coordinator, dispute status, disputed amount etc. Most of the attributes in dispute case can be set automatically using configuration set up. This reduces manual processing.
As per business requirement, based on status, priority, reason code of a dispute case certain changes might be required in the accounting documents. This document contains the information and details about the process of Automatic document changes from dispute case. This document will help to understand the required configuration set up for the automatic document changes.
This for better illustration, dunning letters should not be triggered when approval is requested or confirmed for a dispute case, accordingly a dunning block should be updated in accounting document.
First step is to define triggering attributes for document changes as per the requirement. In defined scenario, a dunning block needs to be updated when dispute case status is “approval requested / confirmed”. Define the attribute as “Status” in below mentioned path
IMG – Financial Supply Chain Management – Dispute Management – Dispute case processing – Process Integration – Automatic Document Changes from Dispute case – Define Triggering Attributes for Document Changes
Select new entries and an add entry for required case type as mentioned below. STAT_ORDERNO is technical label for field “Status” in dispute case. Other parameters of dispute case like Priority, Reason, category etc. can also be used for automatic document changes as per the requirement.
Dunning block configuration should be defined as highlighted below –
IMG – Financial Supply Chain Management – Dispute Management – Dispute case processing – Process Integration with Accounts Receivables Accounting – Automatic Document Changes from Dispute case – Define Document Changes
Select new entries option and add an entry for company code and dispute case type as indicated below.
Select newly created entry and double click the “Selection of Fields” folder symbol in the area on the left as highlighted below
To add target field select option new entries and add an entry as highlighted below. Target field in mentioned configuration step is the field which needs to be updated automatically in accounting document from dispute case.
For mentioned scenario target field should be selected as dunning block. Source field should be a Case-status as defined in steps a and b. This will ensure that when case status is changed, dunning block should be updated. Other parameters such as payment block, payment method, reason code, planning level can also be configured as target fields. Multiple source fields can be defined for a target field.
Once source and target fields are defined, actual values for parameter dunning block should be defined. Select newly created entry and double click the determination of field values folder symbol in the area on the left as highlighted below and Enter the following values
As per the defined business scenario, dunning block “D” is set against case status “Approval – requested” and “Approval – confirmed
Save the entries and exit customizing activity.
Dispute case Example
Following example is to illustrate the automatic update of dunning block from dispute case.
Create a new dispute case Via FBL5N for an overdue item as highlighted below
When dispute case is created dunning block is not set in invoice document. As per the business requirement dunning block needs to be updated automatically for particular status only. For created dispute case, initial status is “New” and hence dunning block is not updated
For the newly created dispute case, change the attributes to check the configuration set in customizing. I.e. change dispute case status to Approval – requested and save the changes. For this status dunning block D is set-up in customizing.
Open the FI document and check the changes in the document. Dunning block D is updated in accounting document as per requirement
Change the Dispute case status to approval rejected and save the changes. For this status dunning block is not set up
Check dunning block status in invoice document –Dunning block is not updated as per configuration setting
Change the Dispute case status to Approval confirmed and save changes. For this status dunning block is set up in configuration
Check dunning block status in invoice document –Dunning block D is updated in the accounting document as per requirement
Document Change displays the dunning block log and current status correctly
Conclusion – As per the business requirement automatic document changes from dispute case can be defined in FSCM. This reduces manual efforts and it is useful to keep automatic track of events for disputed cases.