Anil R Patil's Oracle Applications Blog » Receivables

What is Revenue Recognition ?

anilrpatil — Tue, 22 Dec 2009 04:21:33 +0000

I have seen a lot of people getting confused with the concept of Revenue Recognition. I have also seen some people who very well understand how Revenue Recognition works in Oracle Receivables (in technical terms), but do not clearly understand why it is done and what business objective it serves. Here is my atempt to explain the concept of Revenue Recognition. Hope it helps.

Click here to read the document

[Keywords: Revenue Recognition, Revenue Management, Deferred Revenue, Earned Revenue, Unearned Revenue, Bill in Advance]

How to Implement Oracle Receivables Lockbox Functionality

anilrpatil — Sun, 29 Nov 2009 00:23:10 +0000

The following document gives you a step by step guide for implementing Oracle Receivables Lockbox functionality.

Click here to download the document

[Keywords: AutoLockbox, Lockbox, Receipt Class, Receipt Method, Receipt Source, UMX Security Wizard, Transmission Format, AutoCash Rule Sets, MICR]

Code Snippets: Various Queries on Customer Data (HZ Tables)

anilrpatil — Wed, 18 Nov 2009 18:48:25 +0000

There have been many instances where I have been asked by the Business Users to provide Customer Listing reports based on different parameters. The different requests typically are as follows

Customer listing with all Sites for a specific Org
A listing of only those Customer with whom we have had transactions in the last ‘x’ years
A listing of all Customer Sites that do not have any Business purpose associated with it
Customer Listing By Collector
Customer Listing along with Profile Class names and Collector names
And so on …

We have the Standard Customer Listing Reports in the application. However these reports are not org stripped because the HZ_CUST_ACCOUNTS data is not org stripped plus the standard reports could not be used for all different flavors of the Business requests. In these cases, I used the following queries

Click here to read the queries

[Keywords: hz_parties, hz_cust_accounts, hz_cust_site_uses_all, hz_party_sites, hz_cust_acct_sites_all, hz_locations]

Migrating Customer Call Notes from AR to Advanced Collections using JTF_NOTES_PUB API

anilrpatil — Sat, 24 Oct 2009 04:15:34 +0000

The Objective of this document is to explain how we migrated Call Notes from AR to Advanced Collections

Our client is implementing Advanced Collections. The Client is currently using AR Collections Workbench to manage its Collections Activities. As such the Call notes are currently maintained in AR in the Customer Calls form as a Response Note or a Call Topic Note . These notes are either at the account level or a transaction level. When the Collectors switch to the Collections form in Advanced Collections, the AR Call notes cannot be viewed in the Notes Tab. Hence there is a need to migrate the AR Call notes from AR to Advanced Collections

Click here to read our solution

[Keywords: JTF_NOTES_PUB, API, CRM Notes]

Apply On-Account Credit Memo’s to Invoices using AR_RECEIPT_API_PUB

anilrpatil — Sat, 24 Oct 2009 04:03:28 +0000

Automation of manual activities is the norm and that’s where Oracle Standard API’s helps me a lot. The Business scenario for my client is as follows
1. The Client imports feeder system transactions data into Oracle Receivables using RA INTERFACE
2. Credit Memo’s are imported as On-Account Credit Memo’s because there is not enough matching data available in the feeder system that would allow creating Credit transactions against the Invoices through autoinvoice.
3. The Credit Memo number and the related transaction number are maintained in a custom staging table.
4. The requirement was to be able to apply these On-Account Credit Memo’s to the Invoices.

Click here to read our solution

[Keywords: On-Account Credit Memo, AR_RECEIPT_API_PUB]

Rectifying Lockbox Errors Programmatically

anilrpatil — Sun, 18 Oct 2009 13:31:20 +0000

The purpose of this document is to explain how we rectified some of the recurring Lockbox Errors our client encountered using a custom concurrent program.

The users run the Lockbox process daily. Many receipts are rejected because either the lockbox data is incorrect or it conflicts with the Customer Setup data. The users have to manually correct the lockbox transmission data, which is a time consuming activity. There was therefore a need to write a small magic program (magic – because that’s what my client calls it) that would do the data rectification and clear most of the Lockbox errors. We created a custom concurrent program that the users ran after the first run of the Lockbox process.

The details of the different types of recurring errors encountered and our solution for the same is as follows…

Click here to read our solution for rectifying the lockbox errors

[ Keywords: Lockbox, Receipts, MICR, AR_PLB_BAD_MICR_NUM, AR_PLB_CUSTOMER_CONFLICT, AR_PLB_CUST_NUM_CONFLICT, Cash Application ]