Answer Posted / samaresh
Lexical references are placeholders for columns or
parameters that you embed in a SELECT statement. You can
use lexical references to replace the clauses appearing
after SELECT, FROM, WHERE, GROUP BY, ORDER BY, HAVING,
CONNECT BY, and START WITH. Use a lexical reference when
you want to substitute multiple values at runtime. You
cannot make lexical references in a PL/SQL statement. You
can, however, use a bind reference in PL/SQL to set the
value of a parameter that is then referenced lexically in
SQL, as shown in te example below. You create a lexical
reference by typing an ampersand (&) followed immediately
by the column or parameter name. A default definition is
not provided for lexical references.
Therefore, you must do the following:
Before you create your query, define a column or parameter
in the data model for each lexical reference in the query.
For columns, you must set the Value if Null property, and,
for parameters, you must set the Initial Value property.
Restrictions::::
You cannot make lexical references in a PL/SQL statement.
If a column or parameter is used as a lexical reference in
a query, its data type must be character.
If you want to use lexical references in your SELECT
clause, you should create a separate lexical reference for
each column you will substitute. In addition, you should
assign an alias to each lexical reference. This enables you
to use the same layout field and boilerplate label for
whatever value you enter for the lexical reference on the
Runtime Parameter Form.
If you use lexical references in your SELECT clause, you
must specify the same number of items at runtime as were
specified in the report's data model. Each value you
specify for your lexical references at runtime must have
the same datatype as its Initial Value.
A lexical reference cannot be used to create additional
bind variables after the After Form trigger fires. For
example, suppose you have a query like the following (note
that the WHERE clause is replaced by a lexical reference):
SELECT ENAME, SAL FROM EMP
&where_clauseIf the value of the where_clause parameter
contains a reference to a bind variable, you must specify
the value in the After Form trigger or earlier. You would
get an error if you supplied the following value for the
parameter in the Before Report trigger: WHERE SAL
= :new_bindIf you supplied this same value in the After
Form trigger, the report would run
Reports Builder uses these values to validate a query with
a lexical reference. Create your query containing lexical
references.
| Is This Answer Correct ? | 8 Yes | 2 No |
Post New Answer View All Answers
what are the prerequisites for costing transactions?
where to define interorganization transaction charges and what are the different options?
how can develope the po variance and po summary report? with tables mandatory columns and query please?
How to move the one file from one instance to another instance? And your scripts also?
Which oracle apps version you are very confident in?
CAN YOU CUSTOMISE THE COUTOMISE CUS_TOP
tell me the scenarios of the independent in reports
Pls tel me the best text book for Oracle Apps 11i Tech? & I want D2K Text book also?
pls send me out bound code of supplers,site,bankiformation code pls as soon as
Hi, Anybody please send me the Oracle APPS 1i technical interview questions (Real time) as wel as sample resume also?
Tell me where we find the status of order information?
what are the balancing segments in AR?
In sequence i want to 11 and 15th values how we will write?
what are the different transaction clauses in AR?
tell me the scenarios of the independent in reports
