How to define Bank In R12

By // 8 comments:
Define Bank:

You can define a bank or a clearing house. Define Banks to record internal banks, where you are the account holder of a receipt and/or disbursement account. If you use Payables, you can define external
banks where your suppliers are the account holders. Also, if you use Oracle Receivables, define banks to record external banks where your customers are the account holders of disbursement accounts. Define
Clearing Houses to record banks that process a magnetic tape of your receipt information which you send to them. These clearing institutions then create tapes of your customer receipt information which they forward to each of your remittance banks.

Setups for Defining the Banks

1.Define Grants and Roles:

Navigation: User Management --> Role & Role Inheritance.

Select the User Management Responsibility.

Click on Roles & Role Inheritance.



Enter Type, Category and Name of the payable responsibility name and click on GO.

Click on Update.

Click on Security Wizards.

Click on Save and Proceed.

Click on CE UMX Security Wizard.


Click on Add Legal Entities.



Select Bank Account Grants Use and Maintenance and Bank Account Transfers and then click on Apply.

Click on Apply.

2. Define Bank.

Navigation: Payable Manager --> Setup --> Payments --> Bank and Branches.

Click on Bank tab.

Click on Create.


Enter the Country and Bank Name and then click on Save and Next button.


If you want enter the bank address then enter required the information.


Click on Save and Next.

If you want enter the contacts details of the bank then enter the information.

Click on Finish

Define Branch:

Click on Create Branch.



Click on Continue.



Enter Branch Name Branch Type and then click on save and next button.


Enter the branch address details and then click on save and next button.


Enter the branch contact details and then click on Finsh.


Define Bank Account:

Click on Create Bank Account.


Click on Continue.



Select the Legal entity and Enable modules which we want to use this bank account.

Click on Next.



Enter the Bank account Name, Number and currency and then click on save and next.





Enter the cash and cash clearing accounts and then click on save and next button.



Add Operating unit to your bank

Click on Add Organization Access.



Enable Account use for Payable and Receivables and Organization Name and then click on Continue.



Click on Apply.

Click on Finish.



Defining Internal Bank Accounts:

You define internal bank accounts to define bank accounts for which you are the account holder. Oracle Receivables uses internal bank accounts to receive payments from customers. Oracle Payables uses
internal bank accounts to disburse funds to suppliers.
Prerequisite
  • You have installed Oracle Receivables.
  • Define custom payment formats for Payables payment documents

To define a basic bank account for receipts:
1. In the Banks window query an existing Bank.
2. Choose the Bank Accounts button. Enter the Bank Account Name and Bank Account Number. Optionally enter an Account Type andDescription.
3. If you want to use Bank Account validation, enter Check Digits.
4. Select Internal Account Use.
5. In the GL Accounts region, enter a Cash Account.
6. In the Receivables Options region, enter GL Account informationfor Remitted Receipts, Factored Receipts, and Short Term Debt.
7. In the More Receivables Options region, optionally enter Receipt and Discount GL Account information. 
8. Optionally enter contact information in the Contact region.
9. Save your work.
Prerequisite
  • You have installed Payables
To define a basic bank account for disbursements:
1. In the Banks window query an existing Bank.
2. Choose Bank Accounts. Enter the Bank Account Name and Bank Account Number.. If you will use this bank for payments you make with the EDI Gateway, enter an Account Type. Optionally enter a Description. The currency defaults from your functional currency. If you want to use Bank Account validation, enter Check Digits.
3. Select Internal Account Use.
4. In the GL Accounts region, enter a Cash Account.
5. In the Payables Options region, enter default information for your payment batches. Record whether you allow zero–amount payments and whether this is a pooled account.
6. Optionally enter contact information in the Account Contacts region.
7. Proceed with Defining and Maintaining Payables Payment

Defining Customer Bank Accounts
If you use Oracle Receivables, you can enter bank account information for your customers. Receivables uses this information when you receive electronic payments from your customers.
To define a customer bank account:
1. In the Banks window query an existing Bank.
2. Choose the Bank Accounts button. Enter the Bank Account Name and Bank Account Number. Optionally enter an Account Type and Description.
3. Select Customer Account Use.
4. Optionally enter contact information in the Contact region.
5. Save your work.
Defining Supplier Bank Accounts
You can enter information for bank accounts for which your supplier is the account holder. You then assign these accounts to the supplier and its sites. Payables uses this bank information when you create electronic payments for your suppliers.
Prerequisite
  •  Define the suppliers and supplier sites that use the bank account to receive electronic payments.
