Dunning Activity

Dear Friends,
In a Dunning run, One Particular Customer has 2 overdue bills, of which, one is in the 1st level and other is in the 4th level (Last level).
During the Run, the system identifies the line items in 2 levels but executes Dunning Activity for the higher level as the lower level activity is ignored.
Kindly suggest what could be wrong.
Thanks in Advance.
Regards
R.Vasudeb

Hi,
You can define dunning grouping according to dunning step and, maybe, dunning procedure. But, as a warning, you will have 2 dunning groups and that partner will receive 2 dunning notices, as opposed to 1 if you don't do what I just described. For example, you have 2 invoices, F1 - 100 units, dunning step 1 and F2 - 200 units, dunning step 2.
Case 1 - not grouping by dunning step and dunning procedure. You get:
- 1 dunning group, dunning step 2, customer is warned his debt is 300 units, F1 - 100 units, F2 - 200 units.
Case 2 - grouping by dunning step and dunning procedure. You get:
- 1 dunning group, dunning step 1, customer is warned his debt is 100 units, F1 - 100 units.
- 1 dunning group, dunning step 2, customer is warned his debt is 200 units, F2 - 200 units.
If you want to change dunning grouping, go to Financial Accounting->Contract Accounts Receivable and Payable->Business Transactions->Dunning Notices->Define Dunning Grouping Categories. Use fields MAHNN for grouping according to dunning step and MAHNV for grouping according to dunning procedure.
Hope this helps,
Bogdan

Similar Messages

Custom FM for dunning activity

Dear All,
I want to post a document in customer account after dunning activity. I am trying to do this through ABAP. What i did was that i made a copy of the standard dunning activity FM Z_ISU_DUNNING_EMPTY_ACTIVI_0350. In this FM i added my code which would post a simple document in a customer account.
When i test this function module using se37 the FM works perfectly well and posts a document. However when i put this FM for my dunning activity(Using SPRO>> Configure Dunning activities) and run the dunning proposal and activity, the document does not get posted. I dont know why. Can anyone please help. Would really appreciate
Here is how the code looks like after i added my code for posting a simple document
FUNCTION ZISU_DUNNING_EMPTY_ACTIVI_0350.
""Local Interface:
*" IMPORTING
*"     VALUE(I_TFK047L) LIKE TFK047L STRUCTURE TFK047L
*" TABLES
*"      T_FKKMAZE STRUCTURE FKKMAZE
*"      T_FKKMAKT STRUCTURE FKKMAKT
*"      T_FKKOP STRUCTURE FKKOP
*"      T_FKKOPK STRUCTURE FKKOPK
*"      T_FIMSG STRUCTURE FIMSG
*" CHANGING
*"     VALUE(C_FKKMAKO) LIKE FKKMAKO STRUCTURE FKKMAKO
*"     VALUE(C_FKKKO) LIKE FKKKO STRUCTURE FKKKO
only write success message into job log
DATA:
    documentheader like bapidfkkko,
