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 Engagement Cloud > Reporting and Analytics for Engagement Cloud 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 Cloud 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.
  • Ifeanyi Katchy
    Purchasing Documents Pending Approval274.8
    Topic posted February 24, 2017 by Ifeanyi KatchyBlue Ribbon: 750+ 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
  • Ling Xiang
    R13 Financials OTBI subject area to database lineage mapping...244.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. 

  • Aleksandar Bahchevanov
    Format Date doesn't display month as upper case22
    Topic posted April 4, 2018 by Aleksandar BahchevanovGreen Ribbon: 100+ Points, tagged BI Publisher in Business Analytics > Business Intelligence public
    Title:
    Format Date doesn't display month as upper case
    Summary:
    Format Date doesn't display month as upper case
    Content:

    Hi All,

     

     

    I'm using OTBI release 12 and I have a BI publisher predefined report.

    I have a field where I want the date to be displayed with the following date mask : DD-MON-YYYY. It works almost correct, but the month is not uppercase(e.g. not APR but Apr). Any ideas?

     

    Here is the source I use:

     

     

    <?format-date:(xdoxslt:ora_format_date_offset(xdoxslt:sysdate('YYYY-MM-DD'),7,'+'));'DD-MON-YYYY'?>

     

     

    Thanks in advance,

    Aleks

  • Kumo70
    field cascading grouping in Report Queries - BI publisher21
    Topic posted April 8, 2018 by Kumo70 Red Ribbon: 250+ Points, tagged BI Publisher in Business Analytics > Business Intelligence public
    Title:
    field cascading grouping in Report Queries - BI publisher
    Summary:
    field cascading grouping in Report Queries - BI publisher
    Content:

    Hi,

     

    Please note the below part#1 ive done now and works BUT my problem is part#2 for long running group records which i need to repeat the header on every page.

     

    iam relative new to Oracle BI publisher but iam trying to create a report query + template layout with grouping as below.

     

    PART#1: (DONE)

    ============================================================

    1. query like:

    =========

    though not sure if this query will give me correct output...

    select dept_name, emp_name, manager, country, location from Employees group by country.....

     

    2. report printout should look like:

    =========================

    Country: USA

    Dept: Sales

    emp_name,   location Manager

    --------------------------------------

    ................................................

    ......             .......           ........

     

    Country: Canada

    Dept: HR

    emp_name,  location Manager

    --------------------------------------

    ..............................................

    ......             .......           ........

     

     

    3. here is my screenshot - note there are 2 cascaded grouping outer COUNTRY main grouping then within it DEPT child grouping as below

    pastedImage_0.png

     

     

    PART#2 (i need help on this pls)

    ============================================================================

    IAM PLANNING TO repeat the header information on every page. if records for a manager group contains many (fullname, title, salary) onto the next page then the header details (department) together with column headers should show at the top of the next page

    pastedImage_0.png

    any suggestion is appreciated

     

    ...thanks.

  • 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

  • Antoine KAIBER
    Formatting Data in BI Publisher report17
    Topic posted June 25, 2018 by Antoine KAIBERSilver Medal: 2,000+ Points, tagged Answers, BI Publisher in Business Analytics > Business Intelligence public
    Title:
    Formatting Data in BI Publisher report
    Summary:
    How to give a good format to date in report
    Content:

    Hello,

    I have a report (which I did not create) on Oracle BI Publisher 11.1.1.9.0  and when I launch my report from OTM (software i'm using) without any format I get the right time for the planned arrival date (16:00 -> 4PM) but when I put the format as shown on the screen, I have 17:00 (5PM). Does anyone know how to change that ?

     

    Image:
  • 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