please correct the receivable account assignment in oracle apps r12

R12 – Receivables Setups (AR) in Oracle Apps

• Define Chart of Accounts 
• Define Currencies 
• Define Calendars 
• Define Calendar Period Types 
• Define Ledger
• Assign Ledger to a Responsibility 

Define Chart of Accounts: Define Segments:  Navigation: General Ledger –> Setups –> Flexfields –> Key –> Segments. Query With Accounting Flexfield and click on New. Give your coa name and save.

Click on Segments. Enter your segments names.

Navigation: General Ledger –> Setups –> Flexfields –> Key –>Values. Enter the below information and click on find button.

Enter the company values names and save your work.

Like wish define values for all reaming segments. Define Currencies: Navigation: General Ledger –> Setup –> Currencies –> Define. Enter information and save.

Define Calendar Period Types: Navigation: Setup –> Financials –> Calendars –> Types. Enter the information and save.

Define Calendar: Navigation: Setup –> Financials –> Calendars –> Accounting.

Save. Define Ledger  : See this post for how to define Ledger in R12 . Assign Ledger to a Responsibility: Navigation: System Administrator –> Profile –> Systems.

Click on find. Assign Ledger to GL Responsibility.

Save. Oracle Inventory Setup Steps:

• Define Operating Unit.
• Define Inventory Organizations
• Define Items 

Define Operating Unit:

Enter information in the required fields.

Save your work and click on othres. click on Accounting information.

Enter the required information and save.

Click on Others and select the inventory information.

Under Inventory Parameters tab enter the following information.

Under Costing Information tab enter the following information.

Under the other accounts tab enter the required information.

• Define System Options
• Define Transaction Flexfield Structure
• Define Sales Tax Location Flexfield Structure
• Define AutoCash Rule Sets
• Define Receivables Lookups
• Define Invoice Line Ordering Rules
• Define Grouping Rules
• Define Application Rule Sets
• Define Payment Terms
• Define AutoAccounting
• Open or Close Accounting Periods
• Define Transaction Types
• Define Transaction Sources
• Define Collectors
• Define Approval Limits
• Define Remittance Banks
• Define Receivables Activities
• Define Receipt Classes
• Define Receipt Sources
• Define Payment Methods
•  Define Statement Cycles
• Define System Profile Options
• Define Salespersons
• Define Customer Profile Classes
• Define Customers
• Define Remit–To Addresses

Define Remittance Banks: Proceed to the next step if you already defined your remittance banks in Oracle Payables. Define all of the banks and bank accounts you use to remit your payments. You can define as many banks and bank accounts as you need and define multiple currency bank accounts to accept payments in more than one currency. Define Receivables Activities Define Receivables Activities to provide default accounting information when you create adjustments, discounts, finance charges, miscellaneous cash transactions, and bills receivable. Receivables also uses Receivables Activities to account for tax if you calculate tax on these activities. Navigation: Receivables –> Setup –> Receipts –> Receivable Activities.

Like wise we should define reaming receivable actives also. Define Receipt Classes: Define receipt classes to specify whether receipts are created manually or automatically. For manual receipts, you can specify whether to automatically remit it to the bank and/or clear your accounts. For automatic receipts, you can specify a remittance and clearance method, and whether receipts using this class require confirmation. Navigation: Receivables –> Setup –> Receipts –> Receipts Class.

Click on Bank accounts. Enter information in respective fields.

Save your work. Define Payment Method: Define the payment methods to account for your receipt entries and applications and to determine a customer’s remittance bank information. When defining payment methods, you must enter a receipt class, remittance bank information, and the accounts associated with your payment receivables type. You can also specify accounts for confirmation, remittance, factoring, bank charges, and short–term debt. Navigation: Receivables –> Setup –> Receipts –> Receipts Class.

Define Statement Cycles:   Define statement cycles to control when you create customer statements. You assign statement cycles to customers in the Customer Profile Classes window. Navigation: Receivables –> Setup –> Print –> Statement Cycle.

Define profile options:   Define profile options to provide default values for some Receivables operations, specify how Receivables processes data, and control which actions users can perform. Navigation: Administrator –> Profile –> Systems. During your implementation, you set a value for each Receivables user profile option to specify how Receivables controls access to and processes data. Receivables lets you govern the behavior of many of the windows that use profile options. Profile options can be set at the following levels: • Site: This is the lowest profile level. Site level profile option values affect the way all applications run at a given site. • Application: These profile option values affect the way a given application runs. • Responsibility: These profile option values affect the way applications run for all users of a given responsibility. • User: These profile option values affect the way applications run for a specific application user. The values you enter for options at the User level supersede the values that your system administrator has entered for you for these options. Each of these user profile options affect the behavior of Receivables in different contexts. In Receivables, operations that profile options can affect include receipt application, the entry of adjustments, the creation and remittance of automatic receipts and taxes, and posting to your general ledger. You may also have additional user profile options on your system that are specific to applications other than Receivables. To change profile options at the Site, Application, or Responsibility level, choose the System Administrator responsibility, then navigate to the Personal Profile Values window. Query the Profile Name field to display the profile options with their current settings, make your changes, then save your work. You can change profile options at the user level in the Personal Profile Values window. To do this, navigate to the Personal Profile Values window, query the profile option to change, enter a new User Value, then save your work. Generally, your system administrator sets and updates profile values at each level. Attention: For any changes that you make to profile options to take effect, you must either exit, and then reenter Receivables, or switch responsibilities.

    Define Salespersons: Define salespersons to allocate sales credits to invoices, debit memos, and commitments. If you do not want to assign sales credits for a transaction, you can enter No Sales Credit. If AutoAccounting depends on salesperson, Receivables uses the general ledger accounts that you enter for each salesperson along with your AutoAccounting rules to determine the default revenue, freight, and receivable accounts for transactions. Define Customer Profile Classes: Define customer profile classes to categorize customers based on credit, payment terms, statement cycle, automatic receipt, finance charge, dunning, and invoicing information. When you initially set up your customers, you assign each customer to a profile class. To customize the profile class for a specific customer, use the Customer Profile Classes window. Navigation: Receivables –> Customers –> Profile Classes. In Profile Class window enter the following information.

In Profile class Amount tab enter the following information.

Save your work. Define Customers: Define customers and customer site uses to enter transactions and receipts in Receivables. When you enter a new customer, you must enter the customer’s name, profile class and number (if automatic customer numbering is set to No). You can optionally enter customer addresses, contacts, site uses and telephone numbers. You must enter all the components of your chosen Sales Tax Location Flexfield when entering customer addresses in your home country. Navigation: Receivables –> Customers –> Standard. Define Remit–To Addresses:   Define remit–to addresses to inform your customers where to send payments. Associate each remit–to address with one or more state, country, and postal code combinations. For example, if you want your customers in California and Nevada to send their payments to a specific address, enter the remit–to address and associate the states CA and NV with this address. Remit–to addresses are assigned based on the bill–to address on the transaction. Navigation: Setup –> Print –> Remit-to-addresses. Click on Create Remit to addresses.

Enter the required information 

Click on Apply. Enter the country name in the same page and then click on the GO. Click on the Receipts form Create button.

Enter the following information and click on Apply button.

Share this:

Leave a reply, leave a reply cancel reply, recent comments.

• Guru on R12 Supplier Contact creation API
• himanshu dawra on Oracle E-Business Suite 12 Free Vision Instance
• Saqib ali Ali Khan on FRM-92050 Failed to Connect to Server
• Swapnil Dandgvhal on Inventory Organization and corresponding Operating Unit, Ledger and Legal Entity
• Sakshi Dhokale on HZ tables in Oracle Receivables

Latest Posts

• R12 – How to Handle NULL for :$FLEX$.VALUE_SET_NAME In Oracle ERP August 25, 2023 - 1:20 pm
• R12 – How to Delete Oracle AR Transactions March 22, 2019 - 8:37 pm
• How to Define Custom Key Flexfield (KFF) in R12 January 19, 2018 - 5:43 pm
• AutoLock Box Concepts In R12 November 10, 2017 - 8:30 am
• R12 – java.sql.SQLException: Invalid column type in OAF September 15, 2017 - 9:39 am

Ads Blocker Detected!!!

This site uses cookies and other tracking technologies to assist with navigation and your ability to provide feedback, analyse your use of our services, and provide content from third parties. By continuing to browse the site, you are agreeing to our use of cookies.

Cookie and Privacy Settings

We may request cookies to be set on your device. We use cookies to let us know when you visit our websites, how you interact with us, to enrich your user experience, and to customize your relationship with our website.

Click on the different category headings to find out more. You can also change some of your preferences. Note that blocking some types of cookies may impact your experience on our websites and the services we are able to offer.

These cookies are strictly necessary to provide you with services available through our website and to use some of its features.

Because these cookies are strictly necessary to deliver the website, refusing them will have impact how our site functions. You always can block or delete cookies by changing your browser settings and force blocking all cookies on this website. But this will always prompt you to accept/refuse cookies when revisiting our site.

We fully respect if you want to refuse cookies but to avoid asking you again and again kindly allow us to store a cookie for that. You are free to opt out any time or opt in for other cookies to get a better experience. If you refuse cookies we will remove all set cookies in our domain.

We provide you with a list of stored cookies on your computer in our domain so you can check what we stored. Due to security reasons we are not able to show or modify cookies from other domains. You can check these in your browser security settings.

These cookies collect information that is used either in aggregate form to help us understand how our website is being used or how effective our marketing campaigns are, or to help us customize our website and application for you in order to enhance your experience.

If you do not want that we track your visit to our site you can disable tracking in your browser here:

We also use different external services like Google Webfonts, Google Maps, and external Video providers. Since these providers may collect personal data like your IP address we allow you to block them here. Please be aware that this might heavily reduce the functionality and appearance of our site. Changes will take effect once you reload the page.

Google Webfont Settings:

Google Map Settings:

Google reCaptcha Settings:

Vimeo and Youtube video embeds:

The following cookies are also needed - You can choose if you want to allow them:

You can read about our cookies and privacy settings in detail on our Privacy Policy Page.

Error In Auto Invoice: Please Correct the Revenue Account Assignment

Error In Auto Invoice: Please correct the revenue account assignment Hi, We are unable to see the AR transactions in sales invoice report. Since auto invoice import program shows above error, but those transactions already available in transaction work bench with completed status. Regards, Srikanth reddy.

Thanks your suggestion is very perfect for me. i have resolved issue.

Correct the Revenue account in all transactions distribution accounts. This is a data fix in R12.

Please check the data fix from oracle support to resolve this error permanently.

We are having the same issue OM to AR - Revenue Account is set as Standard Line in Auto Accounting… What did you do to resolve?

What is the solution that you got to resolve this issue?

Thanks everybody.

Issue resolved

According to your Auto Accounting setup, Revenue account should be present in Standard Line and Transaction Type. If any one of this missing, you will encounter this error.

There is another posibility that the values you have given in these setups may be invalid or some security rule existing

Please check these aspects thoroughly

Hi Srikanth

Kindly check the revenue distribution account of that transaction & correct it.

Regards Kishore

For a Memo Line

Responsibility: Receivables Manager Navigation: Setup > Transactions > Memo Lines

Make sure that the Revenue Account is populated

Please check revenue account is attached to standard line. Means at inventory item level or memo line level.

Regards, Milind

We already done the auto accounting setup for revenue…

Segment Table name constant company - 250 cost-center Standard line Account Standard line sub_a/c Standard line Product Standard line Employee Transaction Type Future1 TT

I checked in memo line also there is no setup for revenue. Here I am unable to understand how can we map standard line for inventory item.