partnerpositions type standard table of bapidfkkop with header line,
genledgerpositions type standard table of bapidfkkopk with header line,
documentnumber like bapidfkkko-doc_no,
return type standard table of bapiret2 with header line.
documentheader-fikey                = '100915-001'.
documentheader-appl_area            = 'R'.
documentheader-doc_type             = 'AB'.
documentheader-doc_source_key       = '01'.
documentheader-currency             = 'UNI'.
documentheader-doc_date             = sy-datum.
documentheader-post_date            = sy-datum.
partnerpositions-item                = '0001'.
partnerpositions-comp_code           = 'UNI'.
partnerpositions-buspartner          = '0000014044'.
partnerpositions-cont_acct           = '10000416133X'.
partnerpositions-main_trans          = '6000'.
partnerpositions-sub_trans           = 'AD01'.
partnerpositions-g_l_acct            = '0000140000'.
partnerpositions-doc_date            = sy-datum.
partnerpositions-post_date           = sy-datum.
partnerpositions-net_date            = sy-datum.
partnerpositions-currency            = 'UNI'.
partnerpositions-amount              = '99'.
APPEND partnerpositions.
genledgerpositions-item = '0001'.
genledgerpositions-comp_code = 'UNI'.
genledgerpositions-g_l_acct = '0000299000'.
genledgerpositions-amount = '-99'.
genledgerpositions-profit_ctr = 'IBC'.
   APPEND genledgerpositions.
    CALL FUNCTION 'BAPI_CTRACDOCUMENT_CREATE'
    EXPORTING
      testrun            = ''
      documentheader     = documentheader
    IMPORTING
      documentnumber     = documentnumber
      return             = return
    TABLES
      partnerpositions   = partnerpositions
      genledgerpositions = genledgerpositions.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        wait = 'X'.
    CALL FUNCTION 'FKK_DUNNING_MESSAGE_APPEND'
         EXPORTING
              MSGID   = 'EK'
              MSGNO   = '345'
              MSGPR   = '2'
         TABLES
              T_FIMSG = T_FIMSG.
    IF 1 = 0. MESSAGE S345(EK). ENDIF.
ENDFUNCTION.

The log displays the same message as the one it showed when i had not changed the code.
I also tried to do the same thing with the dunning activity that deactivates the installment plan. i made a copy of the function module ISU_DUNNING_DEACT_INSTPL_0350. In that new func module i copied my code that posts a simple document. then i assigned the new ZISU_DUNNING_DEACT_INSTPL_0350 activity to the dunning procedure in SPRO. I created an installment plan for a business partner and ran the dunning activity. The installment got de activated but no document was posted!
for your help i am providing the code of the ZISU_DUNNING_DEACT_INSTPL_0350
FUNCTION ZISU_DUNNING_DEACT_INSTPL_0350.
""Local Interface:
*" IMPORTING
*"     VALUE(I_TFK047L) LIKE TFK047L STRUCTURE TFK047L
*" EXPORTING
*"     VALUE(TEMP) TYPE OPTXT
*" TABLES
*"      T_FKKMAZE STRUCTURE FKKMAZE
*"      T_FKKMAKT STRUCTURE FKKMAKT
*"      T_FKKOP STRUCTURE FKKOP
*"      T_FKKOPK STRUCTURE FKKOPK
*"      T_FIMSG STRUCTURE FIMSG
*" CHANGING
*"     VALUE(C_FKKMAKO) LIKE FKKMAKO STRUCTURE FKKMAKO
*"     VALUE(C_FKKKO) LIKE FKKKO STRUCTURE FKKKO
DATA: BEGIN OF T_OPBEL OCCURS 1,
          OPBEL LIKE FKKOP-OPBEL,
        END OF T_OPBEL.
