Posts

Posts

  • Ling Xiang
    R13.18A OTBI BI Catalog Lockdown44.6
    Topic posted June 15, 2018 by Ling XiangGold Trophy: 10,000+ Points, tagged BI Publisher, Fusion Financial reporting, OBI Answers, OBIEE Answers, OTBI, Reports, Sample Reports in Reporting and Analytics for ERP public
    Title:
    R13.18A OTBI BI Catalog Lockdown
    Summary:
    With 13.18A release customers will no longer be able to modify the shipped BI catalog content.
    Content:

    R13.18A OTBI Product Alert

    This product alert is published by Oracle OTBI Product Development.

    Release 13.18A Factory BI Catalog Lockdown

    To minimize upgrade regression, an enhancement has been introduced in the 13.18A release to permanently make the shipped BI catalog content read-only.  If users attempt to modify the shipped BI catalog content including folder permissions, they will receive an alert "You are not allowed to modify factory content. Save your own content in /Shared/Custom."  Customers that upgrade from R12 to R13 will no longer be able to make changes to the delivered BI catalog even with BI Administrator role. Starting with R13.18A, BI catalog folders will behave as follows:

    • Customers must save all custom content in /Shared/Custom folder or create new sub-folders under /Shared to maintain custom content.
    • Except for /Shared/Custom folder, customers can no longer make any modifications to the delivered BI catalog. If a user attempts to add, change or remove any object including permission list in the delivered catalog folder, he/she will get an error "You are not allowed to modify factory content. Save your own content in /Shared/Custom."
    • Customers are permitted to retain EXISTING custom top-level folders under Shared. All existing content in those top-level custom folders will be preserved.
    • Customers cannot add, remove or change permissions on the shipped folders, e.g. /Shared/ Human Capital Management
    • Customers cannot modify the folder permissions to 'hide' the shipped factory catalog folder, e.g. hide /Shared/Marketing.
    Impact on R12 upgrade customers:
    • For customers upgrading from R12, all existing custom content in /Shared/Custom or custom folders under /Shared and their sub-folders will remain as they are.  However, if customers have modified the content in the delivered BI catalog folders, e.g. added custom reports, modified delivered reports, modified folder or report permission, all changes to this content will be lost after the R13 upgrade.  Customers are advised to archive their custom BI catalog to a file prior to R13 upgrade; and after R13 upgrade customers can unarchive the custom projects in the /Shared/Custom folder.  

     

    • Fusion application users are auto-provisioned with BI Consumer role, which allows them to read and traverse the BI catalog folders. This access is for folder viewing and navigation only and doesn't give the user the privilege to view, open, edit and execute BI reports, for which the user has no security authorization. An enhancement is in development to restrict access to BI catalog folders such that a user will no longer be able to see and traverse BI catalog folders that he or she has no security authorization to access.
  • Ling Xiang
    R13.18A OTBI BI Catalog Lockdown24.7
    Topic posted June 15, 2018 by Ling XiangGold Trophy: 10,000+ Points, tagged BI Publisher, Reporting and Analytics in Sales > Reporting and Analytics for Sales public
    Title:
    R13.18A OTBI BI Catalog Lockdown
    Summary:
    With 13.18A release customers will no longer be able to modify the shipped BI catalog content.
    Content:

    R13.18A OTBI Product Alert

    This product alert is published by Oracle OTBI Product Development.

    Release 13.18A Factory BI Catalog Lockdown

    To minimize upgrade regression, an enhancement has been introduced in the 13.18A release to permanently make the shipped BI catalog content read-only.  If users attempt to modify the shipped BI catalog content including folder permissions, they will receive an alert "You are not allowed to modify factory content. Save your own content in /Shared/Custom."  Customers that upgrade from R12 to R13 will no longer be able to make changes to the delivered BI catalog even with BI Administrator role. Starting with R13.18A, BI catalog folders will behave as follows:

    • Customers must save all custom content in /Shared/Custom folder or create new sub-folders under /Shared to maintain custom content.
    • Except for /Shared/Custom folder, customers can no longer make any modifications to the delivered BI catalog. If a user attempts to add, change or remove any object including permission list in the delivered catalog folder, he/she will get an error "You are not allowed to modify factory content. Save your own content in /Shared/Custom."
    • Customers are permitted to retain EXISTING custom top-level folders under Shared. All existing content in those top-level custom folders will be preserved.
    • Customers cannot add, remove or change permissions on the shipped folders, e.g. /Shared/ Human Capital Management
    • Customers cannot modify the folder permissions to 'hide' the shipped factory catalog folder, e.g. hide /Shared/Marketing.
    Impact on R12 upgrade customers:
    • For customers upgrading from R12, all existing custom content in /Shared/Custom or custom folders under /Shared and their sub-folders will remain as they are.  However, if customers have modified the content in the delivered BI catalog folders, e.g. added custom reports, modified delivered reports, modified folder or report permission, all changes to this content will be lost after the R13 upgrade.  Customers are advised to archive their custom BI catalog to a file prior to R13 upgrade; and after R13 upgrade customers can unarchive the custom projects in the /Shared/Custom folder.  

     

    • Fusion application users are auto-provisioned with BI Consumer role, which allows them to read and traverse the BI catalog folders. This access is for folder viewing and navigation only and doesn't give the user the privilege to view, open, edit and execute BI reports, for which the user has no security authorization. An enhancement is in development to restrict access to BI catalog folders such that a user will no longer be able to see and traverse BI catalog folders that he or she has no security authorization to access.
  • Ling Xiang
    R13.18A OTBI BI Catalog Lockdown5.0
    Topic posted June 15, 2018 by Ling XiangGold Trophy: 10,000+ Points, tagged BI Publisher, BI Publisher Reports, OTBI, Reporting and Analytics, Sample Reports in Reporting and Analytics for SCM public
    Title:
    R13.18A OTBI BI Catalog Lockdown
    Summary:
    With 13.18A release customers will no longer be able to modify the shipped BI catalog content.
    Content:

    R13.18A OTBI Product Alert

    This product alert is published by Oracle OTBI Product Development.

    Release 13.18A Factory BI Catalog Lockdown

    To minimize upgrade regression, an enhancement has been introduced in the 13.18A release to permanently make the shipped BI catalog content read-only.  If users attempt to modify the shipped BI catalog content including folder permissions, they will receive an alert "You are not allowed to modify factory content. Save your own content in /Shared/Custom."  Customers that upgrade from R12 to R13 will no longer be able to make changes to the delivered BI catalog even with BI Administrator role. Starting with R13.18A, BI catalog folders will behave as follows:

    • Customers must save all custom content in /Shared/Custom folder or create new sub-folders under /Shared to maintain custom content.
    • Except for /Shared/Custom folder, customers can no longer make any modifications to the delivered BI catalog. If a user attempts to add, change or remove any object including permission list in the delivered catalog folder, he/she will get an error "You are not allowed to modify factory content. Save your own content in /Shared/Custom."
    • Customers are permitted to retain EXISTING custom top-level folders under Shared. All existing content in those top-level custom folders will be preserved.
    • Customers cannot add, remove or change permissions on the shipped folders, e.g. /Shared/ Human Capital Management
    • Customers cannot modify the folder permissions to 'hide' the shipped factory catalog folder, e.g. hide /Shared/Marketing.
    Impact on R12 upgrade customers:
    • For customers upgrading from R12, all existing custom content in /Shared/Custom or custom folders under /Shared and their sub-folders will remain as they are.  However, if customers have modified the content in the delivered BI catalog folders, e.g. added custom reports, modified delivered reports, modified folder or report permission, all changes to this content will be lost after the R13 upgrade.  Customers are advised to archive their custom BI catalog to a file prior to R13 upgrade; and after R13 upgrade customers can unarchive the custom projects in the /Shared/Custom folder.  

     

    • Fusion application users are auto-provisioned with BI Consumer role, which allows them to read and traverse the BI catalog folders. This access is for folder viewing and navigation only and doesn't give the user the privilege to view, open, edit and execute BI reports, for which the user has no security authorization. An enhancement is in development to restrict access to BI catalog folders such that a user will no longer be able to see and traverse BI catalog folders that he or she has no security authorization to access.
  • Ling Xiang
    R13 Financials OTBI subject area to database lineage mapping...334.8
    Topic posted August 4, 2017 by Ling XiangGold Trophy: 10,000+ Points, tagged BI Publisher, Fusion Financial reporting, OBI Answers, OBIEE Answers, OTBI, Reports in Reporting and Analytics for ERP public
    Title:
    R13 Financials OTBI subject area to database lineage mapping spreadsheet
    Summary:
    This spreadsheet documents R13 Financials OTBI subject areas to database lineage mapping and subject area security.
    Content:

    This spreadsheet is published by Oracle OTBI Development.  This spreadsheet documents Fusion Financials OTBI subject areas, the corresponding View Objects and database tables and columns.  Customers can use this spreadsheet to search for reporting fields in OTBI subject areas or trace the lineage from subject area to database tables, columns and view objects or vice versa.  

    This spreadsheet also documents subject area security duty roles and job roles.

    The spreadsheet applies to Financials R13. 

  • Ifeanyi Katchy
    Purchasing Documents Pending Approval304.9
    Topic posted February 24, 2017 by Ifeanyi KatchyBronze Medal: 1,250+ Points, tagged BI Publisher, Fusion Procurement reporting, Reports, Sample Reports in Reporting and Analytics for ERP public
    Title:
    Purchasing Documents Pending Approval
    Summary:
    A Report showing purchasing documents which are currently pending approval and the person they are currently assigned to.
    Content:

    - If you want a report that simply shows the current approver for a purchasing document (that is, you want to know with whom a document is pending), you can create one using the BPM UI Views. Please see the image in the attached document BPM UI View - PendingApproverReport. Note that you will need to create a seperate report (i.e. seperate BPM UI View) for each type of purchasing document approval process that you are interested in.

     

    - If you need more details, such as how long the document has been pending with the current approver, the approver's email, their manager's email and so on, follow the instructions below to download and run a report created using BI Publisher. This is a single report which covers purchase orders, contract purchase agreements, blanket purchase agreements and requisitions. The report is only available from Release 12.

    To add this content to your environment:

    1. For R12 environment
      • Download RPT_PendingApprover.xdoz
      • Download DM_PendingApprover.xdmz
      •  
    2. For R13 (and higher) environments
      • Download RPT_PendingApprover.xdoz
      • Download DM_PendingApprover_R13.xdmz
      • Rename DM_PendingApprover_R13.xdmz to DM_PendingApprover.xdmz
      •  
    3. Log in to BI Publisher, click on the Catalogs link and locate the folder where you want to save the report and its corresponding data model e.g. Shared Folders>Custom
    4. Click the ‘Upload Resource’ icon
    5. Select the Data Model File (DM_PendingApprover.xdmz) and click to Upload
    6. Repeat Steps 3 & 4 for the Report File (RPT_PendingApprover.xdoz)
    7. Both the data model and report should now be successfully uploaded and visible in your catalog
    8. Select the report and click on ‘Open’ to run the report
  • Ashish Harbhajanka
    How to Pass Parameter from Dashboard to BI Report214.0
    Topic posted April 26, 2017 by Ashish HarbhajankaGold Crown: 30,000+ Points, tagged BI Publisher, Discussion Forums, OBIEE Answers, Reports in General OBIEE public
    Title:
    How to Pass Parameter from Dashboard to BI Report
    Summary:
    Passing Parameter from Dashboard to BI Report
    Content:

    Hi Experts,

    I have a BI Report which has a parameter. (A List of Value Item which gets value from a SQL Query)

    The standalone BI Report works fine.

    The BI Report is embedded in a Dashboard.

    Now I would like to know how can we ensure that the said BI Report works fine in the Dashboard too.

    Any worked out example (containing a very simple Report and with screen-shots ) would be wonderful

    Thanks in Advance!

    Kind Regards

    Ashish

  • Sachin Mistry
    Hyperlinking PO Number, AP Invoice Number on BI Publisher...Answered185.0
    Topic posted November 13, 2017 by Sachin MistryGold Medal: 3,500+ Points, tagged BI Publisher, Fusion Financial reporting, Fusion Procurement reporting, Fusion Project reporting, Fusion Supply Chain Management reporting, Reports, Sample Reports in Reporting and Analytics for ERP public
    Title:
    Hyperlinking PO Number, AP Invoice Number on BI Publisher reports
    Summary:
    Hyperlinking PO Number, AP Invoice Number on BI Publisher reports
    Content:

    We have a BI Publisher report where we are showing Project profitability and showing all transactions on the project - such as all PO lines, all AP lines, all lines imported into projects that are non PO or AP related such as time and expenses.

    End users will like to see hyperlink to PO numbers where they can open the PO, see attachments and all change history.

    How can we accomplish this?

  • Soumya Parhi
    Supplier Audit ReportAnswered175.0
    Topic posted April 13, 2018 by Soumya ParhiGold Trophy: 10,000+ Points, tagged BI Publisher, OTBI, Reports, Sample Reports, Tip in Reporting and Analytics for ERP public
    Title:
    Supplier Audit Report
    Summary:
    Supplier Audit Report
    Content:

    Good People,

    Anyone create supplier Audit Report as a custom one apart from the one available ?

    Thanks,

    Soumya

  • Junio Vitor de Paula
    How to set/enable the menu "Reports and Analytics"...Answered15
    Topic posted September 10, 2019 by Junio Vitor de PaulaRed Ribbon: 250+ Points, tagged BI Publisher, Fusion Financial reporting, OTBI, Reports in Reporting and Analytics for ERP public
    Title:
    How to set/enable the menu "Reports and Analytics" regardless of responsibility
    Summary:
    We’ve created the BI reports to General Ledger but is not possible see the “Reports and Analytics” option on the responsibility menu area, is possible enable this icon/area?
    Content:

    Hi Community,

    We’ve created the BI reports to General Ledger but is not possible see the “Reports and Analytics” option on the responsibility menu area printed below. The icon is missing!

    There some modules, for example: “Fixed Assets” that this option is totally visible.

    In summary, the question is:
    What I need to do (If possible send us the step by step) to add the Icon/actions “Reports and Analytics” in others responsibilities. Only with this option I can add the reports that was created/granted for a specific user.

    Thanks,
    JV

    Version:
    Oracle Cloud Application 19C (11.13.19.07.0)
    Image:
  • Kamran Butt
    Custom BI Publisher Report SQL ErrorAnswered14
    Topic posted September 16, 2019 by Kamran ButtRed Ribbon: 250+ Points, tagged BI Publisher, Fusion Financial reporting, OBI Answers, OBIEE Answers, OTBI, Public Sector, Reports in Reporting and Analytics for ERP public
    Title:
    Custom BI Publisher Report SQL Error
    Summary:
    SQL or ORA exceptions error.
    Content:

    Hello,

    We are receiving the following error when running a custom built BI Publisher report. This report was functioning without any issues 2-3 weeks prior. No changes were made, but now we are receiving this error when trying to run.

    Please see attached for data model and report.

    SQL or ORA exceptions caused due to invalid sql, database package state or some database exceptions.

    Please advise on how best to debug. Thanks!

    Version:
    Oracle Cloud 19C (11.13.19.07.0)
    Image: