Oracle 11i Application Developer – Technical FAQ – Part 2


Hello Friends, here is the second set of Questions on Application Developers , more of general questions, i am not digging in particular areas , only trying to put question which i normally ask with candidates. If you want help in any specific areas , plz advise, i will try to do that.

Q11 ) What is SET-OF-BOOKS?
Collection of Chat of Accounts and Currency and Calendars is called SOB

Q12 ) What is the interface?
Interface Table is a table which is used as medium for transfer of data between two systems.

Q13 Tell me what is the procedure to develop an interface?
a. First we will get the Requirement document.
b. We will create control file based on that plot file.
c. Then the control files which loads the data into staging tables.
d. Through pl/sql programs we will mapping and validate the data and then dump into the interface tables.
e. Through the standard programs we will push the data from interface tables to Base tables.

Q14) What is multi org?
“Legal entity has more than one operating unit is called as multi org”
a) Business group — Human resources information is secured by Business group
b) Legal entity. — inter-company and fiscal/tax reporting.
c) Operating unit — secures AR, OE, AP, PA and PO Information.
d) Organizations — is a specialize unit of work at particular locations

Q15) What are the User PARAMETERS in the Reports?
P_CONC_REQUEST_ID
P_FLEX_VALUE

Q16) FND USER EXITS:-
FND SRWINIT sets your profile option values, multiple organizations and allows Oracle Application Object Library user exits to detect that they have been called by an Oracle Reports program.
FND SRWEXIT ensures that all the memory allocated for AOL user exits have been freed up properly.
FND FLEXIDVAL are used to display flex field information like prompt, value etc
FND FLEXSQL these user exits allow you to use flex fields in your reports
FND FORMAT_CURRENCY is used to print currency in various formats by using formula column

Q17) what are the two parameters that are mandatory for pl/sql type concurrent program?
Procedure/function (ERRBUF OUT
RETCODE OUT
………………….)
ERRBUF :- Used to write the error message to log or request file.
RETCODE :- Populate log request file with program submission details info.

Q18.) What is Value Set?
–The value set is a collection (or) container of values.
–When ever the value set associated with any report parameters. It provides list of values to the end user to accept one of the values as report parameter value.
n If the list of values needed to be dynamic and ever changing and define a table based values set.

Q19) What r the validation types in Value Set?
1) None ——– validation is minimal.
2) Independent ——input must exist on previously defined list of values
3) Dependent ——input is checked against a subset of values based on a
prior value.
3) Table —– input is checked against values in an application table
4) Special ——values set uses a flex field itself.
5) Pair —— two flex fields together specify a range of valid values.
6) Translatable independent —– input must exist on previously defined list
of values; translated values can be used.
7) Translatable dependent ——- input is checked against a subset of values
based on a prior values; translated value can be used.

Q20) Who information’s?
1) Created by
2) Creation date
3) Last _updated by
4) last_update_date

Thanks  — Shivmohan Purohit

Oracle Applications – Basics – Part 1


Hello Friends, here i am posting some of basic oracle applications questions , will try to collect more and put in future posts, here i am putting quite easy and basic questions. If you like to know Questions of any specific area or modules, plz communicate so i will post those as well.

What are Oracle Apps API?

Where APIs are physically store? n What is the latest version of API?

They are Application Program Interfaces, which are standard stored procedure, package or functions created for performing specific activities in the Oracle Apps E-Business Suite.

Ex: The Order Import API when called would create orders corresponding to the record in the Order Interface tables.

How to attach reports in Oracle Applications?

The steps are as follows:

1.          Design your report.

2.          Generate the executable file of the report.

3.          Move the executable as well as source file to the appropriate product’s folder.

4.          Register the report as concurrent executable.

5.          Define the concurrent program for the executable registered.

6.          Add the concurrent program to the request group of the responsibility.

How to attach Forms in Oracle Applications

1. Develop the form in Developer 2000.

2. Save the FORM and move it to UNIX. [Form to be moved to $CUSTOM_TOP/forms/US]

3. Define the FORM in Application Developer

4. Define FORM as FUNCTION.

5. Identify MENU, where the FORM to be attached. [SysadminResponsibilityDefine]

6.Copy the above MENU and go to Application Developer and query on MENU tab

What is the difference between Customization and Personalization?

Customization is done by making the changes in the cutom.pll whereas the Form Personalization is done through the Front End in Oracle Apps.

Difference between Key and Descriptive Flexfield?

key flex fields are used to identify particular entity like(accounts,objects) supoose take debit cards each debit card contain unique number to identify them. eg; 100-023-323 key flex fields are used to store this number along with description.

Unique Identifier

Key Flexfield are stored in segment

For key flexfield there are flexfield Qualifier and segment Qualifier

DFF’s are used to capture additional informtion required for our organization without any programming.

To capture extra information
Stored in attributes
Context-sensitive flexfield is a feature of DFF. (descriptive flexfield)

What is the difference between data conversion and data migration?

Data Migration is upgrading from one version to another version fro e.g. from 11.5.9 to 11.5.10.. Data Conversion is receiving data from a legacy system or receiving data from another module ( e.g. PA), validating it and converting it to ur our the target module using the standard import program.

What is the difference between Organization_id and Org_id ?

OrgId: Org Id is an unique ID for the Operating Unit.Organisation Id: The Organisation Id is an ID for the Inventory Organisation which is under an Operating Unit.

What are _ALL tables in Oracle Apps?

_all tables will store information about multiple oraganizations. these table contain ORG_ID column that  picks particular organizations from multiple organizations. _all tables will be created when we install multiorg.

What is one full life cycle implementation?

Full Life Cycle means implementing a project from the begining to the production and maintenance stage.

(1) System Planning:

(Scope & Budget of the Project)

(2) Business Analysis:

(Business Requirements, Mapping & GAP Analysis)

(3) System Analysis & Design

(Design Conceptual & Functional Data Models)

(4) System Development

(Programming & System/Integration/Validation Testing)

(5) System Implementation

(Data Conversions, Interfaces, Extensions,User Manuals & User Training)

(6) System Maintenance & Support

Thanks – Shivmohan Purohit

Oracle Project Intercompany Invoices to Payables


Friends, here is Oracle Project billing insight on its integration with AR. How to Interface Oracle Project Intercompany Invoices to Payables

 

To explain how intercompany invoices are interfaced to Payables

 

When the provider operating unit runs the Tieback Invoices from Receivables process, the intercompany invoices are automatically copied into the interface table of the receiver operating unit’s Payables. Intercompany invoices interfaced to Payables are identified with the following attributes:

 

Source. All intercompany invoices have a source of Projects Intercompany Invoices.

• Supplier. The supplier is identified by the provider operating unit’s internal billing implementation options.

• Supplier Site. The supplier site is based on how the provider operating unit defines the receiver controls for the receiver operating unit.

• Invoice Amount. The Payables invoice amount is the amount of the related Receivables invoice, including taxes. The interface process populates the project–related attributes for intercompany Payables invoice distributions, as indicated below:

• Project Number. The number of the cross charged project indicated in the invoice line.

Task Number. The number of the task specified in the Intercompany Tax Receiving Task field on the cross charged project.

• Expenditure Item Date. The invoice date of the intercompany Receivables invoice.

• Expenditure Type. The expenditure type specified by the receiver operating unit in the Receiver Controls tab.

Expenditure Organization. The expenditure organization specified by the receiver operating unit in the Receiver Controls tab.

 

In addition, the interface process matches the tax code from each invoice line of the Receivables invoice to the appropriate Oracle Payables tax code. This process indicates that the Payables invoice distributions do not include tax amounts, so that the Payables Open Interface process creates the invoice distributions for the entire invoice by grouping the tax lines based on the following attributes:

 

Tax code

Project information (project, task, expenditure item date, expenditure type, expenditure organization)

thanks – shivmohan purohit

AR Interview Questions – Technical and Functional


 

 

A part of AR ( Account Receivables ) Interview Questions – Technical & Functional. This is next part. do share your feedback and thoughts

   

Conversion is a process by which we transfer legacy data from temporary tables to base tables. Interfaces also does the same but is a daily process and most of the interfaces are automated by scheduling. Example:AutoInvoice. Conversition is on time process this is before instlation, and interface every time process we can run any time.Conversion is a process by which we transfer legacy data from temporary tables to base tables. Interfaces also does the same but is a daily process and most of the interfaces are automated by scheduling. Example:AutoInvoice. Conversition is on time process this is before instlation, and interface every time process we can run any time.

 

 

 

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

 

 

 

 

 

 

 

 

     Thanks – Shivmohan Purohit

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2. Making the receipts of the customer payments.

 

 

 

 

Explain the process of recievables in oracle financials?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 
 

 

 
 

 

 

 
 

 

 

 

 
 

 

 

 

 

AutoInvoice Program Overview in Oracle Applications – Receivables


AutoInvoice Program Overview in Oracle Applications – Receivables

 

 
 
 

 

 

AutoInvoice is a program that can be used to import and validate transaction data from other financial systems from which one can create invoices, debit memos, credit memos, and on-account credits. It rejects transactions with invalid information to insure the integrity of the data. This fits well with in Oracle ERP or to integrate with any third party application.

Top 10 reasons for using Auto Invoice

1. Powerful Interface Tool
2. Supports Oracle & Non-Oracle Systems
3. Import Large Amount of Data
4. Calculate or Import Tax
5. Group Lines & Invoices

6. Online Error Correction

7 .Lines Validation

8. Derive GL Date

9 .Import Flex fields

10.Import or Derive Accounting Info

What is inside AutoInvoice
AutoInvoice is a program set consists of 3 main programs. Each program will have unique nature of work to do and they are called internally except Purge program whose execution is derived on the setup otherwise ready to execute stand alone.
Master (RAXMTR)
Import (RAXTRX)
Purge (RAXDEL)

