ERP - BI report Migration

BI report migration is very simple. We need to archive the data model and report from one instance and unarchive to higher or another instance.

Steps:

ERP - How to stop auto run of a parameterized BI report

When we use parameters in BI report and go all data case, we observe it starts auto running while we just open the report. To avoid this, we simply need to stop the auto run option from properties.

Detailed Steps are below:

ERP - How to create the RTF Template from MSWORD BI publisher

Use case: we will perform the following in the RTF template:

• Show data in tabular format and provide a report name.
• Repeat table header in each page
• Sort data in Ascending order on Invoice Number
• <?sort:INVOICE_NUM;'Ascending'?>
• Show or limit only 5 records per page
• <if:position() mod 5 =0?><xsl:attribute name="break-before">page</xsl:attribute><?end if?>
• Show "NO DATA FOUND" if query does not fetch any data
• <?choose:?><?when:count(INVOICE_NUM) > 0?><?end when?><?otherwise:?>NO DATA FOUND<?end otherwise?><?end choose?>

Detailed steps with screenshots:

Now, my RTF template is ready. Upload it and use.

ERP BI REPORT - XSLT vs BIP Tags | BI publishers

XSLT vs BIP Tags:

• Simple BI Publisher RTF template can be developed with BIP tags. BIP Tags are easier to use even who does not have XML or XSLT experience.
• Behind the scene, BIP tags are translated to XSL code at runtime.
• To develop rich functionality such as Charts, Graps XSLT is used, wizards can be used to define simple charts and graps but to customize the only option is XSLT coding.
• XSLT and BIP Tags can co-exist in the RTF template. Custom functions can be created in XSL template and can be invoked from RTF template.

Example of XSL :

<OrderNum>

  <xsl:value-of select="/Data_DS/G_1/Order_Number"/>

</OrderNum>

<xsl:for-each select="DATA_DS/G_1">

  <SalesOrder>

    <OrderNum>

      <xsl:value-of select="Order_Number"/>

    </OrderNum>

  </SalesOrder>

</xsl:for-each>

Example of BIP tags :

<OrderNum>

  <?/Data_DS/G_1/Order_Number?>

</OrderNum>

<?for-each select="DATA_DS/G_1"?>

  <SalesOrder>

    <OrderNum>

      <?Order_Number?>

    </OrderNum>

  </SalesOrder>

<?end for-each?>

ERP - Create BI reports with Parameters and Dependent LOVs

Usecase: Here, we will create a BI report with parameters and also create dependent LOVs. We will fetch invoice_num,source and description from ap_invoices_all table using p_source and p_inv_num parameters and here, LOV of invoice num will be depended on the parameter p_source.

logic steps:

• Create 2 parameters - p_source and p_inv_num which will be pointing to the following 2 LOVs
• p_source => source_lov
• p_inv_num => inv_num_lov
• Create 2 LOVs where inv_num_lov depended on p_source
• source_lov = select distinct source from ap_invoives_all
• inv_num_lov = select invoice_num from ap_invoices_all where source =:p_source
• Create data set using sql query
• Select invoice_num,source, description from ap_invoices_all where source=nvl(:p_source,source) and invoice_num=nvl(:p_inv_num,invoice_num)
• Create report based on this data model.

Detailed steps with screenshots:

Navigation >> Tools >> Reports and Analytics >> Browse Catalog >> create >> Data Model

Parameters >> Create 2 parameters(initially with text type)

List of Values >> create 2 LOVs,

Parameters >> update paramter type with Menu and select the respective LOVs.

Data sets >> Click + sign >> SQL Query

Provide Name, data source and SQL query.

Click data

Select the source and dependend invoice >> view

Note: if you want to create custom RTF template, export the data. 

Save as sample data >> save data model

Create report

Cancel >> select Data model >> generate RTF

Save the report name

Save Report >> View Report

Test

We can also export data.