administering oracle analytics for applications - oracle cloud · • ensure that your oracle...

Oracle® CloudAdministering Oracle Analytics forApplications

F15093-11May 2020

Oracle Cloud Administering Oracle Analytics for Applications,

F15093-11

Copyright © 2019, 2020, Oracle and/or its affiliates.

Primary Author: Padma Rao

Contributors: Oracle Analytics for Applications development, product management(contributor), and qualityassurance teams

This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify,license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law forinteroperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it onbehalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,any programs embedded, installed or activated on delivered hardware, and modifications of such programs)and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government endusers are "commercial computer software" or “commercial computer software documentation” pursuant to theapplicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use,reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/oradaptation of i) Oracle programs (including any operating system, integrated software, any programsembedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oraclecomputer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in thelicense contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloudservices are defined by the applicable contract for such services. No other rights are granted to the U.S.Government.

This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications thatmay create a risk of personal injury. If you use this software or hardware in dangerous applications, then youshall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure itssafe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks oftheir respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks areused under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registeredtrademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services unless otherwiseset forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not beresponsible for any loss, costs, or damages incurred due to your access to or use of third-party content,products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

Audience vi

Documentation Accessibility vi

Related Documentation vi

Conventions vii

1 Get Started with Oracle Analytics for Applications

About Oracle Analytics for Applications 1-1

Region Availability 1-2

Prerequisites for Oracle Analytics for Applications 1-2

Place and Activate the Order for Oracle Analytics for Applications 1-2

Before You Begin with Oracle Analytics for Applications 1-2

Typical Workflow to Administer Oracle Analytics for Applications 1-4

Sign In to the Oracle Cloud Infrastructure Console 1-5

Access Your Service 1-5

Add Users with Administrator Permissions 1-5

Identify the Location of Your Oracle Applications Cloud Instance 1-6

Identify the Cloud Account 1-6

2 Set Up Oracle Analytics for Applications

Typical Workflow to Set Up Oracle Analytics for Applications 2-1

Create an Oracle Analytics for Applications Instance 2-1

Verify Your Instance and Sign In 2-3

About Upgrading and Patching 2-3

Upgrade the Target Model 2-3

Check and Apply Available Patches 2-4

View Patch History 2-4

View Work Requests 2-5

Update the Data Source Connection Details 2-5

Update the Offerings 2-5

iii

Update the Administrator Password for Oracle Autonomous Data Warehouse 2-6

3 Configure Oracle Analytics for Applications Data

Typical Workflow to Configure Data 3-2

About Data Pipeline Activation Plans 3-2

About Best Practices 3-3

About Pipeline Parameters 3-3

Set Up the Pipeline Parameters 3-3

About Report Parameters 3-4

About the Reporting Configuration for Enterprise Resource Planning 3-4

About the Reporting Configuration for Human Capital Management 3-5

Set Up the Report Parameters for Enterprise Resource Planning 3-5

Set Up the Report Parameters for Human Capital Management 3-6

Create a Data Pipeline Activation Plan 3-6

Edit a Data Pipeline Activation Plan 3-7

Activate a Data Pipeline Activation Plan 3-7

Deactivate a Data Pipeline Activation Plan 3-7

Delete a Data Pipeline Activation Plan 3-8

Reload a Data Pipeline Activation Plan 3-8

Reset a Data Pipeline Activation Plan 3-9

Reset the Data Warehouse 3-9

View Load Request History 3-9

View Audit Log 3-10

About Enriching Your Data 3-10

Enrich Your Data 3-10

4 Validate Oracle Analytics for Applications Data

About Validating Your Data 4-1

Prerequisites for Data Validation 4-1

Create a Custom BI Abstract Role 4-1

Validate Your Data 4-2

5 Manage Roles, Users, and Access

About Managing Roles, Users, and Access 5-1

About Roles 5-1

Job Roles 5-1

Duty Roles 5-6

Data Roles 5-10

System Roles 5-10

iv

About Users 5-23

About Access 5-23

Create and Associate Users and Job Roles 5-23

Manage Custom Job Roles 5-25

Create Custom Job Roles 5-25

Configure Job Roles 5-25

Assign Job Roles to Users 5-26

Manage Data Security Assignments 5-27

About Data Security Assignments 5-27

Add Security Assignments to a User 5-27

Remove Data Security Assignments for a User 5-28

6 Customize Oracle Analytics for Applications

About Semantic Model Customization 6-1

Create a Customization Branch 6-2

Edit a Customization Branch 6-2

Add a Step to a Customization Branch 6-2

Extend a Dimension 6-3

Add a Fact Table 6-4

Reorganize Subject Areas 6-5

Edit or Delete a Customization Branch Step 6-6

View Details of Failed Customization Branch Steps 6-7

Merge a Customization Branch with the Main Branch 6-7

Reorder Customization Branch Steps 6-8

Create a Version of the Main Branch 6-8

Edit or Delete a Main Branch Step 6-8

Create a Version of the Main Branch 6-9

Test a Branch 6-9

Load Customization Data to the Autonomous Data Warehouse 6-10

Promote Your Customizations to the Production Environment 6-10

View Activity History 6-11

v

Preface

Learn how to get started with Oracle Analytics for Applications.

Topics

• Audience

• Documentation Accessibility

• Related Documentation

• Conventions

AudienceThis document is intended for administrators who implement, configure, and manageOracle Analytics for Applications.

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the OracleAccessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic supportthrough My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related DocumentationThese related Oracle resources provide more information.

• Oracle Cloud http://cloud.oracle.com

• Getting Started with Oracle Cloud

• Managing and Monitoring Oracle Cloud

• Using Oracle Analytics for Applications

• Getting Started with Oracle Analytics Cloud

• Visualizing Data and Building Reports in Oracle Analytics Cloud

• Preparing Data in Oracle Analytics Cloud

Preface

vi

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

http://cloud.oracle.com

ConventionsThe following text conventions are used in this document.

Convention Meaning

boldface Boldface type indicates graphical user interface elements associatedwith an action, or terms defined in text or the glossary.

italic Italic type indicates book titles, emphasis, or placeholder variables forwhich you supply particular values.

monospace Monospace type indicates commands within a paragraph, URLs, codein examples, text that appears on the screen, or text that you enter.

Preface

vii

1Get Started with Oracle Analytics forApplications

Let’s explore Oracle Analytics for Applications and what you need to know to getstarted with administration.

Topics:

• About Oracle Analytics for Applications

• Prerequisites for Oracle Analytics for Applications

• Place and Activate the Order for Oracle Analytics for Applications

• Before You Begin with Oracle Analytics for Applications

• Typical Workflow to Administer Oracle Analytics for Applications

• Sign In to the Oracle Cloud Infrastructure Console

• Access Your Service

• Add Users with Administrator Permissions

• Identify the Location of Your Oracle Applications Cloud Instance

• Identify the Cloud Account

About Oracle Analytics for ApplicationsOracle Analytics for Applications enables you to analyze your Oracle ApplicationsCloud data and generate visualizations and reports.

This service is built on top of Oracle Analytics Cloud and is powered by OracleAutonomous Data Warehouse. The service extracts and loads data from your OracleApplications Cloud into an instance of Oracle Autonomous Data Warehouse. You useOracle Analytics Cloud to create reports and dashboards for this data.

When you subscribe to this service, you get Oracle Autonomous Data Warehouse andOracle Analytics Cloud on Oracle Cloud Infrastructure Gen 2 in North America(Ashburn) and EMEA (London) along with it. This service is a SaaS-packaged contentapplication providing analytics for applications. This service consists of a data pipeline,data warehouse, semantic model, and best-practice content such as prebuilt KPIs,dashboards, and reports. Oracle manages the service starting with deploymentthrough performance turning, upgrades, and maintenance. You can customize thesemantic model to make the data that you moved into the data warehouse more usefulfor reporting.

Oracle Analytics for Applications runs on Oracle Cloud Infrastructure and is integratedwith many infrastructure services. Before you begin using Oracle Analytics forApplications, you should become familiar with Oracle Cloud Infrastructure. See Welcome to Oracle Cloud Infrastructure.

1-1

https://docs.cloud.oracle.com/iaas/Content/GSG/Concepts/baremetalintro.htm

Region AvailabilityOracle Analytics for Applications is available in the following regions currently:

Region Location Region Name Region Key

Ashburn, VA us-ashburn-1 IAD

London, United Kingdom uk-london-1 LHR

Prerequisites for Oracle Analytics for ApplicationsHere's a list of prerequisites for provisioning and using Oracle Analytics forApplications:

• You must have a cloud account with Universal Credits to provision OracleAnalytics for Applications in one of the regions where the product is available.

• Ensure that your Oracle Applications Cloud is on version 19B PB7, or 19C, orlater. Oracle Analytics for Applications supports Oracle Applications Cloud version19B PB7, 19C, and later.

Place and Activate the Order for Oracle Analytics forApplications

Contact your Oracle sales representative to place an order for Oracle Analytics forApplications.

After an order is placed, as the Cloud Account Administrator, you receive an email toactivate the service.

1. In the email, click Activate My Services.

You see the Activate My Services page.

2. On the Activate My Services page, enter a name for the cloud account and theemail for the service administrator. Select North America or EMEA as the dataregion.

Once the order is activated, you receive an email with the details of thesubscription and a temporary password to the cloud account.

3. In the email with subscription details, click the My Services URL and use thetemporary credentials shared in the email.

The My Services page directs you to reset your password.

4. Reset the temporary password.

You use this password to sign in to My Services and access the Oracle CloudInfrastructure Console.

Before You Begin with Oracle Analytics for ApplicationsOracle Analytics for Applications is available on Oracle Cloud Infrastructure.

Chapter 1Prerequisites for Oracle Analytics for Applications

1-2

When you order Oracle Analytics for Applications, you get access to included capacityfor Oracle Autonomous Data Warehouse and Oracle Analytics Cloud Subscription.

When you activate your Oracle Analytics for Applications order, you get the ServiceAdministrator role. This role gives you full administration privileges on the service, soyou can complete all aspects of Oracle Analytics for Applications setup and createother users. There’s no need to delegate this responsibility, but if you want someoneelse to set up Oracle Analytics for Applications, you can add more users and assignthem to the required roles.

Here’s some information about how Oracle Analytics for Applications uses otherservices and what you need to do if you’re setting up Oracle Analytics for Applicationsfor the first time.

Service What is it for? Do I need to do anything?

Oracle Identity Cloud Service Oracle Identity Cloud ServiceFoundation is automaticallyprovided when you subscribeto Oracle Analytics forApplications.

Create and associate usersand application roles. See Create and Associate Usersand Job Roles

Oracle Autonomous DataWarehouse

Oracle Analytics forApplications uses OracleAutonomous Data Warehouseto store the data extractedfrom the Oracle ApplicationsCloud sources.

Provide the autonomous datawarehouse details whilecreating a service instance forOracle Analytics forApplications. See Create anOracle Analytics forApplications Instance

Oracle Analytics Cloud Oracle Analytics forApplications uses OracleAnalytics Cloud to analyzedata, create visualizations,and generate reports from theOracle Applications Clouddata stored in OracleAutonomous DataWarehouse.

No

Chapter 1Before You Begin with Oracle Analytics for Applications

1-3

Typical Workflow to Administer Oracle Analytics forApplications

If you’re setting up Oracle Analytics for Applications for the first time, then follow thesetasks as a guide.

Task Description More Information

Place and activate the orderfor Oracle Analytics forApplications.

Contact your Oracle salesrepresentative to place anorder for Oracle Analytics forApplications. Your salesrepresentative places an orderfor the specific SKU, forexample, Oracle AnalyticsApplications for FusionEnterprise Resource Planningor Oracle AnalyticsApplications for Fusion HumanCapital Management. After theorder is placed, activate yourservice.

Place and Activate the Orderfor Oracle Analytics forApplications

Sign into the Oracle CloudInfrastructure Console.

After you activate the service,use the cloud accountcredentials to access yourservices.If you're the first user on theaccount and were invited byOracle Cloud, then you'reautomatically added to theAdministrators group. You caninvite other members of theorganization by adding usersin Oracle Cloud InfrastructureIdentity and AccessManagement.

If you're an existing OracleCloud Infrastructure user, thenyou must specify whichtenancy you want to use forOracle Analytics forApplications. See Identify theCloud Account.

Sign In to the Oracle CloudInfrastructure Console

Use the Oracle CloudInfrastructure Console toaccess the service pages.

When you sign in to theConsole, you'll see the homepage. Use the navigationmenu in the upper left tonavigate to the service pageswhere you create, manage,and view your cloudresources.

Access Your Service

(Optional) Add a user withadministrator permissions forthe service.

Add a user with fulladministrator permissions ofthe default administrator of theservice.

Add Users with AdministratorPermissions

Chapter 1Typical Workflow to Administer Oracle Analytics for Applications

1-4


Create an instance for OracleAnalytics for Applications.

Use the Console to create aninstance

Create an Oracle Analytics forApplications Instance

Verify the Oracle Analytics forApplications instance.

You receive an email whenyour instance is ready. Checkthat you can sign in and thatyour instance is up andrunning.

Verify Your Instance and SignIn

Create and assign users andapplication roles.

Create Oracle ApplicationsCloud users for OracleAnalytics for Applications inOracle Identity Cloud Serviceand assign groups (job roles)to them.

Create and Associate Usersand Job Roles

Configure data security. Ensure that users haveappropriate access to useOracle Analytics forApplications. Access tosubject areas and datadepends on the roles assignedto the users.

Manage Roles, Users, andAccess

Configure Oracle Analytics forApplications data.

Set up global and reportingconfigurations and create aplan to copy your OracleApplications Cloud data toyour data warehouse.

Configure Oracle Analytics forApplications Data

Sign In to the Oracle Cloud Infrastructure ConsoleAfter you activate the service, use the cloud account credentials to sign in to theOracle Cloud Infrastructure Console to access your services.

If you're the first user on the account and were invited by Oracle Cloud, then you'reautomatically added to the Administrators group. You can invite other members of theorganization by adding users in Oracle Cloud Infrastructure Identity and AccessManagement. See Signing Into the Console.

Access Your ServiceWhen you sign in to the Oracle Cloud Infrastructure Console, you'll see the homepage.

Use the navigation menu in the upper left to navigate to the service pages where youcreate, manage, and view your cloud resources. See Using the Console.

Add Users with Administrator PermissionsOptionally, if you want another user to administer the service, then provide the userwith the same permissions as the default administrator of the service.

• If you're an Oracle Cloud Infrastructure Identity and Access Managementadministrator and want to add another Oracle Cloud Infrastructure Identity and

Chapter 1Sign In to the Oracle Cloud Infrastructure Console

1-5

https://docs.cloud.oracle.com/iaas/Content/GSG/Tasks/signingin.htm

https://docs.cloud.oracle.com/iaas/Content/GSG/Concepts/console.htm

Access Management user with administrator privileges, then complete thefollowing tasks:

– Create a group and add a non-administrator user to the group. Name thegroup, for example, FAWAdmin.grp. See Managing Groups.

– Optionally, create a compartment for creating the Oracle Analytics forApplications instances as per Oracle Cloud Infrastructure Security Guidancepolicies. This limits the access of the new non-administrator user to onlyservices within the compartment that you create. Name the compartment, forexample, FAWServicesCompartment. See Managing Compartments.

– Define the policies for the non-administrator user to access the OracleAnalytics for Applications instances. Name the policy, for example,FAWAdmin.pl. In this policy, add a policy statement such as:

ALLOW GROUP FAWAdmin.grp TO MANAGE analytics-warehouse IN COMPARTMENT FAWServicesCompartment

Add another policy to grant the non-administrator user permission to create anautonomous data warehouse (ADW) in the compartment that you created, forexample, FAWServicesCompartment. Ensure that the compartment in whichyou grant the manage ADW permissions is the same as the compartment inwhich the non-administrator user has a manage permission for OracleAnalytics for Applications instances. Name the policy, for example,FAWADWAdmin.pl In this policy, add a policy statement such as:

ALLOW GROUP FAWAdmin.grp TO MANAGE autonomous-data-warehouse-family IN COMPARTMENT FAWServicesCompartment

See Managing Policies.

• If your tenancy is federated with Oracle Identity Cloud Service, then to add a userwith administrator permissions, see Managing Oracle Identity Cloud Service Usersand Groups in the Oracle Cloud Infrastructure Console.

Identify the Location of Your Oracle Applications CloudInstance

If you have multiple Oracle Applications Cloud instances, then you must specify theinstance available in the North American or EMEA location.

Identify the Cloud AccountIf you have multiple cloud accounts, then choose an account subscribed to either theus-ashburn-1 or uk-london-1 region for activating the Oracle Analytics for Applicationsorder.

Chapter 1Identify the Location of Your Oracle Applications Cloud Instance

1-6

https://docs.cloud.oracle.com/iaas/Content/Identity/Tasks/managinggroups.htm

https://docs.cloud.oracle.com/iaas/Content/Identity/Tasks/managingcompartments.htm

https://docs.cloud.oracle.com/iaas/Content/Identity/Tasks/managingpolicies.htm

https://docs.cloud.oracle.com/iaas/Content/Identity/Tasks/addingidcsusersandgroups.htm

https://docs.cloud.oracle.com/iaas/Content/Identity/Tasks/addingidcsusersandgroups.htm

2Set Up Oracle Analytics for Applications

As the cloud account administrator, create the service instance for Oracle Analytics forApplications.

Topics:

• Typical Workflow to Set Up Oracle Analytics for Applications

• Create an Oracle Analytics for Applications Instance

• About Upgrading and Patching

• Upgrade the Target Model

• Check and Apply Available Patches

• View Work Requests

• Update the Data Source Connection Details

• Update the Offerings

• Update the Administrator Password for Oracle Autonomous Data Warehouse

Typical Workflow to Set Up Oracle Analytics for ApplicationsIf you’re setting up Oracle Analytics for Applications for the first time, then follow thesetasks as a guide.


Create an Oracle Analytics forApplications instance

Create a service instance tomanage your cloud resources.

Create an Oracle Analytics forApplications Instance

Verify your instance and signin

Verify your service instancewhen you receive an emailfrom Oracle that your OracleAnalytics for Applicationsservice instance is ready.

Verify Your Instance and SignIn

Create an Oracle Analytics for Applications InstanceCreate a service instance to manage your cloud resources.

1. Sign in to the Oracle Cloud Infrastructure Console.

2. Open the navigation menu. Under Solutions and Platform, click Analytics, andthen click Analytics Apps for Fusion.

You see the service instances page.

3. On the Instances page, click Create Instance.

4. Optionally, select a compartment if you want to place the service instance in acompartment other than the default root compartment that Oracle created for you.

2-1

Note:

Ensure that you have created a compartment before you select it here.See Managing Compartments.

5. Provide a display name for the service.

This name needn't be unique and can contain alphanumeric and specialcharacters.

6. Provide a name for the instance name.

This name should be unique in your tenancy (only names of deleted services canbe reused). Also, this name can contain only alphanumeric characters withoutspaces.

7. Provide a description for the service.

The description is optional and can contain as many as 255 alphanumeric andspecial characters.

8. Select Development/Test as your first instance.

9. Select the offering corresponding to your subscription of Oracle Analytics forApplications, for example, ERP or HCM or both.

10. For the selected offering, specify either the number of users or employees youhave subscribed to.

11. In Fusion Application Connection, provide the Oracle Applications Cloud URL(not the Login URL) and credentials of the FAWService user from your OracleApplications Cloud instance.

Note:

Ensure that you have reset the password for the FAWService user inOracle Applications Cloud prior to entering the new password. See Reset Passwords.

12. Optionally, click Test Connection to check the connection to the OracleApplications Cloud instance and confirm whether the credentials are valid.

13. In Autonomous Data Warehouse Administrator Credentials, provide anadministrator password for the Oracle Autonomous Data Warehouse that'sprovisioned in your tenancy to store the transformed data.

14. The email address for notification is pre-populated from the user name. If the username isn't an email address, then provide a valid email address for notifications.

15. Optionally, add tags to your instance.

16. Click Create Instance.

Oracle sends an email to the designated email address when your service is ready.Alternatively, you can display the Activity page to check the current status. When thestatus changes from CREATING to ACTIVE, the service is ready to use.Navigate to the Details page for the new service to access the Oracle Analytics forApplications URL and associated Oracle Autonomous Data Warehouse. From here,you can also view or modify details such as the password for your Oracle Applications

Chapter 2Create an Oracle Analytics for Applications Instance

2-2

https://docs.cloud.oracle.com/iaas/Content/Identity/Tasks/managingcompartments.htm

https://docs.oracle.com/en/cloud/saas/applications-common/19c/faser/implementation-users.html#FASER2249892

Cloud instance and the administrator password for the Oracle Autonomous DataWarehouse. You can also delete the service instance that's no longer required.

Verify Your Instance and Sign InOracle sends an email to the designated email address when your Oracle Analytics forApplications service instance is ready.


2. Navigate to Solutions and Platform and click Analytics Apps for Fusion.

3. Navigate to your service instances page.

4. Navigate to the Analytics Application URL to verify that your Oracle Analytics forApplications service instance is up and running.

About Upgrading and PatchingUpgrade the target data model, when you see a message on the user interface that anupgrade is available and then check and apply the patch.

The Upgrade Target Data Model process adds new pillars, modules, data models(facts and dimension tables), KPIs, cards, and decks. The plans that have beenactivated are preserved during the upgrade. The activation plans in Saved orScheduled status are reset to Saved status. To activate these plans, you must setthem to Activated status. You can skip an upgrade for one release. However, you mustupgrade when the next patch is available.

You must upgrade the target data model first using the Pipeline Activation page. Afterthe target data model upgrade is complete, you check and apply the available patchesfrom the Instance page.

Upgrade the Target ModelYou can upgrade the target data model from a previous version to the latest version,when available. For example, upgrade from version 1.1.0.0.0 to 2.0.0.

1. Sign in to your service.

2. In Oracle Analytics for Applications, open the Application Navigation menu, clickConsole, and then click Data Pipeline.

You see the Pipeline Activation page. If a later version of your target data model isavailable, then you see the message informing you that a newer version of yourtarget model is available.

3. On the Pipeline Activation page, click Upgrade adjacent to the message.

4. On the Upgrade Target Model page, select the target model version that you wantto upgrade to and click Next.

5. In Global Parameters, modify existing or select new values if you want to and clickNext. For example, change the value for Analytics Currency from US Dollar toEuro.

6. In Report Configuration, click your service, for example, Enterprise ResourcePlanning and under it Oracle Financial Analytics, modify existing or select newvalues if you want to, and click Next. For example, change the value for Ledgers

Chapter 2About Upgrading and Patching

2-3

from ALL to FGST ledger. Select a ledger set, if your organization uses them,and Next.

7. In Summary, review the global parameters that you have set for the Pipeline targetmodel and the report configurations set for the Reporting target model, and thenclick Finish.

You see a message that the upgrade is in progress and that you can’t perform anyactions until the upgrade is complete. The time taken to complete the upgrade isbased on the amount of data to be processed.

Check and Apply Available PatchesAs the administrator, you can check and apply available patches for Oracle Analyticsfor Applications to your instances.

Typically, Oracle automatically applies patches that contain minor bug fixes. You canapply patches that contain features. Before performing pre-check or applying a patch,ensure that you have upgraded the target data model. See Upgrade the Target Model.




3. On the Instances page, click the instance for which you want to check and applythe available patches.

4. On the instance details page, under Resources, view the available patches in thePatches section.

5. For an available patch, click Actions, and then click Pre-check.

6. In the confirmation message, click Pre-check Patch to perform a pre-checkoperation on the instance. After you see the Pre-check succeeded confirmation,click Close.

7. For the same patch, click Actions, and then click Apply.

8. In the confirmation message, click OK.

View Patch HistoryView the list of patches that you and Oracle have applied to your instance.




4. On the Instances page, click the instance for which you want to view the list ofpatches that have been applied.

5. On the instance details page, under Resources, click Patch History.

You see the patches that have been applied to the instance. In the patch details,the Type column identifies whether you or Oracle applied each patch.

Chapter 2Check and Apply Available Patches

2-4

View Work RequestsView all the actions performed on your instance.




4. On the Instances page, click the instance for which you want to view the list ofactions that have been performed.

5. On the instance details page, under Resources, click Work Requests.

You see the tasks that have been performed on the instance.

Update the Data Source Connection DetailsUpdate your data source connection details such as the URL for the OracleApplications Cloud instance that you specified while creating your Oracle Analytics forApplications instance and the password for the FAWService user.

You may want to update the source URL if you want to point to another sourceenvironment for Oracle Applications Cloud. You may want to update the password forthe FAWService user when your source Oracle Applications Cloud instance has beenrefreshed from another environment, for example, due to a Production to Test refresh.You also update the password for the FAWService user if the passwords differ betweenenvironments or if the password for the FAWService user has expired.




3. On the Instances page, click the instance for which you want to update the OracleApplications Cloud password.

4. On the instance details page, click Update Fusion Connection.

5. In the Update Fusion Applications Credentials dialog, enter the new URL andpassword.

6. Click Test Connection to verify the updated connection details.

7. Click Save Changes.

Update the OfferingsYou can increase or decrease the number of users in an existing offering or add a newoffering.

For example, you can add the Human Capital Management offering to your instancethat has the Enterprise Resource Planning offering.


Chapter 2View Work Requests

2-5



3. On the Instances page, click the instance for which you want to update theofferings.

4. On the instance details page, click Update Offerings.

5. In the Offerings dialog, change the number of users for an existing offering and ifapplicable, then select the check box for a new offering and specify the number ofusers.

6. Enter Update to confirm the changes and then click Save Changes.

Update the Administrator Password for Oracle AutonomousData Warehouse

Update the ADMIN schema password for the Oracle Autonomous Data Warehouse thatis provisioned in your tenancy if the password for that ADMIN schema has changed.




3. On the Instances page, click the instance for which you want to update theadministrator password for the Oracle Autonomous Data Warehouse that isprovisioned in your tenancy.

4. On the instance details page, click the Autonomous Data Warehouse name.

5. On the Autonomous Database Details page, click Actions, and then click AdminPassword.

6. In the Admin Password dialog, provide the password, and then click Update.

Chapter 2Update the Administrator Password for Oracle Autonomous Data Warehouse

2-6

3Configure Oracle Analytics for ApplicationsData

As the cloud account administrator with the Functional Administrator or SystemAdministrator application role, you specify the data load and reporting configurationdetails, and create pipeline activation plans that determine how the source data fromOracle Applications Cloud is loaded and displayed in the data warehouse.

For example, you might specify the Initial Extract Date as January 1, 2019, specify theglobal currency as US Dollars (USD), and select the Exchange Rate to be used forconverting transactions to the global currency.

Note:

The times visible in the Console are in local time zone. However, OracleAnalytics for Applications stores the values for the Warehouse RefreshDate Time and Scheduled Date in the Coordinated Universal Time (UTC) inthe autonomous data warehouse.

Topics:

• Typical Workflow to Configure Data

• About Data Pipeline Activation Plans

• About Pipeline Parameters

• Set Up the Pipeline Parameters

• About Report Parameters

• Set Up the Report Parameters for Enterprise Resource Planning

• Set Up the Report Parameters for Human Capital Management

• Create a Data Pipeline Activation Plan

• Edit a Data Pipeline Activation Plan

• Activate a Data Pipeline Activation Plan

• Deactivate a Data Pipeline Activation Plan

• Delete a Data Pipeline Activation Plan

• Reload a Data Pipeline Activation Plan

• Reset a Data Pipeline Activation Plan

• Reset the Data Warehouse

• View Load Request History

• View Audit Log

• About Enriching Your Data

3-1

• Enrich Your Data

Typical Workflow to Configure DataFollow these tasks as a guide to configure Oracle Analytics for Applications data.


Specify the pipelineparameters

Set up the pipeline parametersfor your data model file beforerunning your data plans.

Set Up the PipelineParameters

Specify the report parameters Set up the report parametersfor your data model file beforerunning your data plans.

Set Up the Report Parametersfor Enterprise ResourcePlanning

Set Up the Report Parametersfor Human CapitalManagement

Create a data pipelineactivation plan

To start analyzing your OracleApplications Cloud data,create a plan to copy data toyour data warehouse.

Create a Data PipelineActivation Plan

Edit a data pipeline activationplan

You can change any details ofyour data pipeline activationplan prior to activating it.

Edit a Data Pipeline ActivationPlan

Activate a data pipelineactivation plan

You must activate the plan torun and load data into yourdata warehouse.

Activate a Data PipelineActivation Plan

Deactivate a data pipelineactivation plan

You can deactivate all theincremental set up and ETLplan jobs of a data pipelineactivation plan.

Deactivate a Data PipelineActivation Plan

Delete a data pipelineactivation plan

You can delete a data pipelineactivation plan prior toactivating it.

Delete a Data PipelineActivation Plan

Reload a plan for a functionalarea

Perform this action to refreshthe data for the selectedfunctional area.

Reload a Data PipelineActivation Plan

Reset a data pipelineactivation plan

You can reset an activateddata pipeline activation plan.Resetting the plan deletes alldata from your datawarehouse.

Reset a Data PipelineActivation Plan

View request history View the load request historyby functional area, load type,and status.

View Load Request History

Enrich your data Enrich your reports by usingdata sets that you create withspecific columns from variousview objects (VOs).

Enrich Your Data

About Data Pipeline Activation PlansData Pipeline Activation plans load data specific to a functional area into the datawarehouse.

Chapter 3Typical Workflow to Configure Data

3-2

These plans hold configuration parameters specific to a functional area. For example,General Ledger is a functional area under Finance.

You can't submit a data pipeline activation plan in the following situations:

• Load in progress: If an incremental load is in progress.

• An impending load: If an incremental load is scheduled to run in the next hour.

• Exceeded the number of daily refresh requests: If you've exceeded the maximumnumber of ad hoc data refresh requests for the day. In this case, you can submit arequest the following day.

About Best PracticesHere's a list of the best practices to follow before running a data pipeline activationplan.

• Define the global and reporting configurations for the functional area accurately.

• Schedule the data load to run during off-peak hours.

• Run initial full warehouse loads during weekends and incremental loads duringweeknights to ensure that users aren't impacted.

About Pipeline ParametersThe pipeline parameters apply to all functional areas.

The pipeline parameters that apply at the functional area levels are currency,exchange rate type, and initial extraction date and time to schedule the incremental jobto run.

• Analytics Currency: Currency conversions are required because your businessmight have transactions captured in multiple currencies. To create meaningfulenterprise-wide analyses, you must use a common currency. Oracle Analytics forApplications allows you to specify an analytics currency to store amounts in thedata warehouse using this common currency. The load process checks thespecified currency value and determines the corresponding exchange rate toconvert the amounts to the analytics currency. For example, if your organization isa multinational enterprise that has its headquarters in the United States, youprobably want to choose US dollars (USD) as the analytics currency.

• Exchange Rate Type: Specify an exchange rate type that you want to use whenconverting the transaction amounts to the analytics currency. For example, youmay set up Corporate as a standard exchange rate across your organization for astable currency.

Set Up the Pipeline ParametersSet up the pipeline parameters for your data model file before running your pipelineplans.

1. Sign in to your service using the following steps:

a. Sign in to the Oracle Cloud Infrastructure console.

Chapter 3About Best Practices

3-3

b. Open the Navigation menu. Under Solutions and Platform, click Analytics,and then click Analytics Apps for Fusion.You see the service instances page.

c. On the service instances page, select the compartment and the instancewhere you need to do the configuration.

d. Click the instance URL to access Oracle Analytics for Applications.


3. On the Data Pipeline page, under Global Configuration, click PipelineParameters.

You see the Pipeline Parameters page.

4. Under Global Parameters:

a. Specify the currency of the transaction data.

b. Select an exchange rate type that you want to use when converting thetransaction amounts to the global currency.

c. Indicate the initial extract date from which to load the transaction data.

5. Under Additional settings, specify the time when you want the incremental dataload to happen daily.

6. Click Save.

About Report ParametersSet up the report parameters to specify how data is presented on the KPI decks,visualizations, dashboards, and reports in Oracle Analytics for Applications.

About the Reporting Configuration for Enterprise Resource PlanningYou specify values for these parameters as you configure reporting for EnterpriseResource Planning:

• Calendar: This parameter specifies the reporting calendar used in Oracle AnalyticsCloud. All time options seen in the reporting layer are based off the calendarchosen in the configuration.

• Chart of Accounts: This parameter controls the list of ledgers used for reportingand is used in tandem with the Calendar parameter.

• Ledgers: This parameter restricts the ledgers in the reporting layer and in thesecurity setup. The list of values for this parameter are the ledgers that share thesame calendar and the chart of accounts selected in the previous two parameters.The ALL option selects all ledgers that share the calendar and the selected chartof accounts.

• Ledger Sets: This optional parameter restricts the ledger sets in the reporting layerand in the security setup. The list of values for this parameter are the ledger setsthat share the same calendar and the chart of accounts selected in the previoustwo parameters.

Chapter 3About Report Parameters

3-4

About the Reporting Configuration for Human Capital ManagementYou specify values for these parameters as you configure reporting for Human CapitalManagement:

• Worker Age Band: This parameter specifies the grouping of the ages of workersby certain ranges. For example, less than 30, 30 to 50, and greater than 50 years.KPIs and analyses related to the headcount of the workers use these age bands.For example, the percentage of workers who are aged 50 and older.

• Tenure Band: This parameter specifies the grouping of the service years ofworkers by certain ranges. For example, less than 5, 5 to 10, and greater than 10years. KPIs and analyses related to the headcount or diversity factors of theworkers use these bands. For example, you can use this parameter to answer abusiness question such as "Show me the percentage of workers in myorganization of various years of service."

• Performance Band: This parameter specifies the grouping of the performanceratings of workers by certain ranges. For example, high, medium, and low. KPIsand analyses related to the performance rating of the workers use theseperformance bands. For example, you can use this parameter to answer abusiness question such as "Who are the top performers for the current reviewperiod in my organization".

Set Up the Report Parameters for Enterprise ResourcePlanning

Specify the report parameters for your data model file.



You see the Data Pipeline page.

3. On the Data Pipeline page, under Global Configurations, click ReportParameters.

You see the Report Parameters page.

4. On the Report Parameters page, click Enterprise Resource Planning and underit Oracle Financial Analytics.

5. Select a fiscal calendar to configure the reporting calendar to be used in OracleAnalytics Cloud.

6. Select a chart of accounts to control the list of ledgers used for reporting.

7. In Ledgers, select ALL to use all the available ledgers in the reporting layer and inthe security setup.

8. Optionally, in Ledgers Sets, select the ledgers sets that you want to use in decksand data visualizations.

9. Click Save.

Chapter 3Set Up the Report Parameters for Enterprise Resource Planning

3-5

Set Up the Report Parameters for Human CapitalManagement

Specify the report parameters for your data model file.




3. On the Data Pipeline page, under Global Configuration, click ReportParameters.

You see the Report Parameters page.

4. On the Report Parameters page, click Human Capital Management and under itOracle Human Capital Management Analytics.

5. Select the worker age band to specify the age range of the workers.

6. Select the tenure band to specify the range of service years of the workers.

7. Select the performance band to specify the range of worker performance ratings.

8. Select the potential band to specify the range of potential ratings for the workers.

9. Click Save.

Create a Data Pipeline Activation PlanTo start analyzing your Oracle Applications Cloud data, create a plan to copy data toyour data warehouse.

Perform this task only after you have set up the pipeline and report parameters.




3. On the Data Pipeline page, click your service. For example, under EnterpriseResource Planning, click Oracle Financial Analytics.

4. On the service page, for example, the Oracle Financial Analytics page, clickCreate.

5. Select your application areas to transfer data to the warehouse, and then clickNext.

6. Review the parameters and click one of the options:

• Cancel: To cancel the plan.

• Save: To save the plan but not activate it.

• Activate: To display the page for scheduling when to run the plan. SelectScheduled Execution Data to specify the date and time on which to run the

Chapter 3Set Up the Report Parameters for Human Capital Management

3-6

plan. Select Run Immediately to create and run a job for the planimmediately.

Oracle Analytics for Applications extracts data only from the initial extract date that youspecify. Any data added prior to the initial extract date won’t be part of this datapipeline activation plan. You see your data pipeline activation plan listed on the DataPipeline page.

Edit a Data Pipeline Activation PlanYou can change any details of your data pipeline activation plan prior to activating it.




3. On the Data Pipeline page, click the Action menu for the data pipeline activationplan that you want to edit, and click Edit.

4. Make the changes, review the changes, and then click Save or Activate.

Activate a Data Pipeline Activation PlanYou must activate the plan to run it and load the data into your data warehouse.




3. On the Data Pipeline page, click the Action menu for the saved pipeline activationplan that you want to activate, and click Edit.

4. Review the plan details and click Activate.

You see step 4 of the Data Pipeline wizard where you can schedule when to runthe plan.

5. Select Scheduled Execution Data to specify the date and time on which to runthe plan. Select Run Immediately to create and run a job for the planimmediately. Click Finish.

Oracle Analytics for Applications runs the data pipeline activation plan, loads data intoyour data warehouse, and displays your activation plan on the Data Pipeline page.Once data is successfully loaded, the system updates the plan status to ActivationCompleted.

Deactivate a Data Pipeline Activation PlanYou can deactivate all the incremental setup and jobs of a data pipeline activationplan. Deactivating a plan ensures that future incremental jobs don't select the specificfunctional area when the plan runs.


Chapter 3Edit a Data Pipeline Activation Plan

3-7



3. On the Data Pipeline page, click the Action menu for the active pipeline activationplan that you want to deactivate, and click Deactivate.

You see your activation plan on the Data Pipeline page with Deactivated status.

Delete a Data Pipeline Activation PlanYou can delete a data pipeline activation plan prior to activating it.

Deleting a plan permanently removes it, so data refreshes of the warehouse won'toccur.




3. On the Data Pipeline page, click the Action menu for the activation plan that youwant to delete, and click Delete.

Reload a Data Pipeline Activation PlanReload an activated data pipeline activation plan to refresh the data for the selectedfunctional area.

Performing this action refreshes the data for the selected functional area. The nextscheduled run may take additional time to complete.

Note:

Executing an on-demand data refresh while working on the data may causetemporary inconsistencies.




3. On the Data Pipeline page, click the Action menu for the data pipeline activationplan whose data you want to refresh, and then click Refresh Data.

The system executes an incremental load immediately. If you had reset a pipelineactivation plan before refreshing data, then the system runs a full load immediatelyfor that functional area.

Chapter 3Delete a Data Pipeline Activation Plan

3-8

Reset a Data Pipeline Activation PlanWhen you reset a data pipeline activation plan, you delete all data from your datawarehouse and the deletion is irreversible.




3. On the Data Pipeline page, click the Action menu for the pipeline activation planthat you want to reset, and click Reset.

You see your activation plan on the Data Pipeline page with Reset Completed status.

Reset the Data WarehouseReset your data warehouse when your source Oracle Applications Cloud instance hasbeen refreshed from another environment, for example, due to a Production to Testrefresh. You may also want to reset the data warehouse when the data has becomecorrupted.



3. On the Data Pipeline page, under Global Configuration, click PipelineParameters.

You see the Pipeline Parameters page.

4. On the Pipeline Parameters page, click the Reset Data Warehouse menu option.

5. Click OK in the message dialog.

You must activate each of your data pipeline activation plans. See Activate a DataPipeline Activation Plan.

View Load Request HistoryYou can view the load request history by functional area, load type, and status alongwith other details.




3. Click Application Navigation on the top left and then click Request History.

4. On the Request History page, view the history of loads that have been performed.

Chapter 3Reset a Data Pipeline Activation Plan

3-9

Note:

The request history doesn't display the incremental loads.

View Audit LogYou can view the modifications made to entities in the Data Pipeline Activationprocess such as Ledgers, Analytics Currency, and functional areas.




3. Click Application Navigation on the top left and then click Audit Log.

4. On the Audit Log page, view the list of all the modifications.

About Enriching Your DataEnrich your reports by choosing specific columns from various view objects (VOs) fromthe Oracle Applications Cloud data sources.

You can select the columns from various VOs, create an enrichment data set, and usethat data set to create a data pipeline activation plan. This enables you to seamlesslyextract and load data from additional Oracle Applications Cloud VOs and make itreadily available in tables populated in the autonomous data warehouse. You can thenuse the data for visualization and analysis. minimize data transfer as

Enrich Your DataYou can supplement the data in your reports by using data sets that you create withspecific columns from various view objects (VOs) from Oracle Applications Cloud datasources.




3. On the Data Pipeline page, under Applications, click Data Enrichment.

4. On the Data Enrichment page, click Create.

You see the data enrichment wizard with three steps.

5. In step 1 of the wizard, select a pillar to add a data enrichment plan, and then clickNext.

6. In step 2 of the wizard, select a view object from your pillar.

7. In the Available Attributes pane, select the check box for the attributes that youwant, and then click Add Selected.

Chapter 3View Audit Log

3-10

You see the attributes that you had selected in the Target attributes pane and therecommended (defined) primary key. You can either accept this key or override itwith your own primary key definition.

8. Optionally, select Advanced to reorganize the order of columns that are markedas primary keys and specify one of your incremental keys to use when determiningthe initial extract date.

9. In step 3 of the wizard, enter a suffix for the target table name that is automaticallycreated by the data enrichment process, provide a description, and specify theoptions to save the data enrichment plan without executing it, or schedule theexecution date and time, or execute it immediately.

10. Click Finish.

You see the data enrichment plan on the Data Enrichment page with one of thesestatuses:

• Activation in Progress - You can’t edit, delete, or schedule a data enrichmentplan while activation is in progress.

• Activation Completed - You can edit the data enrichment to add or delete VOattributes and save the changes. You can’t modify the schedule in this status.

• Activation Scheduled - You can edit the data enrichment to add VO attributes,save the changes while retaining the existing schedule, reschedule theexecution date and time, or execute the plan immediately.

Chapter 3Enrich Your Data

3-11

4Validate Oracle Analytics for ApplicationsData

As the cloud account administrator with the Functional Administrator or SystemAdministrator application role, you validate the data after loading the source data fromOracle Applications Cloud in to your data warehouse.

Topics:

• About Validating Your Data

• Create a Custom BI Abstract Role

• Validate Your Data

About Validating Your DataAs an administrator, you can validate a library of metrics between your OracleAnalytics for Applications instance and the Oracle Transactional Business Intelligenceinstance. The library of metrics is part of Oracle Analytics for Applications.

Prerequisites for Data ValidationHere's a list of prerequisites for validating your data as an administrator:

• Ensure that you can access the Oracle Transactional Business Intelligenceinstance and run queries.

• Ensure that you have the same data security privileges in Oracle Analytics forApplications instance and the Oracle Transactional Business Intelligence instance.

• Create a custom BI Abstract role and associate it with the FAWService user.

Create a Custom BI Abstract RoleYou create a BI Abstract role and associate it with the FAWService user.

Use the Security Console of Oracle Applications Cloud. See Create Roles in theSecurity Console

1. Sign in to Oracle Applications Cloud with your administrator credentials.

2. Navigate to Tools and then to Security Console.

3. In the Security Console, select the Roles tab, and then click Create Role.

4. In the Create Roles wizard, on the Basic Information page, enter a role name suchas OAX Custom Data Validation Role and a role code such asOAX_CUSTOM_DATA_VALIDATION_ROLE, and select BI - Abstract Roles asrole category.

4-1

https://docs.oracle.com/en/cloud/saas/applications-common/20b/faser/role-configuration-using-the-security-console.html#FASER1636952

https://docs.oracle.com/en/cloud/saas/applications-common/20b/faser/role-configuration-using-the-security-console.html#FASER1636952

5. In the Create Roles wizard, on the Role Hierarchy page, add the BI Impersonatorrole as a member of the newly created BI Abstract role.

6. In the Create Roles wizard, on the Users page, add the FAWService user to thenewly created BI Abstract role.

7. In the Create Roles wizard, on the Summary page, verify the details, save, andthen close the wizard.

Validate Your DataValidate the data after loading the source data in to your data warehouse.


2. In Oracle Analytics for Applications, open the Application Navigation menu, clickConsole, and then click Data Validation.

You see the Data Validation page.

3. On the Data Validation page, select the subject area such as Financials - GLBalance Sheet, a metric related to the selected subject area, and the validationcontext that you want to validate.

You see the Required Parameter section. You see the Optional Parameter sectiontoo, if optional parameters are defined for the selected metric.

4. In Required Parameter, for each parameter, click the magnifying lens icon to openthe Parameter Value Selection dialog.

5. In Parameter Value Selection, select the values that are displayed, or search forvalues, or click Show More Values, and then move them to the Selected Valuesbox using the arrows.

6. Click Select to retain the selection.

7. On the Data Validation page, click Run to show the metric values in the OracleAnalytics for Applications instance and the Oracle Transactional BusinessIntelligence instance.

Chapter 4Validate Your Data

4-2

5Manage Roles, Users, and Access

As the functional administrator or security administrator, you manage users and theiraccess to subject areas and data.

Topics:

• About Managing Roles, Users, and Access

• Create and Associate Users and Job Roles

• Manage Custom Job Roles

• Manage Data Security Assignments

About Managing Roles, Users, and AccessAs an administrator, one of your initial tasks is to ensure that users have appropriateaccess to use Oracle Analytics for Applications.

Access to subject areas and data depends on the roles assigned to the users.

About RolesOracle Analytics for Applications provides four role types:

• Duty roles – Define the duties of a job as an entitlement to perform a particularaction, such as access to an AP Transactions subject area.

• Data roles – Provide access to the transactional data in the tables. Data rolesgroup the users based on the functional access they have through a particular jobrole and a particular dimension of data. For example, a group of users based oninvoices relevant only to their business unit.

• System roles – Provide a set of privileges that allows users to perform systemtasks after signing into Oracle Analytics for Applications, such as administeringsystem settings, performing functional setup, managing security, and modelingdata.

• Job roles – Inherit duty roles, data roles, and application roles that are assigned tousers. A job role defines a user business function such as Vice President of Sales,Human Resources Analyst, and Procurement Buyer. Job roles and users aresynchronized from Oracle Applications Cloud to Oracle Identity Cloud Service. Thejob roles are mapped as groups in Oracle Identity Cloud Service. You can alsocreate custom job roles based on your business requirements.

Job RolesJob roles synchronized from Oracle Applications Cloud into Oracle Identity CloudService are:

5-1

Job Role Code Job Roles Name Description Associated DataRole, Duty Role,and ApplicationRole

Functional Area

ORA_GL_FINANCIAL_ANALYST_JOB

Financial Analyst Has Authorprivileges

Author

OA4F_FIN_GL_ACCESS_SET_DATA

OA4F_FIN_GL_BALANCE_SHEET_ANALYSIS_DUTY

OA4F_FIN_GL_BUDGETS_ANALYSIS_DUTY

OA4F_FIN_GL_DETAIL_TRANSACTIONS_ANALYSIS_DUTY

OA4F_FIN_GL_PROFITABILITY_ANALYSIS_DUTY

GL

ORA_GL_GENERAL_ACCOUNTANT_JOB

GeneralAccountant

Has Authorprivileges

Author






GL

Chapter 5About Managing Roles, Users, and Access

5-2


Functional Area

ORA_GL_GENERAL_ACCOUNTING_MANAGER_JOB

GeneralAccountingManager


Author






GL

ORA_AP_ACCOUNTS_PAYABLE_MANAGER_JOB

AccountsPayable Manager


Author

OA4F_FIN_AP_AGING_ANALYSIS_DUTY

OA4F_FIN_AP_BUSINESS_UNIT_DATA

OA4F_FIN_AP_EXPENSES_ANALYSIS_DUTY

OA4F_FIN_AP_HOLDS_ANALYSIS_DUTY

OA4F_FIN_AP_INVOICES_ANALYSIS_DUTY

OA4F_FIN_AP_LIABILITIES_ANALYSIS_DUTY

OA4F_FIN_AP_PAYMENTS_ANALYSIS_DUTY

AP


5-3


Functional Area

ORA_AP_ACCOUNTS_PAYABLE_SPECIALIST_JOB

AccountsPayableSpecialist


Author








AP

ORA_AP_ACCOUNTS_PAYABLE_SUPERVISOR_JOB

AccountsPayableSupervisor


Author








AP


5-4


Functional Area

ORA_AR_ACCOUNTS_RECEIVABLE_MANAGER_JOB

AccountsReceivableManager


Author

OA4F_FIN_AR_ADJUSTMENTS_ANALYSIS_DUTY

OA4F_FIN_AR_AGING_ANALYSIS_DUTY

OA4F_FIN_AR_APPLICATIONS_ANALYSIS_DUTY

OA4F_FIN_AR_BUSINESS_UNIT_DATA

OA4F_FIN_AR_CREDITMEMO_ANALYSIS_DUTY

OA4F_FIN_AR_TRANSACTIONS_ANALYSIS_DUTY

OA4F_FIN_AR_REVENUE_ANALYSIS_DUTY

AR

ORA_AR_ACCOUNTS_RECEIVABLE_SPECIALIST_JOB

AccountsReceivableSpecialist


Author








AR


5-5


Functional Area

ORA_FND_INTEGRATION_SPECIALIST_JOB

IntegrationSpecialist

Individualresponsible forplanning,coordinating, andsupervising allactivities relatedto the integrationof enterpriseinformationsystems. Hasauthor privileges.

Author

OA4F_COMMON_DATA_ADMIN_ANALYSIS_DUTY

Common

ORA_PER_HUMAN_RESOURCE_ANALYST_JOB

Human ResourceAnalyst


OA4F_HCM_HR_ANALYST_VIEW_ALL_DATA

OA4F_HCM_WORKFORCE_CORE_ANALYSIS_DUTY

Author

Workforce

ORA_PER_LINE_MANAGER_ABSTRACT

Line Manager Has Authorprivileges

OA4F_HCM_LINE_MANAGER_DATA


Author

Workforce

Duty RolesDuty roles to secure subject areas are:

Duty Role Code Duty Role Name Duty RoleDescription

Functional Area Gets access toSubject AreaDisplay NameORAssociatedRole


General LedgerBalance SheetAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancials GLBalance Sheetsubject area.

GL Financials - GLBalance Sheet


5-6




ProfitabilityAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancials GLProfitabilitysubject area.

GL Financials - GLProfitability


General LedgerDetailTransactionsAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancials GLDetailTransactionssubject area.

GL Financials - GLDetailTransactions


General LedgerBudget AnalysisDuty

Object securityrole to controlpresentationcatalog access toFinancials GLBudgets subjectarea.

GL Financials - GLBudgets


AccountsPayable AgingAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancialsAccountsPayable Agingsubject area.

AP Financials – APAging


AccountsPayable InvoicesAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancialsAccountsPayable Invoicessubject area.

AP Financials – APInvoices


AccountsPayableLiabilitiesAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancialsAccountsPayableLiabilities subjectarea.

AP Financials – APLiabilities


5-7




AccountsPayablePaymentsAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancialsAccountsPayablePayments subjectarea.

AP Financials – APPayments


AccountsPayableExpensesAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancialsAccountsPayableExpenses subjectarea.

AP Financials - APExpenses


AccountsPayable HoldsAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancialsAccountsPayable Holdssubject area.

AP Financials - APHolds


AccountsReceivable AgingAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancialsAccountsReceivable Agingsubject area.

AR Financials – ARAging


AccountsReceivableTransactionsAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancialsAccountsReceivableTransactionssubject area.

AR Financials – ARTransactions


5-8




AccountsReceivableReceipts andApplicationsAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancialsAccountsReceivableReceipts andApplicationssubject area.

AR Financials – ARReceipts andApplications


AccountsReceivable CreditMemoApplicationsAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancialsAccountsReceivable CreditMemoApplicationssubject area.

AR Financials – ARCredit MemoApplications


AccountsReceivableAdjustmentsAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancialsAccountsReceivableAdjustmentssubject area.

AR Financials – ARAdjustments


AccountsReceivableRevenueAnalysis Duty

Object securityrole to controlpresentationcatalog access toFinancialsAccountsReceivableRevenue subjectarea.

AR Financials - ARRevenue

OA4F_COMMON_DATA_ADMIN_ANALYSIS_DUTY

Data WarehouseRefresh andUsage TrackingAnalysis Duty

Object securityrole to controlpresentationcatalog access toWarehouseRefresh subjectareas and UsageTracking subjectareas.

Common Common -Usage TrackingStatisticsCommon -WarehouseRefreshStatistics


5-9




Workforce CoreAnalysis Duty

Object securityrole to controlpresentationcatalog access toWorkforce Coresubject area.

Workforce Workforce -Core

Data RolesData roles to secure data are:

Data Role Code Data Role Name Description Functional Area


General LedgerAccess Set DataSecurity

Data security role toaccess ledger setbased data

GL


Accounts PayableBusiness Unit DataSecurity

Data security role toaccess accountspayable business unitbased data

AP


Accounts ReceivableBusiness Unit DataSecurity

Data security role toaccess accountsreceivable businessunit based data

AR

OA4F_HCM_LINE_MANAGER_DATA

Oracle Analytics forApplications HR LineManager Data Role

Human CapitalManagement DataSecurity Policy forSupervisor Hierarchy

Workforce

OA4F_HCM_HR_ANALYST_VIEW_ALL_DATA

Oracle Analytics forApplications HRAnalyst View All DataRole

Human CapitalManagement DataSecurity Policy forView All Data

Workforce

System RolesThe system roles for Oracle Analytics for Applications available in Oracle IdentityCloud Service through Oracle Analytics for Applications provisioning are:


5-10

Role Name Role Description Purpose Permissions

Administrator Tenant administratorfor service instances

Creates and managesOracle Analytics forApplications instancesand administersOracle Identity CloudService users androles.

• Creates andmanages OracleAnalytics forApplicationsinstances

• AdministersOracle IdentityCloud Serviceusers and roles

• Has no access tothe Data Pipelineuser interface

• Has no access tothe Data Securityuser interface

• Has no access tothe JobMonitoringConsole userinterface

• Has no access tothe Consolemenu

• Has no access touser and roleadministration

• Has no access todecks, cards,KPIs,visualizations,projects, andcontent


5-11


Service Administrator Oracle Analytics forApplications serviceadministrator

Customer facing(Snapshots,Connections, SystemSettings) administratoraccess to OracleAnalytics forApplications.

• Can't createsnapshots ormodify the datamodel file (RPD)

• Can access theData Pipelineuser interface

• Can access theData Securityuser interface

• Has no access tothe JobMonitoringconsole

• Can access theConsole menu

• Can access theuser and roleadministrationpages

• Can access theSemantic ModelExtensions userinterface

• Has read-onlyaccess to theready-to-useOracle AnalyticsCloud objects(visualizationprojects,dashboards, andanalyses)

• Requests fromOracle Analyticsfor Applications toOracle AnalyticsCloud are routedthrough theServiceAdministratoruser

• Can create,update, anddelete the OracleAnalytics Cloudcontent

• Has read-onlyaccess to theready-to-use KPIs

• Can create,update, anddelete KPIs

• Can create,update, and


5-12


delete decks andcards

• Can share decksand cards

• Can createOracle AnalyticsPublisher reports

• Has no access todata modeling

• Has access toOracle BIScheduler

• Has access tocreate OracleAnalytics Cloudconnections toother non-OracleApplicationssources, such asExcel files andGoogle drive

• Has access tocreate OracleAnalytics Clouddata sets


5-13


FunctionalAdministrator

Oracle Analytics forApplications functionaladministrator

Performs functionalconfiguration (pipeline,reporting) in OracleAnalytics forApplications.

• Can access theData Pipelineuser interface





• Has no access tothe SemanticModel Extensionsuser interface

• Has no access tothe ready-to-useOracle AnalyticsCloud objects(visualizationprojects,dashboards, andanalyses)

• Has no access tothe ready-to-useKPIs

• Has no access todecks, KPIs, andOracle AnalyticsCloud projects

• Can't create anyOracle AnalyticsCloudcontent andKPIs

• Can't create,update, anddelete decks andcards

• Can't share decksand cards

• Has no access toOracle AnalyticsPublisher


• Has no access toOracle BIScheduler

• Has no access tocreate OracleAnalytics Cloudconnections


5-14


• Has no access tocreate OracleAnalytics Clouddata sets


5-15


Security Administrator Oracle Analytics forApplications securityadministrator

Administers systemroles and datasecurity.

• Has no accessthe Data Pipelineuser interface

• Has access to theData Securityuser interface



• Has access touser and roleadministration


• Has no access tothe ready-to-useOracle AnalyticsCloud objects(visualizationprojects,dashboards, andanalyses)

• Has no access tothe ready-to-useKPIs

• Has no access todecks, KPIs, andOracle AnalyticsCloud projects

• Can't create anyOracle AnalyticsCloud contentand KPIs



• Has no access toOracle AnalyticsPublisher anddata modeling



• Has no access tocreate Oracle


5-16


Analytics Clouddata sets


5-17


Modeler Administrator Oracle Analytics forApplications datamodel administrator

Promote data model(RPD) customizationto the Oracle AnalyticsCloud instance.







• Can access theready-to-useOracle AnalyticsCloud objects(visualizationprojects,dashboards, andanalyses)

• Can access theready-to-use KPIs

• Can create KPIs• Can createOracle

Analytics Cloudcontent






• Can createOracle AnalyticsCloudconnections

• Can createOracle AnalyticsCloud data sets


5-18


Modeler Oracle Analytics forApplications modeler

Modify the semanticmodel to bring incustom dimensionsand attributes.







• Can access theready-to-useOracle AnalyticsCloud objects(visualizationprojects,dashboards, andanalyses)

• Can access theready-to-use KPIs

• Can createOracle AnalyticsCloud content

• Can create KPIs• Can't create,

update, anddelete decks andcards





• Can createOracle AnalyticsCloudconnections

• Can createOracle AnalyticsCloud data sets


5-19


Author Oracle Analytics forApplications author

Create and edit KPIs,cards, decks,visualization projects,reports, anddashboards.







• Has read-onlyaccess to theready-to-useOracle AnalyticsCloud objects(visualizationprojects,dashboards, andanalyses); if youneed a change,then create acopy using "SaveAs"


• Can edit thecustom OracleAnalytics Cloudobjects(visualizationprojects,dashboards, andanalyses)

• Can edit thecustom KPIs

• Can change thefilter values forexistingvisualizationprojects

• Can add filters forexistingvisualizationprojects

• Can create andedit Oracle


5-20


Analytics Cloudcontent, KPIs,decks, and cards

• Can deletecustom KPIs,decks, and cards

• Can consumeKPIs, cards, anddecks created byother users onwhich they haveaccesspermissions








5-21


Consumer Oracle Analytics forApplications consumer

Read access toOracle AnalyticsCloud content and cancreate cards anddecks.







• Has read-onlyaccess to theready-to-useOracle AnalyticsCloud objects(visualizationprojects,dashboards, andanalyses)


• Has read-onlyaccess to thecustom OracleAnalytics Cloudobjects(visualizationprojects,dashboards, andanalyses)

• Has read-onlyaccess to thecustom KPIs

• Can change thefilter values forthe existingvisualizationprojects

• Can't add filtersfor the existingvisualizationprojects

• Can't create anyOracle AnalyticsCloud content


5-22


• Can't create anyKPIs

• Can create,update, anddelete decks andcards


• Has read-onlyaccess to OracleAnalyticsPublisher





About UsersOracle Analytics for Applications uses the Oracle Applications Cloud users fromOracle Identity Cloud Service.

You also create job roles in Oracle Identity Cloud Service and then assign the job rolesto the users. See Create and Associate Users and Job Roles

About AccessYou provide access to subject areas and data by assigning job roles to users in OracleFusion Application Services. Job roles are associated with duty and data roles.

Create and Associate Users and Job RolesTo access Oracle Analytics for Applications, create Oracle Applications Cloud usersand groups (these are the equivalent of job roles in Oracle Applications Cloud) inOracle Identity Cloud Service and then assign the groups (job roles) to users.

You can either manually create users and job roles and associate them in OracleIdentity Cloud Service or synchronize new users and job roles in Oracle ApplicationsCloud with Oracle Identity Cloud Service. See Synchronize Oracle Fusion ApplicationsCloud Service User Identities and Roles with Oracle Identity Cloud Service.

Chapter 5Create and Associate Users and Job Roles

5-23

https://docs.oracle.com/en/solutions/extend-saas-with-java-cloud-service-apps/synchronize-oracle-fusion-applications-cloud-service-user-identities-and-roles-oracle-identity-cloud1.html#GUID-611F888F-8BDE-4240-BBF3-D315DBA68DEF

https://docs.oracle.com/en/solutions/extend-saas-with-java-cloud-service-apps/synchronize-oracle-fusion-applications-cloud-service-user-identities-and-roles-oracle-identity-cloud1.html#GUID-611F888F-8BDE-4240-BBF3-D315DBA68DEF

Note:

If you create job roles, job role assignments, and users or revoke existing jobroles, job role assignments, or users in Oracle Applications Cloud, then youmust also maintain these changes in Oracle Identity Cloud Service eachtime.

1. Make a list of the user and job roles in Oracle Applications Cloud who needaccess to Oracle Analytics for Applications.

Note:

You need the exact user and job role names as they are in OracleApplications Cloud. The names are case-sensitive.

2. Create Oracle Applications Cloud users in Oracle Identity Cloud Service.

a. Sign in to Oracle Identity Cloud Service with your administrator credentials.

b. Navigate to Users and click Add.

c. Enter the user details as they are in Oracle Applications Cloud and then clickFinish.

Note:

The user name is case-sensitive.

3. Create Oracle Applications Cloud groups (job roles) in Oracle Identity CloudService.

a. Navigate to Groups and click Add.

b. Enter the job role name as it is in Oracle Applications Cloud and then clickFinish.

4. Assign the group (job role) to the users.

a. On the Groups page, select a group.

b. For the group specific to the Oracle Applications Cloud job role, in the Userstab, click Assign and select the users that you want to associate with thegroup (job role).

5. As the service administrator, if you need to assign additional groups (job roles)such as service administrator, functional administrator, or security administrator tousers, then perform the following steps:

a. Sign in to Oracle Analytics for Applications, open the Application Navigationmenu, and then click Console.

b. On the Console page, click Groups Management. You see the Groups pagein Oracle Identity Cloud Service.

c. On the Groups page, create the OAX Service Administrator group, OAXFunctional Administrator group, and OAX Security Administrator group one ata time following these instructions:

Chapter 5Create and Associate Users and Job Roles

5-24

i. Click Add. You see the Add Group page.

ii. In Step 1: Group Details, enter the group name, and click Next.

iii. In Step 2: Assign Users to Group (Optional), select the check box next tothe name of each user that you want to add and then click Finish. Performthis action for each group.

d. Return to the Console page in Oracle Analytics for Applications and clickRoles Management. You see the Job Roles page.

e. On the Job Roles page, search for each group (job role) that you newlycreated, select the group (job role), and then click Add.

f. In Add Roles, search for Service Administrator - OAX Service Administrator,select the role, and click Add. Repeat this step for Functional Administrator -OAX Functional Administrator and Security Administrator - OAX SecurityAdministrator.

g. Click Back to Console and then click Apply.

The mappings that you make become available after approximately 20 minutes. Theusers that you added receive an email to activate their account. After activation, theymust sign in to Oracle Analytics for Applications and verify their access to data andobjects.

Manage Custom Job RolesService administrators create custom job roles in Oracle Applications Cloud andsynchronize them into Oracle Identity Cloud Service.

Topics:

• Create Custom Job Roles

• Configure Job Roles

• Assign Job Roles to Users

Create Custom Job RolesAs a security administrator, you can create custom job roles to meet your businessrequirements.

You create custom job roles in the Security Console of Oracle Applications Cloud. See Create Roles in the Security Console.

To use the custom job roles from Oracle Applications Cloud in Oracle Analytics forApplications, you must either manually create and associate them in Oracle IdentityCloud Service or synchronize them with Oracle Identity Cloud Service. See Create andAssociate Users and Job Roles.

Configure Job RolesAs a security administrator, you can map the data, duty, and system roles available forOracle Analytics for Applications with the job roles.


Chapter 5Manage Custom Job Roles

5-25

https://docs.oracle.com/en/cloud/saas/applications-common/19d/faser/role-configuration-using-the-security-console.html#FASER1636952

2. In Oracle Analytics for Applications, open the Application Navigation menu, clickConsole, and then click Roles Management.

You see the Job Roles page displaying all the available job roles.

3. On the Job Roles page, click a job role. For example, Accounts Payable Manager.

You see the job role details page listing the various data, duty, and system roles.

4. On the job role details page, to remove an existing data, duty, or system rolemapped to a job role, select the check box for the existing role, and then clickRemove.

5. On the job role details page, to add a data, duty, or system role, click Add.

You see the Add Roles dialog displaying available roles that haven't beenassigned to this job role.

6. Select the data, duty, or system role that you want to add to the job role and clickAdd.

You see the Job Roles page with pending alerts for changes to the job roles thatyou updated.

7. Click Discard Changes to abandon the planned changes or click Apply to confirmthe changes.

Assign Job Roles to UsersAssign job roles to users to define their business functions such as Vice President ofSales, Human Resources Analyst, and Procurement Buyer.


2. In Oracle Analytics for Applications, open the Application Navigation menu, clickConsole, and then click User Management to access the Oracle Identity CloudService console for assigning roles to users.

3. In the Oracle Identity Cloud Service console, expand the Navigation menu, andthen click Users.

4. Click the user account that you want to modify.

5. Click Groups.

Note:

Groups are equivalent to job roles. See Understand Groups.

6. Click Assign.

To search for groups to assign to the user account, in the Search field, enter all orpart of the beginning of the group names or descriptions that you want to locate,and then click Enter.

7. In Assign Groups, select the check box for each group that you want to assign tothe user account.

8. Click OK.

Chapter 5Manage Custom Job Roles

5-26

https://docs.oracle.com/en/cloud/paas/identity-cloud/uaids/understand-groups.html

Manage Data Security AssignmentsAs a security administrator, you need to map data security assignments to users toenable them to access content.

Use the Manage Data Security Assignments page to search all currently setup datasecurity assignments. You may either search on all records or narrow your search to aspecific security context, security value, or user. You can remove a securityassignment that you had set up or add new security assignments to a user.

Topics:

• About Data Security Assignments

• Add Security Assignments to a User

• Remove Data Security Assignments for a User

About Data Security AssignmentsData security assignments apply data filters to display only the data corresponding tothe security assignment values mapped to the users.

You ensure data level security with a combination of data roles and securityassignments mapped to the user. You assign a user one or more job roles. The jobroles have data roles assigned to them, and when querying data, the semantic layerapplies data filters by data roles.

For Enterprise Resource Planning, the ledger, payables business unit, and receivablesbusiness unit values are restricted by the number of ledgers selected in the reportingconfiguration user interface. For Enterprise Resource Planning, to establish thesecurity permissions, you'd need to map users to security assignments. If a userdoesn't have security assignment values mapped, then the user doesn't get to see anydata sets corresponding to the job role (and implicitly data role) assigned to them.When you add data security assignments to a user, you ensure that the user canaccess specific data within a security context, such as ledger, payables business unit,or receivables business unit. The list of values for ledger, payables business unit, andreceivables business unit are restricted by the ledgers that you selected while settingup the report parameters. See Set Up the Report Parameters for Enterprise ResourcePlanning.

For Human Capital Management, the data security is based on the line managerhierarchy defined in the Oracle Applications Cloud for user having the Line Managerrole. A user with the HR Analyst role has access to all Human Capital Managementdata and no security restrictions are applied to the Human Capital Management dataset.

Add Security Assignments to a UserThe security assignment values that you can assign to a user are based on the user’saccess to a ledger or business unit. You can assign a single user multiple securityassignment values or multiple users to a single or multiple assignment values.


Chapter 5Manage Data Security Assignments

5-27

2. In Oracle Analytics for Applications, open the Application Navigation menu, clickConsole, and then click Data Security.

3. On the Manage Data Security Assignment page, click Add Assignments.

4. In Add Security Assignments:

a. Select the security context for which you want to add data security for theuser. For example, Ledgers or a business unit.

b. From the list of security values that you see based on the security context thatyou selected, select the values that you want to add to the user and movethem to the right.

Note:

Previously added security assignments remain in place. The AddSecurity Assignment process adds only the new values.

c. From the list of users that you see, select a user or multiple users to whomyou want to assign the data security values and move them to the right.

d. Click Add Assignments.

Remove Data Security Assignments for a UserAs a security administrator, you can remove data security assignments that you hadpreviously assigned.


2. In Oracle Analytics for Applications, open the Application Navigation menu, clickConsole, and then click Data Security.

3. On the Manage Data Security Assignment page, enter a user name in User orselect a user from the drop-down list, and click Search.

You can also filter by context or security value.

4. From the search results, select the check box for the security assignments thatyou want to remove and click Remove Assignment.

Chapter 5Manage Data Security Assignments

5-28

6Customize Oracle Analytics forApplications

You can customize the semantic model and job roles.

As a modeler or modeler administrator, you can customize your semantic model.Customization enables you to make the data that you moved into the analyticswarehouse more useful for reporting. As a security administrator, you create,configure, and assign custom job roles to users. See Manage Custom Job Roles.

Topics:

• About Semantic Model Customization

• Create a Customization Branch

• Edit a Customization Branch

• Add a Step to a Customization Branch

• Edit or Delete a Customization Branch Step

• View Details of Failed Customization Branch Steps

• Merge a Customization Branch with the Main Branch

• Reorder Customization Branch Steps

• Edit or Delete a Main Branch Step

• Create a Version of the Main Branch

• Test a Branch

• Load Customization Data to the Autonomous Data Warehouse

• Promote Your Customizations to the Production Environment

• View Activity History

About Semantic Model CustomizationYou can customize the semantic model to make the data that you moved into thewarehouse more useful for reporting.

You customize your semantic model by creating a customization branch and addingcustomization steps to that branch. You use a customization branch to test yourchanges to the model. You can apply the model from the customization branch to alocal service instance for testing. When the changes are correct, you can merge thatbranch with the main branch. You can merge multiple customization branches with themain branch over time. When you have a set of changes finalized, you can version themain branch and promote that branch to the production environment.

You can customize the model by extending ready-to-use dimensions with additionalattributes from another data source, by adding a fact to an existing subject area, andby reorganizing the ready-to-use subject areas to create a new subject area.

6-1

Create a Customization BranchTo begin customizing your semantic model, create a customization branch of the mainsemantic model.

You can add customizations to a test instance only. After you have added and testedyour customizations, you can promote them to the production environment. See Promote Your Customizations to the Production Environment.


2. In Oracle Analytics for Applications, open the Application Navigation menu, clickConsole, and then click Semantic Model Extensions.

You see the Semantic Model Extensions page listing the main branch of yoursemantic model file and any existing customization branches.

3. On the Semantic Model Extensions page, click Create on the main branch, andthen click Create Branch to create a customization branch as an empty container.

4. In Create a New Branch, enter a name for your customization branch, for example,Add Cost Center.

5. Optionally, add a description and click OK.

You see the new customization branch in the Semantic Model Extensions page.You can add steps to the new customization branch container using the Add Stepbutton or the customization branch menu. See Add a Step to a CustomizationBranch

Edit a Customization BranchBefore you apply the customization branch to the main branch of your semantic model,you can edit the customization branch.




3. On the Semantic Model Extensions page, under Customization Branch, hover overa customization branch to view the Actions menu.

4. From the Actions menu, click Edit Branch, and then click Add Step.

See Add a Step to a Customization Branch.

Add a Step to a Customization BranchYou can add customization types such as "Extend a Dimension" as a step to anexisting un-applied customization branch or a new customization branch that youcreate.


Chapter 6Create a Customization Branch

6-2



3. In Semantic Model Customizations, hover on a customization branch to view theaction menu.



6. In Add step, select a customization type such as Extend a Dimension, Add aFact, Reorganize Subject Area.

You see the wizard sequence to add details for the selected customization type.

Extend a DimensionExtend ready-to-use dimensions with additional attributes from another data source.






5. In Add step, select Extend a Dimension.

You see the wizard sequence to extend a dimension.

6. Enter a name for your customization, for example, Add Cost Center Type.

7. Select a target subject area, for example, Financials GL Profitability.

8. In Folder, select a dimension that you want to extend, for example, CostCenter.

9. Select a logical table, for example, Dim – Cost Center.

You see the available attributes in the table.

10. Click Next.

11. Select a schema and table from the database.

You see the available attributes in the table.

12. Select the columns that you want to expose or use as a key for creating the join.

13. Click in the Display Name table field to enter a new name for the column or to editan existing one and then click Enter to accept or click Esc to cancel.

14. Click Add Column to create a new column in the selected dimension table.

15. In Create a new column, enter a display name, for example, Cost Type.

Chapter 6Add a Step to a Customization Branch

6-3

16. Enter an expression, for example, Case when substring(cc_name,1,10) in('FIXED','SEMI-FIXED') then 'Fixed' else 'Variable' End.

17. Click Save.

18. Click in the Source Column table field to edit the column definition.

19. Click Save.

You see the new column in the Data preview section in a highlighted color.

20. Click Next.

21. Select a join key to pair with the source column.

22. Click Next.

23. Select the subject areas that should use this customization.

Note:

The Subject Area that you initially selected is selected by default and isread-only. By default, all additional subject areas are selected. Deselectthe additional subject areas that shouldn’t use this customization.

24. Click Done.

You see the new customization step in the customization branch. You can nowapply the customization branch to the main branch or edit it to add more steps.

Add a Fact TableAdd a fact table to an existing subject area.






5. In Add step, select Add a Fact.

You see the wizard sequence to add a fact.

6. In step 1 of the wizard, enter a name for your customization, for example, AddTravel Expense and add a brief description.

7. Select a target subject area to which you want to add the fact. For example,Financials - AP Expense.

You see the details of the selected subject area.

8. Click Next.

9. In step 2 of the wizard, select the schema, and then select the source table. Forexample, FCT_CALC_Extensions.


6-4

You see the fact table for the selected source table.

10. In the details of the fact table for the selected source table, click the Select Factand Select Join Key check boxes for the source columns that you want to add toyour new fact table in the target subject area.

11. Optionally, click Create Column to add a new column to your new fact table in thetarget subject area.

12. Click Next.

13. In step 3 of the wizard, for each selected fact key column, select join type,dimension table, and dimension key column to define a join to link your new facttable to the dimensions in the selected subject area.

14. Click Next.

15. In step 4 of the wizard, select the aggregation rule for each fact column to set theaggregation behaviors.

16. Optionally, you can set the time-balanced aggregation rule for a time dimensionand hierarchy level-based aggregation rule for a dimension using these steps:

a. Under Options, click Time-Balanced Aggregation.

b. In the Time-Balanced Aggregation dialog, click Add Time Dimension, adjustthe aggregation rule, and then click OK.

c. Click Hierarchy Level-Based Aggregation, select the dimension and level.Click Add Dimension to add more dimensions. Click OK.

Use a time-balanced aggregation when the added measure mustn't be"aggregated" by default across a time dimension. Oracle Analytics for Applicationssupports non-aggregation types like "Last" or "First" in place of the "SUM"aggregation type when required. Use a level-based aggregation when theunderlying measure must always be calculated to a specific level of a pre-defineddimensional hierarchy. For example, if there is a product hierarchy with thefollowing four levels, Product Total, Product Category, Product Sub-Category, andProduct Details and you need to add a new measure called "Revenue". If this"Product Category Revenue" measure must always be aggregated to ProductCategory, then you must use the level-based aggregation and choose the rightlevel of the Product Dimension. This setting enables Oracle Analytics forApplications to always aggregate and show the value of the measure at theProduct Category level. This is useful when you need to calculate ProductRevenue as a % of Category Revenue.

17. Click Next.

18. Optionally, select additional subject areas to add the fact.

19. Click Done.

You see a message that your step is being applied to the customization branch.After it's applied, you see the new customization step in the customization branch.You can now apply the customization branch to the main branch or edit it to addmore steps.

Reorganize Subject AreasReorganize the ready-to-use subject areas to create a new subject area.



6-5





5. In Add step, select Reorganize Subject Area.

You see the wizard sequence to reorganize subject areas to create a subject area.

6. In step 1 of the wizard, enter a name for your customization.

7. From the list of subject areas in your data warehouse, select a primary subjectarea to create a new subject area, and then click Next.

8. In step 2 of the wizard, from the primary subject area, select the data elementsthat you want in your new subject area.

You see the selected data elements in the Selected Data Elements pane.

9. Optionally, you can add another subject area and then select the data elements toadd to your new subject area.

10. Click Next.

11. In step 3 of the wizard, in the new subject area that this process creates with“Custom” prefix, such as Custom – Financials – AP Balances, drag or right-clickitems to organize and rename them.

12. In step 4 of the wizard, review your new subject area with its data elements andthen click Finish.

You see a message that your step is being applied to the customization branch.After it is applied, you see the new customization step in the customization branch.You can now apply the customization branch to the main branch or edit it to addmore steps.

Edit or Delete a Customization Branch StepEdit a step to modify the details or delete it if it's no longer required.




3. On the Semantic Model Extensions page, under Customization Branch, click abranch to display the steps.

4. Hover over a step to view the Actions menu.

5. Click Edit Step and update the details.

6. Click Delete Step to remove it from the customization branch.

Chapter 6Edit or Delete a Customization Branch Step

6-6

View Details of Failed Customization Branch StepsYou can view the reasons why a customization branch step had failed and then correctthe errors.




3. On the Semantic Model Extensions page, under Customization Branch, click thebranch with the Failed icon to view the details.

4. On the Customization Branch details page, click the Failed status for a step thathas failed and view the error details.

Merge a Customization Branch with the Main BranchMerge the customization branch with the main branch to use the customization stepsas the sequence of steps.

The main branch lives in the test environment. When you edit a customization branch,the system automatically locks it to prevent another user from simultaneously editingthe same branch. As you complete each step or reorder the steps, the system unlocksthe customization branch, saves it, and notes the change in the change log tab.





4. From the Actions menu, click Merge to Main Branch, and then click Ok.

The system updates the time stamp on the main branch and you see an indicatoron the main branch that changes have been applied since the last version wassaved.

While applying a customization branch to the main branch, if the system detectsthat a new version has since been saved, then your check-in is out ofsynchronization. You see a message explaining that the system has detected aconflict while synchronizing. For example:

a. You create a customization branch based on main branch version 1.0.

b. You add steps to your branch.

c. Meanwhile, a new version of main branch saved as 1.1.

d. You attempt to check in your customization branch.

e. The system detects a conflict while synchronizing and notifies you.

Chapter 6View Details of Failed Customization Branch Steps

6-7

Reorder Customization Branch StepsYou can reorder the steps in a customization branch that has been applied or is yet tobe applied to the main branch.




3. On the Semantic Model Extensions page, under Customization Branch, click acustomization branch to display the steps.

4. Click Reorder Steps to enable Drag mode to reorder the steps.

You see the drag handles appear on each row. The branch menu and Add Stepbutton aren’t available during the reorder process.

5. Drag and drop the steps in the new order that you want.

6. Click Done Reordering.

You see a validation message and after the validation is complete, the branchmenu, Add Step, and Reorder Steps buttons are available.

7. Click Merge to Main Branch to re-apply this customization branch and update themain branch with the changes.

Create a Version of the Main BranchOnce you have a set of customizations ready for promotion and merged them with themain branch, you must version the main branch.

You later promote the version to the production environment. See Promote YourCustomizations to the Production Environment.




3. On the Semantic Model Extensions page, click Create on the main branch, andthen click Create Version.

4. In the Create a New Version dialog, enter a name of the main branch version.

5. Select a merged branch that you want to include in this version.

6. Click OK.

Edit or Delete a Main Branch StepAs a modeler administrator, you can edit and delete all steps that have been eitherapplied or have failed. With modeler permissions, you can edit and delete only failedsteps.

Chapter 6Reorder Customization Branch Steps

6-8




3. On the Semantic Model Extensions page, click the Main Branch to view thedetails.

4. Hover over a step to display the options.

5. Click Edit Step and update the details.

6. Click Delete Step to remove it from the main branch.

Create a Version of the Main BranchOnce you have a set of customizations ready for promotion and merged them with themain branch, you must version the main branch.

You later promote the version to the production environment. See Promote YourCustomizations to the Production Environment.




3. On the Semantic Model Extensions page, click Create on the main branch, andthen click Create Version.

4. In the Create a New Version dialog, enter a name of the main branch version.

5. Select a merged branch that you want to include in this version.

6. Click OK.

Test a BranchYou can test the main development branch and the customization branches to ensurethat there are no errors.




3. To test the main development branch, select the Main branch, click Actionsmenu, and then click Test Model.

You can select the main branch, or a version of the main branch, or select theoption to reset the main branch to the original state before any customizationswere merged with the main branch.

Chapter 6Create a Version of the Main Branch

6-9

4. To test a customization branch, select the customization branch, click Actionsmenu, and then click Test Branch.

Load Customization Data to the Autonomous DataWarehouse

You can load your customization data to the autonomous data warehouse provisionedwith your Oracle Analytics for Applications instance.

1. Connect to the autonomous data warehouse corresponding to your OracleAnalytics for Applications instance.

You need the autonomous data warehouse wallet and credentials of theadministrator. The credentials of the administrator are same as what you hadmentioned for the autonomous data warehouse resource while creating the OracleAnalytics for Applications instance. See Create an Oracle Analytics forApplications Instance .

2. Create a custom schema to store the customization data.

Syntax: create user <custom_schema-name> identified by <custom_schema-password>;

Example: create user example_schema identified by abcDEF123654;

3. Create one or more tables in the custom schema that you created.

Syntax: CREATE TABLE <custom_schema-name>.<custom_extent_table_name>(<parameters>));

