Oracle Functional Consultant Blog

Oracle Functional Blogs

Oracle Payables Escheatment Process Howto

Posted by Kumar on March 12, 2009

Hi

If you are working  with Oracle Payables you might come across on questions related to Escheatment process.  The payables user guide does not have much info on this. Let me explain what  it is and how to go about it. Many a times Some vendors forget to cash their check for various reasons. Believe me it happens in real world for whatever reason it is . We had over  200k (dollar amount)  in uncashed checks. The US law requires that  you remind the suppliers about the uncashed checks . If  those checks remain uncashed after enough efforts you are required to   cancel the checks and remit the amount to the State  as the amount is not yours but it belongs to the suppliers who did not cash it.

In India  Companies are  required to remit the amount  to the Comapny Law board. How do you go about it.

It is very simple. As this happens with Checks run the query to identify  the checks, suplliers etc. I  have given a date of  01-Jan-2008 to identify the checks mailed in the years prior to 2008. Based on the results  you send out letters to the suppliers identified by the query.  Some suppliers might encash it or request for a new check, if they have lost the check (Void and reissue in such cases). Or ellse cancel the checks and remit the amount to the state after some time.

The query is as follows. You may have to modify it based on your AP department’s requirement.

select vendor_name,vendor_site_code, amount,check_date,check_number,
checkrun_name from ap_checks_all
where  1=1
and status_lookup_code=’NEGOTIABLE’
and check_date <’01-JAN-2008′

Thanks

Kumar

Posted in Oracle Functional, Oracle Functional ERP | Leave a Comment »

Make Concurrent Programs Incompatible Howto

Posted by Kumar on March 12, 2009

Many a times you have to make certain Concurrent Programs incompatible with itself or other programs.Oracle has defined many incompatiblity rules for you. But sometimes you may have to define additional incompatibility rules  to meet your business requirement.

In this case we found that AP Invoice validation and Taxware (third party tax software in the US) have some issues in our instance. So we defined an incompatibility  rule to solve the issue.

The same solution was used by me to fix some payment batch set issues.We had defined different pay groups like Special handling(tax related payments), Vendor, Small Business etc. We created a batch set with all these paygroups and one catch all batch with no pay group  to run the batch for  all the other suppliers. Due to a bug Special handling  paygroup checks are created in its batch as well as the catch all pay group.To prevent this from happening  we defined an incompatibility rule  for Invoice selection. This served our purpose.We retained the payment batch sets  and run them now. It initially kicks off the selection program which would run one after the other.  Rest of the  programs like build, format and confirm would run simultaneously.

This helped us in a big way as we did not want to apply a patch to fix the bug at the year end.  This simple solution gave us the breather to carry on with our work at the year end.

So it is our ability to apply simple solutions that makes us happy at the end of the day.

Kumar

Make Concurrent Programs Incompatible Howto

Posted in Oracle Functional | Leave a Comment »

Oracle Advanced Collections

Posted by Kumar on March 11, 2009

collections_part 1

Oracle Advanced Collections Part  1

I had prepared a document on Oracle Advanced Collections. The document introduces Oracle Advanced Collections module and  how to configure it.

Part 2  of the document is under preparation and I will post it as soon as it is ready.

Posted in Advanced Collections | Tagged: | Leave a Comment »

 
Follow

Get every new post delivered to your Inbox.