Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
2. What is the difference between Master - Detail Report and report created by
breaks?
Master/detail data models are very similar to break report data models. However, a
master/detail data model is created using two queries, each of which owns at least one
group, and a data link. A break report data model is created using one query and at least
two groups. While reports based on a single query are usually more efficient than reports
based on multiple queries, sometimes the structure of your data tables may require you to
link multiple tables.
Implicit Anchors : At runtime, Oracle Reports generates an implicit anchor for each
layout object that does not already have an explicit anchor. It determines for each layout
object which objects, if any, can overwrite it, then creates an anchor from the layout
object to the closest object that can overwrite it. This prevents the object from being
overwritten. The implicit anchor functionality saves you from having to define the
positioning of each object. Implicit anchors are not visible in the Layout editor. However,
you can specify that the Object Navigator display anchoring information using the Object
Navigator Options dialog.
Explicit Anchors: Create an anchor in the Layout editor by clicking on the Anchor tool,
dragging from one edge of the child to the one of the parent's edges, then specifying the
anchor's properties in its property sheet. Any anchor you create for an object will override
its implicit anchoring. Explicit anchors are always visible in the Layout editor unless you
specify otherwise via the Layout Options dialog
5. What are the various report triggers? What is their order of firing?
There are eight report triggers. Of these there are five global triggers called 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 triggers:
* Validation Triggers
* Format Triggers
* Action Triggers
Before Form: Fires before the Runtime Parameter Form is displayed. From this trigger,
you can access and change the values of parameters, PL/SQL global variables, 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 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. 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 parameters or other data).
Before Report: Fires before the reports is executed but after queries are parsed and data
is fetched.
Between Pages: Fires before each page of the report is 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: 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.
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 validate 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 attributes of the
object.
Action Triggers: Action Triggers are PL/SQL procedures executed when a button is
selected in the Previewer. The trigger can be used to dynamically call another report (drill
down) or execute any other PL/SQL.
6. 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 you want to
selectively populate a column with a value (e.g., each time the nth record is fetched, or
each time a record is fetched containing a specific value, etc.).
Physical Page: A physical page (or panel) is the size of a page that will be output 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 Previewer displays the logical
pages of your report output, one at a time.
Lexical Referencing: Lexical references 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.
15. 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.
21. What are the various values of the 'Print Condition Type' property in Reports?
* 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 overflow 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 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.
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.
*Default: Default means that Oracle Reports will use object positioning to set the Print
Condition Type to either *First or *Last for you. (The asterisk indicates 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 formatted 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 formatted after the Print
Condition Object and will overflow to subsequent pages, if necessary.
* For repeating frames, the print condition type property refers to every logical 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 every logical page. If you specify a
Print Condition Type setting of All but First 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 one 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 be printed on all subsequent pages of this instance except the first page.
25. 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 formatted
objects or data within it are short enough, but it cannot increase to a height 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 less than that shown in
the editor. (You can think of this option as meaning "only expand, do not contract.")
Fixed: Fixed means the height of the object is the same on each logical page, regardless
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 accommodate
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.
27. 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.
Across/Down: Across/Down means that each instance of the repeating frame subsequent
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 margin of the logical page. At that
time, Oracle Reports prints the instance below the left-most instance on the logical page,
provided there is enough vertical space left on the logical page for the instance to print
completely.
Down: Down means that each instance of the repeating frame subsequent to the first
instance is printed below the previous instance down the logical page.
Down/Across: Down/Across means that each instance of the repeating frame subsequent
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.
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, graphics, 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.
44: What are Difference between and Lexical and Bind Parameter?
Ans:
Bind Parameter Lexical Parameter
With the help of Bind Parameter You Can With the help of Lexical Parameter You can
Pass Values. pass string. You can pass lexical parameter in
Select, From , Where Clause
User exits are used to set profile options and are actually used to pass the control from
4gl to 3 gl language to do complex calculations for ex from Oracle reports to outside and
return back to reports.
Few of the commonly used user exits are
fnd.srwinit (It allows oracle AOL user exits to detect that they have been called by oracle
reports Called from before report trigger)
fnd.flexsql (for retrieving data from the flex-fields in the report using lexical reference)
fnd.flexidval (use to display the data retrieved by flexsql using a formula column)
fnd.srwinit (used to release all the memory allocated by oracle AOL used in
After report trigger)
48: In Which Folder You will put the Report on the Server?
/reports/us/
Token is nothing but an interface between report builder parameters and concurrent
program parameter.
Report builder parameters are not in sequence. That is why we combine with token.
51: 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.
There is special purpose of using application names at the time of Executable definition
and Concurrent program definition. The Application which is used during Executable
definition, the reports should be under that $Appl_TOP/Reports/Lang otherwise the
concurrent program will error out due to no file found.
The purpose of application name using in concurrent program definition, the log and out
files are generated under that particular $Appl_TOP/log or /out directory.
Whatever application you use during your concurrent program definition or executable
but always consider the above two points.
INCOMPATIBLE means: Two incompatible reports or request set are not allowed to run
in parallel. Incompatible reports /program can only run sequentially, the first one must
terminate before the other is allowed to start.
57. What is the purpose of XML report when compared to reports 6i & discoverer?
XML/BI Publisher gives the flexibility to users in order to select the output type in
EXCEL/HTML/PDF/FO etc as per their requirement. If a User ran a report in PDF and
wants to get the same in EXCEL its not required for them to re-run the report Instead
they can republish it using Republish option in Tools and can select the output type
whatever is required.
XML/BI Publisher reports give you additional features for Reports 6i. You can get the
XML Report in EXCEL/HTML/PDF etc as per the output type selected. Data Model in
Reports 6i RDF will be the same but you don’t require a Layout model in the RDF File.
You instead create the Layout in a Word Document using the XML Publisher Desktop
installed. You can directly implement XML Publisher and is not required to implement
Discoverer again.
Before the release of Discoverer 10g Discoverer is a license free version and after its
release the license has become too costly due to which the clients are going for XML
Publisher reports ignoring Discoverer.
1] Add the “Xml Publisher Administrator” Responsibility to the user through the front
end.
2] Create the Report (Data Model or we can say the .Rdf file) using Oracle Report
Builder.
3] Set the user parameter as P_Conc_Request_id.
4] Add the default values to the Before Report and After Report triggers (not mandatory)
5] Ftp the Report to the Cust_Top/Report/Us.
6] Open the Oracle E-Business Suite then go to
Sysadmin>Concurrent>Program>Executables, Here we have to create one executable file
for that RDF.
7] Then go to Sysadmin>Concurrent>Program>Define, Here we have to make a
Concurrent Program for that Executable. Make sure that the output format must be XML.
8] Go to the Sysadmin>Security>Responsibility>Define. Query for the Xml Publisher
Administrator. See the Request Group attached to this. Attach the Concurrent Program to
this Request Group.
9] Design the template in Ms Word (Using the .Rtf file).
10] Go to responsibility XML PUBLISHER ADMINISTRATOR. Then Go to
HOME>DATA DEFINITION>CREATE DATA DEFINITION and create a new data
definition. Make sure that your Data Definition’s Code should be same as Concurrent
Program’s Short Name used by you to create the RDF file.
11] Now go to Xml publisher administrator>Home>Template. Create a new template
with template type=’Rtf’. Then upload the RTF File by browsing the path.
12] Now go to the Responsibility and run the request.
FND FORMAT_CURRENCY
CODE=: column containing currency
DISPLAY_WIDTH=field width for display
AMOUNT=: source column name
DISPLAY=: display column name
[MINIMUM_PRECISION=:P_MIN_PRECISION]
[PRECISION={STANDARD|EXTENDED}]
[DISPLAY_SCALING_FACTOR=:P_SCALING_FACTOR]
FND FLEXSQL
Call this user exit to create a SQL fragment usable by your report to tailor your SELECT
statement that retrieves flex field values. This fragment allows you to SELECT flex field
values or to create a WHERE, ORDER BY, GROUP BY, or HAVING clause to limit or
sort the flex field values returned by your SELECT statement. You call this user exit once
for each fragment you need for your select statement. You define all flex field columns in
your report as type CHARACTER even though your table may use NUMBER or DATE
or some other data type.
Syntax:
FND FLEXSQL
CODE=”flex field code”
APPL_SHORT_NAME=”application short name”
OUTPUT=”:output lexical parameter name”
MODE=”{ SELECT | WHERE | HAVING | ORDER BY}”
[DISPLAY="{ALL | flex field qualifier | segment number}"]
[SHOWDEPSEG="{Y | N}"]
[NUM=":structure defining lexical" | MULTINUM="{Y | N}"]
[TABLEALIAS="code combination table alias"]
[OPERATOR="{ = | < | > | <= | >= | != | "||" | BETWEEN | QBE}"]
[OPERAND1=":input parameter or value"]
[OPERAND2=":input parameter or value"]
FND FLEXIDVAL
Call this user exit to populate fields for display. You pass the key flex fields data
retrieved by the query into this exit from the formula column. With this exit you display
values, descriptions and prompts by passing appropriate token (any one of VALUE,
DESCRIPTION, APROMPT or LPROMPT).
Syntax:
FND FLEXIDVAL
CODE=”flex field code”
APPL_SHORT_NAME=”application short name”
DATA=”:source column name”
[NUM=":structure defining source column/lexical"]
[DISPLAY="{ALL|flexfield qualifier|segment number}"]
[IDISPLAY="{ALL|flexfield qualifier|segment
number}"]
[SHOWDEPSEG="{Y | N}"]
[VALUE=":output column name"]
[DESCRIPTION=":output column name"]
[APROMPT=":output column name"]
[LPROMPT=":output column name"]
[PADDED_VALUE=":output column name"]
[SECURITY=":column name"]
If 2nd parameter value is based on 1st parameter then how do u declare it?
Let v2 be the value set definition of 2nd parameter and v1 be the value set definition for
the first parameter then
In the value set definition of v2 = value $FLEX$.v1
What is the minimum number of groups required for a Matrix type report?
To create a matrix report, you need at least four groups: one group must be a cross-
product group, two of the groups must be within the cross-product group to furnish the
"labels," and at least one group must provide the information to fill the cells. The groups
can belong to a single query or to multiple queries.
A matrix (cross tab) report contains one row of labels, one column of labels, and
information in a grid format that is related to the row and column labels. A
distinguishing feature of matrix reports is that the number of columns is not known until
the data is fetched from the database.
To better see execution plans in a trace file, you need to format the
Generated traces file with tkprof statement.
What is the significance of P_Conc_Request_id?
P_Conc_Request_id is declared as the user parameter for reports which will get org
specific data. P_Conc_Request_id data type is character and length is 15.
FND_REQUEST.SUBMIT:
Begin
v_request_id:= fnd_request.submit_request (applicationshortname
concurrentprogramshortname description parameters)
Commit;
If v_request_id > 0 then
dbms_output.put_line (‘successfully submitted')
Else
dbms_output.put_line ('Not Submitted');
End;
What is Boilerplate?
Ans: Boilerplate is any text or graphics that appear in a report every time it is run. Report
Builder will create one boilerplate object for each label selected in the Report Wizard (it
is named B_Column name). Also, one boilerplate object is sometimes created for each
report summary. A boilerplate object is owned by the object surrounding it, unless
otherwise noted.
System parameters
Oracle Reports is shipped with the following system parameters. You can change their
default values as described above.
Table 1-1 System parameter descriptions
System
Parameter Description
COPIES Is the number of report copies that should be made when the report is
printed.
DESFORMAT Is either:
the output format for the report (for example, PDF, HTML, HTMLCSS,
RTF, XML, SPREADSHEET, DELIMITED, or DELIMITEDDATA
for bitmapped reports).
the printer definition to use when formatting the report when
DESTYPE=FILE and DESNAME=filename. If MODE=BITMAP, this
is the name of the printer. If MODE=CHARACTER, this is the
character mode printer definition file (.prt file).
DESNAME Is the name of the output device (for example, the file name, printer's
name, mail user ID).
DESTYPE Is the type of device that will receive the report output (for example,
System
Parameter Description
SCREEN (to format the report using screen fonts), FILE, PRINTER,
MAIL, SYSOUT, CACHE, or LOCALFILE.
MODE Is whether the report should run in CHARACTER mode or BITMAP.
ORIENTATION Is the print direction for the report (LANDSCAPE, PORTRAIT,
DEFAULT).
PRINTJOB Is whether the Print Job dialog box should appear before the report is
run.
First of all we need to configure Reports to use your SMTP server to send emails. The
SMTP server address is held in a configuration file called rwbuilder.conf. Follow the
steps below:
1. Find this file (usually in /reports/conf or search for it using Windows search)..
2. Open it for editing in your favorite editor.
3. Find an entry like 192.168.100.100 (Please note that the IP address in the file on your
PC will be different to this one).
4. Change the IP address found in the above step to your SMTP server's NAME or IP
Address.
5. Save and close this file
6. Close Oracle reports if it up and then restart it (so it can read the changed config file)
The above steps would configure Reports to use your SMTP server.
Set the following "System Parameters" under Data Model in Oracle Reports for your
report.
* DESTYPE = Mail
* DESNAME = email address where you want the ouput to go to
Run your report and if all goes well you should have an email in your inbox (if you
supplied your email address in DESNAME parameter of course!!).
I switched the page size to 11x 8.5, but the printer still prints in Portrait.
Even though we set the page size in the report properties, there is a another variable in the
system parameters section under the data model in the object navigator called orientation.
This sets the printer orientation. Oracle starts by setting it to "default" which means that
no matter how we set the page size, the user's default printer setup will be used. We can
also set it to either "Landscape" or "Portrait" to force the printer orientation no matter
what the user has set as default.
User-created Repeating Frames Create a repeating frame in the Layout editor by clicking
on the Repeating Frame tool, dragging a region, then specifying its properties in its
property sheet.
The parameter retcode returns 0 for success, 1 for success with warnings, and 2 for
error.
How the stored procedures in the report are are called. What is the use of that?
There is no separate method for calling a database stored procedure in Oracle Reports.
When a procedure is called form Oracle Report and a procedure with that name is
available at several places namely Program Units, Attached Library and Database. The
order will be.
1. Program Units
2. Attached Library
3. Database.
How do you write the report output to Excel file or text file?
A. 1.Use TEXT_IO package 2.Use SPOOL in after Report trigger 3.Use UTL
Package
What is the difference between Conditional Formatting and format trigger?
Both provide the same functionality, used to format the output based on particular
conditions. Format triggers provide a wide variety of options when compared to
conditional formatting (GUI). In format Triggers we have the option to write PL/SQL
code where as conditional formatting is GUI based which provide limited options.