Skip to Content

Introduction:

In conventional SAP, the form provided for the Dunning Letter is a sap script, whereas in SAP Best Practice, SAP has provided a smartform for Dunning Letter.

In this edition, I will share my findings in one of my SAP Best Practice imply project.

This blog is related to Dunning Letter config & coding  from ABAPer prospective only.You may find some other ways also to do the same.

We have to follow below mentioned steps:

  • Copy Smartform
  • Config BTE
  • Attach dunning form to Dunning procedures
  • Coding for email
  • Final Output

 

1.   Copy Smartform

  • Smartform for Dunning Letter – YBUS_FIMA.
  • We just need to copy it into our Z* smartform and make the changes.
  • This smartform has almost everything, you only need to add company logo & address

F Only catch here is the length of smartform name, it should not exceed 16.

/wp-content/uploads/2015/03/1_665323.png

  • SAP Best Practice also provided the smart style YBUS_SFSTYLE, we can copy it and use it OR we can make the changes in it as well

/wp-content/uploads/2015/03/2_665393.png

2. Config BTE

  • Transaction code – FIBFMaintenance transaction BTE
  • Click on Settings->P/S Modules->…of an SAP Application (check figure)

/wp-content/uploads/2015/03/3_665394.png

  • Hit ENTER 2 times
  • Check for Event 00001720 FI-FI (check figure)
  • Change the FM to FI_PRINT_DUNNING_NOTICE_SMARTF

/wp-content/uploads/2015/03/4_665395.png

  • Save it

3. Attach dunning form to dunning procedures

  • Go to tcode FBMP

/wp-content/uploads/2015/03/5_665399.png

  • Double click on Procedure 0001
  • Click on Dunning texts (check figure)

/wp-content/uploads/2015/03/6_665401.png

  • Enter company code 1000

/wp-content/uploads/2015/03/7_665402.png

  • Change the form name to Z* dunning smartform for all the four levels OR if you have different dunning forms for each level, maintain those forms here for each procedure

/wp-content/uploads/2015/03/8_665403.png

  • Save it

4. Coding for email

  • There is standard BTE 00001040 provided by SAP which is called when dunning is running (F150). SAP has also provided sample function module SAMPLE_PROCESS_00001040 to indicate how to use this BTE. The FM imports I_KNA1 structure and return structure C_FINAA.
  • Copy this FM SAMPLE_PROCESS_00001040 to Z*FM

/wp-content/uploads/2015/03/9_665404.png

  • Here we have passed C_FINAA-NACHA = ‘I’, C_FINAA-INTAD = customer email id(check the coding)
  • And also pass email Subject in C_ITCPO-TDCOVTITLE = ‘Reminder: Dunning Letter’
  • For email body we have to create a text ID in SO10 as

/wp-content/uploads/2015/03/10_665411.png

/wp-content/uploads/2015/03/11_665412.png

  • We need to attach this Z*FM to BTE 00001040
  • Go to transaction FIBF. Settings-> Process Modules-> of SAP Application
  • Add new entry with Process 00001040 FI-FI and FM as Z*FM created above

/wp-content/uploads/2015/03/12_665413.png

5. Final Output

  • Transaction code – F150, click Dunn.history

/wp-content/uploads/2015/03/13_665418.png

  • Next screen enter the values

/wp-content/uploads/2015/03/14_665419.png

  • On next screen, select one entry and click on Display dunning notice icon

/wp-content/uploads/2015/03/15_665420.png

  • Print preview

/wp-content/uploads/2015/03/17_665421.png

  • On print preview screen hit … F3…will get a popup as

/wp-content/uploads/2015/03/18_665422.png

  • Press Yes, it will trigger an email
  • You can check in tcode SOST
  • The above popup email id will appear automatically if it is maintained in the customer master

/wp-content/uploads/2015/03/19_665423.png

Thanks,

Rahul

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply