Pages

OracleEBSpro is purely for knowledge sharing and learning purpose, with the main focus on Oracle E-Business Suite Product and other related Oracle Technologies.

I'm NOT responsible for any damages in whatever form caused by the usage of the content of this blog.

I share my Oracle knowledge through this blog. All my posts in this blog are based on my experience, reading oracle websites, books, forums and other blogs. I invite people to read and suggest ways to improve this blog.


Saturday, February 16, 2013

AR Interview Questions – Technical and Functional


AR Interview Questions – Technical and Functional
   
How many reporting currencies can be attached to Primary Set of Books?   

We can have a total of 8 SOB’s (including the Primary SOB). Therefore, we can have 7 Reporting SOB.

What are Different types of transactions in AR?
There are 7 type of transactions in AR- Invoice, Debitmemo, Creditmemo, Chargeback, Deposits, Guarenty, and Bills Recivable.
What is the use of lockboxes?
AutoLockbox (or Lockbox) is a service that commercial banks offer corporate customers to enable them to outsource their accounts receivable payment processing. An AutoLockbox operation can process millions of transactions a month. AutoLockbox eliminates manual data entry by automatically processing receipts that are sent directly to your bank. You specify how you want this information transmitted and Receivables ensures that the data is valid before creating QuickCash receipt batches.
Steps for lock box are :
1. The first step involves reading and formatting data from your bank file into AutoLockbox tables.
2. The second step involves submitting the validation program which checks data in the AutoLockbox tables for compatibility with Receivables.
3. Once data is validated, it is transferred into QuickCash tables. At this point, you can optionally query your receipts in the QuickCash window and change how they will be applied before submitting the final step,
4. Post QuickCash. Submitting Post QuickCash updates your customer’s balances.
What are the interface tables used for ar invoices, customers, receipts for conversion process?
Customer interface tables:
Ra_customer_interface


ra_contant_phones_interface
ra_customer_banks_interface
ra_customer_profiles_interface
ra_cust_pay_method_interface
Invoice interface tables:
ra_interface_lines_all
ra_interface_sales_credits
ra_interface_distributions
Following are the Validation for Autoinvoice:
1-       AR Transaction Type Validation : Check if the Transaction type provided in data file is defined in AR transaction types(RA_CUST_TRX_TYPES_ALL)
2-        
2- Transaction Batch Source Validation: Check if the source provided in data file is defined in AR transaction Batch source (RA_BATCH_SOURCES_ALL).
3- Invoice Currency Validation: Check if the currency provided in data file is defined in AR Currency (FND_CURRENCIES).
4- Customer Validation: Check if the Bill to Customer Number, Ship to Customer Number, Bill to Custom Location, Ship to Customer Location provided in the data file is defined in AR Customer(ra_customers).
5- Primary Sales Representative Validation: Sales representative number to be hardcode to “-3” for “No Sales Credit.”
6- Term Name : Check if the Term name provided in the data file is defined in Payment terms (RA_TERMS)
7- Validate Sales Credit Type : Sales Credit to hardcode to “Quota Sales Credit”
8- Inventory Item Validation: Check if the Item provided in data file is defined in Inventory Items (MTL_SYSTEM_ITEMS).
9- Unit of Measurement validation: Check if the UOM provided is defined in MTL_UNITS_OF_MEASURE Table
10- Invoice Tax Code Validation : Check if the Tax Code provided in data file is defined in AR_VAT_TAX_ALL_B Table.
11- Invoice GL Date Validation : Check if the GL Data of provided invoices is in open period.Used ARP_UTIL.IS_GL_DATE_VALID API to validate.
Following are the base tableshz_parties
hz_cust_accounts
hz_cust_acct_sites_all
hz_cust_sit_use_all
hz_party_sites
hz_locations
hz_party_site_uses
hz_customer_profiles
hz_organization_profiles
hz_person_profiles
What is Auto Invoicing? Explain?
Auto Invoicing is a process of Importing Invoice related information from External / Internal Sources.External will be your business Legacy Systems like Main Frame / AS400 or Non Oracle ERP systems like SAP / JDE or From Custom Oracle Applications. The data is placed into Interface tables and from there either from Application or from PL/SQL , you can call Auto Invoice Concurrent request to validate and transfer data into AR Transaction tables. The data from these tables can be seen when queries from Transaction Screens. Auto Invoicing is a process of creating an invoice automatically in AR when a sales order has been shipped and closed. This process is triggered by a concurrent request ‘AUTO INVOICE MASTER PROGRAM’. Auto invoicing is used to import the AR invoices direclty into the AR module.
  
