select distinct CLASS_ID || '-' || CLASS_DESCR clsfrom S_DEPT_CLASS_SUBCLASwhere (least(:P_DEPT) is null or DEPARTMENT_ID || '-' || DEPT_NAME in (:P_DEPT))and BUSINESS_UNIT_ID = (:P_BU)ORDER BY TO_NUMBER(regexp_substr(CLS,'^[0-9]+')),LOWER(CLS) Is this a LOV or a Data Set query? In the first case the error could occure…

Take a look at http://www.jfree.org/jfreechart/ The default xml-charts are not that great

Ivalid Parameters occure when you refer to other parameters which are null inside of another LOV. Add NVLs or rework your parameter "hierachy"

I don't think that's what's planned for BI Publisher. But you can achieve this but "merging" your two data modells into a single one. Then you can gerenate your two reports as sub templates and a report which data source is the new data modell can call these sub templates conditionally

As Venkat already said... better use a rtf template because you can achieve much more with it

<?import:xdoxsl:////Components/Subtemplates/Subtemplate.xsb?> You've a slash too many It should be: <?import:xdoxsl:///Components/Subtemplates/Subtemplate.xsb?>

Do you recieve any error or is the output not like you've expected? Without that info it'll be hard to help you... But I'll take a guess to speed things up... Even if your code won't lead to a error the output should be something like 12345 12 345 when amount1 would be 12345. You've got two different and separate…

There are two different ways... ​Do it in the data model (more efficent ): <span class="kwd">select</span><span class="pln"> listagg</span><span class="pun">(</span>element<span class="pun">,</span><span class="str">', '</span><span class="pun">)</span><span class="pln"> </span><span class="kwd">within</span><span…

You should do that in the data model. Just use NVL in your query. It'll perform much quicker than it does inside the template.

Declare the format at the very start of your template: <xsl:decimal-format xdofo:ctx="begin" name="NL" decimal-separator="," grouping-separator="."/> Show the formatted number: <?format-number(NUM_COLUMN,'#.###.###.##0','NL')?>

You don't need to reference the whole xml-tree again, when you're inside a group. So <?Nombre?> should be enough inside the for-each

Hello Thomas, You're doing this way too complicated. You don't have to pass all the parameters from your Data Model to the package function... they just have do be defined in the package. This makes the package interface much clearer Compare the Doc: If you define a default package then you must define all parameters as a…

PKG_REPORT_AUTO_DETAILS.RM_WISE_SUMMARY_FOR_ALL_PRODS(P_FROM_DATE:DATE , P_TO_DATE:DATE) Why are you writing that :DATE behind the parameters? PKG_REPORT_AUTO_DETAILS.RM_WISE_SUMMARY_FOR_ALL_PRODS(:P_FROM_DATE, :P_TO_DATE) This would be the right call. The ':' works as a reference to an data model parameter, not as a data…

It's nice to see that there are different approaches out there... I regulary use Choose or the "plain" BI-If Choose-Statement would be something like this: <xsl:decimal-format xdofo:ctx="begin" name="GER" decimal-separator="," grouping-separator="."/> <?choose:?> <?when: p_scaling = "m.0" or p_scaling = "bn.0" ?>…

Ohh I see... so you want different formats for single cells in your header? Technically it could work with some "control cloumns" in your data set. Like the data shown in column 1 got an "1" in the data set. So you could toggle the different formats based on that column. But this becomes very complex... and after all it…

Your second LINE_AMOUNT already has a formatting (like 9G999D99). The format-number tag is compartible only with plain numbers. So if your xml would be like <LINE_AMOUNT>1000<LINE_AMOUNT/> the formatting should be used and therefore the output should also be correct.

I would assume that you should do that in the data model and not inside of a template. A relatively simply PLSQL-Loop where you extract one digit after another and "translate" it should be enough

As Venkat-BIP already mentioned parameters defined in the data model work as report parameters which means that they are constant through the report once it got executed. This shouldn't be a problem as far as your requirements go. Besides the report parameters there is another possible solution: You could define sub…

The standard way I use to format numbers is the following: Declare the format <xsl:decimal-format xdofo:ctx="begin" name="GER" decimal-separator="," grouping-separator="."/> Show the formatted number <?format-number(NUM_COLUMN,'#.###.###.##0,00','GER')?> I don't think that you can design the format itself conditional but…

Why to use a function any way? Just go like <?if: LK_CODE = getVariable?> <? LK_NAME?> <?end if?>