DATA: H_ATEXT(100).
DATA: OPBEL_C(12).
DATA: H_UPDATE.
DATA: H_FKKMAHNV LIKE FKKMAHNV.
DATA: H_TFK033D LIKE TFK033D.
DATA: H_DEAGD LIKE RFKN1-DEAGD,
documentheader like bapidfkkko,
partnerpositions type standard table of bapidfkkop with header line,
genledgerpositions type standard table of bapidfkkopk with header line,
documentnumber like bapidfkkko-doc_no,
return type standard table of bapiret2 with header line.
documentheader-fikey                = '100915-001'.
documentheader-appl_area            = 'R'.
documentheader-doc_type             = 'AB'.
documentheader-doc_source_key       = '01'.
documentheader-currency             = 'UNI'.
documentheader-doc_date             = sy-datum.
documentheader-post_date            = sy-datum.
partnerpositions-item                = '0001'.
partnerpositions-comp_code           = 'UNI'.
partnerpositions-buspartner          = '0000014030'.
partnerpositions-cont_acct           = '10000416119X'.
partnerpositions-main_trans          = '6000'.
partnerpositions-sub_trans           = 'AD01'.
partnerpositions-g_l_acct            = '0000140000'.
partnerpositions-doc_date            = sy-datum.
partnerpositions-post_date           = sy-datum.
partnerpositions-net_date            = sy-datum.
partnerpositions-currency            = 'UNI'.
partnerpositions-amount              = '66'.
APPEND partnerpositions.
genledgerpositions-item = '0001'.
genledgerpositions-comp_code = 'UNI'.
genledgerpositions-g_l_acct = '0000299000'.
genledgerpositions-amount = '-66'.
genledgerpositions-profit_ctr = 'IBC'.
APPEND genledgerpositions.
CALL FUNCTION 'BAPI_CTRACDOCUMENT_CREATE'
EXPORTING
testrun            = ''
documentheader     = documentheader
IMPORTING
documentnumber     = documentnumber
return             = return
TABLES
partnerpositions   = partnerpositions
genledgerpositions = genledgerpositions.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
temp = return-message.
temp = documentnumber.
CALL FUNCTION 'ISU_DUNNING_DEACT_INSTPL_LOAN'
       EXPORTING
            I_LOAN    = space
       TABLES
            T_FKKMAZE = T_FKKMAZE
            T_FKKMAKT = T_FKKMAKT
            T_FIMSG   = T_FIMSG
       CHANGING
            C_FKKMAKO = C_FKKMAKO.
exit.
get update flag from global memory
Parameter, ob Testdruck vorgesehen ist, aus dem globalen Memory holen
CALL FUNCTION 'FKK_DUNNING_PARAMETER_GET'
       IMPORTING
            E_UPDATE   = H_UPDATE
            E_FKKMAHNV = H_FKKMAHNV.
new: reason for deactivation of installment plan in
business area 1102
CALL FUNCTION 'FKK_ACCOUNT_DETERMINE_1102'
       EXPORTING
            I_APPLK   = H_FKKMAHNV-APPLK
       IMPORTING
            E_TFK033D = H_TFK033D
       EXCEPTIONS
            OTHERS    = 3.
IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
H_DEAGD = H_TFK033D-FUN01.
inside the dunned items, look if there installments in the highest
dunning level
innerhalb der gemahnten Forderungen nach Raten suchen, die die
höchste Mahnstufe erreicht haben
LOOP AT T_FKKMAZE
    WHERE STAKZ = 'R'
    and xinfo   = ' '.
     AND MAHNS = C_FKKMAKO-MAHNS.                  "Note 182489
    READ TABLE T_OPBEL WITH KEY OPBEL = T_FKKMAZE-OPBEL.
if the document number is new, go on
Nur weitermachen, wenn die Nummer noch nicht geprüft wurde
    CHECK SY-SUBRC NE 0.
    T_OPBEL-OPBEL = T_FKKMAZE-OPBEL.
    APPEND T_OPBEL.
    WRITE T_OPBEL-OPBEL TO OPBEL_C NO-ZERO.
deactivate installment plan only in update mode
Ratenplan nur im UPDATE-Modus deaktivieren
    IF H_UPDATE = 'X'.
      CALL FUNCTION 'FKK_S_INSTPLAN_DEACTIVATE'
           EXPORTING
                I_OPBEL = T_OPBEL-OPBEL
                I_DEAGD = H_DEAGD
                I_DEADT = sy-datum
           EXCEPTIONS
                OTHERS = 1.
    else.
      clear sy-subrc.
    ENDIF.
    IF SY-SUBRC = 0.
success message in job log
Nachricht, daß Ratenplan deaktiviert wurde, ins Protokoll :News that installment plan has been disabled, the log
      CALL FUNCTION 'FKK_DUNNING_MESSAGE_APPEND'
           EXPORTING
                MSGID   = 'EK'
                MSGNO   = '304'
                MSGV1   = OPBEL_C
                MSGPR   = '2'
           TABLES
                T_FIMSG = t_fimsg.
      IF 1 = 0. MESSAGE S304(EK) with OPBEL_C. ENDIF.
