Random Questions From Apps

1. What is overlay in payables
Ans: Over lay is used in payable open interface where we would like to pass and overwrite certain value which is set to appear by default when data is inserted into the production tables.
2. What is rollup group
Ans: rollup group we define and attached with the parent segment in the accounting flexfield for summary total for which summary template is defined. This identify at what level and how the summing up should be computed for the level.
3. What way payment batch is different from other module batches.
Ans: It identifies the invoices for the payment automatically based on the criteria we specify in payment batch for the payments.
4. What is balancing segment in AR.
Ans: The Account Generator ensures that Receivables substitutes the correct balancing segment values during various accounting activities against transactions and receipts.
Receivables uses the Account Generator to update the balancing segment values during various accounting activities against transactions and receipts. By matching the balancing segments for different accounting activities back to the original transaction or receipt, the Account Generator ensures that Receivables uses the correct balancing segment values during this substitution process. For example, if an invoice’s balancing segment that you assess finance charges for has a value of ’01’ and the balancing segment of your finance charges account is ’02’, when Receivables accrues finance charges for this invoice, the Account Generator automatically changes the balancing segment of the finance charges account to ’01’. The Account Generator in Receivables utilizes Oracle Workflow
5.What is deposit in AR? Have you used it?
Ans: It is a commitment type of transaction where in we take deposit from the customer and get into the agreement that we will make supply of certain goods and services for certain period of time.
7.What is flexfield qualifier in accounting flexfield.
Ans: Balancing Segment, Cost Center Segment, Natural Account Segment & Inter-company segment.
8.Which SRS is used for AR To GL Interface.
ANS: General ledger option is given in the menu option interfaces in AR.
9.What are required setup for AP.
Ans: Required setup in AP is as under
1. Install or upgrade payables
2. Select primary set of books
3. Use the system administrator responsibility to assign your set of books to a responsibility. (Profile Option)
4. Define financials options.
5. Define payables options.
6. Define payment terms.
7. Define banks, bank transmission details and bank accounts
8. Open payable accounting period
9. Set up Print Styles and Drivers for the supplier Mailing labels report
10.What are required setup for GL.
Ans: Required setup in GL is as under
1. Source (Required step with defaults)
2. Category (Required step with defaults)
3. System Control (Required step with defaults)
4. Profile Options (required)
5. Open Close Accounting Periods (required)
Before that set of books setup needs following:
1. Chart of Accounts (Accounting Flexfields) - (Required)
2. Define Period Types (Required step with defaults)
3. Define Calendar (Required)
4. Currency (Required step with defaults)
5. Set Of Book (Required)
6. Assign set of books to a Responsibility in Profile Option(Required)
7. Daily Conversion Rate Type (Required step with defaults)
11.How you will print user name of the person logged on to see the report.
ANS: SELECT FND_GLOBAL.USER_ID FROM DUAL; STORE IT IN A VARIABLE AND FIND IT IN THE FND_USER
select user_name from fnd_user where user_id = (select fnd_global.user_id from dual)
12.What is the table name for GL Interface. From here data goes to which tables.
ANS: GL_INTERFACE Table Updates GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES.
13.Can we insert journal name in the GL Interface table
Ans: There is no such column in GL interface table hence we cannot enter it.
14.Where Reference fields are found in GL production tables. What is its use.
Ans: Reference fields are found in GL_JE_LINES it is used to store reference of sub-ledger enables us to drill down from gl to subledger.
15.Where journal name will be stored in GL_INTERFACE TABLE, Name the column.
ANS: REFERENCE4 (Journal Entry name will go in this field)
16.How to set dependent and independent value set and how you will insert values for the segments having these value sets.
ANS: First define independent value set and then while defining dependent value set give reference of independent value set along with default value and description. At time of entering values, enter values for independent first and then while entering values for dependent it will first force you to select value of independent segment.
17.SRS Name for AP TO GL.
ANS: Payable Transfer to General Ledger.
18.Can you delete the records after the interface has uploaded the records in the GL interface table?
ANS: Yes we can delete and correct the records from the front end after importing data into GL_INTERFACE Table. Sub menu options as correct and delete are given under import menu option. We have to specify source name. Menu option is import under journal in GL.
19.Required parameter for PL/SQL Procedure registered in Oracle. What will happen if these are not included?
ANS: Retcode and Errbuf are two out parameters having varchar2 datatype that are required. Use errbuf to return any error messages, and retcode to return completion status. The parameter retcode returns 0 for success, 1 for success with warnings, and 2 for error. After your concurrent program runs, the concurrent manager writes the contents of both errbuf and retcode to the log file associated with your concurrent request. If we do not include these two parameters, it will give run time error.
20.How to judge the number of descriptive fields defined from the front end itself.
ANS: In front end we will find [] open close square bracket which indicate the presence of descriptive flexfield. In other words, dff appears on form as a single-character, unnamed field enclosed in brackets
21.What is context field is all about.
ANS: Context field is used to make descriptive flexfield segments context sensitive, so that segment that may or may not appear depending upon what other information is present in your form
22.What is use of custom.pll what triggers are fired to support the customization you do using custom.pll
Ans: WHEN-FORM-NAVIGATE
WHEN-NEW-FORM-INSTANCE
WHEN-NEW-BLOCK-INSTANCE
WHEN-NEW-RECORD-INSTANCE
WHEN-NEW-ITEM-INSTANCE
WHEN-VALIDATE-RECORD
SPECIALn (1 to 45)
ZOOM
EXPORT
KEY-fn (1 to 8)
23.What are various customer interface tables?
ANS: RA_CUSTOMERS_INTERFACE_ALL
RA_CUSTOMER_PROFILE_INT_ALL
RA_CUSTOMER_BANKS_INT_ALL
RA_CUST_PAY_METHOD_INT_ALL
RA_CONTACT_PHONES_INT_ALL
24.Where invoices gets stored in payables
ANS: AP_INVOICES_ALL
AP_PAYMENT_SCHEDULES_ALL
AP_TERMS_LINES
AP_BANK_ACCOUNTS_ALL
AP_BANK_BRANCHES
AP_INVOICE_PAYMENTS_ALL
25.What will happen if you will type select * from ap_invoices in the multi org setup.
Ans: No row selected because it is a view having where condition for ord_id to match with operating unit context that are extracted from client_info global variable at application run time. From sql prompt run Fnd_client_info.setup.org_context(org_id). It will set the operating unit context or run fnd_clinet_info.setup_client_info(resp_appl_id,resp_id,user_id, security_group_id)
26.Why it does not show records and show records for ap_invoices_all where as both the table has got org_id columns.
Ans: Because operating unit context is not set that is why ord_id can not retrieved to meet the where condition specified in the view. Set it up with followings,
Fnd_client_info.setup_client_info(resp_appl_id,appl_id,user_id) or
Fnd_client_info.set_org_context(org_id)
27.What mechanism or logic oracle apps have applied to drill down the records in AP from the GL module after the records are transferred from AP to GL.
ANS: Uses reference column (1-8) to store information about sub-ledger.
28. What is auto accounting?
ANS: It is a required setup before to enter any transaction in AR. We have to define code combinations for different transaction type such as revenue, receivables, bills receivables, charge back, deposit and guarantee to default
29. What is major risk you find in Project? How to mitigate it.
ANS: Resource is a major risk in oracle apps projects. To mitigate it we need to have resource in reserve right from the beginning of the project.
30. What are CR.010 all about?
ANS: It is a Project Management Plan Document.
31. How you maintain time sheet.
ANS: Time sheet is maintained in WM.020 In MS Project format.

