Skip to main content

The steps for creating a BI Publisher Report

The steps for creating a BI Publisher Report

BI Publisher is a great tool for creating and publishing pixel-perfect reports – for documents such as statements, letters, etc. It has a lot of great features that will take some time to master but getting started is fairly straightforward.  In OBIEE 11g, BI Publisher can be accessed directly from the main web interface that you see when you log into OBIEE, and you can get started directly from there.
Here are the steps …
1. Create a Data Source (if not already created) – or in other words, create a connection to a Data Source (such as an Oracle database)
2. Create a Data Model or select an existing one – defines the data used by reports (data will come from the Data Source above). The Data Model will include …
  • 2b. Create one or more data sets in the data model – the actual data selected
  • 2c. Create one or more List of Values (LOVs)  –  primarily for use in drop down lists
  • 2d. Create one or more parameters – to add flexibility to your report
  • 2e. Save Sample Data to data model (optional but important – report previews will display better when creating layouts)
3. Design one or more layouts for the report data (template file and set of properties for rendering template file) Layout can be created using MS Word, Adobe Acrobat, MS Excel, Adobe Flashm and BI Publisher Layout Editor). BTW, a report can include multiple layouts.
4. Configure properties for the report – this includes properties that affect the formatting and output of the report.
5. Add translations (optional) – this allows you to add translations for any text that is translatable in your report.
6. View the report using the report viewer – to make sure it looks good and is formatted correctly.
7. Schedule the report and set its destination (basically creating a Report Job) – set the time and report output type.
If you would like to get more details, a tutorial on Getting Started with BI Publisher can be found here on OLL.

Comments

Popular posts from this blog

Create Accounting for a Payment generates errors 95333 and 95359

Create Accounting for a Payment generates errors 95333 and 95359 Error: 95333: A conversion rate does not exist to convert USD to AUD for the conversion type Corporate and conversion date 20-MAR-09 for line -25. Please use the Daily Rates form in General Ledger to enter a conversion rate for these currencies, conversion date and conversion type. 95359: There is no accounted amount for the subledger journal entry line. Please inform your system administrator or support representative that: The source assigned to the accounting attribute Accounted Amount has no value for extract line number 88547. Please make sure the source assigned to the accounting attribute Accounted Amount has a valid value, or assign a different source to this accounting attribute. Solution: 1. Specify a conversion rate for the currencies and conversion date mentioned in the error message 95333 Navigation under the General Ledger responsibility: Setup > Currencies > Currency Rates Manager > Daily Rates ...

Public API’s for FA Transactions

Public API’s for FA Transactions So far Oracle FA is have all the good things except the lack on reporting.Oracle FA is now offer lot of public API's that can be used to interfacing with third party or Oracle application other modules. Here are some of transaction's API's:   Additions API if you have requirement to add assets directly via PL/SQL then use  FA_ADDITION_PUB.DO_ADDITION. If you have selected the Allow CIP Assets check box on the Book Controls window of a tax book when adding CIP assets using the Additions API, the this API automatically adds those CIP assets to that tax book at the same time that they are added to the corporate book. Adjustments API you can make cost adjustments to your assetsdirectly via PL/SQL using  FA_ADJUSTMENT_PUB.DO_ADJUSTMENT  for any  process adjustment. Detail can be found in appendix H) You can use this API if you have a custom interface that makes it difficult to use with the existing Oracle Assets interfaces for adjusti...

AP Table Relation Oracle Apps

AP Table Relation Oracle Apps ORACLE PAYABLE TABLE RELATION Source Table Dependent Table Condition AP_INVOICE_LINES_ALL AIL ZX_LINES_SUMMARY ZLS AIL.invoice_id = ZLS.trx_id and  ZLS.application_id  = 200 and  ZLS.entity_code  = 'AP_INVOICES' and  ZLS.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.summary_tax_line_id = ZLS.summary_tax_line_id AP_INVOICE_LINES_ALL AIL ZX_LINES ZL AIL.invoice_id = ZL.trx_id and  ZL.application_id  = 200 and  ZL.entity_code  = 'AP_INVOICES' and  ZL.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.line_number = ZL.trx_line_number AP_INVOICE_DISTRIBUTIONS_ALL AID ZX_REC_NREC_DIST ZD AID.invoice_id = ZD.trx_id and  ZD.application_id  = 200 and  ZD.entity_code  = 'AP_INVOICES' and  ZD.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and...