Oracle Application's Blog: REPORTS

Oracle Fusion BIP AND OTBI Report Security Concept

Hi Friends, In this post , we will discuss about BIP and OTBI reports security concept. How we can implement security in these reports so that we can control the access of these reports and their data to Business users in Oracle Fusion.

Subject Area :-

In Fusion , Our BIP and OTBI reports creates in the Standard Subject area folder given by Oracle fusion. In OTBI , we can also use the Standard Subject areas to create our Analysis reports. But how we can control the access of these subject areas in Fusion, like which subject area user can access and which cannot.

Subject areas are functionally secured using duty roles. The names of duty roles that grant access to subject areas include the words Transaction Analysis Duty. so by that way we can control which the access of subject area in fusion BIP and OTBI reports.

BIP and OTBI Report Security:- When you creates OTBI and BIP report you can also set permission to these report by right click on these reports. You can control the access of these reports by setting permission like which Role or Which user can access these reports.

If you have not set permission then reports are secured based on the folders in which they're stored.

You can set permissions to Reports:

Read, Execute, Write, or Delete

Change Permissions

Set Ownership

Run Publisher Report

Schedule Publisher Report

View Publisher Output

Complete Tax Setups in Oracle Fusion

Reporting Data Duty Roles

The data that's returned in Oracle Fusion Transactional Business Intelligence (OTBI) reports can also be secured by Data Duty Roles.

Each of the Transaction Analysis Duty roles that grants access to subject areas and Business Intelligence Catalog (BI Catalog) folders inherits one or more Reporting Data Duty roles. These duty roles grant access to the data.

if you found this post helpful and you liked it then follow this blog to get notifications for the upcoming posts.

BI Roles For BIP and OTBI reports

BI roles uses for both BIP and OTBI reports. They grant access to Business Intelligence functionality, such as the ability to run or author reports

BI Consumer Role	Runs Business Intelligence reports.
BI Author Role	Creates and edits reports.
BI Administrator Role	Performs administrative tasks such as creating and editing dashboards and modifying security permissions for reports, folders, and so on.
BI Publisher Data Model Developer Role	Creates and edits Oracle Business Intelligence Publisher data models.

If you Want to Learn Oracle Fusion , Please Follow the Oracle Fusion Tutorial

Before and After Report trigger in Fusion BIP Reports.

Hi Friends, In this post I will explain you the Fusion BIP report triggers, How we can use these trigger in Fusion.

We all knows that in Oracle Report 10g , we use Report triggers to create dynamic where condition in our reports. We create bind variables in the report and set where conditions to these bind variables based on the input parameter values and then reference this variable in report query. This is really an very important feature.

But in Fusion BIP reports , Oracle has only given two report triggers that is :

2 Types of Report Triggers in Fusion BIP Reports

before Data
After Data

To implement this , first we will create a parameter p_where_clause to create dynamic where condition

Now we will create a before data Trigger. For that we need to create a DB Package first. All the parameters defined in the report must be defined In the package specification as global variable.

Complete Tax Setups in Oracle Fusion

The Logic I am going to use is , If P_VENDOR_NAME paramters is null then where condition will set like P_WHERE_CLAUSE= 'AND 1=1'

CREATE OR REPLACE PACKAGE XX_FUSION_REPORT_TRIGGER
IS

P_VENDOR_NAME VARCHAR2 (100);
P_WHERE_CLAUSE VARCHAR2 (1000);

FUNCTION before_data
RETURN BOOLEAN;
END XX_FUSION_REPORT_TRIGGER;

CREATE OR REPLACE PACKAGE BODY XX_FUSION_REPORT_TRIGGER
IS
FUNCTION before_data
RETURN BOOLEAN
AS
BEGIN
IF (P_VENDOR_NAME IS NULL)
THEN
p_where_clause := ' AND 1=1';
ELSIF P_VENDOR_NAME IS NOT NULL
THEN
p_where_clause := ' AND upper(a2.vendor_name) like ''%'||UPPER(:P_VENDOR_NAME)||'%'' ';
ELSE
p_where_clause := NULL;
END IF;
RETURN TRUE;
EXCEPTION
WHEN OTHERS
HEN
RETURN FALSE;
END;
END XX_FUSION_REPORT_TRIGGER;

if you found this post helpful and you liked it then follow this blog to get notifications for the upcoming posts.

Before Report Trigger.

Use the package name in the Oracle DB Default Package.

Move the Package name with procedure from Available function to Event Trigger as below.