Académique Documents
Professionnel Documents
Culture Documents
Posted on August 12th, 2007 by Sanjit Anand | Print This Post | Email This Post
We can integrate Oracle reports with Oracle Application Object Library, and run them as concurrent
programs from your forms or through standard request submission.
These are the user exits available in Oracle Reports that makes AOL integration.
FND SRWINIT
o This is a User Exit which sets your profile option values and allows Oracle AOL user
exits to detect that they have been called by oracle repots.
o FND SRWINIT also allows your report to use the correct organization automatically.
o Can be used in BEFORE-REPORT Trigger.
FND_SRWEXIT
o This user exit ensures that all the memory allocated for AOL user exits has been freed
up properly.
o Can be used in AFTER- REPORT Trigger
USER EXITS
o are used in Oracle APPS to access user profile values and perform proper calculation.
o Ex. of Other AOL User exits available in Reports are given below.
FND FORMAT_CURRENCY
o To format the currency amount dynamically depending upon the precision of the actual
currency value, standard precision, users profile values and location (country) of the
site.
o You obtain the currency value from the database into an Oracle Reports column.
Define another Oracle Reports column, a formula column of type CHAR, which
executes the FORMAT_CURRENCY user exit to format the currency value. A displayed
field has this formula column as its source so that the formatted value is automatically
copied into the field for display.
Syntax
FND FORMAT_CURRENCY
CODE=â€:column containing currency codeâ€
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
o This user exits allows you to use Flex fields in Reports.
Syntax:
FND FLEXSQL
CODE="flexfield code"
APPL_SHORT_NAME="application short name"
OUTPUT=":output lexical parameter name"
MODE="{ SELECT | WHERE | HAVING | ORDER BY}"
[DISPLAY="{ALL | flexfield 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
Syntax:
FND FLEXIDVAL
CODE="flexfield 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"]
This is an AOL user exit available to populate key flexfields for display
CODE means Key flexfield code(GL# is for Accounting Flex field, for all other check the table
FND_ID_FLEXS)
NUM is the structure of the key flex field(Chart of Accounts Number)
DATA is where you store the retrieved data (your sql output).
Example
SRW.REFERENCE(:SEC_SEG);
SRW.USER_EXIT('FND FLEXIDVAL CODE="GL#"
DATA=":SEC_SEG"
APPL_SHORT_NAME="SQLGL"
VALUE=":SEC_SEG_DISP"
DISPLAY="ALL"
NUM=":P_STRUCT_NUM" ');
return(:sec_seg_disp);
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
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 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 report 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.
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.
23. What are the various page layout sections in Oracle Reports ?
A A report has three sections : the report header pages, report body/margin pages, and report trailer
pages.
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.
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
44. 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.
45. What are the various values of the 'Print Condition Object' property in Reports ?
* The various values are :
Anchoring Object : Anchoring Object is the parent object to which the current object is implicitly or
explicitly anchored.
Enclosing Object : Enclosing Object is the object that encloses the current object.
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 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.
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.
56. What are the various values of the 'Print Direction' Property of Repeating frames ?
* 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 logical page.
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.
FNDLOAD
FNDLOAD
The Generic Loader (FNDLOAD) is a concurrent program that can transfer Oracle Application entity
data between database and text file. The loader reads a configuration file to determine which entity
to access. In simple words FNDLOAD is used to transfer entity data from one instance/database to
other. for example if you want to move a concurrent program/menu/valuesets developed in
DEVELOPMENT instance to PRODUCTION instance you can direct use this command.
Steps to Move a Concurrent program from one instance(Database) to other
· Define your concurrent program and save it in first instance(for how to register a concurrent
program click here)
· Connect to your UNIX box on first instance and run the following command to download the .ldt file
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt
PROGRAM APPLICATION_SHORT_NAME="Concurrent program application short name"
CONCURRENT_PROGRAM_NAME="concurrent program short name"
Note: Make sure you are giving proper .lct file in the commands and don’t confuse with .lct and .ldt
files
These following are the other entity data types that we can move with FNDLOAD
1 - Printer StylesFNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct
file_name.ldt STYLE PRINTER_STYLE_NAME="printer style name"
2 - LookupsFNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct
file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME="FND"
LOOKUP_TYPE="lookup name"
3 - Descriptive Flexfield with all of specific ContextsFNDLOAD apps/apps O Y DOWNLOAD
$FND_TOP/patch/115/import/afffload.lct file_name.ldt DESC_FLEX
P_LEVEL=’COL_ALL:REF_ALL:CTX_ONE:SEG_ALL’ APPLICATION_SHORT_NAME="FND"
DESCRIPTIVE_FLEXFIELD_NAME="desc flex name" P_CONTEXT_CODE="context name"
4 - Key Flexfield StructuresFNDLOAD apps/apps O Y DOWNLOAD
$FND_TOP/patch/115/import/afffload.lct file_name.ldt KEY_FLEX
P_LEVEL=’COL_ALL:FQL_ALL:SQL_ALL:STR_ONE:WFP_ALL:SHA_ALL:CVR_ALL:SEG_ALL’
APPLICATION_SHORT_NAME="FND" ID_FLEX_CODE="key flex code"
P_STRUCTURE_CODE="structure name"
5 - Concurrent ProgramsFNDLOAD apps/apps O Y DOWNLOAD
$FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM
APPLICATION_SHORT_NAME="FND" CONCURRENT_PROGRAM_NAME="concurrent name"
6 - Value SetsFNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct
file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME="value set name"
7 - Value Sets with valuesFNDLOAD apps/apps O Y DOWNLOAD
$FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET
FLEX_VALUE_SET_NAME="value set name"
8 - Profile OptionsFNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct
file_name.ldt PROFILE PROFILE_NAME="profile option" APPLICATION_SHORT_NAME="FND"
8 - Request GroupsFNDLOAD apps/apps O Y DOWNLOAD
$FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt REQUEST_GROUP
REQUEST_GROUP_NAME="request group" APPLICATION_SHORT_NAME="FND"
10 - Request SetsFNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct
file_name.ldt REQ_SETAPPLICATION_SHORT_NAME="FND" REQUEST_SET_NAME="request
set"
11 - ResponsibilitiesFNDLOAD apps/apps O Y DOWNLOAD
$FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY
RESP_KEY="responsibility"
12 - MenusFNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct
file_name.ldt MENU MENU_NAME="menu_name"
13 - Forms PersonalizationFNDLOAD apps/apps 0 Y DOWNLOAD
$FND_TOP/patch/115/import/affrmcus.lct file_name.ldt FND_FORM_CUSTOM_RULES
function_name=FUNCTION_NAME
Note: UPLOAD command is same for all except replacing the .lct and passing any extra parameters
if you want to pass
FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/corresponding.lct
upload_file.ldt