Create an entry in dunning history for deactivating an installmt plan
Für das Deaktivieren des Ratenplans wird noch eine Mahnaktivität
definiert.
      CLEAR T_FKKMAKT.
      MOVE-CORRESPONDING C_FKKMAKO TO T_FKKMAKT.
      H_ATEXT = 'Ratenplan & wurde deaktiviert'(001).
      REPLACE '&' WITH OPBEL_C INTO H_ATEXT.
      CONDENSE H_ATEXT.
      T_FKKMAKT-ATEXT = H_ATEXT.
    concatenate 'Ratenplan'(001)
                t_opbel-opbel
                'wurde deaktiviert'(002)
      into t_fkkmakt-atext separated by space.
      APPEND T_FKKMAKT.
    ELSE.
Write error in job log
Fehlermeldung aus dem Funktionsbaustein wird in Tabelle geschrieben,
sie kommt dann nach der Abbruch-Meldung ins Protokoll.
      CALL FUNCTION 'FKK_DUNNING_SYST_MESSAGE_APP'
           TABLES
                T_FIMSG = T_FIMSG.
error message in case of error
Dann wird die Abbruchmeldung direkt ausgegeben
      MESSAGE E305(EK) WITH OPBEL_C.
    ENDIF.
ENDLOOP.
ENDFUNCTION.

Dunning Activity send by mail. but mail does not contain a subject.

Hello Friends,
I am facing a issue of "subject missing in the mail",
we are running the F150 transaction to send a mail to customer as an attachment of dunning activity.
But mail does not contain a subject.
kindly let me know how to maintain a subject for the mail.
Regards,
Munvar BAsha

Hi,
check the SAPNET notes 521585, 554408, 1042992 + related notes.
Best regards, Christian

Dunning Activity FPVB - Document No - Reconciliation Key

I would like to know how SAP system determines document number for late payment charge documents and reconciliation key for those late payment charge documents during dunning run FPVB.
I wonder whether there are any customization for that or FPVB is calling any particular FM for that.
Thanks in advance

Thank you William for such a precise answer.
I am having a peculiar problem during dunning activity run FPVB. I ran a dunning proposal with following parameters:
DateID : 05/20/2011
Identifcation : FPVA1
SAP suggested by default following dunning parameters :
Date of Issue : 05/20/2011
Reconciliation Key : 11140FPVA1
After completion of dunning run, we got late payment charge documents. Out of those documents, some documents took reconciliation key same as it's document no. (as follows) :
..._DateID_ ........          Identification      ............ Document No.   .......... Rec. Key
05/20/2011........ FPVA1    ............    342076625 ............ 11140FPVA2AN
05/20/2011........FPVA1     ............     329388504 ............ 000329388504   (Rec key same as document no.)
05/20/2011........FPVA1    ............   329546609 ............ 000329546609   (Rec key same as document no.)
05/20/2011........FPVA1      ............ 349378503 ............ 11140FPVA2AM
....... and so on
Now I don't understand why it is taking reconciliation key same as document no. And why those document numbers are random and not sequential.
Edited by: Poddar Anujit on May 27, 2011 11:19 PM

No printing date is printed while running the dunning activity?

Hi SAP Experts,
The dunning proposal is created successfully but when I run the dunning activity the dunning level is updated with issue date but the printing date is not printed. Can any one let me know the root cause of this issue.
Thanks

Hi Moin,
You are right in saying, that the print date field in the dunning history gets updated after the dunning activity is executed successfully.
This is a standard SAP functionality and if the dunning level is getting incremented, then the print date field should also get updated in the Dunning History.
Is this happening for all accounts or some of them?
As a starting point, I would recommend you to start seeing the application logs for the Dunning Activity, once it gets completed.
Hope it helps...
Thanks,
Amlan

I am trying to create worklist using RMCA dunning.Activity assigned is wl01

Hi,
I am trying to create worklist using RMCA dunning.Activity assigned is wl01.
Getting an error during dunning activity run is 'Error determining responsible persons' Please help.
Jayant

