Oracle Auto Receipt in R12

5/21/2018 Oracle Auto Receipt in R12

1/17

Cash Study on Automatic Receipt in R12

Product: Oracle Receivables EBusiness Suite Product: 12.0.6

Author : TG Saravanan

Company : Hexaware TechnologiesDate : 18-Jan-2009

Case Study Abstract

This case study describes the setups and transactions for automatic receipts in R12. In this casestudy, we have shared our experience in configuring the clients requirements in creating the

automatic receipts. Unlike R11, we need to perform the dummy funds capture setups for theautomatic receipts in R12.

Client Requirement

One of our client is having more than 30 branches and sale is done from all these branches.Money is received in terms of Cash, Local Cheque, Outstation Cheque, Credit Card and DirectDebit. These sales are captured in a web portal and the details should be transferred to

receivables. For each branch and for each receipt method (cash, local cheque, etc), onereceivable invoice should be created automatically with invoice number as Pay-in slip number

(which is the reference number from the Potal) from the data received from the portal in an excelfile. Pay-in slip number is unique for branch and receipt method combination. Receipt

transaction should also be created along with the invoice as money is received during the sale.The receipt number should be same as that of the invoice number (Pay-in slip number)

The accountant at the branch will create the remittance transaction and deposit the cheques/cash

in the bank. The remittance challan contains the pay-in slip number. As soon as all the chequesare cleared, the bank captures the pay-in slip number with the total cleared amount. Hence it

becomes easier to reconcile the receipts.

We will explain how we have accomplished the invoice with automatic recipt in R12 satisfyingthe clients requirements. Remittance and reconciliation transactions are not covered in this

document.

Setup

The service for the customer is rendered only after receiving the money. There are different

receipt methods such as Cash, Check and Credit Card. Hence we need to create both invoice and

receipt automatically for all the receipt methods. The scope is not to integrate the oracle system

with the customer payment system. Hence we have done a dummy funds capture setup.


2/17

The steps followed is given below.

Sr No Step

1 Create Payment System

2 Create a Payee3 Create a Funds Process Profile

4 Attach Payment system and Funds Process Profile in Payee

5 Create a Automatic Receipt Method

6 Create a Document Sequence and Attach with Receipt Method

7 Attach Receipt Method and Customer Bank Account to Customer

8 Create an Invoice with Automatic Receipt Method

9 Create a Receipt

We created a Role called Funds Capture Admin Setup using sysadmin and attached with the

user. The details of creation of role and attaching the role to the user is not covered in this

document.

1. Create Payment System

We created a dummy payment system as described below.


3/17

We created the payment system with the following values.

Code XYZ

Name XYZ Payment SystemProcessing Model Processor

Bank Account Transfer checkbox is checked in Funds Capture Tab.

Formats Name Electronic Bank Remittance FormatPayment System Code XYZ Dummy

Name XYZ Dummy Payment SystemData Type Number

Bank Account Lead Days 0

After creating the payment system, we have done the account creation by clicking Save andAdd Accounts button.


4/17

We have created one dummy account called XYZ Dummy Account. With this, we completed

the Payment System Setup.


5/17

2. Create Payee

We created a payee with the following details.

Code ABCName ABC DUMMY CUSTOMER

Payment System XYZ Payment System (created in the previous step)Payment System Account XYZ Dummy Account (created in the previous step)

Supported Processing Types Bank Account Transfer checkbox is checked.


6/17

3. Create Funds Process Profile

We created the funds capture process profile for the payment system created in step 1 (XYZ

Payment System).


7/17

We created the funds capture process profile with the following values.

Code XYZ Funds Process ProfileName XYZ Funds Process Profile

Processing Type Bank AccountOutbound Format Electronic Bank Remittance Format

Settlement Grouping

First Party Organization Checkbox is uncheckedFirst Party Legal Entity Checkbox is checked

Internal Bank Account Checkbox is checkedSettlement Currency Checkbox is checked

Settlement Date Checkbox is unchecked


8/17

In the Payment System Account, enabled checkbox is checked.


9/17

4. Attach Payment system and Funds Process Profile in Payee

In this step, we attached the payment system account (created in step 1) and Funds capture

process profile (created in step 3) with the Payee created in step 2.

The Payee created in step 2 was queried and updated with payment system account and funds

capture process profile.


10/17

We created a routing rule as given below.

Rule Name One Rule for AllCriterion Amount

Operator Greater than or Equal to

Value 1


11/17

5. Create Automatic Receipt Method

We created a receipt with the creation method as Automatic. As we require the receipt number

to be same as that of invoice number, Receipts Inherit Transaction Numbers checkbox is

checked. In the funds processing section, we have selected Bank Account Transfer.


12/17

6. Create a Document Sequence

We created a sequence name and attached it with the automatic receipt method created in the

previous step. We have set profile Option Sequence Numbering at the responsibility level to

Partially Used.


13/17

7. Attach Receipt Method and Customer Bank Account to Customer

We created customers and attached the receipt method and customer bank account.

With this, we have completed all the setups.


14/17

Transactions

8. Create Invoice

AR invoice is created with automatic payment details. The sale is made only after the payment is

received. Hence the payment term is always immediate for these kinds of sale and due date is

same as that of the invoice date. When we create this invoice through Autoinvoice program,

PAYMENT_TRXN_EXTENSION_ID was populated in the AR_INTERFACE_LINES table using the

API IBY_FNDCPT_TRXN_PUB.Create_Transaction_Extension.

Mandatory for

Automatic Receipts


15/17

9. Run Automatic Receipts Creation Program (API) concurrent program.

We run this program (scheduled) with the following parameter values

Batch Date Current Date. As due date is the invoice date, the automatic receiptprogram will select the invoices for the current date.

Batch GL Date Current DateApprove Yes

Format YesCurrency Currency was different for different schedule programs (INR, USD,

AED, etc)Receipt Class Automatic Receipt (Created in step 5)

Receipt Method The receipt method selected in the invoice was selected here.

The batch date given in the parameter and the lead days given in the receipt method are moreimportant for the invoices to get selected in the automatic receipt. Basically, Batch Date plus

lead days should be less than or equal to the due date of the invoice. Also we found that paymentmethod parameter is mandatory in the Automatic Receipts Creation Program (API) SRS.

When Approval and Format parameters are given as Yes, the receipt batch is approved andformatted.


16/17

Automatic receipt batch is created with the status of Completed Format.

If Receipts Inherit Invoice Number is not enabled in the receipt method, then we found that the

receipt number is created in the following format.

Receipt Number Format: -.

If Receipts Inherit Invoice Number is enabled in the receipt method, then receipt was created

with receipt number same as that of the invoice number.


17/17

References

R12 - Oracle Receivables Implementation Guide

Metalink Note ID 471418.1 - Oracle Payments Setup For Funds Capture ProcessingMetalink Note ID 560573.1 - Autoinvoice: The Customer_Bank_Account_ID is Obsolete

Metalink Note ID 749032.1 - R12: Automatic Receipts Progam Does Not Assign Invoice

Number As Receipt Number

Date post:	11-Oct-2015
Category:	Documents
Upload:	ali-ibrahim-hussein
View:	55 times
Download:	1 times

Oracle Auto Receipt in R12

Documents