Oracle Receivables – FAQ , Interview Questions ( Functional & Technical)
Hello Friends, As part of putting Oracle Application Interview Questions for various modules, here i am putting Receivables , most of them are quite functional and link with Oracle Receivables features, still it is good to learn and know for a technical developer to get overall understanding. do share your feedback n thoughts.
(when we raise the invoice with invoicing rule as advance)
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))
There are 8 value set types:
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
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
HZ_CONTACT_POINTS. few to name.
_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)
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).