Within Oracle R12 it’s possible to Personalize Self-Service pages. To enable this option you need to set the the following  profile options at user level.

• Personalize Self-Service Defn
• FND: Personalization Region Link Enabled

After setting the above profile options you can see now different region links which you can click on and do personalization for.

• Navigate> Functional Administrator Responsibility
• Click Personalization tab
• Fill in the Application Name or Document Path
• Select you personalization
• Choose one of the options like;  Delete Personalization or Deactivate

In R12 when setting up a new supplier in AP, you can add a bank account number at 4 different levels, namely:

1. Address
2. Address – Operating Unit
3. Site
4. Supplier (system default)

Because of mostly third party banking tools like APRO Banking Gateway requires to  add a bank account number at Site Level, you have to change manually the bank account assignment level from Supplier to Site Level. This is a frequently forgotten step when creating a new supplier.

You can easily change the default bank account assignment level from Supplier to Site Level by personalization.

-Create a new supplier or change an existing one.

-Click on the banking details hyperlink on the left menu.

-Click on Personalize “Bank Account and Assignment Details”

-Click on Personalize “Message Choice: Select Account Assignment Level”

-Change the initial value to “SITE”
-Click on apply

Result after personalization:

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.