Dispute case Creation using tcode fbl5n

Hi ....
Could u please explain me about dispute case creation using fbl5n tcode.
in my requirement i need to update some custome fields existed in tcode fileds like bank name etc..
while recording m not getting those custom fields are not recoded so could u please suggest
how to rectify this wheather i have to use BAPI with Extention(BAPI Name) r some other.
Thanks in Advance please suggest the solution.
Thanks & Regards,
Skumari.

adding the credit memo is not available as standard.
Object type BUS2094 is the object type for a sales order - so you could use this - but this will bespoke

Similar Messages

Automatic dispute case creation

Hi All,
How we can configure, automatic dispute case creation for bank statement upload (short payments).
Regards
Satya

there are no config steps as far as I understand.
As said earlier, go to documentation of t-code FDM_AUTO_CREATE and review the piece for bank statement upload.

Dispute case creation from FBL5N

Hi, I am getting following error while trying to create dispute case from FBL5N. Please guide me how can I correct this error. Please also help me with config steps (tcodes) in creating dispute case.
I will award full points for the relevant answers. Thanks
Error changing attribute FIN_PROC_SEQNR
Message no. UDM_MSG002
Diagnosis
An error occurred when you tried to change attribute FIN_PROC_SEQNR. The attribute should have the value 001.
Procedure
Contact your system administrator.

adding the credit memo is not available as standard.
Object type BUS2094 is the object type for a sales order - so you could use this - but this will bespoke

Dispute Case creation (credit memo reference to Billing invoice)

Hey
We are using SD module to create Billing invoices and Credit Memo's.
1. Dispute case created for Accounting invoice (Generated from Billing invoice).
2 Credit memo raised in reference to billing invoice and FI document generated for Credit memo.
We are in need to add Credit memo to the existing Dispute case in the Billing invoice.
I have tested this scenario and this is not an standard. Any inputs in this regard is highly appreciated.
Thanks
Rajanikanth.

adding the credit memo is not available as standard.
Object type BUS2094 is the object type for a sales order - so you could use this - but this will bespoke

Auto Creation of Dispute Case based on dunning level

Dear All
We want to create the dispute case automatically using T.Code FDM_Auto_Create. We want to default the title as dunning level + External reference. We know the BADI for this but how to check which dispute cases are created automatically due to dunning level.
Thanks and Best Regards
Farhan Qaiser

Hi Farhan,
I presume you are creating your disputes against open items, and not incoming payments.
If this is correct, the dunning level field is part of the selection parameter.
Are you planning on disputing all open items, that have a specific Dunning level, if that is the case you can include this in your selection parameter.

Dispute Cases on partial Payments

Hi
How to create Dispute cases for partial payments?
I have an invoice. A payment comes and its partial. We dont set up residuals. So on the invoice it says partially paid for some amount. And we want the job to create the dispute for the remaining amount.
Do i need to define anything new in case record model for this?
Thanks for help.

I have an invoice for 1000. No dispute case is created till now.
I made a pyment for it for 500.
And now If I run FDM_AUTO_CREATE what is my selection criteria to select this invoice for dispute case creation.
We want to schedule a job everyday to pick up all invoices that are partial paid and we want to create cases for them.
Can it be done in FDM_SUTO_CREATE?
If it can be done then how the program knows which invoices has partial payments and how does it change the disputed amount to invoice amount minus partial payment?
I know how to do it manually by selecting both debit and credit item in FBL5N to create the case.
I also know that when case is created and if a payment is made partially it reflects the case disputed amount.
I just want to know if FDM_AUTO_CREATE can be used to to create cases on invoices that are partially paid.
If it can then how?
Thanks,

Add/remove open items to dispute case

Hello..
I'm finding a way to add/remove open items to dispute case in a program level for example using RFC.
I already made a program to create dispute case refer to tcode FDM_AUTO_CREATE but add/remove open items seems to be not simple...
Is there any way to add/remove disputed items using 2~3 functions in my Z-program?

Bapi functions of dispute case are too complex and not automated for example amount calculation.
I found another easy function FDM_AR_CDIS_ADD_ITEM.
It seems to be only for customer-disputed item but it works well in case of normal invoice.
Thank you for good help!

Error - Dispute Case Data Could Not Be Read

I got above error while creating the dispute case in production server.
Anyone have an idea how I fixed it, does it need to see RFC?
Please guide me
Krunal