To define a supplier bank account:
1. In the Banks window query an existing Bank.
2. Choose the Bank Accounts button. Enter the Bank Account Name and Bank Account Number. Enter the EDI ID number. Optionally enter an Account Type and Description. Optionally change the account currency, which defaults from your functional currency. If you want to use Bank Account validation, enter Check Digits.
3. Select Supplier as the Account Use.
4. In the Supplier Assignments region list the supplier, and optionally list supplier sites, that use the account to receive electronic payments.
5. Optionally enter account holder information in the Account Holder region. Optionally enter contact information in the Account Contacts region.
6. Save your work.
7. In the Bank Accounts region of the Suppliers and Supplier Sites windows, verify for each supplier and site that all appropriate bank accounts are listed. For suppliers and supplier sites with multiple bank accounts, designate as the primary bank account one bankaccount per period and per currency.
Defining Multiple Currency Bank Accounts
If you define a multiple currency bank account, you should use manual payment reconciliation with it. Payables stores the payment currency you enter when you initiate a Payment Batch, enter a manual payment,
or create a Quick payment. The bank file details you receive from a bank will contain the bank account currency. Since the payment and bank account currencies could differ when you use a multiple currency
bank account, automatic reconciliation could result in numerous exceptions.
If you define a multiple currency bank account for payments, the currency of the bank account must be the same as your functional currency.
Prerequisites 
  • Enable the Use Multiple Currencies Payables option.
  • Enable the currencies you need in the Currencies window.
To define a multiple currency bank account:
1. Define a basic bank account for receipts or disbursements.  
• If you are defining a bank account for receipts, in the Receivables
Options region, enable the Multiple Currency Receipts option.
• If you are defining a bank account for disbursements, in the
Payables Options region, enable the Multiple Currency Payments
option and enter Realized Gain and Realized Loss accounts.
Payables Setup 2 – 123
Proceed with Defining and Maintaining Payables Payment
Documents: page 2 – 124. You can define payment documents
that use a payment format with any currency.
2. Save your work.
Defining Foreign Currency Bank Accounts
Prerequisites
q Enable the Use Multiple Currencies Payables option.
q Enable the currencies you need in the Currencies window. See:
Currencies Window (Oracle Applications System Administrator’s
Guide).
To define a foreign currency bank account:
1. Define a basic bank account for receipts or disbursements. 
• If you are defining a bank account for disbursements, in the Payables Options region, enter Realized Gain and Realized LossAccounts.
2. Save your work.

Mass Additions Create FAQ's R12

By // No comments:
Mass Additions Create FAQ's:



1. How often can you run Mass Additions Create during an open period?

A: You can run Mass Additions Create as often as you like during an open period.  You should run the create program regularly so that you do not have an excessive number of invoice distributions to review at one time.
   
2. What data is transferred when an invoice line becomes a mass addition line?

A:There is confusion over the actual data that is sent from the invoice line into the mass addition line.Here is a quick guide to the important fields that exist on the Prepare Mass Additions form and what they represent:
Invoice Number - This defaults from the invoice header.
Line Number - This defaults from the invoice distribution line number.
Queue - All Mass Additions from AP come in on the NEW queue.
Description - This corresponds to the invoice line distribution description. One mass addition line is created per invoice distribution.
Units - If the invoice is not matched to a purchase order then mass addition lines will be created with a default of one unit.
Cost - This will match the invoice line distribution amount.
Category - This will ONLY be populated if the item on your invoice line is defined in Oracle Inventory with a default category. Normally this field is NULL.
Supplier Name and Number - These default from the invoice header.
PO Number - This will be populated if the invoice is matched to an Purchase Order.
Source Batch - This will be populated if you entered a Batch Name when as a Parameter when running the Payables Transfer to GL.
Project Number - This will contain the Project Number if the line came from Oracle Projects.
Task Number - Oracle Projects field.
Create Batch - This number represents the concurrent request id of the Create Mass Additions run that created the line.
Create Date - This is the same as the invoice date.
Source System - This is how we can tell where the line originated e.g. Oracle Payables.
Invoice Date - This is populated from the invoice.
Clearing Account - This will contain the invoice line distribution GL Account that would correspond to an existing Asset Categories Clearing Account segment.
Asset Type - This is defaulted from the asset category - e.g Capitalized if the invoice line matched an Asset Clearing Account and Expensed if the invoice line was an expensed item that was tracked as an asset.
Book - This is defaulted from the book that Mass Additions Create was run.
Depreciate - This is automatically checked if the asset type is capitalized and not checked if the mass addition line is of type Expensed.
Date in Service - This depends on the sysdate.
  