Jayant:
I will assume that the settings for that activity use 'Determine responsible agent', and in that case you need to maintain the rules and responsibilties for the workitems so that they can be routed correctly. You will need to create organization structure as well.
regards,
bill.

Avoid a student from registration if he has a dunning process active

Hi to all,
How can we configure FICA with CAMPUS Management to avoid that the students which owe one or more open items can register for a SC?
We are running the dunning process with no problem, and we have placed as an activity of the dunning a the FM CMAC_EVENT_0350_HOLD_SET. But the problem is that this FM sets a financial hold, not an academic hold.
How can we relate an academic hold with this dunning activity?
Is also neccessary that if the students pay all the open items that had a dunning procedure, these academic holds which prevent the students of registering, are turn off.
Thank you
Sergio

Sergio,
You can certainly just link that Financial Hold to the callup point for Registration, and the registration would then be blocked. This is done in the IMG under:
SLCM -> Processes in SLCM -> General Settings -> Holds -> Assign Hold Types to Callup Points.
Just assign your Financial Hold type to Callup Points 0012 and 0022 to block any program registrations
Michael.

Print Date issue in Dunning Correspondence

Hi,
I have an issue with Print Date in Dunning correspondence. The dunning proposal and activity run has happened. The correspondence printing will fetch the accounts from the database as per the print date.
1. I would like to know where and how the dunning activity data stored?
2. Where and How the Print date assigned for accounts which helps FPCOPARA to retrieve accounts on that particular date?
Please HELP

Hello Joe,
I still have the issue with this print date.
I have given only cores type and as u said the real print.
when i checked the corrhist for a particular CA, different times different future date has come.
For eg: date is issue: 12/01/2009 (mmddyyyy) printdate is 12/20/2009.
10/01/2009 10/15/2009
like this, many cust have this issue.
why this prind date for some CAs are different or future dates?
where the settings for this print date will be?
Because of this, on a particular day all the dunned CAs are not picking up for Correspondence printing. these excepted CAs will come on another future day printing.
please share some ideas to solve this issue
Regards,
Sunitha

Through Programaticaly How To change Dunning Procedure and Dunning level

I am having the requirement to change the dunning procedure and dunning level programatically.
Is there any Function module or BAPI or sample code where I can change the dunning procedure and push the dunning level to
30(No matter at what level but it has to push to 30).

Try these function modules available through T.code FQEVENTS
FKK_SAMPLE_0351 or FKK_SAMPLE_0307 or FKK_SAMPLE_0744 or FKK_SAMPLE_0304
Or try creating one procedure to exclusively handle a particular level /dunning activity only and replace the procedure in the master data
Hope it offers some help

Interest Calculation in Dunning & Print Correspondence...

Dear Experts...
The below settings are in place.
1) Interest is calculated along with dunning level 2. Config is done for the same.
2) Ther are 2 customized Zforms available for DL2 notice letter and interest invoice.
3) Correspondence Type 0003 & 0007 are available for dunning & interest notification respectively.
Requirement:
Once DL2 is carried out, the interest is also posted in contract account , but correspondence DOES NOT print the Interest invoice through T Code: fpcopara, but the dunning letter for DL2 is printed in fpcopara.
May I know any function module to be attached in either Dunning activity or Correspondence so that the interest notification is also printed simaltaneously after dunning notice is printed.
Also mention any other config setting to be maintained in both Dunning & Correspondence.
Note: No separate Interest Run(T Code: FPINTM1) is carried out. Interest Key is assigned in dunning itself.
Thanks in advance.
Best Regards,
B.Kartthik.

Hi,
Maybe the easiest way would be to adapt your dunning form to print as a second page the interest notice? I've already done this for the interest over installment plans as we need them to be printed as an invoice (With official document number). In FKKMAKO you have the interest document number (Field MIBEL) that you can use during the printing to trigger the second page.
I don't know any specific activity to generate the interest notice during dunning, but you can create it by creating a new function module using sample FKK_FILL_SAMPLE_0350 that will call the interest notice trigger event (FKK_SAMPLE_0713) to create a second correspondence container during dunning. If you create the correspondence container like this it will be then normally printed with FPCOPARA.
Regards,
Adriano da Silva.

