Dispute case ID no longer in cleared document visible

Hi,
we have voided a dispute case.
Now, when I go back into document display or through FBL5n I have no longer visibility of the case. How can that be?
The disputed FI document has been cleared. And the FI document is still visible as linked document in the case.
for reporting reasons and account overview I would need to see this.
What can I do?
Thanks + Regards
Hein

Are you saying you disputed an item.
Then you voided it
Then the item was cleared
If that is the case I believe everything is fine.
You will always be able to see a voided dispute - you can use the status to remove it from reporting
By voiding the item - the AR data will no longer link back to the dispute. This allows the AR item to be disputed again.
Hope this helps

Similar Messages

Dispute Case - Paid amount shown in 'Cleared Manually' field

Hi
I am configuring dispute mnagement. When I pay an invoice using standard incoming payments transaction F-28, then the dispute case status changes to CLOSE, but the amount paid is being shown in the 'Cleared Manually' field rather than 'Paid' field. What is the cause of this issue and how can this be fixed?
Thanks

I used case record model UDM_DISPUTE as a copy template. It had following structure nodes: Business partner, Disputed objects;Resolved objects;Items assigned during clearing; Other objects;and Various.
Now, amongst these I cannot see anything which says 'Paid' and Cleared Manually' . Could you elaborate which values would have been copied incorrectly in your opinion?I am testing a full payment scenario and not Residual or Partial payment.

Automatic Write-off Document in Dispute Case

Hi,
I was wondering once the dispute case is automatically written off, should the financial document should be updated in the dispute case, because technically the write off document is the resolved object in the dispute case.
When i performed automatic write off, the accounting document is not updated anywhere in linked objects in any sub folder, however the dispute case was confirmed.
Should it update or is there something needs to be done to update in the dispute case?
Thanks.
Jen

Hi Mark,
Thanks for your reply. In auto status changing, I dont have the option other than defining status for automatic reopen, written off and close. I did check the status, but its not relevant.
Here is what I am looking for, the automatic written off accounting document should be available or updated under resolved objects under linked objects.
Thanks in advance
Jen

Table for Dispute case ID and accounting document number

Hi,
For a given dispute case ID (EXT_KEY) I am unable to find the corresponding accounting document number ( BELNR ) for this dispute case. I am able to see the accounting document for the dispute case on the transaction UDM_DISPUTE but then I am not finding the same in any tables. Can anyone let me know in which table can I find the relationship to determine this. Thanks in advance.
Rgds,
Sowmya

Hi Sowmya,
check the table UDMCASEATTR00.it contains all the details about disputemanagement
please reward poitns if helpful

How to relate dispute case for a AR document

Hi Gurus,
I have a requirement to change the reason code change date of dispute case(DIspute management) for the related AR document.
Basically i am posting a AR document through BAPI. Now i wanted to take the last dunned date(MADAT) and find the related dispute case after that change the reason code change date using last dunned date.
so my question how to relate relevent dispute case for the AR document?
Thanks advance.
Regards,
Radhakrishna.

Hi.............
Better and simplest way you can get it through a simple qury report. Create a query by joining two tables ODLN and OINV. OINV's docdate means the closing date of delivery challan.
Regards,

Dispute Case - Additional Documents Attachment

Hi Experts
During the creation of dispute Case we have a requirement to Store attachments ( PDF, XLS or Word files) of customer business with Dispute case itself.
Can we utilize the Note functionality or Services for object?
In either cases where does SAP Stores the Documentation ? more details.... please
Please reply accordingly
Thanks
Regards,
Meenakshi.N

this is available as standard.
In the dispute - linked objects - the last tab various you can add a document.
you need to make sure you define the document type in the config screen "Define Document Category for Attachments to Dispute Cases"

Dispute case with parked document

Hi,
Does anyone know if it's possible to create a dispute case from a parked document?
Thanks,
CC

Hi,
Parked documents concept in SAP is only for managment approval.
You can park any kind of document before simulating.
If you want to send dispute case to management approval then go for parking or else you can post directly.
Thanks
Chandra

Dispute Case:UDM_Dispute Attach document

Dear All
We want to attach document to dispute case. We know attachment function available when someone open the dispute case from inbox but in this way only a person who is assigned as processor can assign the document to dispute case. But if someone other than processor wants to assign any document from UDM_Dispute.
Thanks and Best Regards
Farhan Qaiser

