Controlling Accounting when Creating Receipt via AR_RECEIPT_API_PUB.CREATE_CASH

Controlling Accounting when Creating Receipt via AR_RECEIPT_API_PUB.CREATE_CASH

A prospect asked this question during an API Wizard Demo:

"Can we control the GL Accounting for a receipt created via API as we can by choosing Receipt Class when entering a Receipt Batch in Oracle forms?"

Answer:

Yes. In Oracle, a Receipt Class is comprised of some basic information, the most important of which is the 'Receipt Method'. It is the Receipt Method that actually controls the GL accounting, not the Receipt Class (but since a Receipt Method is associated with a Receipt Class and the user selects the Receipt Class when creating a batch in Oracle, it is more familiar). Receipt Methods can be associated with one or more Bank/Branch/Account combinations.

The key GL accounts which can be defaulted for a Receipt Method include: Cash, Bank Charges, Unapplied Receipts, Unidentified Receipts, On-Account Receipts, Unearned Discounts, Earned Discounts, and Claim Investigations.

The public API AR_RECEIPT_API_PUB.CREATE_CASH allows you to pass the Receipt Method as well as Bank info, providing the same control of GL Accounts as when entering a batch using a Receipt Class.

By the way, there are several other things you can do with ar_receipt_api_pub, including procedures: apply, apply_in_detail, unapply, process_payment, create_and_apply, create_payment_extension, reverse, apply_on_account, unapply_on_account, unapply_other_account, activity_application, activity_unapplication, create_misc, apply_open_receipt, unapply_open_receipt.  There's so much you can do with ar_receipt_api_pub.  Unfortunately, as many of you know, the one thing it can't do is create a receipt batch.  It's been on the Oracle enhancement list for a while, hopefully they get to it soon!