Posting date in Dunning Document

Hello Everybody,
I need to know how I can put my desired posting date in a dunning document ,which is generated through tcode FPVA and FPVB. As of now it is automatically taking the present date(date at which tranaction is run) as posting date.
It would be of great help if you can help me out in this.
Thanks in advance
Kunal

Hi:
During the Dunning Proposal, you can set your own date. The details are as
1. Dunning Proposals
The dunning proposal examines the customers contract account for open items and applies the rules established by the customers dunning procedure to these items. The output of this process is a proposal (a list of accounts with the proposed actions) which identifies the actions which will be enacted by the activity run. This proposal allows the user to review the list of business partners who should not be included in the run and to reverse them out of the proposal.
Transaction FPVA requires the user to input a date and initial to identify the particular run. Upon entry, the system allows the user to identify the options for the proposal. These parameters can include general items such as a specific range of contracts, contract accounts, business partners, companies or general items. Once these general parameters are determined (It is acceptable to leave them all blank and run against all accounts) the specific dunning parameters are input which define the date of issue , open item due dates to be considered, and ranges of dunning procedures to be considered. The date of issue and the open item due date are the key data for these procedures. The remaining tabs control parallel processing and the level of detail in the program logs. The level of detail in the logs should be limited as a large number of entries can be generated from a single proposal. The selection entries should be saved and the proposal should be scheduled for execution.
SAP Easy Access→ Utility Industry →Contract Accounts Receivable and Payable →Periodic Processes→ For Contract Accounts →Dunning Notice →Dunning Proposal Run (Transaction FPVA).
2. Dunning activity
The activity run can not be performed unless a proposal exists. The system uses existing proposals as input for the activity. The activity run executes all actions identified by the dunning procedure for those customers remaining in the proposal.
SAP Easy Access→ Utility Industry →Contract Accounts Receivable and Payable →Periodic Processes→ For Contract Accounts →Dunning Notice →Dunning Activity Run (Transaction FPVB)
This includes:
Generating the identified collection letters.
Generating disconnect service orders.
Identifying and initiating the delivery of accounts to third party collection agencies.
The identification of candidates for write-off.
The updating of customers creditworthiness totals.
Generate lien placement warning letter (addressed to premises owner).
Hopefully it would be helpful.
Regards
Shashi

Posting date of Dunning document

Hello Everybody,
I need to know how I can put my desired posting date in a dunning document ,which is generated through tcode FPVA and FPVB. As of now it is automatically taking the present date(date at which tranaction is run) as posting date.
It would be of great help if you can help me out in this.
Thanks in advance
Kunal
My apologies for posting the same message twice
Message was edited by:
Kunal Handa

Hi Kunal
In dunning in FICA there are two dates, the first one is the issue date. This can be chosen in FPVA and is the key date for which dunning notice. Next to that you've got the print date, and that is the date on which the activity is executed. You cannot choose this date, the system decides it automatically at the time of execution of the dunning activity run. And I do not think that this can be changed.
So I think you should use the issue date.
Best regards,
Dimitri Vandenborn

Payment block through dunning

Dear X'perts, I need to set up a dunning activity that blocks the contract accounts for payments, I though to use a payment and clearing lock but this activity is not the last one, therefore I cannot use the payment and clearing lock, do you know any other way I could resolve this issue?
Best regards.

Hi RBK,
I'm not sure about your business requirement as when the Customer is on DD, you cannot Dun him.
If you want to Block the Payments,
you can
1. Lock the Customer at DD level in CA> Payment /Taxes>Incoming Payments-->Lock
2. Else put the lock at each and every Individual Item level using FKLOCK2 program.
Rgds
Rajendra

Auto reduction of Dunning Level