Are you asking how to add an excel spreadsheet into a dispute or something like that?
It is fairly simple,
This is done via linked objects.
In the other folder, you can add attachments.
There is config to be defined for the file type i.e. pdf, or xls.
Document types for Attachments for Dispute cases is the config task.

BAPI Needed of uploading document in already existing Dispute Case

Hi,
I need BAPI for uploading document in already existing Dispute Case...
Thanks,
Ajit

I tried to use the following program to upload a document and it is not working, any feedback would be helpful:
*& Report ZTEMP_DISPUTE_12
REPORT ztemp_dispute_12.
PARAMETER : l_fname TYPE char255.
DATA : l_file TYPE string,
      lv_xstring TYPE xstring,
       l_return TYPE bapiret2,
       l_filecontent TYPE bapiconten,
       i_case TYPE REF TO if_scmg_case_api,
        l_initial_dir     TYPE string,
        l_window_title    TYPE string,
        l_filename_disp   TYPE string,
        l_filename_string TYPE string,
        l_user_action     TYPE i,
        l_rc              TYPE i,
       l_v_lines TYPE i,
       l_mime TYPE skwf_mime,
       l_filelength TYPE i,
       l_component TYPE bapidoccomp,
       l_skwf_filnm TYPE skwf_filnm,
       li_file_tab        TYPE filetable,
       lwa_file_tab        TYPE file_table,
       li_bin_content TYPE STANDARD TABLE OF bapiconten,
       l_v_size TYPE i.
DATA: BEGIN OF itab OCCURS 0,
       line TYPE sdok_sdatx.
DATA: END OF itab.
DATA: BEGIN OF i_component OCCURS 0,
        comp_count TYPE bapipos,
        comp_id     TYPE bapidocid,
        mimetype    TYPE bapimimetype,
        comp_size   TYPE bapipos,
        binary_flag TYPE bapigsbool,
        comp_num    TYPE bapipos.
DATA: END OF i_component.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR l_fname.
l_window_title = 'Upload Document'(001).
Call the file selection dialog
CALL METHOD cl_gui_frontend_services=>file_open_dialog
    EXPORTING
      window_title            = l_window_title
      initial_directory       = l_initial_dir
    CHANGING
      file_table              = li_file_tab
      rc                      = l_rc
      user_action             = l_user_action
    EXCEPTIONS
      file_open_dialog_failed = 1
      cntl_error              = 2
      error_no_gui            = 3
      not_supported_by_gui    = 4
      OTHERS                  = 5.
IF sy-subrc = 0.
    READ TABLE li_file_tab INTO lwa_file_tab INDEX 1.
    IF sy-subrc = 0.
      l_file = lwa_file_tab-filename.
      l_fname = lwa_file_tab-filename.
    ENDIF.
ENDIF.
START-OF-SELECTION.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                      = l_file
FILETYPE                      = 'ASC'
HAS_FIELD_SEPARATOR           = ' '
HEADER_LENGTH                 = 0
READ_BY_LINE                  = 'X'
DAT_MODE                      = ' '
CODEPAGE                      = ' '
IGNORE_CERR                   = ABAP_TRUE
REPLACEMENT                   = '#'
CHECK_BOM                     = ' '
VIRUS_SCAN_PROFILE            =
NO_AUTH_CHECK                 = ' '
IMPORTING
FILELENGTH                    =
HEADER                        =
    TABLES
      data_tab                      = itab
EXCEPTIONS
FILE_OPEN_ERROR               = 1
FILE_READ_ERROR               = 2
NO_BATCH                      = 3
GUI_REFUSE_FILETRANSFER       = 4
INVALID_TYPE                  = 5
NO_AUTHORITY                  = 6
UNKNOWN_ERROR                 = 7
BAD_DATA_FORMAT               = 8
HEADER_NOT_ALLOWED            = 9
SEPARATOR_NOT_ALLOWED         = 10
HEADER_TOO_LONG               = 11
UNKNOWN_DP_ERROR              = 12
ACCESS_DENIED                 = 13
DP_OUT_OF_MEMORY              = 14
DISK_FULL                     = 15
DP_TIMEOUT                    = 16
OTHERS                        = 17
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
DESCRIBE TABLE itab LINES l_v_lines.
l_v_size = l_v_lines * 255.
l_filename_string = l_file.
CALL METHOD cl_gui_frontend_services=>file_get_size
    EXPORTING
      file_name = l_filename_string
    IMPORTING
      file_size = l_v_size
    EXCEPTIONS
      OTHERS    = 1.