Hi Mark,
Thanks, while I create one document for dispute case system is not able to read the document. It is in productive client. we have cluster specific transactions in one cluster we post documents and another cluster dispute cases create. so when I tried to create dispute case in main cluster with ref to document system gives me below error.
Normally we post transctions in G cluster and after posting in G we process dispute case in G cluster and after it open in E cluster for details about dispute case.
Using UDM_DISPUTE transction code for look into dispute cases in E cluster, here we canonot proceed from G to E, In G Cluster we find this error and because of this we unable to create dispute case in E cluster.
If you need more information, Please ask me.

When using program RFDM3000/Automatic creation of dispute cases what is the difference with the option of Automatic incoming payment and Open items?

We currently have a batch jobs running for each, automatic incoming payment and open items. This was set up in the past and we are trying to determine what the difference is for each of these functions? Do you need to have the automatic incoming run prior to the open items for residuals and payments on accounts?

Hi Chris,
Program RFDM3000 creates dispute cases for residual items arising during automatic incoming payments (account statement, lockbox), during check presentation, or in postprocessing.
Alternatively, you can use the program to create dispute cases for open receivables items. You can use the selection criteria to restrict the quantity of open items (for example, using the document type and posting key for residual items from incoming payment postings).
You will find more information in the link below
http://help.sap.com/saphelp_erp2004/helpdata/en/0b/e07340b0c6980ae10000000a155106/content.htm
Regards,
Jose

Add new field during the creation of a dispute case from AR

Hi experts,
Can you help me out with the steps necessaries to create a new field and add it and completed during the creation of a dispute case from AR.
Many thanks.

Yes, BADI fdm_user_screen has to be used.
1 method GET_CREATE_SCREEN to define the screen with the new attribute/s
2 method CREATE_SCREEN_PBO to define the logic tht u want to get processed before the screen is up for display, (possibly pre-population of the attribute/s)
3 method CREATE_SCREEN_PAI for logic after the user has entered value in the attribute/s

Upload data for Tcode LT06(Transfer order creation) using BDC -very urgent

hi experts,
I got stucked up in writing a BDC for the Tcode LT06(Transfer order creation using wearhouse number) in MM module,
the problem is like this, when i go to the tcode LT06 , it will ask for material doucument,mat. docu. year and wearhouse number, iam entering the inputs and then press enter, as soon as i press enter it takes me to the second screen where i will be selecting the item and then click on the button called 'Generate TO item'
here the problem arises, as soon as i click the button iam getting a standard SAP error message(No Destination Storage Bin found in storage type 'IMP'). Due to this errror iam not able populate the batch input data on the screen, suggest me a proper solution. rewards will given if solution found useful.
Kishore K

Hi ,
I have done the same in Background with BDC and TR Number for Multiple Materials ,
Can u please explain the scenario, so then I would be able to try for solution ?
Warm Regards.

Uploading the Notes text pool using Conversion method for Dispute Cases.

Hi Everybody,
Please can anybody give the solution for uploading the Notes textarea in tab(Notes in dispute cases) using BDC method for transaction FDM_AUTO_CREATE(Dispute Cases).
Here, the problem is, Notes is text area which is not having proper reference.
We have tried few BAPI's like BAPI_DISPUTE_CREATE but did not worked.

Hello! Anyones could resolve this?
Regards,
Federico

Creation of Dispute Case in FI-CA

Hello,
Anyone provide me insight for:
Creation of Dispute Case - As per SAP Standard functionaliy we can create the Dispute Case from FPL9/FPE2 and UDM_DISPUTE
Problem 1 : I am facing a problem to create dispute case from transaction UDM_DISPUTE for RMS ID UDM_FICA_DISPUTE(Error Message: UDM_FICA001 You can only create cases from Account Receivable and Payable) and case type FICA-Dispute Missing Payment.
Problem 2. Configured intergration with Contract accounting but I can't see any option to create case from FPL9 and FPE1/2/3.
Thanks in Advance...

Hi Rickyranjan, please provide additional information about your current settings:
Have you activated Dispute management in the activity Set up Company codes for contract accounts receivable and payable?
Have you defined the case types in FICA?
Best regards,
Cristobal.

Case creation with "Parties Involved" using WST

Dear All,
We are creating a case in CRM system 7.0 using the webservice created by WST tool. The case number is generated successfully, however, u2018Parties Involvedu2019 is not created in the case.
Error obtained:
TypeID = 300(CRMOST),
SeverityCode = 3,
Note = Object CmgRecord with ID 02 could not be created,
Processing Result Code = 4
As per the help available in :
http://help.sap.com/saphelp_crm70/helpdata/EN/29/35173e04b64782a831ac600536e906/content.htm
We are populating the values as follows:
PARTNER_FCT = 00000009 (00000009 stands for Activity Partner)
BOR_KEY = 8000000014 (8000000014 is the BP number thats exists in CRM system)
BOR_TYPE = BUS1006 (BUS1006 is the object type)
CRM_MAIN_PARTNER = True (Setting the BP as Main partner)
Please note that the case gets created with "Parties Involved" in WebUI with the above parameters.
Kindly let us know your inputs. Thank you in advance.
Regards,
Pritish

