Dunning Letters: Introduction Dunning
Reports are used by Oracle Receivables to inform your customers of past
due invoices, debit memos, and chargebacks. When dunning letters are
printed, Oracle Receivables prints a copy of each invoice which has line
items that are past due. Dunning letters can be defined at various levels to change the tone each time. There is flexibility within Oracle Receivables to define Dunning Letter Sets and Dunning Letters to correspond to that. These
dunning letter sets can then be defined against customer profiles to
determine the dunning letter that would be sent to a given customer. The default Oracle program only provides for Text based dunning letters and not RTF based letters. Background Dunning letters can be modified to look at RTF templates by understanding the following: 1. Dunning letters are generated using the concurrent program: Dunning Letter Generate.(ARDLGP) This
can be run as a preliminary report where the invoices of customers are
listed out without printing dunning letters or as a final report by
setting the preliminary flag to No. When the dunning report is run in the preliminary mode it launches the concurrent program: Dunning Letters - Preliminary(ARXDUNP) In Final mode it launches the program: Dunning Letter Print from Dunning Letter Generate(ARDLP_NON_SRS) Both
the dunning letters programs are not standalone programs and would be
launched by the spawned process Dunning Letter Generate. The programs Dunning Letters - Preliminary and Dunning Letter Print from Dunning Letter Generate(ARDLP_NON_SRS) are both oracle reports. Therefore these can both be modified to output xml as the output rather than text. However these are launched by spawned processes and hence they cannot be launched standalone. These need to have their templates set in the post-report trigger. This can be done by calling out to the concurrent program: l_req_id := FND_REQUEST.SUBMIT_REQUEST('XDO','XDOREPPB',NULL,NULL,FALSE, Similarly if we need to burst the xml output we can call out to the program: l_burst_id :=fnd_request.submit_request('XDO','XDOBURSTREP','','',FALSE,l_req_id ,'Y',chr(0), |
Technical > BI Publisher >