convert binary255 to binary1024 table
CALL FUNCTION 'SCMS_BINARY_TO_XSTRING'
    EXPORTING
      input_length = l_v_size
    IMPORTING
      buffer       = lv_xstring
    TABLES
      binary_tab   = itab
    EXCEPTIONS
      failed       = 1
      OTHERS       = 2.
IF sy-subrc <> 0.
       rv_failed = 'X'.
       RETURN.
ENDIF.
CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
    EXPORTING
      buffer     = lv_xstring
    TABLES
      binary_tab = li_bin_content.
l_skwf_filnm = l_file.
CALL FUNCTION 'SKWF_MIMETYPE_OF_FILE_GET'
    EXPORTING
      filename                   = l_skwf_filnm
X_USE_LOCAL_REGISTRY       =
   IMPORTING
     mimetype                   = l_mime.
l_component-comp_count    = 1.
l_component-comp_id       = l_fname.
l_component-mimetype      = l_mime.
l_component-comp_size     = l_v_size.
l_component-binary_flag   = 'X'.
l_component-comp_num      = 1.
APPEND l_component TO i_component.
DATA:
lo_case_api TYPE REF TO cl_scmg_case_api,
   lo_case_api_intf       TYPE REF TO if_scmg_case_api.
CALL METHOD cl_scmg_case_api=>if_scmg_case_api~open_case
    EXPORTING
      im_case_guid    = 'E99B284FC272B720E100000092D79319'
      im_enqueue      = 'X'
    RECEIVING
      re_case         = lo_case_api_intf
    EXCEPTIONS
      failed          = 1
      enqueue_failed = 2
      invalid_guid    = 3
      cx_srm_gsp_back = 4
      OTHERS          = 5.
lo_case_api ?= lo_case_api_intf.
*DATA : l_if_case_api      TYPE REF TO if_scmg_case_api.
       CALL METHOD cl_scmg_case_api=>open_case
         EXPORTING
           im_case_guid    = 'E99B284FC272B720E100000092D79319'
         RECEIVING
           re_case         = l_if_case_api
         EXCEPTIONS
           failed          = 1
           enqueue_failed = 2
           invalid_guid    = 3
           cx_srm_gsp_back = 4
           no_authority    = 5
           OTHERS          = 6.
CALL FUNCTION 'UDM_BD_CREATE_ATTACHMENT'
    EXPORTING
      i_guid      = 'E99B284FC272B720E100000092D79319'              "E99B284FC272B720E100000092D79319
      i_case      = lo_case_api
      i_testrun   = space           " '003A3A4FAD54D97CE100000092D79319'
    TABLES
      bin_content = li_bin_content
      components = i_component
    CHANGING
      es_return   = l_return.
IF sy-subrc = 0.
    COMMIT WORK.
ENDIF.
CALL FUNCTION 'DEQUEUE_ALL'.
break 50120i1120.

Auto closing of dispute cases--only for some company codes

Hi
We have activated dispute management for several company codes in our system. The auto closing of dispute cases also has been activated in status management. Cases are automatically closed by the system (through a batch job) when the last disputed object is cleared.
Now there is a requirement to deactivate auto closing only for some company codes. They want to close cases manually in these company codes.
Is this possible and if so how?
Regards
Raj.

You cannot deselect at a company code level.
Can we go through you proposed process.
So you have a dispute for $100.
The customer pays it and the dispute closes.
Then the customer calls up and says they have an issue with the invoice they paid previously.
I have seen this happen before but there was a little twist
1 - The customer raised a debit note against the client for the issue that they had. The original invoice is cleared but a debit note is created and then disputed and processed. So you can close the original dispute and create a new dispute against the debit note
2 - The customer paid the wrong invoice. The dispute was closed. However to rectify the miss allocation the clearing document will be reversed meaning the dispute is "re-opened" and can be processed.
I am unaware of any other requirement for a customer to "re-dispute" a paid item in SAP.

Dispute Case - Write-off entry