1. Auto Invoice Master program RAXMTR
Selects and marks records in the interface tables to be processed based on the parameters the user entered and then calls the AutoInvoice Import program. Auto Invoice Master program has no report output.
•Gathers statistics, it means it gathers the stats on interface tables and set the stats on certain indices on interface tables
•Marks interface records for processing by marking request_id
•Submits multiple workers for Parallel Processing by creating instances for request.

2. Auto Invoice Import Program Validates the selected record and creates transaction if it passes validation. Any record that fails validation is left in the interface table with an error code. Depending on the setup, related records may be rejected as well. This program has an output file called Auto Invoice Execution report, which you can view by clicking the View Report button in the Requests window.Working of Auto invoice , Validates data, Inserts records, Deletes interface data Only when system option purge set to ‘Y’

3. Auto Invoice Purge Program Deletes records from the interface tables. If you set the Purge Interface Table system option to No in Define System Option window, Auto Invoice does not delete processed records from the interface tables after each run,and we must submit Auto Invoice Purge Program periodically to clean up the interface tables. This program only deletes transaction lines that have been successfully imported.
Deletes all rows where interface_status =‘P’
• Ra_interface_lines
• Ra_interface_distributions
• Ra_interface_salescredits

Oracle Receivable’s Auto Invoice program will be used to import and validate Invoices. A custom feeder program is required to transfer data from the Advantage extract files and populate the Auto Invoice interface tables (RA_INTERFACE_LINES_ALL and RA_INTERFACE_DISTRIBUTIONS_ALL).If there is need to run populate sales credit into RA_INTERFACE_SALESCREDITS_ALL table. When run, AutoInvoice produces the AutoInvoice Execution Report and the AutoInvoice Validation Report. Any entries which failed validation can be reviewed in Oracle Receivables’ AutoInvoice Interface Exceptions window. Depending on the error, changes may need to be made in Receivables, the feeder program or the imported records in the interface tables.

How Autoinvoice Execution works
Normally, Auto Invoice can be divided into three major phases, Pre-grouping: here the validates all of the line level data takes place, Grouping: groups lines based on the grouping rules and validates header level data, Transfer :validates information that exists in Receivables tables

What happen when AutoInvoice run?
Once the Auto invoice Program gets called, the following activity takes place is part of execution process. This can be analyzed by debug options.
Line, accounting, and sales credit information for each line populates 3 interface tables
Lines are ordered and grouped
Tax is calculated
GL date is determined
GL accounts are assigned using Auto Accounting
Tax, freight, commitments, and credit memos are linked to transaction lines
All transactions are batched
Validated lines are used to create the transaction

How Data is flowing?
Select, insert and update and delete take place on certain tables once it is logged out.

Selects
– RA_INTERFACE_LINES_ALL
– RA_INTERFACE_DISTRIBUTIONS_ALL
– RA_INTERFACE_SALESCREDITS_ALL
Updates/Insert
– RA_INTERFACE_ERRORS_ALL
– RA_CUSTOMER_TRX_ALL
– RA_CUSTOMER_TRX_LINES_ALL
– AR_PAYMENT_SCHEDULES_ALL
– AR_RECEIVABLE_APPLICATIONS_ALL

Inserts
– RA_INTERFACE_ERRORS_ALL

AutoInvoice Exception Handling
Records that fail validation are called ‘Exceptions’. Exceptions stay in Interface Tables which is RA_INTERFACE_ERRORS_ALL. Errors can be corrected in the Exception Handling window. Once corrections are made, Auto invoice must be resubmitted. Records that pass validation get transferred to Receivables tables

AutoInvoice Exception Handling Windows
-Interface Exception window displays exception messages associated with all invalid records
-Interface Lines window displays records that fail validation, provides an error message and can be used to correct the errors
-The Line Errors windows displays errors associated with a specific line, and can only be opened from Interface Lines window
-Interface Exceptions window displays Interface Id, Exception Type, Error Message and Invalid Value associated to the error
-Data cannot be edited in this window, but error can be viewed and corrected by clicking the Details button
-Error Message and Column name with invalid data are displayed in the Message column, and the invalid value that needs to be corrected is displayed in the Invalid Value column

Thanks – Shivmohan Purohit

 

 

 

 

Supplier Open Interface in 11i10 and family pack F


Oracle Account Payables:

The New Supplier Open Interface Feature is Now Available in Financials Family Pack F for 11i  

Payable has added new open interface tables and concurrent programs to support the automated import of supplier records from external sources. This feature offers the same validations as the Suppliers and Suppliers Sites window.  This feature is available as of 11.5.10 or 11i Financials Family Pack F and will not be back ported to any prior release. The Supplier Open Interface Request Set submits:

Supplier Open Interface Import
Supplier Site Open Interface Import
Supplier Site Contacts Open Interface Import

More details about the Supplier Open Interface can be found on page G-5 and G-6 of the latest Oracle Payables User’s Guide. If you like to furthur on this in any way either functinally or technically, plz let me know i will dig into it.

Below is just a Payables functionality in a diagram.

thanks – Shivmohan