Cannot log dispute in FBL5N after entering wrong RMS ID Error in called SP Client

[Former Member]

My user tried to enter a dispute case from FBL5N before she had set her RMS ID to UDM_DISPUTE for the first time. She got the error: Error in called SP Client. She then went to UDM_DISPUTE and when prompted for the RMS ID, she entered her SAP User ID....which of course failed. Then she called IT support. I told her how to set her RMS ID properly, but she is still getting the Error in called SP Client from FBL5N. And, she cannot log a dispute in UDM_DISPUTE either. There she gets

Could not save record (no authorization)
[Details, see application log ...where is this log? AND - she also sees Unexpected error in SP client after that. It seems she has herself corrupted now and I'm at a loss on how to unwind this. I've tried changing her RMS ID and changing it back...no help. I've had Security check her authorizations and they are good. Any advice is appreciated!

-Lori

[pablo_lozano]

Have you checked SAP KBA 2406490 - Dispute Case XXX: Error in Called SP Client (Message FDM_GENERAL100) ?

Could you please share the error message IDs and numbers? Is this happening for more users or just the one?

[Former Member]

Hello Pablo, thank you for your response. My user doesn't get this far - although they are seeing that Error in call SP Client message in FBL5N. It is only happening with the one user who attempted to save the dispute case from FBL5N before setting the RMS ID. The message in FBL5N is

Error in Called SP Client

Message No. UDM_MSG008

When trying to create a case in UDM_DISPUTE - first comes:

Could not save record (no authorization)
[Details, see application log]

Then this:

Unexpected Error in SP Client - with no message ID underneath that.

Thanks!

-Lori

[pablo_lozano]

If you are running on SAP_BASIS 700, I would ask you to check SAP note 935484 - "Creating dispute case: Error in SP client"

If this does not solve the issue, I would ask you to open a ticket for component FIN-FSCM-DM and provide the user credentials so we can reproduce the issue in your system and further analyse it.