What is AUTO Accounting what are the steps for setting up auto accounting?
Auto Accounting is a mechnism for generating defualt accounting flexfields for revenue , receivables, frieght and tax based on the other parameters associated with the invoice you are entering.. since auto accounting looks at the following tables to get the data so please set/define the following depending upon your requirement.

1.Salesrep.
2.Transaction Types.
3.Standard Lines.
4.Taxes.
5.Customer bill-to-site
Receivables uses the Auto Accounting rules to determine the GL Accounts that you Enter manually or import using Auto invoice. Receivables creates the Default accounts for the Receivable, revenue, Freight, Tax, Unerned revenue, Finance charges, Unbilled receivables, Bills receivables, and Auto invoice Clearing Accoutns.You need to define these accoutns before you start entering the transactions in AR. However, you can overide these accounts during the Transaction Entry in AR.Setup Autoaccounting:AR>Setup>Transactions>AutoAccountingSelect the Type of the accoutn you wish to define the auto accoutning.In the Segments Block:Choose the segment for which you wish to assign the Auto accounting.Choose the Table Name : Sales Rep, Trxn Type, Site, Std Lines.If you wish to use a Default Constant value, then enter the value in the Constant Field.
What are the standard concurent programs for auto invoice interface and customer interfaces?
Autoinvoice Import Program — for auto invoice program

 Customer Interface Master Conc Program –> for Customer Interface
AR Complete Cycle (hoping that GL is already implemented)Define Transaction SetupsDefine Receipt and Receipt Application SetupsDefine CustomerCreate an InvoiceCreate a ReceiptApply Receipt to InvoiceReview Customer balances (Collections). The BASIC process of Receivables involves the following:
1. Creation of Customer Invoices.

3. Remittance fo the same to the bank.


How do we segregate debit & credit transactions in Receivables and where we will do it?

Basically the debit and credit transaction are classified by the transaction class.
Whether we are defining customer in AR? If it is in AR then how are we placing the order and how the shipment will be done?
Customers and the associated information is stored in TCA structure, which is shared across All oracle application modules. If you add a customer in AR, it gets stored TCA underlying tables. When you want to create an Order in Order Management, the customer LOV displays data from Record Group that is created on TCA tables.
The basic Oracle ERP data model is the single Data model shared (integrated) by multiple application. The owner of the creation of customer is the AR schema and is shared by other application such as OM. These are usually called as shared entities (Supplier,Partners,Items etc)
How To Close Periods In AR?
After raising transactions and receiving the RECEIPT amount, transfer the all TRANSATIONS and RECEIPTS to the GENERAL LEDGER. And then only close the PERIOD in AR. 

Explain about Party and Customer in AR?
Party could be a person or an organization which has no business relation with your entreprise, if you establish a sales relation with a department in a party then that particular department is your customer.

What is MRC and what is its use?
The Multi Reporting Currency Feature allows you to report and maintain records at the transaction level in more than one functional currency. You can do by defining one or more set of books in addition to primary set of books. 
Accointing for invoice in advance


a) Receivable A/c …………………Dr.
To Unearned revenue a/c

(when we raise the invoice with invoicing rule as advance)