Regards, Srikanth Reddy

Hi Srikanth,

Please provide Auto Accounting rule for revenue. So based on this setup Revenue Account will be pickup.

AR: Auto Accounting Receviable Manager> Setup> Transactions> AutoAccounting

Related Topics

Oracle Apps Knowledge Sharing

Meant for sharing our knowledge related to Oracle E-Business Suite

• TECHNICAL TUTORIALS
• USEFUL LINKS
• ARTICLE INDEX
• VIDEO INDEX

Wednesday, March 24, 2010

R12 account receivables: receipt application overview.

We can apply a receipt against the below canditates,  1. Credit Memo  2. Invoice  3. Related Customer’s Invoice  4. Deposit  5. Chargeback  6. Debit Memo and even open Receipts. Further we can do three more actions named Refund, Receipt Write-off’s, On Account. For every application we can find a new record in the table named “ AR_RECEIVABLE_APPLICATIONS_ALL ” with the application type as “CASH”. For example, If Receipt amount = 1500 and got applied against a invoice with amount 500. Then APPLIED_AMOUNT becomes 500 and UNAPPLIED AMOUNT becomes 1000. Further if you want to see the above data from back end use the below query, SELECT status               , SUM ( amount_applied ) FROM    ar_receivable_applications_all WHERE cash_receipt_id = '&cash_receipt_id' GROUP BY status ; Further we have the below important columns in “AR_RECEIVABLE_APPLICATIONS_ALL” table,  Payment_schedule_id ,code_combination_id ,apply_date ,applied_customer_trx_id,  Incase, if the application is at line level then we have the below columns also,  Rule_set_id ,line_applied ,tax_applied ,applied_customer_trx_line_id ,freight_applied If you want to know more information about the “RULE_SET_ID” then please check the below tables AR_APP_RULE_SETS AR_APP_RULES This rule_set_id defaulted to each org_id and the corresponding information can be found in the table AR_SYSTEM_PARAMETERS_ALL

Do you think this Article is useful?

0 Responses to “R12 Account Receivables: Receipt Application Overview”

Post a comment, stay connected.

Popular Posts

• Query to Fetch Employee Details in Oracle Apps R12 (PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_JOBS, PER_ALL_POSITIONS, PER_PHONES)
• Query to get active Customer and their Profile Details (HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUSTOMER_PROFILES, HZ_CUST_PROFILE_AMTS)
• Query to fetch Purchase Receipt and its related Purchase order, Vendor details in Oracle Apps R12 (RCV_TRANSACTIONS, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES)
• WSH_DELIVERY_DETAILS.RELEASED_STATUS ( Pick Release Status)
• How to get Oracle Application User Password from database - oracle.apps.fnd.security.WebSessionManagerProc.decrypt
• Query to get basic AP Invoice and Payment information from Oracle Apps R12
• Query to fetch Legal Entity, Business group details in Oracle Apps R12 - per_business_groups,xle_firstparty_information_v
• How to find Order types in R12 (Script for Order types)
• Query To Fetch Customer Account/Site Contact Details in R12
• Query to fetch Purchase Requisition, BPA, Purchase Order and Vendor Details in Oracle Apps R12 (PO_REQUISITION_HEADERS_ALL, PO_HEADERS_ALL)

Blog Archive

shareoracleapps.com

Site Stats (Last 30 Days)

Pay On Receipt (Evaluated Receipt Settlement)

Introduction:  

Oracle Receivables – Version 12.1 and later

Pay on Receipt, also known as ERS (Evaluated Receipt Settlement), or Self-Billing, is an Oracle Purchasing concurrent program, which automatically creates invoices in Payables and matches them with Purchase Orders for the received amount.

How do we solve:

When Pay on Receipt Auto invoice (PRA) is ran, it in turn launches Payables Open Interface Import program (PII). PRA updates invoice_status_code of rcv_transactions (Receipt – Receiving) to INVOICED, then populates records in ap_invoices_interface and ap_invoice_lines_interface. Then the interface data is committed and PII is invoked to create the invoices.