Dear Experts,
When we write off any invoice through UDM_AUTOWRITEOFF in FSCM, system Debits the Bad debts write off (P&L) A/c and Credits the Customer A/c. However, we want system to segregate VAT, Tax and Freight amount from Bad debts write off A/c. So that the entry would be VAT -Dr. Tax-Dr. Freight -Dr. Bad debts -Dr. and Customer -Cr. Please could you through some light on How to achieve this?
Thank you.
With Kind Regards,
Naresh B. Pandya

HI Naresh,
To my understanding there is no configuration in FSCM by which you can achieve what you have stated, since we want to achieve something in FI area by doing an acitivity in FSCM, whereas vice-versa would probably work. I can possibly think of a work around. You can post a normal write-off entry giving the tax code therein, which will clear customer open item, and post to tax GL as well. Now, since the open item (document) which was "disputed object" in FSCM - Dispute case, that object will get updated with resolved object as the new document posted. Basically, the dispute case attribute will reflect the changes that has occurred in FI (FI-FSCM integration). However, I'm not sure whether this amount will get updated in field "paid amount" or "written off" amount. You can simulate and check out.
I am also interested to know how you deal with this, so keep me posted.
regards,
TV.

Table staring changes to dispute cases

Hi experts,
What is the table that stores the changes to dispute cases?
I need to build a report on how of fields change, and about how long do they stick in a parcular value.
Regards,
Mario.

Please note that FDM_LDDP records the automatic changes made by the system on accounting documents.
So you could have a rule to say all new disputes, put a dunning block on the accounting documents that have been disputed, and when resolved it is taken away.

Error updating Dispute case: FDM_PROCESS_BUFFER Internal error: ENQUEUE

Whenever we clear a Disputed Invoice with an incoming payment, we receive this error message if the Dispute is unresolved: -
An error occurred during the update of case xxxxx
Update Case with Program FDM_PROCESS_BUFFER
You can start the program by running this document.
However, when we run FDM_PROCESS_BUFFER we get an error: -
Dispute Case xxxxx: Internal Error: ENQUEUE
Has anyone come across this error before? Or can anyone suggest a solution for this error given the scenario we are using i.e. clearing unresolved Disputes?
Thank you.

We have gotten this error when the status of the dispute case was "new" which is not in the range of allowed statuses allowed for the automatic change in status needed for the closure.
If we change the status to an "in processing" status the error is cleared.
Try that to see if it fixes the error.

EhP5 Functionality for Dispute Case

Just wondering if anyone knows if Enhancement Pack 5 provides functionality to link a credit as a "disputed object"? Currently we can only link the credit as a "customer-disputed object". This has all sorts of drawbacks for us (case doesn't close when document closes, the details from the accounting document do not populate into the dispute case, etc).
Thanks,
Melissa

Hi,
Can you be more specific?
You can include a credit note in a disputed object if the dispute is created with the debit (needs to be higher amount) at the same time.
You cannot add an open credit to the disputed item, but this would be done through a clearing transaction e.g. F-32. This will update the disputed object in de credited amount section.
You cannot create a disputed object on a credit only. If this is needed, why is the credit disputed? Bcs this is perhaps a deduction? Then I belongs to a debit or multiple debits. You can add all together in one dispute perhaps?
Regards,
Richard

FSCM- Dispute cases were not closed automatically for credit disputed amounts

Dear All,
We are creating the dispute cases for overpayment or un-applied cash payments (that is credit document) through FDM_AUTO_CREATE. But those credit dispute cases were not closed automatically after I cleared the documents through F-26 or F-32.
We are running FDM_PROCESS_BUFFER program through batch job for every hour. And we made correct configuration for automatic dispute case close in SPRO. Also the debit disputes were closed automatically.
Especially we are facing this issue for credit special g/l transaction (partial/residual/charge of difference clearing) documents.
Note : I can see two changes automatically in credit dispute cases these are, 1) Disputed amount get zero 2) Disputed objects (that is credit document) is automatically removed (Attributes => Linked Objects => Disputed Objects) in the credit dispute cases
Can you please help me how to resolve this issue.
Thank you in advance.
Thanks & Regards,
KVP

Dear Experts,
Can I have solution for this issue.
Thanks & Regards,
KVP

Dispute case ID no longer in cleared document visible

Similar Messages

Maybe you are looking for