3. Mass Addition Lines have been created but the log file shows a warning about the number of units being invalid. What does this mean?

A: If an invoice is not matched to a Purchase Order then Mass Additions Create will always create a mass addition line with one unit and you would get a warning in the log file along the lines of:
Invoice ID: 119788 Distribution Line Number: 10 Warning!
Warning: Invalid Units. Mass Additions created with 1 unit
Cause: The invoice line from which you created a mass addition has units greater than the limit of 9999, null units or fractional units.
When an invoice line is not matched to a Purchase Order, the units associated with the invoice line are NULL. In Oracle Assets, the units column is required to permit the assignment of depreciation expense account distributions.  Therefore a default value of 1 is assigned to these lines.
  
4. How is the DPIS for the mass addition line determined?

A: You may expect that the date placed in service should be the invoice date, however this is not true.
If the sysdate is in the current open period, the default date placed in service is the calendar date you enter the asset.  If the calendar date is before the current open period, the default date is the first day of the open period.  If the calendar date is after the current open period, the default date is the last day of the open period.  You have the choice of accepting this date or entering any other date in the current accounting period or any prioir period.  You can never add assets with a future DPIS.  You can change the DPIS at any time.  If you change it after depreciation has been run, Oracle Assets treats this as a financial adjustment and the depreciation reserve is recalculated accordingly.
 
5. What is the 'Track As Asset' flag for on the invoice line?

A: If you enter an Asset account on the invoice line, then the track as asset flag will automatically be checked.  However only Asset accounts that are setup as asset clearing accounts are accepted by the Mass Additions Create Program.
If you want to send expensed lines over to Assets i.e. lines that will become expensed assets and not depreciate then you can manually check the Track as Asset box and these will be picked up by the Mass Additions Create program as Expensed lines.

 
6. Can I create Mass Addition lines from invoices in AP that were submitted for approval but placed on hold?

A: Invoice lines with certain types of holds can still be sent to Oracle Assets.  For details on the different types of holds please review Appendix E in the Oracle Payables User Guide.
   
7. How To Run Mass Additions Again In AP For Data Already Flagged For FA?

A: You need to run the Create Mass Additions Process again but the standard process for running Create Mass Additions is that once it is run, it can not be run again. The Create Mass Additions process flags the invoice distributions as already tested for FA, and will not pick them up the next time it is run. The question is how can you update the data to allow the process to run again. Please contact Oracle Support Services for assistance updating tables using SQL
 
8. Mass Additions Create created duplicate lines. How did this happen?

A: The problem could be the fact that several Mass Additions Create Programs were submitted in parallel and the Concurrent Program Definition for the executable APMACR is not incompatible with itself.
Login to System Administration responsibility and set the program to be incompatible with itself under concurrent>program>define. Auto Install does not set the incompatibility of this program.

9. How is the PO information transferred to FA?

A: If you created an invoice based on a PO then FA will take this information from AP.
However, if your PO and your invoice are not associated in AP and you just need to add the PO number or other data then you will need to enter this information in the descriptive flexfields. You can only use ATTRIBUTE column from 1 to 15 in FA_MASS_ADDITIONS.
 


Receivables Setups in R12

By // 64 comments:
Receivables overview:


Accounts receivable is an asset account in the general ledger that documents money owed to a business by customers who have purchases goods or services on credit.
Accounts receivable can be contrasted with accounts payable, a liability account in the GL that documents money the business owes for the purchase of goods or services.
Accounts receivable, accounts payable and payroll are usually listed as the top three mission-critical business processes in a disaster recovery plan .


Receivables Workbenches:

Oracle Receivables provides four integrated workbenches that you can use to perform most of your day–to–day Accounts Receivable operations. You can use the Receipts Workbench to perform most of
your receipt–related tasks and the Transactions Workbench to process your invoices, debit memos, credit memos, on–account credits, chargebacks, and adjustments. The Collections Workbench lets you review customer accounts and perform collection activities such as recording customer calls and printing dunning letters. The Bills Receivable Workbench lets you create, update, remit, and manage your bills receivable.

Each workbench lets you find critical information in a flexible way, see the results in your defined format, and selectively take appropriate action. For example, in the Transactions Workbench, you can query transactions based on the bill–to or ship–to customer, currency, transaction number, or General Ledger date. You can then review financial, application, and installment information, perform adjustments, create a credit memo, or complete the transaction. All of the windows you need are accessible from just one window, so you can
query a transaction once, then perform several operations without having to find it again.


Receivables Setups in R12:

Overview of Setting Up:

During setup, you define business fundamentals such as the activities you process and their accounting distributions, your accounting structure, and various control features. Setup is also the time to define
comprehensive defaults that Receivables uses to make data entry more efficient and accurate. In addition, setup lets you customize Receivables to employ the policies and procedures that you use in your business.
You can set up Receivables a number of different ways. The following graphic shows the most complete setup scenario. If you use the Oracle Applications Multiple Organization Support feature to use multiple sets of books for one Receivables installation, please refer to the Multiple Organizations in Oracle Applications manual before proceeding. If you plan to use Oracle Cash Management with Oracle Receivables, additional setup steps are required.

Note: If you plan to use Multiple Reporting Currencies (MRC) with Receivables, additional setup steps are required. For more information, refer to the Multiple Reporting Currencies in Oracle Applications manual.

Related Product Setup Steps:

The following steps may need to be performed to implement Oracle Receivables. These steps are discussed in detail in the Setting Up sections of other Oracle product user guides.

Set Up Underlying Oracle Applications Technology 

The Implementation Wizard guides you through the entire Oracle Applications setup, including system administration. However, if you do not use the Wizard, you need to complete several other setup steps, including:

• performing system–wide setup tasks such as configuring concurrent managers and printers
• managing data security, which includes setting up responsibilities to allow access to a specific set of business data and complete a specific set of transactions, and assigning individual users to one or more of these responsibilities.
• setting up Oracle Workflow

General Ledger Setup Steps:

The following table lists steps and a reference to their location within the Applications Implementation Wizard (AIW).

  • 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.



and save your work.

Assign Flexfield Qualifiers to Company and Accounting segments.

Select Company segment and then Click on Flexfield Qualifiers.

Select Balancing segment qualifiers and save.

 Select Accounting segment and then click on flexfield qualifiers.

Select Natural Account Segment and save.



Define Value sets:

Click on Value set.



Enter the value set Name and Size.


Save your work.

Like wise define value set for all reaming segments.

Assign Value sets to respective segments.


Save your Work.

Select Allow Dynamic inserts and Freeze Flexfield Defination and then click on Compile.



Wait untill the following program are successfully completed.



Define Values:


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 My Blog 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:


See my blog how to define Operating unit in R12.


Define Inventory Organization:


Navigation: Inventory --> Setup --> Organizations --> Organizations.

Click on New.


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 Revision and Lot Serial And LPN enter the required information.


Under the other accounts tab enter the required information.

Save your work.

Define Items:
Navigation: Inventory --> Items --> Master items.
Enter the name and description.

Go to Tolls and click on copy from.


Enter Finished good and then click on Apply and done button.



Receivable Setups:

  • 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 System Options: 
Define your accounting, discount, tax, and invoice system options to control how Receivables works. System options determine your accounting method, set of books, accounting flexfields, whether you use header or line–level rounding, and control the default operation of the AutoInvoice and Automatic Receipt programs.
System options also control how Receivables calculates tax on your transactions. You must specify a tax method, choose a Location Flexfield Structure, indicate whether to compound tax, select the address validation to use, and define tax defaults and rounding options. As you can set up your system to calculate Sales Tax, Value Added Tax, or Canadian Tax, we recommend that you carefully review the appropriate implementing tax essay before defining your system options.
Navigation: Receivables --> Setups --> System --> System Options.

Enter the required information in respective fields.






Define Transaction Flexfield Structure:

Transaction flexfields are descriptive flexfields that AutoInvoice uses to identify transactions and transaction lines. Receivables lets you determine how you want to build your transaction flexfield structure and what information you want to capture.

There are four types of transaction flexfields:

• Line Transaction Flexfield
• Reference Transaction Flexfield
• Link–To Transaction Flexfield
• Invoice Transaction Flexfield
You must define the Line Transaction Flexfield if you use AutoInvoice. You can use the Line Transaction Flexfield to reference and link to other lines because the Line Transaction Flexfield is unique for each
transaction line. AutoInvoice always uses the Line Transaction Flexfield structure for both the Link–to and Reference information when importing invoices. You must explicitly define the Link–to, Reference,
and Invoice Transaction Flexfield structures only if this information is to be displayed on a custom window.
Receivables gives you the option of displaying Invoice Transaction Flexfield information in the reference column of invoice lists of values.
Use the System Profile Option AR: Transaction Flexfield QuickPick Attribute to select the Invoice Transaction Flexfield segment that you want to display. For example, if you want to be able to reference the
order number for imported invoices when using an invoice list of values, you must assign the transaction flexfield segment that holds the order number to the AR: Transaction Flexfield QuickPick Attribute
profile option. The order number will now display in the reference column of invoice lists of values.
Line Transaction Flexfield:
Use columns INTERFACE_LINE_ATTRIBUTE1–15 and INTERFACE_LINE_CONTEXT to define the Line Transaction Flexfield. Line Transaction Flexfields are unique for each record in the interface table and therefore can be used as record identifiers.
Reference Transaction Flexfield:
Reference Transaction Flexfields have the same structure as the Line Transaction Flexfields.
Transactions 4 – 235 Reference Transaction Flexfields are used to apply a credit memo to an invoice or associate an invoice to a specific commitment. 
For example, to refer a credit memo to a specific invoice, use the REFERENCE_LINE_ATTRIBUTE1–15 and REFERENCE_LINE_CONTEXT columns of the credit memo to enter the Line Transaction Flexfield of the invoice. To refer an invoice to a specific commitment, use the REFERENCE_LINE_ATTRIBUTE1–15 and REFERENCE_LINE_CONTEXT columns of the invoice to enter the Line Transaction Flexfield of the commitment.
Link–To Transaction Flexfield:
Link–To Transaction Flexfields also have the same structure as the Line Transaction Flexfield. Use Link–To Transaction Flexfields to link transaction lines together in the interface table. For example, you might want to import tax and freight charges that are associated with specific transaction lines. If you want to associate a specific tax line with a specific transaction line, use the LINK_TO_LINE_ATTRIBUTE1–15 and LINK_TO_LINE_CONTEXT columns of the tax line to enter the Line Transaction Flexfield of the invoice.
Invoice Transaction Flexfields:
Create a new flexfield with a similar structure as the Line Transaction Flexfield, but only include header level segments. For example, if the Line Transaction Flexfield structure has four segments and the last two segments contain line level information, define your Invoice Transaction Flexfield using the first two segments only. Segments included in the Invoice Transaction Flexfield should be included in the AutoInvoice grouping rules.


Define Sales Tax Location Flexfield:
Receivables uses the customer shipping address to determine the sales tax rate on transactions for all customers in the country that you define in the Systems Option window as your home country. Proceed to the next step if you are not charging your customers tax based on their shipping address.
Following are the seeded Sales Tax Location Flexfield structures:
• Country
• State and City
• Province and City
• City
• Province
• State, County and City
Use the Key Flexfield Segments window to select the seeded Sales Tax Location Flexfield structure, or to set up a new structure, that you want Receivables to use to determine your sales tax rates and to validate
your customer addresses.
You can confirm that the required segments are enabled by navigating to the Segments Summary window. Navigate back to the Key Flexfield Segments window to freeze your flexfield structure by checking the
Freeze Flexfield Definition check box and then compiling the flexfield.
Note: When you define tax system options in the System Options window, use the list of values in the Location Flexfield Structure field to select the same Sales Tax Location Flexfield structure that you selected in the Key Flexfield Segments window.

Navigation: Receivables --> Setup --> Financials --> Flexfield --> Key --> Segments.

Query with Sales Tax Location Flexfield
 Enter the required information in respective filelds.


