Explore topic-wise InterviewSolutions in .

There are 3 types of columns in the REPORTS BUILDER:

1. PLACEHOLDER Column
2. Formula Column
3. SUMMARY Column

There are 3 types of columns in the reports builder:

When we SET LOCK OPTION we cannot move the fields in the layout editor outside the FRAME. This is very USEFUL for maintaining the fields.

When we set lock option we cannot move the fields in the layout editor outside the frame. This is very useful for maintaining the fields.

FOUR GROUPS are REQUIRED for a MATRIX REPORTS.

Four groups are required for a matrix reports.

When we SET confine MODE is “ON” then OBJECT cannot be moved OUTSIDE its parent in the report layout.

When we set confine mode is “ON” then object cannot be moved outside its parent in the report layout.

When we set flex MODE is ON then reports AUTOMATICALLY resize the PARENT when the CHILD is resized.

When we set flex mode is ON then reports automatically resize the parent when the child is resized.

The various values are:

1. 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 overflow pages of the Print Condition Object and will be truncated at the logical page boundary, if NECESSARY.
2. All but First: All but First means the object and all of its contents will be printed on all logical pages of the Print Condition Object except the first logical page. The object will be formatted only on overflow pages of the Print Condition Object and will be truncated at the logical page boundary, if necessary.
3. All but Last: All but Last means the object and all of its contents will be printed 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 Object except the last one and will be truncated at the logical page boundary, if necessary.
4. Default: Default means that Oracle Reports will use object positioning to set the Print Condition Type to EITHER *First or *Last for you.
5. 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 formatted and will overflow to SUBSEQUENT pages, if necessary.
6. 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 formatted after the Print Condition Object and will overflow to subsequent pages, if necessary.

The various values are:

‘Print Condition TYPE’ property specifies the frequency with which you want the 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.

‘Print Condition Type’ property specifies the frequency with which you want the 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.

Page protects property for an object indicates whether to try to keep the ENTIRE 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.

Page protects property for an object indicates whether to try to keep the entire 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.

You can SET the MAXIMUM records per page property of the REPEATING FRAME to.

You can set the maximum records per page property of the Repeating frame to.

1. SINGLE QUERY
2. MULTI query
3. Nested Query
4. MATRIX Break

1. Bind PARAMETERS are used to replace a single value in SQL or PL/SQL, such as a character string, number, or date.
2. Lexical parameters are placeholders for text that you EMBED in a SELECT statement. Use Lexical reference when you want the parameter to SUBSTITUTE multiple values at runtime. You can use lexical references to replace the clauses appearing after SELECT, FROM, WHERE, GROUP BY, ORDER BY, HAVING, CONNECT BY, and START WITH.

There are TWO TYPES of parameters:

1. SYSTEM Parameters
2. User defined (BIND and lexical) parameters

There are two types of parameters:

A report has three MAIN SECTIONS:

1. Report header PAGES
2. Report body/margin pages
3. Report trailer pages

A report has three main sections:

A placeholder is a logical column for which you can CONDITIONALLY SET the datatype and VALUE via PL/SQL or a user exit. Placeholder COLUMNS are useful when you want to selectively populate a column with a value.

A placeholder is a logical column for which you can conditionally set the datatype and value via PL/SQL or a user exit. Placeholder columns are useful when you want to selectively populate a column with a value.

There are five reports TRIGGER with order:

1. Before Parameter Form
2. After Parameter Form
3. Before Report
4. Between Pages
5. After Report

Before Form Trigger: It wills Fires before the Run time Parameter Form that will displayed on screen. By using this trigger you can change the value of the parameters.
After Form Trigger: Fires after the Run time Parameter Form is displayed. From this trigger, you can access parameters and check their values. This trigger can also be used to change parameter values or, if an error occurs, return to the Runtime Parameter Form.
Before Report Trigger: It will Fires before the report is executed but after queries are parsed and data is fetched.
Between Pages Trigger: Fires before each page of the report are formatted, except the very FIRST page. This trigger can be used for customized page formatting. (Note: In the Previewer, 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 Trigger: Fires after you exit the Previewer, 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, such as deleting tables. Note, however, that this trigger always fires, whether or not your report completed successfully.

Format Triggers: Format Triggers are PL/SQL functions executed before the OBJECT is formatted. The trigger can be used to dynamically change the formatting attributes of the object.

There are five reports trigger with order:

Before Form Trigger: It wills Fires before the Run time Parameter Form that will displayed on screen. By using this trigger you can change the value of the parameters.
After Form Trigger: Fires after the Run time Parameter Form is displayed. From this trigger, you can access parameters and check their values. This trigger can also be used to change parameter values or, if an error occurs, return to the Runtime Parameter Form.
Before Report Trigger: It will Fires before the report is executed but after queries are parsed and data is fetched.
Between Pages Trigger: Fires before each page of the report are formatted, except the very first page. This trigger can be used for customized page formatting. (Note: In the Previewer, 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 Trigger: Fires after you exit the Previewer, 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, such as deleting tables. Note, however, that this trigger always fires, whether or not your report completed successfully.

Format Triggers: Format Triggers are PL/SQL functions executed before the object is formatted. The trigger can be used to dynamically change the formatting attributes of the object.

A There are TWO types of anchors in ORACLE Reports:

• Implicit (Created when a REPORT will RUN)
• EXPLICIT (Anchors you create)

A There are two types of anchors in Oracle Reports:

An anchor defines the actual POSITION of an OBJECT. Anchors are used to determine the vertical and horizontal POSITIONING of a child object relative to its PARENT.

An anchor defines the actual position of an object. Anchors are used to determine the vertical and horizontal positioning of a child object relative to its parent.

• Tabular
• Master DETAIL REPORTS
• Form Reports
• From Letter Reports
• MAILING LABELS Reports
• MATRIX Reports