Oracle apps Finance Technical Interview Questions

Oracle apps Finance Technical Interview Questions

Hi friends, we are going to discuss about the Oracle apps Finance Technical Interview Questions. We will share some of the most important Oracle apps Finance Technical Interview Questions which we should read and prepare for oracle apps interview questions. We would recommend to go through these Finance Technical Questions for the preparation of Interviews for oracle apps. Please find below the complete details about Finance Technical Interview Questions.

Oracle apps Finance Technical Interview Questions

Question 1:

What is MOAC in Oracle apps?

Multi-Org or multiple organization access (MOAC) is basically an ability to access multiple operating units from a single application responsibility. MOAC in r12 technical is the great feature in Oracle Apps.

In 11i, end users must change the responsibilities to do transactions in different operating units. This is a very time consuming and inefficient way of recording transactions when you have 100s of operating units specially Internet based organizations who have worldwide operations in almost all the countries.

To address this, a new feature in R12 has been introduced in which user can switch between operating units within a responsibility something like “Change Organization” feature in inventory. Prior to R12, user would have to switch responsibilities to enter transactions in respective operating units.

Question 2:

How to set multi org in r12 from backend?

Answer:

If you are using the Back-end procedure to insert some values in the Standard Base tables and you want to follow and to put the control on the basis of Multi Org setup (MOAC) then you need to use these below steps before using any API or Interface code.

begin

fnd_global.apps_initialize(p_user_id, p_resp_id, p_resp_appl_id);

end;

 

begin

fnd_global.apps_initialize(p_user_id, p_resp_id, p_resp_appl_id);

end;

 

begin

mo_global.init (<APPLICATION SHORT NAME>);

end;

For example

begin

mo_global. init (‘AR’);

end;

This is one of the most important package to be use in the backend to set the multi org concept. With the help of this Procedure, Bank end system, able to drive all the profile values assigned to this responsibility and user in Oracle application. So that we can put Data access control on the base of Multi org.

 

Question 3:-

What are the Payment Process Request Tables in Oracle apps ?

AP_SELECTED_INVOICES_ALL

/AP_SELECTED_INVOICES_ALL is a temporary table that stores

information about invoices selected for payment in a

payment batch. Your Oracle Payables application

inserts into this table after you initiate a payment batch.

There will be one row for each invoice that Payables selects for

payment in the current payment batch. When you build payments

in a payment batch, your Oracle Payables

application uses information in this table to create

rows in AP_SELECTED_INVOICE_CHECKS. */

SELECT * FROM AP_SELECTED_INVOICES_ALL

SELECT * FROM AP_SELECTED_INVOICE_CHECKS_ALL

AP_UNSELECTED_INVOICES_ALL

 

In this table, system stores information’s about that invoices which are due for payment but not rejected by the payment batch due to some issues. We can also get the rejection details for the invoice too.

SELECT * FROM AP_UNSELECTED_INVOICES_ALL

--This table contains Invoice details, Payment details, payer, payee information against PPR/ Payment Batch

 SELECT * FROM IBY_DOCS_PAYABLE_ALL;

SELECT * FROM IBY_PAYMENTS_ALL;

SELECT * FROM AP_INVOICE_PAYMENTS_ALL;

--Payment Documents to be used for Printed type Payments

SELECT * FROM CE_PAYMENT_DOCUMENTS;

SELECT * FROM AP_CHECK_FORMATS;

-- Payable Formats

SELECT * FROM IBY_FORMATS_B;

--Payable Profiles

SELECT * FROM IBY_SYS_PMT_PROFILES_B

SELECT * FROM IBY_EXTRACTS_TL;

-- Payment Methods

SELECT * FROM IBY_PAYMENT_METHODS_B;

-- XML documents associated with a transaction generated by FORMAT PAYMENT INSTRUCTION Program

SELECT * FROM IBY_TRXN_DOCUMENTS;

-- Stores PPR instructions

SELECT * FROM IBY_PAYMENT_INSTRUCTIONS_ALL

--Payables Payments Data

SELECT * FROM AP_CHECKS_ALL;

 

Oracle apps Finance Technical Interview Questions

Question 6:-

What are the Payables Payment Terms Table in Oracle Apps ?

Answer:

AP_TERMS

AP_TERM_LINES

 

Question 7:-

What are the Receivables Payment Terms Table in Oracle Apps ?

Answer:

RA_TERMS

RA_TERM_LINES

Question 8:-

What is the Payment Method table in oracle apps r12 ?

Answer:

IBY_EXT_PARTY_PMT_MTHDS

Question 9:-

What are the AP Invoice Interface Tables in Oracle Apps r12 ?

Answer: 

AP_INVOICE_INTERFACE :-

 

We will create Single record for Each Invoice in this AP invoice Interface table. Like for above Example , where we have two lines for Single Invoice but we will insert Single record in this Interface table for this above case.

 

AP_INVOICE_LINES_INTERFACE:-

In this table , We creates multiple Lines for the Single Invoice as like above case , We will create two records for the Invoice 'A001'.

Question 10:

Which table stores the AP Invoice Interface Rejection Details ?

Answer:

