How to Begin with Oracle BI Cloud Service


Oracle BI Cloud Service offers features for different kinds of users. Most users will develop or consume content, such as visualizations, analyses and dashboards, to help them glean important information about their business.

Before users can sign in, administrators must have configured the user population and set up any database connections that their users will require. After they sign in, users can get started with Data Visualization right away.
Analyses and dashboards are based on subject area data models. To get started with these, loaders must have loaded data in to connected databases and modelers must have modeled the data. When data is modeled, users can create analyses and dashboards that allow them to glean important information about their business

Typical Workflow for Data Visualization

Task
User
Access the service
All
Add data
Content developers
Blend data
Content developers
Select data sources
Content developers
Add data elements
Content developers
Adjust the canvas layout
Content developers
Filter content
Content developers and content consumers
Set visualization interaction properties
Content developers
Build stories
Content developers and content consumers

Typical Workflow for Analyses and Dashboards

Task
User
Access the service
All
Create analyses that show the data in views on dashboards. Share these analyses with coworkers, clients, and business partners.
Content developers
Filter the data in the analyses
Content developers
Add views to the analysis
Content developers
Add interactivity to the analysis.
Content developers
Create prompts to drive the display of data in the analyses on dashboard pages
Content developers
Build interactive dashboards for users to analyze data
Content developers
Find and explore content
Content developers and content consumers
Analyze information for insight
Content developers

Comments

Post a Comment

Popular posts from this blog

How to use lexical parameters in Data template (XML document) R12

Lexical parameters can be added in data definition using &variable name This is flexible variable string where you can execute runtime conditions based on user-inputs Example 1. Append &gc_journal_filter at the end of sql statement 2. Define beforereport function in package signature FUNCTION beforereport RETURN BOOLEAN; 3. Define all the report parameters as a package variable in package signature including lexical parameters 4. Implement beforereport function by building your runtime conditions to be added to SQL statements  FUNCTION beforereport RETURN BOOLEAN IS  BEGIN          IF p_journal_source IS NULL THEN       gc_journal_filter := ' AND jh.je_source IN (''AutoCopy'',''Manual'')';     END IF;          IF p_journal_category IS NULL THEN       gc_journal_filter := 'AND jh.je_category IN (''Other'') ';     END IF;    RETURN TRUE;  END;
Read more

Query to get FSG report details with row/column set

Below query is to fetch FSG report titles, names, and description along with will give a view to list of row sets and column sets associated with the report. -- FSG REPORTS -- SELECT fst.id_flex_structure_name , R.NAME , R.report_title , R.DESCRIPTION , R.column_set "COLUMN SET" , rw2.structure_id , rw2.DESCRIPTION "COL DESC" , R.row_set "ROW SET" , rw.DESCRIPTION "ROW DESC" , R.report_display_set "DISPLAY SET" , R.content_set "CONTENT SET" , R.row_order "ROW ORDER" , R.rounding_option "RND" , u.user_name , u.DESCRIPTION , R.creation_date FROM rg_reports_v R    , fnd_id_flex_structures_v fst    , fnd_user u    , rg_report_axis_sets_v rw    , rg_report_axis_sets_v rw2 WHERE r.structure_id = fst.id_flex_num AND R.row_set_id     = rw.axis_set_id AND r.column_set_id  = rw2.axis_set_id AND SUBSTR(fst.id_flex_structure_name,1,2) IN ('DC') AND R.created_by     = u.user_id OR
Read more

Sub Inventory Transfer API.

Image
Sub Inventory transfer is used to move materials from one sub-inventory to another within same organization. This is especially used to 1. Adjust on-hand quantities between sub-inventories 2. Transfer to another sub-inventories for specific business need like additional sales 3. Damages/expiry products can be moved to non-asset sub-inventories to discard it from inventory valuation report and so on., Key elements 1. From sub inventory 2. To sub inventory 3. Organization 4. Inventory item 5. Transact quantity 6. Transact unit of measure 7. Transaction type 8. Transaction action 9. Transact Reference 10. Transact date 11. Lot Number Open Interfaces mtl_transactions_interface - is used to populate sub inventory transfer details mtl_transaction_lots_interface - is used to populate lot details for particular sub inventory transfer Base Tables mtl_material_transactions - is used to get all type of material transactions like sub-inventory transfer, inter-org tra
Read more