b) Unearned Revenue A/c ………….. Dr.
To Revenue A/c
(when we receive the payment, the number of journal entry (b) is depend upon the accounting rules which can be fixed or variable)
Accounting for invoice in arrear
a) Unbilled receivable a/c ………………..Dr.
To Revenue a/c
(when we receive the payment of unbilled invoice, the number of journal entry (a) is depend upon the accounting rules which can be fixed or variable))
b) Receivable a/c …………………….Dr.
To Unbilled receivable a/c
(when we raise the invoice, with invoicing rule arrear)
What is the use of Transaction Flexfield in Autoinvoice ?
Transaction Flexfield actually identifies the the uniqueness among the Multiple lines of a single Invoice 

What are value sets?
Value sets are the defined as list of possible values for a specific purpose. These are assigned to flexfields. These are the only possible values to be choosen from. This eliminates the data entry errors.
Value set is a set of possible values.
There are 8 value set types:

1.Dependent
2.Independent
3.Table
4. None
5.Pair
6.Translatable Dependent
7.Translatable Independent
8. Special
Describe the main tables involved in AR, and what is the data stored in them?
RA_BATCHES_ALL — Information about Transaction BATCHES RA_CUSTOMER_TRX_ALL — Header information about Transaction
RA_CUSTOMER_TRX_LINES_ALL — Lines information about Transaction
RA_CUST_TRX_LINE_GL_DIST_ALL – Distribution information about Transaction

RA_CUST_TRX_LINE_SALESREPS_ALL — Sales representative of Transaction Information
AR_PAYMENT_SCHDULES_ALL – Information about Payment Schedules
AR_APPLICATION_PAYABLES_ALL
RA_INTERFACE_ERRORS – Errors in AutoInvoice Interface Data
RA_INTERFACE_LINES_ALL – Use this table to enter Header and Lines information in AutoInvoice Interface program
RA_INTERFACE_DISTRIBUTIONS_ALL – Distribution Table in AutoInvoice Interface program
RA_INTERFACE_SALESCREDITS_ALL – Sales Credits information in AutoInvoice Interface


 What do you mean by HZ_ in customer tables?
HZ stands for Human Zone(HZ_). Anytihing which is related to the human like Customer profiles, their accounts, locations, relationships are stored in these tables only. From release 11i TCA came into picture in Accounts Recievable module, where oracle has grouped all the customer information at one place. Most important tables in TCA are-
HZ_PARTIES,
HZ_CUST_ACCOUNTS_ALL,

HZ_CUST_ACCT_SITES_ALL,
HZ_CUST_SITE_USES_ALL,
HZ_LOCATIONS,
HZ_PARTY_SITES,
HZ_PARTY_SITE_USES,
HZ_CONTACT_POINTS. few to name.
What is the difference between _all, _tl, _vl, _v tables in Oracle Apps ? Also name various other table suffix.
_ALL : Table holds all the information about different operating units. Multi-Org environment. You can also set the client_info to specific operating unit to see the data specific to that operating unit only.
_TL are tables corresponding to another table with the same name minus the _TL. These tables provide multiple language support. For each item in the table without _TL there can be many rows in the _TL table, but all with different values in the LANGUAGE column.
_B these are the BASE tables. They are very important and the data is stored in the table with all validations. It is supposed that these table will always contain the perfect format data. If anything happens to the BASE table data, then it is a data corruption issue.

_F these are date tracked tables, which occur in HR and Payroll. For these there are two date columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE which together with the PK identifies a row uniquely. The date intervals cannot overlap. Many think they are Secured data. Guess someone from Oracle confirms.
_V tables are the views created on base tables _VL are views for multi language tables which combines the row of the base table with the corresponding row of the _TL table where the LANGUAGE = USERENV(’LANG’).
_S are sequences, used for finding new values for the primary key of a table.
_A are Audit Shadow Tables
_AVN and _ACN are Audit Shadow Views (when data was changed, and with what values)
How many Flex fields are there in AR and what are they?

Required Key Flex fields:
1. Territory Flex field
2. Sales Tax Location flex field

Optional Key Flex fields:

1. Transaction flex field (requied only if Auto Invoicing is enabled)
2. System Items Flex field (If Inventory or OM is installed this should be defined there. other wise, it should be set up in AR).

No comments:

Post a Comment