Posts

Posts

  • 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.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.
  • Senthilrajan Vaithianathan
    Deprecating BI Publisher connectivity to the Oracle Fusion...75.0
    Topic posted Yesterday by Senthilrajan VaithianathanBronze Trophy: 5,000+ Points, tagged BI Cloud Connector, BI Publisher, Fusion Financial reporting, Fusion Procurement reporting, Fusion Project reporting, Fusion Supply Chain Management reporting, OBI Answers, OTBI, Reports in Reporting and Analytics for ERP public
    Title:
    Deprecating BI Publisher connectivity to the Oracle Fusion Tables
    Summary:
    Restricting access to Fusion Cloud database via BI Publisher Data Model
    Content:

    Heard that Oracle is planning is to restrict the access to Oracle Fusion cloud tables via BI Publisher data models? If that is true we will not be able to perform direct query on the SaaS Tables. Already OTBI Direct query access has been revoked.

    Has anyone got this news?  If this is true, what options we will have to perform any query on the Transactional tables for data validations and how can we create a custom reports and what will happen to existing custom BI Publisher reports that are built on custom data models?

  • MANISH KUMAR
    App Composer to use standard asset fields, Asset Descriptive...
    Topic posted Yesterday by MANISH KUMARBronze Medal: 1,250+ Points, tagged Asset Master Data Management, Maintenance Analytics, OTBI, Tip in Manufacturing & Maintenance > Maintenance public
    Title:
    App Composer to use standard asset fields, Asset Descriptive fields and custom fields
    Summary:
    App Composer to use standard asset fields, Asset Descriptive fields and custom fields
    Content:

    We have more attributes for an Asset than what Asset Descriptive field allows to store. We understand App composer is good tool in Maintenance Cloud for that purpose. My question is can i use App Composer to create new screen and new tables and use the asset fields and descriptive flexfields along with custom fields.

    Also, the custom fields in app composer can be context sensitive?

    Any pointer or info in this regard will be really useful.

     

    Regards,

    Manish

  • Dharmendra Jha
    Displaying the PO MATCHED DATE from the Procurement Subject...1
    Topic posted Yesterday by Dharmendra JhaGreen Ribbon: 100+ Points, tagged OBIEE Answers, OTBI in Reporting and Analytics for ERP public
    Title:
    Displaying the PO MATCHED DATE from the Procurement Subject area
    Summary:
    Displaying the PO MATCHED DATE in PO Details report.
    Content:

    I want to display PO Matched Date and PO receipt date in my PO Details report. for the receipt date issue I have already raised a SR with Oracle but I am unable to find PO Matched Date in any of the subject areas in Procurement.

     

    Currently I am using Procurement - Purchase real time & Procurement - Procure to Pay real time.

     

    Thanks

    Dharmendra

    Version:
    OTBI -19C version.
  • Kevin Haas
    How to use Seniority Date in Analysis?1
    Topic posted November 12, 2019 by Kevin Haas, tagged OBI Answers, OBIEE Answers, OTBI in Reporting and Analytics for ERP public
    Title:
    How to use Seniority Date in Analysis?
    Summary:
    19D release includes new Seniority Date fields which I can't figure out how to use
    Content:

    Hi, 

    According to the documentation for the 19D release, Seniority Date is now enhanced and can be used in OTBI. I've tried creating several Analysis in OTBI using various fields from the 3 subject areas in Workforce Management without success. 

    The subject areas are:
    Workforce Management - Worker Assignment Event Real Time
    Workforce Management - Worker Assignment Real Time
    Workforce Management - Work Relationship Real Time

    I've attempted many reports using columns such as Worker Name, ID, Assignment, Job, Position data and as soon as I pull in any fields within "Seniority Date" the analysis fails, returning "No Results" every time no matter what the combination of columns is used.

    I can't figure out what I need to do to get data from any of the Seniority Date fields. Does anyone out there have a good handle on how to use the new fields?

     

    Thank you very much for your help.

     

     

    Version:
    19D
  • Stephanie Gott
    Convert Date FieldAnswered2
    Topic posted November 12, 2019 by Stephanie GottSilver Medal: 2,000+ Points, tagged Analyses, OBI Answers, OBIEE Answers, OTBI in General OBIEE public
    Title:
    Convert Date Field
    Summary:
    Convert from MM/DD/YYYY to YYYY-Qx
    Content:

    Hello,

    I have a date field I want to convert. I want to convert that from MM/DD/YYY to "YYYY-Qx". Any thoughts on how to do this? I've tried using the Calendar functions in the formula. They work, but don't get me the exact above format. I have to use two separate columns. One gets the quarter number so, in the example above, it would just say "1". The other column I'm able to get the year "2020". When I try do a Concat in the 3rd column, I get syntax error b/c I think it doesn't like to concatenate formulas apparently. Any help would be appreciated. 

    Thanks,

    Stephanie

  • Dev Thota
    Suggestions in Return to Vendor process15.0
    Topic posted November 11, 2019 by Dev ThotaGold Trophy: 10,000+ Points, tagged Approvals, Approvals/Notification, BI Publisher Reports, Business Intelligence, Create Requisition, How-To, Manage Procurement Catalog, OTBI, Public Sector, Requisition Processing, Setup, White Paper in Inventory and Logistics > Inventory public
    Title:
    Suggestions in Return to Vendor process
    Summary:
    Suggestions in Return to Vendor process
    Content:

    Hi All,

     

    While responding to a High-Tech Contract Manufacturer Client RFP, looking for suggestions to provide solution for their major pain point - ‘Return to Vendor’.

     

    For them, this is an issue, since once they receive the goods in Inventory, they may use it only after 3-6 months. While using in Work order, if they find any item is defective, they raise OSP for this item and send to Supplier for repair/replacement.

    They have to raise OSP instead of Return to Vendor, because of the delay in using the items in Work order, and by that time, Purchase Order against which item was received would have been Finally Closed.

     

    We are planning to suggest Oracle Cloud – Return to Vendor with replacement. Kindly suggest :

    1.     How can we address returns for Finally Closed POs ?

    2.     If any better solution to above problem?

     

    Thanks,

    Dev Thota

    Version:
    19D
  • MANISH KUMAR
    Assets Descriptive Flexfield history trackingAnswered3
    Topic posted November 8, 2019 by MANISH KUMARBronze Medal: 1,250+ Points, tagged Asset Master Data Management, Maintenance Analytics, OTBI in Manufacturing & Maintenance > Maintenance public
    Title:
    Assets Descriptive Flexfield history tracking
    Summary:
    Assets Descriptive Flexfield history tracking
    Content:

    Can anyone confirm if the Assets Descriptive Flexfield values are history tracked. We have some asset attributes which need to be captured in Flexfield but some of our department( especially Tax) need to know what was the previous attribute value. Can we do this or what is the approach to achieve this.

     

    Regards,

    Manish

  • Dev Thota
    How to create a OSP PO with 3 lines in a single purchase...1
    Topic posted November 7, 2019 by Dev ThotaGold Trophy: 10,000+ Points, tagged OTBI, Public Sector, Tip, White Paper in Manufacturing & Maintenance > Maintenance public
    Title:
    How to create a OSP PO with 3 lines in a single purchase order
    Summary:
    How to create a OSP PO with 3 lines in a single purchase order
    Content:

    Hi all,

    The requirement is if we create a work order and approve it will trigger to create PO with a single line.

    Our requirement is we need 3 lines in a PO.

     

    Thanks,

    Dev Thota.

    Version:
    19D