If PII program errors out for some reason during the validation of AP interface data then the records stay in interface tables with REJECTED status and the associated error information will be stored in AP_INTERAFACE_REJECTIONS table.

PRA sets invoice_status_code of rcv_transactions, for transaction_type RECEIVE, to INVOICED for both successfully imported invoices and for invoices rejected by PII.

If Pay on Receipt AutoInvoice is ran again later then it will pick only those records which have invoice_status_code as ‘PENDING. It will not pick/process the records which have invoice_status_code = INVOICED.

Before this, at the time receiving transactions ( Receipt ), system checks for the value of the vendor site’s Pay On Code. If Pay On Code is set to ‘Receipt’ (Pay On = Receipt), then invoice_status_code is inserted into rcv_transactions as ‘PENDING’, otherwise it will be inserted as null. PRA Program will process the receiving transactions with invoice_status_code as ‘Pending’ only and updates the status to ‘Invoiced’.

1.Basic Setup Required

1) Navigation: Purchasing Super User Responsibility > Supply Base > Suppliers. Query the Supplier to be associated with the Purchase Order. Select Site button. In the General Tab, select the Pay and Purchasing check boxes:

2) In the Purchasing Tab of the Supplier Sites form in the Self Billing section, the Pay On and Invoice Summary Level fields are set as follows (this set up is done in Payables):

Pay On = Receipt

If Pay On is set to ‘Receipt’, Invoice Summary Level settings may be one of the following:

• Pay Site = one invoice is created per supplier pay site.
• Packing Slip = one invoice is created per packing slip per supplier pay site.
• Receipt = one invoice is created per receipt per supplier pay site.

The above settings will determine how the invoice number is created:

The Invoice Number is of the following format:

‘ERS’–where:

– ERS is the default prefix for Pay On Receipt invoices, or any prefix specified in

the profile option PO:ERS Invoice Number Prefix.

In the above setting, ‘Seq#’ is a unique system generated number, where X Depends on the summary level indicated above in the Invoice Summary Level Setting:.

3) Navigation: Purchasing Super User > Purchase Order > Purchase Order > Terms window.

The Pay On field should be set to ‘Receipt’:

4) Navigation: Payables > Setup > Options > Payables > Invoice Tab:

Under GL Date Basis, there are four options. The accounting date will be based on the option selected here:

• Invoice Date (Invoice date entered on the Invoice in Accounts Payable)
• System Date (Current/system date the invoice was entered in Accounts Payable)
• Goods Received / Invoice Date (Invoice date entered on the receipt in Accounts Receivable)
• Goods Received / System Date (Current/system date the receipt was entered in Accounts Receivable)

Pay on Receipt(s) in Oracle Apps R12

Pay on Receipt(s) in Oracle Apps R12 POR (Pay on Receipt) is a feature in P2P cycle. Its helping to generate the invoice automatically when you receive the goods.

Pre-Requisites 1. Supplier site should be enabled the following flags. (PAY and PURCHASING) 2. “Pay on” field should have a value “Receipt”. The invoice summary level should also have the value of “Receipt”. 3. In Purchase Order; Terms window “Pay On” field value should be “Receipt”.

1. Supplier Creation Navigation (Purchasing Super User > Supply Base > Suppliers > Create Supplier) Name    : SUPPLIER_1 Type     : Standard Country : United States

• Supplier Site Creation (Address Book) Enter valid address and check the PURCHASING & PAYMENT flags.

(Approval Notification)

Inventory Responsibility >> Receipts

Purchasing Responsibility >> Requests >> Submit Request (“Pay On Receipt Autoinvoice”)

It’s automatically submits the “Payables Open Interface Import”. Verify the invoice details.

Conclusion:

POR (Pay on Receipt) is a feature in P2P cycle. It’s helping to generate the invoice automatically when you receive the goods.

Start typing and press Enter to search