1. What are the report triggers? · Before Parameter Form · After Parameter Form · Before Report · Between Pages · After Report 2. Are there any other triggers? Format Triggers 3. During run time, if you want to change the SQL fragments of the query in data model, then how will you do it? · Create the lexical parameters with default value and add them to the query as &P _WHERE. · The values of these lexical parameters can be dynamically changed in the Before Report Trigger. 4. If the report is using multi org views then what set up is required in .rdf r eport? · Create user parameter P_CONC_REQUEST_ID as type Number, size minimum 15 · Call the user exit in Before Report Trigger FND SRWINIT · Call the user exit in After Report Trigger FND SRWEXIT 5. Once the report is ready, what is the complete procedure of report registrati on right from putting the file on server up to set up in oracle applications? · Select the application in which the report is to be registered. · Find the top directory on the server for above application · FTP the .rdf file in binary mode to the reports/US sub directory of above director y · In oracle applications, create the executable of Oracle Reports type with applicat ion name as above and execution file name as the rdf file name without file exte nsion · Create a Concurrent Program and attach the above executable · Set the printing options in concurrent program · Create the required parameters · Add the concurrent program name into request group attached to the concerned use r s responsibility. · If the existing report is customized, the corresponding concurrent program can b e copied using the Copy To option on Concurrent Programs definition form and the n ew executable can be attached to this program. 6. How is the flex filed reporting made in .rdf reports? Call the user exit (with appropriate values) FND FLEXSQL in Before Report trigge r and FND FLEXIDVAL in the corresponding formula columns. 7. If the report is running in multi currency environment then how are the curre ncy fields formatted? Using the user exit FND_FORMAT_CURRENCY. AOL 8. Can a concurrent program parameter be made as mandatory? Yes. By checking the check box Required 9. Can you hide a concurrent program parameter? Yes. By checking the check box Display
10. What is the relevance of Token field in parameter It is the same as the user parameter in .rdf report which receive the parameter values. 11. Can you pass the default values to concurrent program parameters? Yes. 12. What are the different default types? Constant, Profile, SQL Statement, Segment 13. What are the types of value sets None, Independent, Dependent, Table, Special, Pair, etc. 14. Have you ever created the table validated value set? 15. Can I use multiple tables in the table validation? Yes. 16. Can I use views in the table validation? Yes. 17. What is the relevance of Value, Meaning and Id columns? Value is listed in the list of values, Meaning is shown on the parameter window on t he right hand side and id is passed to the program. 18. Can I have some more columns in the list of value of table validation set? Yes. By including those column names in the additional columns field of table valu e set. 19. In where clause, if I wish to refer the value of preceding parameter then ho w can I do that? By referring the value set of preceding parameter as :$FLEX$.. 20. In where clause, if I wish to refer the value of a profile option then how c an I do that? By referring the profile option name as: $PROFILES$. 21. If Tokens are used to pass the parameter values to oracle report, what is us ed for passing the values to SQL script programs and Host (Shell script) program s? · SQL scripts receive the parameter values in the sequence as they have defined in to lexical parameters as &1, &2, &3, and so on. · Shell script receives the parameters into defined variables as $1, $2, $3, and s o on. However, the first four parameters are hidden as username and password , user id, username & requested. The first user parameter value is received as $5 in th e shell script. Multi Org Concept 22. What do you know about the multi org concept in Oracle Applications? 23. What is the difference between PO_HEADERS and PO_HEADERS_ALL table? PO_HEADERS_ALL is the table containing data of all organizations (operating unit s) and PO_HEADERS is the view showing the data for the organization for the curr ent session.
24. On SQL prompt a simple sql statement select po_header_id from po_headers not return any row. What could be the reason and how can I see the data? The org_id needs to be populated for that sql session using the package nd_client_info.set_org_context (); Forms 25. What is the standard process of creation of new form in Oracle Apps? Using TEMPLATE.fmb, etc. 26. What code have you added in custom.pll? Have you ever enabled the zoom?
does
execute f
27. In Template.fmb, what is the typical name of the standard list of value, whi ch is attached to the Date field for showing the calendar? ENABLE_LIST_LAMP 28. What are the forms Registration process in Oracle Applications?
· Register the Form using Forms window · Create a Form function of FORM Type using Forms Function window. · Attach the forms function to the sub menu or Menu attached to the user s responsibili y. 29. How can I pass the values to the forms parameters while calling it from menu ? You can mention these values in the Parameters column of while defining the Form F unction which are passed while calling the form from Menu. 30. Have you worked on migration of reports/ forms/ sql scripts/ shell scripts f rom Oracle Apps 10.7 to 11i? 31. How did you migrate reports from 2.5 to 6i? You can open 2.5 reports in 6i and use the convert option. Make some dummy chang es in query to re compile queries. Change the column names, table names, call to the procedures or functions if they have changed in 11i. Then re compile the wh ole report and test again. If table and/or column names in table validated value sets or in the SQL statements in default values of concurrent program parameter s are changed they also need to be changed. 32. How did you migrate CUI forms to 6i GUI forms? Recreate them in 6i. Interfaces 33. 34. 35. 36. 37. 38. What interface you have worked on? What was the structure of these interface? Any specific one from above. Then questions specific to that interface Did you code specific validations? Name a few How did you generate the Error Report? What was the strategy to identify and reload the error records?
HYPERLINK "./About Oracle Apps Interview Questions on Oracle Reports 6i_files/A bout Oracle Apps Interview Questions on Oracle Reports 6i.htm" Interview Question s on Oracle Reports 6i
1. What are the various types of reports? * Tabular, Master Detail, Form, Form Letter, Mailing Labels, Matrix 2. What is the difference between Master - Detail Report and report created by b reaks? * Master/detail data models are very similar to break report data models. Howeve r, a master/detail data model is created using two queries, each of which owns a t least one group, and a data link. A break report data model is created using o ne query and at least two groups. While reports based on a single query are usua lly more efficient than reports based on multiple queries, sometimes the structu re of your data tables may require you to link multiple tables. 3. What are Anchors? * An anchor defines the relative position of an object to the object to which it is anchored. Anchors are used to determine the vertical and horizontal position ing of a child object relative to its parent. Since the size of some layout obje cts may change when the report runs (and data is actually fetched), you need anc hors to define where you want objects to appear relative to one another. 4. What are the various types of anchors in Reports? A There are two types of anchors in Oracle Reports: * implicit (anchors that Oracle Reports creates when a report is run) * explicit (anchors you create) Implicit Anchors : At runtime, Oracle Reports generates an implicit anchor for e ach layout object that does not already have an explicit anchor. It determines f or each layout object which objects, if any, can overwrite it, then creates an a nchor from the layout object to the closest object that can overwrite it. This p revents the object from being overwritten. The implicit anchor functionality sav es you from having to define the positioning of each object. Implicit anchors ar e not visible in the Layout editor. However, you can specify that the Object Nav igator display anchoring information using the Object Navigator Options dialog. Explicit Anchors: Create an anchor in the Layout editor by clicking on the Ancho r tool, dragging from one edge of the child to the one of the parent's edges, th en specifying the anchor's properties in its property sheet. Any anchor you crea te for an object will override its implicit anchoring. Explicit anchors are alwa ys visible in the Layout editor unless you specify otherwise via the Layout Opti ons dialog 9. What are the various report triggers? What is their order of firing? A There are eight report triggers. Of these there are five global triggers calle d the Report Triggers. They are fired in the following order: * Before Parameter Form * After Parameter Form * Before Report * Between Pages * After Report Apart from the above Five Report Triggers, there are three other types of trigge rs: * Validation Triggers * Format Triggers * Action Triggers Before Form: Fires before the Runtime Parameter Form is displayed. From this tri gger, you can access and change the values of parameters, PL/SQL global variable s, and report-level columns. (Note: If the Runtime Parameter Form is suppressed, this trigger still fires. Consequently, you can use this trigger for validation of command line parameters).
After Form: Fires after the Runtime Parameter Form is displayed. From this trigg er, you can access parameters and check their values. This trigger can also be u sed to change parameter values or, if an error occurs, return to the Runtime Par ameter Form. Columns from the data model are not accessible from this trigger. ( Note: If the Runtime Parameter Form is suppressed, the After Form trigger still fires. Consequently, you can use this trigger for validation of command line par ameters or other data). Before Report: Fires before the report is executed but after queries is parsed a nd data is fetched. Between Pages: Fires before each page of the report is formatted, except the ver y first page. This trigger can be used for customized page formatting. (Note: In the Previewed, this trigger only fires the first time that you go to a page. If you subsequently return to the page, the trigger does not fire again.) After Report: Fires after you exit the Previewed, or after report output is sent to a specified destination, such as a file, a printer, or an Oracle*Mail userid . This trigger can be used to clean up any initial processing that was done, suc h as deleting tables. Note, however, that this trigger always fires, whether or not your report completed successfully. Validation Triggers: Validation Triggers are PL/SQL functions that are executed when parameter values are specified on the command line and when you accept the Runtime Parameter Form. (Notice that this means each Validation Trigger may fire twice when you execute the report). Validation Triggers are also used to valida te the Initial Value of the parameter in the Parameter property sheet. Format Triggers: Format Triggers are PL/SQL functions executed before the object is formatted. The trigger can be used to dynamically change the formatting attr ibutes of the object. Action Triggers: Action Triggers are PL/SQL procedures executed when a button is selected in the Reviewer. The trigger can be used to dynamically call another r eport (drill down) or execute any other PL/SQL. 19. What are Placeholder Columns? A placeholder is a "dummy" column for which you can conditionally set the data type and value via PL/SQL or a user exit. Placeholder columns are useful when yo u want to selectively populate a column with a value (e.g., each time the nth re cord is fetched, or each time a record is fetched containing a specific value, e tc.). 20. What are the various Module Types in Reports? A You can build three types of modules with Oracle Reports: * external queries, which are ANSI-standard SQL SELECT statements that can be re ferenced by modules * external PL/SQL libraries, which are collections of PL/SQL source code that ca n be referenced by modules * reports, which are collections of report-level objects and references to exter nal queries and PL/SQL libraries (optional) that can be referenced by modules 22. What are Physical and Logical pages in Reports? A report page can have any length and any width. Because printer pages may be sm aller or larger than your report's "page," the concept of physical and logical p ages is used. Physical Page: A physical page (or panel) is the size of a page that will be out put by your printer.
Logical Page: A logical page is the size of one page of your actual report; one logical page may be made up of multiple physical pages. The Reviewer displays th e logical pages of your report output, one at a time. 23. What are the various page layout sections in Oracle Reports? A report has three sections: the report header pages, report body/margin pages, and report trailer pages. 27. What are various types of parameters? A There are two types of parameters: * default (called system parameters) * user-created (called bind and lexical parameters) 30. How do you reference parameters and columns in reports? A In two ways: * As bind references * As lexical references 31. What are Bind Referencing and Lexical Referencing? * Bind Referencing: Bind references are used to replace a single value in SQL or PL/SQL, such as a character string, number, or date. Use bind reference when yo u want the parameter to substitute only one value at runtime. Specifically, bind references may be used to replace expressions in SELECT, WHERE, GROUP BY, ORDER BY, HAVING, CONNECT BY, and START WITH clauses of queries. Lexical Referencing: Lexical references are placeholders for text that you embed in a SELECT statement. Use Lexical reference when you want the parameter to sub stitute multiple values at runtime. You can use lexical references to replace th e clauses appearing after SELECT, FROM, WHERE, GROUP BY, ORDER BY, HAVING, CONNE CT BY, and START WITH. 33. Can you create a group without any break columns? * No. 35. Types of Matrix report? * 1. Single query 2. Multi query 3. Nested Query 4. Matrix Break 37. In Reports, how can you print one record per page in the output? * Set the Maximum records per page property of the Repeating frame to 1. 38. How do you print a Report 2.5 report in character mode? * Set MODE = 'Character' in the Parameter form 39. What are widow lines? * Widow lines are the minimum number of lines of the boilerplate text or field t hat should appear on the logical page where the text starts to print. If the num ber of lines specified for this property cannot fit on the logical page, then al l lines of the boilerplate are moved to the next page. 40. What are widow records? * Widow records are the minimum number of instances (records) that should appear on the logical page where the repeating frame starts to print. If the number of instances specified for this property cannot fit on the logical page where the repeating frame is initially triggered to print, then the repeating frame will s tart formatting on the next page. 41. What is 'page protect' property for objects?
* Page protects property for an object indicates whether to try to keep the enti re object and its contents on the same logical page. Checking Page Protect means that if the contents of the object cannot fit on the current logical page, the object and all of its contents will be moved to the next logical page. 42. What is the 'Print Condition Type' property? * 'Print Condition Type' property specifies the frequency with which you want th e object to appear in the report. The Print Condition Type options indicate the logical page(s) on which the object should be triggered to print with regard to the Print Condition Object. 44. What are the various values of the 'Print Condition Type' property in Report s? * The various values are: All: All means the object and all of its contents will be printed on all logical pages of the Print Condition Object. The object will be repeated on any overflo w pages of the Print Condition Object and will be truncated at the logical page boundary, if necessary. All but First: All but First means the object and all of its contents will be pr inted on all logical pages of the Print Condition Object except the first logica l page. The object will be formatted only on overflow pages of the Print Conditi on Object and will be truncated at the logical page boundary, if necessary. All but Last : All but Last means the object and all of its contents will be pri nted on all logical pages of the Print Condition Object except the last logical page. The object will be repeated on any overflow pages of the Print Condition O bject except the last one and will be truncated at the logical page boundary, if necessary. *Default: Default means that Oracle Reports will use object positioning to set t he Print Condition Type to either *First or *Last for you. (The asterisk indicat es that Oracle Reports specified the setting for you.) First: First means that the object and all of its contents will only be printed on the first logical page of the Print Condition Object. The object will be form atted and will overflow to subsequent pages, if necessary. Last: Last means that the object and all of its contents will only be printed on the last logical page of the Print Condition Object. The object will be formatt ed after the Print Condition Object and will overflow to subsequent pages, if ne cessary. * For repeating frames, the print condition type property refers to every logica l page of every instance (record) of the repeating frame. If you specify a Print Condition Type setting of All and a Print Condition Object setting of Enclosing Object for a field F_1, it prints in every instance of repeating frame R_1 on e very logical page. If you specify a Print Condition Type setting of All but Firs t in the above case , then the field will be printed only in those cases where a single instance (row or record) of the repeating frame spans across more than o ne page (which is normally not the case since many records are there in a single logical page and not one record in many pages). In such a case the field will b e printed on all subsequent pages of this instance except the first page. 43. What is the 'Print Condition Object' property? * 'Print Condition Object' property specifies the object on which to base the Pr int Condition Type of the current object. For example, if you specify a Print Co ndition Type of All and a Print Condition Object of Anchoring Object, the curren t object will be triggered to print on every logical page on which its anchoring object (parent object) appears.
45. What are the various values of the 'Print Condition Object' property in Repo rts? * The various values are: Anchoring Object: Anchoring Object is the parent object to which the current obj ect is implicitly or explicitly anchored. Enclosing Object: Enclosing Object is the object that encloses the current objec t. 46. What is the horizontal of vertical sizing property of objects? * Horizontal of vertical sizing property specifies how the horizontal or vertica l size of the object may change at runtime to accommodate the objects or data wi thin it. 47. What are the various values of the horizontal of vertical sizing property? * The various values are : Contract : Contract means the vertical size of the object decreases, if the form atted objects or data within it are short enough, but it cannot increase to a he ight greater than that shown in the editor. Note : Truncation of data may occur. (You can think of this option as meaning "only contract, do not expand.") Expand: Expand means the vertical size of the object increases, if the formatted objects or data within it are tall enough, but it cannot decrease to a height l ess than that shown in the editor. (You can think of this option as meaning "onl y expand, do not contract.") Fixed: Fixed means the height of the object is the same on each logical page, re gardless of the size of the objects or data within it. Note: Truncation of data may occur. The height of the object is defined to be its height in the editor. Variable: Variable means the object may expand or contract vertically to accommo date the objects or data within it (with no extra space), which means the height shown in the editor has no effect on the object's height at runtime. 51. How do you display a message in reports? * SRW.Message 54. What are the various values of 'Print Panel Order' property of report? * The various values are: Across/Down: Across/Down means the physical pages of the report body will print left-to-right then top-to-bottom. Down/Across: Down/Across means the physical pages of the report body will print top-to-bottom and then left-to-right. 55. What is the 'Print Direction' Property of Repeating frames? * 'Print Direction' Property specifies the direction in which successive instanc es of the repeating frame appear. 56. What are the various values of the 'Print Direction' Property of Repeating f rames? * The various values are: Across: Across means that each instance of the repeating frame subsequent to the first instance is printed to the right of the previous instance across the logi cal page. Across/Down: Across/Down means that each instance of the repeating frame subsequ ent to the first instance is printed to the right of the previous instance until an entire instance cannot fit between the previous instance and the right margi n of the logical page. At that time, Oracle Reports prints the instance below th
e left-most instance on the logical page, provided there is enough vertical spac e left on the logical page for the instance to print completely. Down: Down means that each instance of the repeating frame subsequent to the fir st instance is printed below the previous instance down the logical page. Down/Across: Down/Across means that each instance of the repeating frame subsequ ent to the first instance is printed below the previous instance until an entire instance cannot fit inside the bottom margin of the logical page. At that time, Oracle Reports prints the instance to the right of the topmost instance on the logical page, provided there is enough horizontal space left on the logical page for the instance to print completely. 59. What is the 'Keep with Anchoring Object' object property? * 'Keep with Anchoring Object' object property indicates whether to keep an obje ct and the object to which it is anchored on the same logical page. Checking Kee p with Anchoring Object means that if the object, its anchoring object, or both cannot fit on the logical page, they will be moved to the next logical page. 60. What is 'Page Break Before' object property? * 'Page Break Before' object property indicates that you want the object to be f ormatted on the page after the page on which it is initially triggered to print. Note that this does not necessarily mean that all the objects below the object with Page Break Before will move to the next page. 61. What is 'Page Break After' object property? * 'Page Break After' object property indicates that you want all children of the object to be moved to the next page. In other words, any object that is a child object of an anchor (implicit or explicit) to this object will be treated as if it has Page Break Before set. Note that this does not necessarily mean that all the objects below the object with Page Break After will move to the next page. 63. What is the 'Break Order' property of columns? * The 'Break Order' property is the order in which to display the column's value s. This property applies only to columns that identify distinct values of user-c reated groups (i.e., break groups). The order of column values in a default grou p is determined by the ORDER BY clause of the query. For column values in user-c reated groups, however, you must use Break Order to specify how to order the bre ak column's values. 64. What are the various types of links? * The Data Link tool draws a link between a parent group and a child query. Crea ting a link is a drag and drop operation. Clicking and dragging from one column to another creates a link between those two columns (column to column link). Cli cking and dragging from one query to another creates all possible links between columns selected by the queries based on database constraints (query to query li nk). Clicking and dragging between two groups creates a group-to-group link (i.e ., a link with no columns). 65. Name some of the procedures in the SRW package? * SRW.Message, SRW.User_Exit, SRW.Do_Sql, SRW.Run_Report 66. What are the various report layout regions? * There are three report regions in the Layout editor: * header * body/margin * trailer
Header: The report header pages appear once at the beginning of each report on a set of separate pages. They can contain text, graphics, data, and computations. Body/Margin: The body/margin pages appear between the header and trailer pages, and are the bulk of the report. Each physical page in this section consists of a body and a margin. The body contains the majority of the report's text, graphic s, data, and computations. A top and bottom margin appear on each page, until all data within the body has been formatted. A margin may include text, graphics, page numbers, page totals, and grand totals. The default margin size is one half inch each for the top and bottom margins and zero for the left and right margins. Trailer: The report trailer pages appear once at the end of each report on a set of separate pages. They can contain text, graphics, data, and computations. 70. What is more efficient: Maximum rows or Group Filter? * Maximum Rows in the Query property sheet restricts the number of records fetch ed by the query. A group filter determines which records to include and which re cords to exclude. Since Maximum Rows actually restricts the amount of data retri eved, it is faster than a group filter in most cases. If you are using a Filter of Last or Conditional, Oracle Reports must retrieve all of the records in the g roup before applying the filter criteria. As a result, Maximum Rows or a Filter of First is faster. Q: How will you developed reports from scratch to Registrations. A: STEP1: Write Query according to Specs. STEP2: Add User Parameter in Query. STEP3: Design Data Model. STEP4: Design Layout according to specs. STEP5: Defined Mandatory Parameter P_CONC_REQUEST_ID in report. STEP6: Use User exit in reports. STEP7: FTP the report the appropriate top in reports/US folders. STEP8: registered reports in Oracle Apps (Note Explain all steps of apps registr ations) Q: What is Difference between D2k and APPS Reports? D2K Apps Reports No User Exit User Exit P_Conc_Request_id not Required P_CONC _REQUEST_ID Mandatory Parameter Q: What is Format Trigger? A: Format trigger is used to print conditionally printing of Layout. Format trig ger return Boolean values. Q: What do you mean by Anchoring in Reports? A: With the help of Anchoring Relative position of two objects will be fixed. Q: What are Reports Trigger and Their Firing Sequence? A: BEFORE PARAMETER FORM AFTER PARAMETER FORM BEFORE REPORT BETWEEN PAGES AFTER REPORT Q: What do you mean by Confine Mode in Reports? A: Confine Mode mean Locking of Frames. If Confine Mode is on then you can not m ove the Object outside the Frame. If it is off you can move the objects. Q: What is Difference between Formula Column, Summary and Placeholder Column? A: Formula Column: Formula Column is used to compute Values. Formula Column alwa
ys returns the Values. Summary Column: Summary Column is used for Calculating summary function like Sum , Max. Min, Count. Placeholder Columns: Placeholder Column is used to place the Variables. Q: What are Difference between and Lexical and Bind Parameter? A: Bind Parameter Lexical Parameter With the help of Bind Parameter You Can Pass V alues. With the help of Lexical Parameter You can pass string. You can pass lex ical parameter in Select, From , Where Clause Denoted by Colon Denoted by Amper sand(&) sign Q: How will you Print Conditionally Layout in reports. A: With the help of Format trigger. For example code like: IF: P_TYPE Q: How will you call Concurrent Program through Reports? Q: What is User Exit in Reports? Q: In Which Folder You will put the Report on the Server? Q: How will you register the Reports? Q: What do you mean by Token in Reports? Q: What is Various Default Type in Concurrent Programs? Q: What do you incompatibility in Concurrent Programs? Q: How will you Capture ORG_ID Dynamically in Concurrent Programs. Q: Suppose I have two Parameter Start Date and End Date and I want My Start Date should be lower then End Date. How will you validate. Q: What is Various Execution Method in Concurrent Programs in executables? Q: What is Difference between Application Name Defined in Concurrent Program Exe cutables and Concurrent Programs? Q: What is Mandatory Parameter to Register PL/SQL Procedure in Apps? Q: How will you Call Reports with in Reports? Q: What do you mean by Incompatibility in Reports? Q: What is significance of Mandatory Parameter in P_CONC_REQUEST_ID? Q: How will you put Message in Log File? Q: How will you put Message of Reports in LOG Files?