Dear All,
We are creating a case in CRM system 7.0 using the webservice created by WST tool. The case number is generated successfully, however, u2018Parties Involvedu2019 is not created in the case.
Error obtained:
TypeID = 300(CRMOST),
SeverityCode = 3,
Note = Object CmgRecord with ID 02 could not be created,
Processing Result Code = 4
As per the help available in :
http://help.sap.com/saphelp_crm70/helpdata/EN/29/35173e04b64782a831ac600536e906/content.htm
We are populating the values as follows:
PARTNER_FCT = 00000009 (00000009 stands for Activity Partner)
BOR_KEY = 8000000014 (8000000014 is the BP number thats exists in CRM system)
BOR_TYPE = BUS1006 (BUS1006 is the object type)
CRM_MAIN_PARTNER = True (Setting the BP as Main partner)
Please note that the case gets created with "Parties Involved" in WebUI with the above parameters
We are able to create a case with the "Parties Involved" (using the same above parameters) successfully using the case creation in WebUI manually but with the webservices the error is obtained.
Kindly let us know your inputs. Thank you in advance.
Regards,
Pritish

Standard tcode FBL5N dump in pre production.

I am getting a dump when I execute the standard tcode FBL5N (Customer line item) with one company code. FBL5N tcode is not at all giving dump in production system, however it dumps in pre production.
The dump exists in the function module : fdm_local_get_objects_range while executing the SELECT stmt
*SELECT * FROM fdm_dcobj*
           INTO CORRESPONDING FIELDS OF TABLE et_object_data
           WHERE logsys        LIKE i_logsys
           AND   obj_type      LIKE i_obj_type
           AND   obj_key       IN   it_range_obj_key
           AND   relation      LIKE i_relation
           AND   case_guid_loc IN   it_guid
           AND   is_confirmed LIKE i_confirmed
           AND   is_voided     LIKE i_voided.
Do I need to search for sap note ?
Below is dump analysis
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
     in    procedure "FDM_LOCAL_GET_OBJECTS_RANGE" "(FUNCTION)", nor was it propagated by
     a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    The SQL statement generated from the SAP Open SQL statement violates a
    restriction imposed by the underlying database system of the ABAP
    system.
Possible error causes:
     o The maximum size of an SQL statement was exceeded.
     o The statement contains too many input variables.
     o The input data requires more space than is available.
     o ...
You can generally find details in the system log (SM21) and in the
    developer trace of the relevant work process (ST11).
    In the case of an error, current restrictions are frequently displayed
    in the developer trace.
How to correct the error
    The SAP Open SQL statement concerned must be divided into several
    smaller units.
    If the problem occurred due to the use of an excessively large table
    in an IN itab construct, you can use FOR ALL ENTRIES instead.
    When you use this addition, the statement is split into smaller units
    according to the restrictions of the database system used.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:

Note Still Valid in Market place.
"SAP Note 1111155 - FSCM-DM: Termination "Open SQL
statement is too large."
Note Language: English Version: 10 Validity: Valid Since 07-28-2010
Summary
Symptom
When you access dispute case using the integration (creating dispute case
using FI transactions (for example, FBL5N), clearing items to which dispute
case have been assigned), the system issues the dump "Open SQL statement is
too large".
The error occurs if there are many (more than 1000) dispute cases for a
customer.
Other terms
FBL5N, FBZ1, F-32, integration
Reason and Prerequisites
This problem is due to a very large dispute case volume.
Solution
Import the relevant Support Package or implement the attached correction
instructions.
Header Data
Release Status: Released for Customer
Released on: 07-28-2010 08:02:45
Master Language: German
Priority: Correction with medium priority
Category: Program error
Primary Component: FIN-FSCM-DM Dispute Management
Valid Releases
Software Component Release From
Release
To
Release
and
Subsequent
SAP_APPL 600 600 600
SAP_APPL 602 602 602
SAP_APPL 603 603 603
SAP_APPL 604 604 604
SAP_APPL 605 605 605
PI 2004.1 2004_1_47"

Dispute case Creation using tcode fbl5n

Similar Messages

Maybe you are looking for