Since receivables dunning letters have been obsoleted in R12, it’s hard to find useful information on the Oracle Support site about dunning letters in R12, especially about running dunning letters at delinquency level. In R12 now you will need to run Oracle Advanced Collections Dunning Plans instead.
A couple of months ago one of our customers asked me to find out if it’s possible to send dunning letters at delinquency level per customer/transaction type. They were using 4 transaction types and wanted also a different dunning letter template for each transaction type, so I was facing another challenge on that.
I knew before I started my research that dunning letters in R12 were based on transaction scoring. You have to define one or more score components, score-engines and dunning plans to get this all working. Oracle delivers seeded score components and score-engines, but all that seeded stuff wasn’t really helpful for me.
First thing I did was searching for more information on the Oracle Support site and reading the implementation guide to get an idea where to begin with the setup. As you can guess I could find hardly any information about dunning letters at delinquency level. All information I found was about dunning letters at customer level, because 95% of the Oracle eBS customers is using dunning letters at customer level.
R12: Create dunning letters at delinquency level
Since receivables dunning letters have been obsoleted in R12, it’s hard to find useful information on the Oracle Support site about dunning letters in R12, especially about running dunning letters at delinquency level. In R12 now you will need to run Oracle Advanced Collections Dunning Plans instead.
A couple of months ago one of our customers asked me to find out if it’s possible to send dunning letters at delinquency level per customer/transaction type. They were using 4 transaction types and wanted also a different dunning letter template for each transaction type, so I was facing another challenge on that.
I knew before I started my research that dunning letters in R12 were based on transaction scoring. You have to define one or more score components, score-engines and dunning plans to get this all working. Oracle delivers seeded score components and score-engines, but all that seeded stuff wasn’t really helpful for me.
First thing I did was searching for more information on the Oracle Support site and reading the implementation guide to get an idea where to begin with the setup. As you can guess I could find hardly any information about dunning letters at delinquency level. All information I found was about dunning letters at customer level, because 95% of the Oracle eBS customers is using dunning letters at customer level.