AP_INTERFACE_REJECTIONS

Question 11:

Which are the Supplier Interface Tables in Oracle apps ?

Answer:

Interface Tables for Supplier Conversion in oracle apps r12

1.ap_suppliers_int

2.ap_supplier_sites_int

Question 12:

2 Important Supplier Interface tables having error details

1.ap_suppliers_int

2.ap_supplier_sites_int

There are two Important Columns in the ap_suppliers_int interface table which helps to find out the supplier interface error records in oracle apps. 

1.REJECT_CODE

2.STATUS

Here below is the sql query which helps to extract the Supplier header interface error or rejected records.

select reject_code,status from apps.ap_suppliers_int

where status='REJECTED'

Oracle apps Finance Technical Interview Questions

Question 13:

What is the Oracle Standard Import Program name to import Suppliers Interface Records in to the Base Tables?

 

Answer:

 Standard Import Program's to Import Supplier Interface records in Supplier Base Tables.

Supplier Open Interface Import

Supplier Sites Open Interface Import

Supplier Contacts Open Interface Import

Question 14:

What are the Projects Table in Oracle apps ?

Answer:

1.PA_PROJECTS_ALL

2.PA_TASKS

3.PA_PROJECT_TYPES

4.PA_PROJECT_PLAYERS

5.PA_AGREEMENTS_ALL

6.PA_CUSTOMERS_ALL

7.PA_BUDGET_VESIONS

8.PA_BUDGET_LINES

9.PA_DRAFT_REVENUES_ALL

10.PA_DRAFT_REVENUE_ITEMS

Question 15

What is TCA in Oracle Apps?

Answer:

We all know that TCA. TCA (Trading Community Architecture) comes for picture in Oracle apps r12. TCA more related to Party and more about Customer Oriented. In TCA, Oracle treats everything in Oracle application as party , which could be become its potential customer in future. To more clarifying this Statement, I will share the Working Examples as below.

 

For Example, I have create the Supplier A in Oracle apps but as per TCA architecture, Oracle will automatically create this Supplier A as an Party because according to TCA, Supplier can also be my Potential Customer in Future. So, in Future If I need to sell some goods to this Supplier A, then I can directly create the Customer From this Party A So One Party will become my Supplier and Customer Both but with Different Relation Ship.

Oracle apps Finance Technical Interview Questions

Question 16:

Where we can find the Application short name and basepath names in Oracle Apps?

Answer:

We can find the Short Name and base path from two ways.

From Back End: -

Select basepath, application_short_name from fnd_application from the backend.

From Front End: -

we can get it Navigation Application Developer.—–> Application—->Register.

Question 17:

What are the Bank Tables in Oracle Apps R12 ?

Answer:

2 Types of Banks in Oracle apps

1. Internal Bank

2.External Bank

 

Internal Bank:-

 

Internal Bank are the Oracle our Internal Banks or Business Unit /Organization Internals Banks which they uses to Pay Customer Invoice's and to do the receiving of the Customer Payments.

 

3 Important Tables of Internal Banks

 

1.CE_BANK_ACCOUNTS

2.CE_BANK_ACCT_USES_ALL

3.CE_BANKS_V

 

External Banks :-

 

External Banks are those Banks , Which is related to Our or Organization/ Business unit Customers and Suppliers. Both Customer and Suppliers are external Entities so Oracle has stored these Banking Information's in different tables as compared to the Internal Banks.

 

3 Important External Bank Tables

`1.iby_external_payers_all

 2.iby_pmt_instr_uses_all

 3. iby_ext_bank_accounts

Question 23

What is the Difference Between Interfaces and Conversions in Oracle apps ?

Answer:

Interface Process is the Subset of the Conversion Process. It Means , When we migrating the Data from External source to the Oracle Apps, but the data is not in the Form or in the shape like Oracle apps required Data format , so we need to massage this data or to put extra efforts to prepare this data in the form of Oracle Required format data that process is called conversion. Once the data prepared in the format of Oracle apps required format then the Interface process starts to import or migrate the data in Oracle apps.

Conversion most of the Time is the one-time process when we are doing implementation or we are switching the ERP application from other application to Oracle application. But Interface is the continuous on-going task which helps to sync the external applications with the Oracle application.

Oracle apps Finance Technical Interview Questions

Question 24

What are the XLA tables in Oracle apps and their links with subledgers in oracle apps ?

Answer:

xla tables in r12

GL_JE_BATCHES (je_batch_id)                                   => GL_JE_HEADERS (je_batch_id)

GL_JE_HEADERS (je_header_id)                                  => GL_JE_LINES (je_header_id)

GL_JE_LINES (je_header_id,  je_line_num)                      => GL_IMPORT_REFERENCES (je_header_id, je_line_num)

GL_IMPORT_REFERENCES (gl_sl_link_table, gl_sl_link_id)        => XLA_AE_LINES (gl_sl_link_table, gl_sl_link_id)

XLA_AE_LINES (application_id, ae_header_id)                   => XLA_AE_HEADERS (application_id, ae_header_id) 

XLA_AE_HEADERS (application_id, event_id)                     => XLA_EVENTS (application_id, event_id)