Hi
When we run the dunning activity run dunning level is automatically reduced to lower level. The details are as below
Dunning Procedure- L1
Dunning Levels- 10,20,30,40.
First invoice reached Level 40 this is highest level
after this we did invoicing
now there two open items in the contract account. Open item 1 is at dunning level 40 and open item 2 is not dunned at.
Now when we run the dunning, both items picking in dunning run and both item are showing at dunning level 10 in contact account display-FPL9.
The issue is - open item which was dunned at highest level should not reduce to lowest level. In this case this was reduced from 40 to 10.
We need dunning level should not reduce from highest level to lowest level.
Please help.
Regards
Srinivas
Edited by: srinivas rao on Oct 10, 2009 9:58 PM

Hi Narendar
Thanks for your reply. This check already selected in the dunning procedure. we found the issue is with FM.
Regards
Srinivas

Dunning Level Repeated in Dunning Run

Hi,
We need your help in resolving a peculiar issue we are facing relating to Dunning:
The Dunning Activity is picking up Contract Accounts repeatedly at the same Dunning Level.
For example,
the Contract Account CA - 1 contains two open items:
Document Number
Due Date
Dunning Procedure
Document 1
01.06.2014
ZA
Document 2
05.06.2014
ZA
the Dunning Procedure ZA contains 4 Dunning Levels as follows:
Dunning Procedure
Dunning Level
Days in Arrear
ZA
1
10
ZA
2
20
ZA
3
30
ZA
4
40
While analyzing the issue we are facing, we have observed that one of the scenarios when the Contract Account is repeatedly picked at the same dunning level is the following:
if the Contract Account - CA - 1 is picked in the Dunning Activity Run at Dunning Level 3 for the Dunning Procedure ZA on 30.06.2014(when the Document 1 is reaching the days in arrear for Dunning Level 3)
The same Contract Account - CA - 1 is picked in the Dunning Activity Run at same Dunning Level 3 for the Dunning Procedure ZA once again on 05.07.2014(when the Document 2 is reaching the days in arrear for Dunning Level 3)
The scenario mentioned above is not the only scenario when we are facing this issue of Contract Account getting picked at the same dunning level repeatedly.
The Dunning Procedure mentioned in the example has been configured as follows:
The field - Always Dun, has not been checked.
The correct days difference between two Dunning levels has been maintained in the field - Dunning frequency for every Dunning level.
The field - Days in arrears, has been maintained correctly for each of the Dunning Levels
But as per the business requirement and our understanding of the behaviour of standard SAP, the Contract Account - CA - 1 which is picked at the Dunning Level 3 for the Dunning Procedure ZA on 30.06.2014, should be picked in the Dunning Activity Run only when:
the open item in the CA- 1 remains outstanding till the number of days to reach the next Dunning Level, which in this example would be reached when the outstanding item remains open for 40 days (CA - 1 would reach Dunning Level 4)
Further, As per the F1 help mentioned for the field - Dunning frequency:
The second dunning notice at dunning level 3 is prevented if you specify a dunning frequency of 10 days for dunning level 3. In that case, a dunning notice at dunning level 4 will be created ONLY on 10.07.2014, since the days in arrears for dunning level 4 have been reached.
So currently, the system is behaving in a way which is contradicting the details mentioned in F1 help.
Please advise how can we ensure that the CA - 1 is not picked up at the same Dunning Level repeatedly and confirms with the details mentioned in the F1 help.
Thanks and regards,
G. Ajit Kumar

Hi Ajit,
Check the parameter value for the last dunning level against the dunning procedure ZA in the SPRO config.
I think it is currently configured as 2-Dun after end of dunning frequency for all line items.
Ideally it should be 3-Dunning for new overdue items only
You can find this in the following config-
SPRO-->Financial Accounting--->Contract Accounts Receivable and Payable-->Business Transactions-->Dunning--->Configure Dunning Procedure
Select the Dunning Procedure and click on display and you will find it under the parameters section.
Hope it helps...
Thanks,
Amlan

Dunning Activity

Similar Messages

Maybe you are looking for