RFDM2000: UDM_AUTOWRITEOFF: No document exist for dispute case

[sap_vijaykk]

Hello All,

AR user sets the escalation reason for a dispute case. Afterwards, we have a background job for the program UDM_AUTOWRTOFF, which in turn calls the program RFDM2000 to perform actual write off. For one of the dispute case, the job log says "no documents exist for dispute case" though they're still out standing. This is a case of offset where debit equals to credit.

Can you please advise on the issue?

Thanks,

VJ

[sap_vijaykk]

Hi b.petrushchak, Thanks for your response.

Following are the documents listed under the dispute objects. Customer Invoice & Credit Memo

I realized that during post processing of statement in FEBAN, user didn't specify the Reason code during on-account (customer) posting. It's corrected and the original dispute case has been voided. Thought it's going to solve the issue.

I'm still facing the same issue on the new dispute that's raised.

Auto Write-off has been successful in on other cases. Not sure what's happening on this one.

Thanks,

VJ

[Bohdan]

Hi sap.vijaykk,

So from what I see, you have an invoice and a credit memo / overpayment as a disputed objects. Do I understand correctly that the dispute case is created based on the overpayment, which is linked to the invoice ?

If yes, I think that's what might be causing the trouble. Normally, the dispute case is generated based on residual item which is generated because of underpayment. In that case when we do the posting, the system is writing off part of the original (underpaid) invoice in correspondence with the expense GL account maintained in the settings for write-off. Standard logic that SAP provided for the write off generates the posting:

Cr. Receivables (i.e. customer open item)

Dr. Expense GL account

In your case, you probably expect a different posting. Because if the customer overpaid, you will probably need not an expense account, but a revenue account i.e. the posting should look something like this:

Dr. Receivables (i.e. customer overpayment)

Cr. Revenue (i.e. other income)

Therefore my suggestion is the same. You need to debug the standard class CL_EX_FDM_AR_DISP_WRITEOFF, where the write off logic was implemented and check why it fail. Alternatively, check if there is implementation of BADI FDM_AR_DISP_WRITEOFF. Eventually, you might need to define a dedicated escalation reason for similar (overpayment) cases and implement separate logic via BADI.

Regards,

Bohdan

[Bohdan]

Hi sap.vijaykk,

What are the documents listed under the disputed objects ? Do you have there a residual item or a customer invoice ?

Normally, when you create a dispute case automatically (e.g. via background job for FDM3000), each dispute case is linked to a residual item or at least a customer invoice. Standard write-off logic is finetuned in such a way that it can easily write-off the residual item. But it checks a lot of things including tax categories of residual items, tax codes etc. You can check this logic out in a class CL_EX_FDM_AR_DISP_WRITEOFF.

But if you created the dispute case manually and did not link it to any object, in that case SAP does not know which customer's open item to write-off and clear.

So I'd suggest to check out the list of disputed objects, then debug the class CL_EX_FDM_AR_DISP_WRITEOFF, it has only one method, so it will not be complicated. Alternatively, check out if you have implemented BADI FDM_AR_DISP_WRITEOFF. If the BADI is implemented, standard class won't be triggered. So you'll need to debug the BADI implementing class.

Regards,

Bohdan