Example: CREATE TABLE example_schema.ABC_EXTN ("DATE" DATE, "CATEGORY"VARCHAR2(1024 BYTE) , "MANAGER" VARCHAR2(1024 BYTE) );

4. Populate the required data and grant select permissions to OAX$OAC.

Syntax: grant select on <custom_schema-name> to OAX$OAC;

Example: grant select on example_schema.ABC_EXTN to OAX$OAC;

5. Commit the changes to the autonomous data warehouse and disconnect.

Promote Your Customizations to the ProductionEnvironment

Once you have a set of changes to the semantic model, customized job roles, andcustomized KPIs ready for promotion, you can version the main branch, and thenpromote the version to the production environment. You can also reset the lastpromoted main branch with the original main branch before any customizations weremerged with it.


2. In Oracle Analytics for Applications, open the Application Navigation menu, clickConsole, and then click Promote Objects.

You see the Promote Objects page.

Chapter 6Load Customization Data to the Autonomous Data Warehouse

6-10

3. On the Promote Objects page, select the target environment to which you want topublish your customizations.

4. Select the customized objects that you want to promote to the target environment.

For example:

• Select the Semantic Model Extensions check box and the saved version ofthe main branch or the original main branch.

• Select the Security Customizations check box to promote the customizedjob roles.

• Select the KPIs check box, click Choose KPIs, search for and select thecustomized KPIs that you want to promote, and then click OK.

5. On the Promote Objects page, click Promote.

6. Click Check Status to view the progress.

View Activity HistoryView an audit of all activities performed on the semantic model.




3. Click Activity History to view an audit of all activities performed on the semanticmodel.

4. Hover over an activity to view details of the activity.

Chapter 6View Activity History

6-11

administering oracle analytics for applications - oracle cloud · • ensure that your oracle...

Documents