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.

After the ‘ultimate collection’ of PeopleSoft and Siebel, this last post in the series is an ‘ultimate collection’ of E-Business Suite (re)sources.

• E-Business Suite Wiki: E-Business Suite Wiki by Oracle
• Product tagged E-Business Suite : Siebel related products from the Oracle Mix Social Network
• Ideas tagged E-Business Suite: Ideas about E-Business Suite via the Oracle Mix Social Network
• Oracle Mix E-Business Suite Groups: E-Business Suite groups via the Oracle Mix Social Network

Did you ever had to revise custom reports? DId you ever try to move the address a few millimetres to the right because off the introduction of new corporate stationery? Did you ever get headaches because the reporting tool Oracle Reports Developer was crashing once more destroying your recent modifications?

There is a new kid in (reporting) town…

With the introduction of the reporting tool BI Publisher (formerly XML Publisher) these problems are history. Using the tool introduced by Oracle in 2004 as XML Publisher the main disadvantages of the classic reporting environment become outdated:

1. No open standard
2. Not a user-friendly interface
3. No automatic report translations
4. No support for all formats
5. Extraction of data from a non-Oracle DB is problematic
6. Extensive tool training
7. High development costs
8. ‘Eternal’ maintenance
9. High upgrade costs