Save your work.
Like wise we can define other sales tax location flexfields,
Define AutoCash Rule Sets:


If you are using AutoCash, define your AutoCash rule sets before defining system parameters or customer profiles classes. AutoCash rules determine the sequence of application methods Receivables uses when applying receipts imported using AutoLockbox to open debit items.

Navigation: Receivables --> Setup --> Receipts --> Autocash rule sets.

Define Receivables Lookups:


Receivables provides several default lookups which are used throughout the application to provide validated default values and list of values choices. You can add or update these to customize your list of values and speed data entry. For example, you can define additional reasons for creating credit memos or enter the names of each freight carrier used by your business.

Navigation: Receivables --> Setup --> System --> Quickcodes --> Receivables.

Define lookups as you like.


Define Invoice Line Ordering Rules:

If you are using AutoInvoice, define invoice line ordering rules to specify how you want to order and number transaction lines after AutoInvoice groups them into invoices, debit memos, and credit memos. Receivables provides many attributes that you can use to define your line ordering rules.


Navigation: Receivables --> Setup --> Transactions --> Autoinvoice --> Line Ordering rule.



Define Grouping Rules:

If you are using AutoInvoice, define grouping rules to indicate how you want to group transaction lines imported by AutoInvoice. For example, to include specific transaction lines on a single transaction, certain attributes must be identical. Receivables provides many attributes that you can use to define your grouping rules.

Navigation: Receivables --> Setup --> Transactions --> Autoinvoice --> Grouping Rule.


Define Application Rule Sets:

Define Application Rule Sets to control how Receivables reduces the balance due for your open debit items when you apply payments using either the Applications window or Post QuickCash. You can define your own application rule sets, assign them to transaction types, and specify a default rule set in the System Options window.

Navigation: Receivables --> Setup --> Receipts --> Application Rule sets.




Define Payment Terms:

Define payment terms to determine the payment schedule and discount information for customer invoices, debit memos, and deposits. You can also define proxima payment terms to pay regular expenses such as telephone bills and credit card bills that occur on the same day each month and create split payment terms for invoice installments that have different due dates.

Navigation: Receivables --> Setup --> Transactions --> Payment terms.


Define AutoAccounting:

Define AutoAccounting to specify the general ledger accounts for transactions that you enter manually or import using AutoInvoice. AutoAccounting uses this information to create the default revenue, receivable, freight, tax, unearned revenue, unbilled receivable, finance charges, bills receivable accounts, and AutoInvoice clearing (suspense) accounts.

Navigation: Receivable --> Setup --> Transactions --> Auto Accounting.


Like wise we should also define reaming auto accounting types.

Open or Close Accounting Periods:

Navigation: Receivables --> Control --> Accounting --> Open/Close Periods.



Define Transaction Types:

Define the transaction types that you assign to invoices, debit memos, commitments, chargebacks, credit memos, on–account credits, and bills receivable. Receivables uses transaction types to default payment term,
account, tax, freight, creation sign, posting, and receivables information. Receivables provides two predefined transaction types: Invoice and Credit Memo.

Navigation: Receivables --> Setup --> Transaction --> Transaction Types.




Define Transaction Sources:

Define the transaction sources that you assign to invoices, debit memos, commitments, credit memos, on–account credits, and bills receivable. Receivables uses transaction sources to control your transaction and transaction batch numbering, provide default transaction types for transactions in batch, and to select validation options for imported transactions. Receivables provides the following predefined transaction sources: MANUAL–OTHER, DM Reversal, and Chargeback.
Navigation: Receivables --> Setup --> Transaction --> Sources.
 Define Collectors:

Define collectors to assign to your customers through credit profile class assignments. Collectors can use the Collections windows and Receivables collection reports to keep apprised of a customer’s past due items. Receivables provides a predefined collector called DEFAULT.

Navigation: Receivables --> Setup --> Collections --> Collectors.



 Define Approval Limits:

Define approval limits to determine whether a Receivables user can approve adjustments or credit memo requests. You define approval limits by document type, dollar amount, reason code, and currency.
Approval limits affect the Adjustments, Submit AutoAdjustments, and Approve Adjustments windows as well as the Credit Memo Request Workflow.

Navigation: Receivables --> Setup --> Transactions --> Approval Limits.


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.