NOTE: Sorry if any questions are repeated

Happy New Year 2009 to One and All

Dear All,

Wishing you a Very Very Happy New Year 2009 and may all your wishes come true in this year,lets kick the sad moments of 2008 as well as memorise the beautiful moments of 2008 and welcome to 2009 year.

Regards

Sunil Dutt.B

Sorry for the belated wishes

Template Form in Oracle Apps 11i

Template Form in Oracle Apps 11i
This is an overview of the template form.This form derives its importance from the fact that this form is the starting point of all development involving forms. The document highlights the importance of Template.fmb in forms development and also provides a detailed explanation of the various components of the Template form.
Overview of the Template Form
The TEMPLATE form is the starting point for all development of new forms. The first step in creating a form for use in Oracle Applications is to copy the template form from $AU_TOP/forms/US, to a local directory and renaming it.
The Template form is unique because it contains some special libraries and triggers that render the application using the template form some standard characteristics. The components of the template form are:
· References to object groups: The template form contains platform–independent references to predefined standard object groups in the APPSTAND form (STANDARD_PC_AND_VA,STANDARD_TOOLBAR, and STANDARD_CALENDAR).
· Libraries: The template form contains platform–independent attachments of several libraries (including FNDSQF, APPCORE, and APPDAYPK).
· Special triggers: The template form contains several form–level triggers with required code. These are responsible for standard the behavior of the form.
· Predefined Program Units: The template form contains predefined program units that include a spec and a body for the package APP_CUSTOM, which contains default behavior for window opening and closing events.
· Applications Color Palette: The template form contains the application color palette. This gives the forms developed using the template form the look and feel of Oracle applications.
· Many referenced objects (from the object groups) that support the Calendar, the toolbar, alternative regions, and the menu. These objects include LOVs, blocks, parameters, and property classes, and so on.
· The TEMPLATE form contains sample objects that can be seen as examples for the expected layout cosmetics. These samples can be completely removed from the form later as they are only examples and are not required. The following objects are the samples and can be removed:
o Blocks: BLOCKNAME, DETAILBLOCK
o Window: BLOCKNAME
o Canvas–view: BLOCKNAME
Hence, the template form comes along with many attachments, predefined program units, and defined visual attributes as well as examples that not only give the forms that are developed using the template.fmb a standard look and feel, but also make t easier to develop forms with consistent and standard functionality.
Libraries in the Template form
As stated above, the template form contains platform–independent attachments of several libraries. These libraries are used while running the form as a part of Oracle Applications. Hence, these libraries should not be changed or modified. There are three main libraries that are attached to the template form:

APPCORE

APPDAYPK

FNDSQF Each of these libraries is explained in detail below.
APPDAYPK
The APPDAYPK library contains the packages that control the Oracle Applications Calendar feature. The calendar (or the date picker) is a utility that oracle apps provide to pick the dates for a date type field.
FNDSQF
FNDSQF contains packages and procedures for Message Dictionary, flexfields, profiles, and concurrent processing. It also has various other utilities for navigation, multicurrency, WHO, etc. 23–4 Oracle Applications Developer’s Guide Procedures and functions in FNDSQF typically have names beginning with ”FND”.
Other Libraries
The template form also contains a few other libraries that are not linked directly to the template form, but are linked to the three libraries listed above. Although, while using the form it makes no difference whether the library is linked directly to template or to another library that is linked to template. These are discussed below.
CUSTOM library:
The CUSTOM library (CUSTOM.pll) is probably the most widely used and customized in the libraries attached to the template form. This library allows extension of Oracle Applications forms without modification of Oracle Applications code. Any form goes to the CUSTOM.pll whenever any event fires on the form. Code can be written in the CUSTOM.pll with the logic branching based on the form, block and trigger on which you want it to run.
You can use the CUSTOM library for customizations such as Zoom (such as moving to another form and querying up specific records), enforcing business rules (for example, vendor name must be in uppercase letters), and disabling fields that do not apply for your site.
GLOBE:
The GLOBE library allows Oracle Applications developers to incorporate global or regional features into Oracle Applications forms without modification of the base Oracle Applications form. Oracle Applications sends events to the GLOBE library. Regional code can take effect based on these events. The GLOBE library calls routines in the JA, JE, and JL libraries.
VERT:
The VERT library allows Oracle Applications developers to incorporate vertical industry features (for automotive, consumer packaged goods, energy, and other industries) into Oracle Applications forms without modification of the base Oracle Applications form. Oracle Applications sends events to the VERT library. Vertical industry code can take effect based on these events. The VERT library calls routines in various other libraries.
JA
The JA library contains code specific to the Asia/Pacific region and is called by the GLOBE library.
JE
The JE library contains code specific to the EMEA (Europe/MiddleEast/Africa) region and is called by the GLOBE library.
JL
The JL library contains code specific to the Latin America region and is called by the GLOBE library.