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 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 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.
  • Angel Martin
    Fusion OTBI - Structure and Components Real Time
    Topic posted June 27, 2019 by Angel Martin, tagged BI Publisher, BI Publisher Reports, Dashboards, OTBI, Product Development, Reporting and Analytics, SCM in Reporting and Analytics for SCM Cloud public
    Title:
    Fusion OTBI - Structure and Components Real Time
    Summary:
    Fusion OTBI - Structure and Components Real Time subject area
    Content:

    HI

    I am trying to do an OTBI Analysis with Structure and Components Real Time subject area  to have all the structures and all the components that belons to the structture, but when I use diffferent attributes for the different folders to combine structure item number and component item number I got some errors and I cannot buid the analysis. Can someone guide to me on that or send to me any example?

    Many thanks

    Angel

  • Ekansh Jain
    How the Service Request can be billed to Customer
    Topic posted June 11, 2019 by Ekansh JainBronze Medal: 1,250+ Points, tagged Channels, Configuration and Administration, Integration, Performance - Fusion, Reporting and Analytics, Service Request Management, Setup and Configuration, UX in Engagement Cloud > Engagement Cloud – Service public
    Title:
    How the Service Request can be billed to Customer
    Summary:
    How the Service Request can be billed to Customer
    Content:

    Hi,

    We are looking for a solution where we can bill the service request to the customer. For example, any kind of the services provided to customer which need to be billed than how we can achieve it?

    Thanks

    Ekansh

  • Mohammed Rafi
    Contract Start Date and End Date25.0
    Topic posted June 10, 2019 by Mohammed RafiBlack Diamond: 60,000+ Points, tagged Reporting and Analytics in Engagement Cloud > Reporting and Analytics for Engagement Cloud public
    Title:
    Contract Start Date and End Date
    Summary:
    Contract Start Date and End Date
    Content:

    Hi,

     

    I am building analysis report on Enterprise Contract please help me to locate Contract Start Date and Contract End Date from the folders under the subject area Enterprise Contract

     

    Attached screenshot

     

    pastedImage_0.png

  • Boby Jacob
    Merging multiple Rows in a Report
    Topic posted May 29, 2019 by Boby JacobGreen Ribbon: 100+ Points, tagged Reporting and Analytics in Engagement Cloud > Reporting and Analytics for Engagement Cloud public
    Title:
    Merging multiple Rows in a Report
    Summary:
    In OSvC, how do merging of multiple Rows to One ?
    Content:

    Hi, 

    I have a requirement in Rightnow to merge multiple rows in  a report to one by comma separated. Please have a look at the attached image for a better idea.

    Thanks

    Boby B Jacob

    Image:
  • premanayagam velayudan
    Customizing a Seeded BI Publisher U.S. 1099 Payments Report...1
    Topic posted May 29, 2019 by premanayagam velayudan, tagged BI Publisher, Reporting and Analytics in Engagement Cloud > Reporting and Analytics for Engagement Cloud public
    Title:
    Customizing a Seeded BI Publisher U.S. 1099 Payments Report - Editing the Data Model - not working
    Summary:
    Unable to modify Seeded BI Publisher Data Models
    Content:

    Hi Team,

    While we are trying to extend existing U.S. 1099 BI Publisher Data Model, unable to modify the SQl due to Bind Global temporary Tables.

    Error while modifying Data model SQL: ORA-00907: missing right parenthesis

    Due to Parameters: &C_DYNAMIC_SQL ,&LP_QUERY_DRIVER unable to edit data model, Please advice on how to modify seeded BI Publisher reports.

    PS:
    Seeded Data Model Path: /Shared Folders/Financials/Payables/Income Tax and Withholding/Data Models/U.S. 1099 Data Model
    Seeded Report Path: /Shared Folders/Financials/Payables/Income Tax and Withholding/U.S. 1099 Payments Report

     
     

    ORA-00907: missing right parenthesis

  • Jeevthan J
    Export GeographiesAnswered55.0
    Topic posted May 29, 2019 by Jeevthan JRed Ribbon: 250+ Points, tagged Core SFA, Reporting and Analytics, Setup and Maintenance in Engagement Cloud > Engagement Cloud – Sales public
    Title:
    Export Geographies
    Summary:
    We need to export list of Country and Country Code from oracle Sales Cloud
    Content:

    We need to export list of Country and Country Code from Oracle Sales Cloud.

     

    Export values of Countries and it's Country Code from "Manage Geographies" task. If it's not feasible, provide us a workaround where we ca get this information. 

    We need this information to load into an external table to cleanse the initial customer data for data load. 

    Version:
    19B
  • Harshavardhan Konathala
    Incentive compensation: CRM SALES and IC dimensions linking...5.0
    Topic posted May 28, 2019 by Harshavardhan KonathalaBlue Ribbon: 750+ Points, tagged Activity, BI Publisher, Business Plan, Business Plan Objective, Channel Account Manager, Channel Sales Manager, Chart, Competitors, Customer, Dashboard, Data Visualization, Forecast, Infolets, Leads, MDF, Opportunity, Opportunity Management, Partner, Partner Announcements, Pipeline, Quota, Reporting and Analytics, Sales, Sales Campaign, Sales Executive, Sales Manager, Sales Representative, Shared Reports, Trends, Users in Sales Cloud Report Sharing Center public
    Title:
    Incentive compensation: CRM SALES and IC dimensions linking using common 'Resource Hierarchy'
    Summary:
    The below prototype helps in building common reporting solutions across fusion CRM and IC Pillars, current DWH model doesn't have direct reporting solution across the pillars.
    Content:

    Background & Business Case - 

    • Customers who are using both CRM SALES and IC, as of now they are unable to create the report with common dimensions and metrics from both the pillars.
    • Any customer whose sales representatives involved in SALES activities and to check their compensation details till now customers are importing the same sales representatives data into IC and creating the reports.
    • Any customer if wants to create the report using SALES and IC dimensions there is no proper linking between these pillars and end up creating a cross SA with completely improper data.
    • Hence to resolve this we have an idea on joining CRM sales resource hierarchy and IC participant hierarchy, functionally which is same but technically there is no implementation.
    • CRM resources or sales representatives are the same IC participants who are getting compensation in IC. Hence using this functional derivation we are joining the CRM resource hierarchy and IC participant hierarchy details to get the common report across both the pillars.
    • CRM sales data ends once the order details have been placed, from there IC starts with the order data and ends with payment information.
    • As of now, we don't have any direct reports which have complete sales details along with the Incentive compensation metrics.
    • With this joining, we can get a complete report with SALES dimensions and metrics followed by IC metrics.

    FA Implementation - 

    To implement this requirement we have to make a couple of table joins from FA side which was not implemented as of now.

    Customers which are importing sales data into IC and creating reports from them we have to provide a solution with FA database tables join like below:

     

    FA%20DB%20Joins.png?version=1&modificationDate=1549990664000&api=v2

    • JTF_RS_REP_MANAGERS_CF is used to fetch manager/hierarchy for resources stored in JTF_RS_RESOURCE_PROFILES in Sales. IC participants are stored in CN_SRP_PARTICIPANTS_ALL and the hierarchy is sourced from HCM table  PER_MANAGER_HRCHY_REPORTEES_DN
    • Sales resource hierarchy and participant hierarchy are not stored in a common table. There is no process to sync this data either. The only link is the hz_parties.party_id (TCA) present in both Sales and IC tables.
    • Ideally, a customer implementing both IC and Sales will import sales resources in IC as participants. So, yes, jtf_rs_resource_profiles.party_id can be looked up for matching party_id records in cn_srp_participants_all

    Data Mockups - 

    Need to consider the participant's data directly from the database, so that we can cross-compare the same when implemented in OTBI.

    SALES DATA with PARTYID as main columns followed by all the main dimensions columns BASE ID values, FOR IC data, we have participant ID for the equivalent PARTYID columns followed by all the base dimensions columns BASE ID values. Please refer to attached Mockups  

    Points to note - We have to make the join between PARTID from sales and PARTYID from IC.

    Mandatory Join, We have to join ORDER_ID from sales and TRANSACTION_ID from IC. Because functionally OREDR_ID = TRANSACTION_ID. I.E. SALES REPS who are making orders, only those are considered as TRANSACTIONS in IC. Hence we have to consider this joins for PROPER reporting data.

     

    SALES%20AND%20IC%20REPORT.PNG?version=1&modificationDate=1549991819000&api=v2

    REPORT WITH BOTH SALES AND IC ATTRIBUTES - 

     

    COMMON%20REPORT.PNG?version=1&modificationDate=1549991989000&api=v2

     

    Final Dashboard - Entire Prototype built on Oracle Data visualization Desktop Tool.

     

    Final%20Report.jpg?version=1&modificationDate=1556281441000&api=v2

     

    Note - 

    1) Credit AMOUNT calculated based on the SPLIT PCT for each transaction handled by the participant.

    2) SPLIT PCT was given if two participants involved in one single transaction.

    3) Earning AMOUNT will be 5% of the credit amount.

    4) Transactions with status "CREDITED" are only considered for credit amount calculations

    5) Similarly credits with status "Credited" are only considered for earning calculations.

     

    Please find the complete observations and current standings –

    • The entire idea of building this prototype is to provide a reporting solution which has both SALES and IC metrics.

    • The current model doesn’t support continuous reporting from sales to IC, hence to achieve this we want to integrate common dimensions shared across both the pillars i.e. joining both the pillars data using employee resource hierarchy from sales and participant hierarchy from IC. Similar to the partner dimension project.

    • By considering the above assumption we have started building the prototype by using SALES mockup (The one used for all the SALES POCS) and IC mockup(One we built completely new).

    • Sales mockup flow “Campaign-Lead-Opty-Order”, IC mockup flow “Transaction-Credit_earning-Payment”.

    • Joins established to build the prototype are SALES.PartyID = IC.PartyID and SALES.OrderID = IC.TransactionID.

     Pointes to Note:

    • Entire data model and dashboard was completed by considering above joins.

    • Current joining flow is “IC → Resource Hierarchy → SALES”, from the current FA model we were able to identify the joins to link IC facts to resource hierarchy dimensions(PFA FA tables screenshot).

    • Whereas we are encountering trouble finding the joins to resource hierarchy → sales facts. Because in the current model Order details are coming from ORDER management and SALES data ending with Opportunity data.

    • using Order_num from transactions table we can join IC data with Order management data but later from order management to SALES Oppty, we don't have proper joins to establish. 

    • There are no proper joins to get SALES Oppty data and SALES facts to build the solution at RPD level.

    Version:
    Oracle DV Version 12.2.5.0.0-20180829155113
    Image:
    Document:
    Document:
  • Yannik Pietschmann
    SQL statements for Datastores5.0
    Topic posted May 24, 2019 by Yannik Pietschmann, tagged BI Publisher, Opportunity, Reporting and Analytics in Engagement Cloud > Reporting and Analytics for Engagement Cloud public
    Title:
    SQL statements for Datastores
    Summary:
    What are the concrete SQL statements for an Datastore and what kind of joins are used for joining relevant database tables?
    Content:

    Hello,

    we are looking for the concrete SQL statements, which are used for getting the data of an datastore. Especially we need to know how multiple database tables are joined (inner/outer joins?).

    For example the datastore Opportunity (CrmAnalyticsAM.OpportunityAM.Opportunity) uses multiple tables like MOO_OPTY, MOO_REVN, HZ_PARTIES, ... This information can be found in the mapping spreadsheet R13.19A CX OTBI Subject Area Database Mapping.xlsx, which was posted by Ling Xiang (https://cloudcustomerconnect.oracle.com/posts/38c32f731c). What are the concrete SQL statements for getting the data from these tables for the datastore?

    Is there any documentation which provides this kind of information for datastores?

     

    Thanks,

    Yannik