How to pass values in lexical parameters in BIP seeded report

1/ First open the SQL Query 

 2/ If your query is like 

 Select abc, def, ghi 

from ap_invoice 

 &FROM_clause 

Where &WHERE_Clause 

p=q 

and m=t 

&ORDERBY_Clause 

 so while running the BI report in fusion please pass on below parameter: 

 &FROM_CLAUSE value will be ,ap_invoices_all or value can be any valid table name exist in entire query. 

 &WHERE_Clause value will be 1=1 and

&ORDERBY_Clause  value will be order by 1

In same fashion we can pass on lexical parameters and see how our query is and after passing parameters how it should look like in real . 

One more example :

SELECT gcc.CODE_COMBINATION_ID,
GCC.ATTRIBUTE_CATEGORY,
gcc.segment1 seg1,
gcc.segment2 seg2,
gcc.segment3 seg3,
gcc.segment4 seg4,
gcc.segment5 seg5,
&VSH_SELECT account
FROM GL_CODE_COMBINATIONS GCC
WHERE gcc.CHART_OF_ACCOUNTS_ID = 9090
AND &VSH_WHERE

&VSH_SELECT value will be null

&VSH_WHERE value will be 1=1

How to put watermark in the RTF template in BIP Oracle Fusion

Step 1: Go to RTF template Step 2: Click on Design > Watermark > Custom Watermark

Now Yellow highlighted above should be printed on output . Let suppose we have to print that if invoice has been printed already then watermark should show as "duplicate" else nothing . Two things: we can make changes in the Data model SQL query itself. Example below decode(printing_pending,'N','Duplicate')"Printing" And we can plag/map "printing" column or XML tag in RTF template.

Now run the rtf template after putting XML values into it. second thing we can make the changes in RTF template itself. Use ifelse condition to decide. xdoxslt:ifelse(.//CF_DUP_FLAG='Y','DUPLICATE','') this condition specifies, if CF_DUP_FLAG is 'Y' then DUPLICATE else NULL 2. Assign to variable to wMark (this is seeded variable)

Cheers

How to call Custom report(which was seeded earlier) from standard ESS job

To customize seeded report please refer my blog https://happyrahoalways.blogspot.com/2021/04/customize-seeded-report-in-oracle-bi.html When you customize the seeded report then standard ESS job will automatically point to customized one. ESS job will check first if custom is there otherwise it will call Standard one. PLease make sure Data Model name of standard and Custom should be same. Similary Reporting name for custom and standard should be same. Also Path should be same for both (standard and Custom)