Narrative Reporting
Narrative Reporting
Narrative Reporting
E94194-34
Oracle Cloud Administering Narrative Reporting,
E94194-34
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license 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 for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you 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 on
behalf 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 end
users are "commercial computer software" or "commercial computer software documentation" pursuant to the
applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use,
reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or
adaptation of i) Oracle programs (including any operating system, integrated software, any programs
embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle
computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the
license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud
services 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 that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used 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 registered
trademark 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 expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise
set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be
responsible 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
Documentation Accessibility
Documentation Feedback
3 Overview of an Application
Learning About an Narrative Reporting Application 3-1
What is an Narrative Reporting Application? 3-2
iii
Working with Data 3-3
Reasons to Create an Application 3-4
Using the Sample or Custom Application 3-4
Creating Your Custom Application 3-5
Artifact Locking 3-5
Dimension Basics 3-6
Security 3-7
iv
Using the Formatting Tab 7-4
Using the Library Tab 7-6
Resetting Preferences 7-6
Previewing a Report POV 7-7
9 Installing Samples
11 Granting Access
Granting Access to Report Packages 11-4
Granting Access to Folders and Third-party Documents 11-7
Granting Access to an Application 11-9
Granting Access to Dimensions 11-12
13 Performing an Audit
Creating a System Audit 13-2
Creating an Artifact or Folder Audit 13-6
v
14 Migrating Artifacts
Migrating Artifacts from One Environment to Another Environment 14-1
Exporting and Downloading Artifacts Using the Library 14-2
Importing Artifacts into the New Environment Using the Library 14-2
Migrating Artifacts within the Same Environment 14-3
vi
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility
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 support through 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.
vii
Documentation Feedback
Documentation Feedback
To provide feedback on this documentation, click the feedback button at the bottom of
the page in any Oracle Help Center topic. You can also send email to
[email protected].
viii
1
Overview of Narrative Reporting
Related Topics
• Icons
Icons are used to define areas on the Home Page.
• Settings and Actions Menu
This menu has options to select from, based on you role.
• User Assistance
This menu is used for help on Narrative Reporting, a place to connect with other
members, the support site, and to provide feedback.
• Accessibility Settings
Use this for accessibility.
• Welcome Panel
Quickly displays your status, create, open, or take a tour.
• Conventions Used
These are the most popular icons used in Narrative Reporting.
• Roles and Permission-Based Access
Based on your roles provisioned, you have access to certain roles.
• Which Tasks Should I Do First?
Explains, to an administrator, what tasks to do.
• How Do I Get Additional Help
This explains how to obtain user assistance.
• Configuring SPF Record for Oracle Cloud Email Verification
Oracle publishes Sender Protection Framework (SPF) policy that identifies the Oracle
server IP addresses and subnets that are permitted to send cloud services emails.
• Using Translations
This tells you the languages translated for Narrative Reporting.
Icons
Icons are used to define areas on the Home Page.
There are up to thirteen main icons accessible from the Home Page for a System
Administrator.
1-1
Chapter 1
Icons
Note:
The above image is captured using the Redwood theme. Click Tools, and
then select Appearance. Explore the default Redwood theme.
Tasks
Displays tasks to perform such as reviewing a doclet or signing off on report
packages.
Messages
Displays notifications about actions you need to take or others took; for example,
confirmation that an export file was created.
Report Packages
Displays the list of report packages that you can access.
Books
Displays the list of books that you can access.
Reports
Opens Reports.
Notes
Opens the Note Manager.
1-2
Chapter 1
Icons
Bursting
The ability to run a report or book for more than one member of a single dimension for one
data source, generating a PDF output for each member.
Library
The central repository for report packages, folders, and artifacts such as audit files as well as
an application.
Application
Used to create a sample or custom application that stores data in the Oracle Cloud for
Narrative Reporting.
Tools
The Tools card links to the following tasks in Narrative Reporting: Access Control,
Appearance, Clone Environment, Connections, Daily Maintenance, and User
Preferences.
Access Control
Used by administrators to can create and manage group, where as in Narrative Reporting,
an Application Administrator can create and maintain all artifacts, such as applications,
models, dimensions, and data grants.
Appearance
Used by administrators to set default display options for all users. For example, a company
logo and background logo for the Home page.
Clone Environment
Used by administrators to perform a Clone Snapshot on a specific target instance.
Connections
Used by administrators to create and manage remote connections directly from the Narrative
Reporting Cloud page.
Daily Maintenance
Used by administrators to set the daily maintenance time and perform backup and restore
actions.
User Preferences
Used by administrators to upload a photo, set your language and time zone, set notification
email addresses, and customize other display items.
Academy
Displays links to videos and to the Cloud Help Center on using Narrative Reporting.
1-3
Chapter 1
Settings and Actions Menu
Use the Home icon in the upper right area of the Home page to return to the Home
Page.
Select the caret beside your user name to display the Settings and Actions menu.
1-4
Chapter 1
Settings and Actions Menu
Preferences
Upload a photo, set your language and time zone, set notification email addresses, and
customize other display items. See Managing User Preferences.
Downloads
Depending on your assigned roles, allows you to install the following client software:
• Sample Content – Selecting the Get Sample Content displays an information message
that upload samples has completed and the Samples folder has been created at the
Library root folder. See Install Samples.
• Oracle Smart View for Office – Download the latest version of Smart View from the
Oracle Smart View for Office software download page. See Setting Up Narrative
Reporting in Smart View .
• Smart View Extension for Narrative Reporting. Allows users to perform assigned tasks
and analyze model data from within the Microsoft Office suite.
• Smart View Extension for Disclosure Management. Allows users to perform Disclosure
Management activities, including tagging, validation and instance generation from within
Microsoft Word.
• Smart View Extension for Disclosure Management Auto Tagging. Provides the ability to
perform high volume XBRL for auto tagging as part of Disclosure Management from
within Microsoft Excel.
Help
Access videos and other task-related topics in the Oracle Cloud Help Center.
Provide Feedback
A diagnostic utility called Provide Feedback is available within your Enterprise Performance
Management cloud service. If you encounter an issue while using the service, use the
Provide Feedback utility to describe the issue and the steps to reproduce it. See Helping
Oracle Collect Diagnostic Information Using the Provide Feedback Utility.
Oracle Support
My Oracle Support site.
1-5
Chapter 1
User Assistance
About
Contains Narrative Reporting notices and version information.
Sign Out
Exits Narrative Reporting.
User Assistance
This menu is used for help on Narrative Reporting, a place to connect with other
members, the support site, and to provide feedback.
A User Assistance icon is available on certain screens. Click the icon to display
the available options.
Help
This option displays help for Narrative Reporting.
1-6
Chapter 1
User Assistance
Oracle Support
Select this option to navigate directly to the My Oracle Support site to search for solutions,
download patches and updates and create a service request.
Provide Feedback
Note:
Only in User Assistance Menu.
If you encounter an issue while using the service, use the Provide Feedback option to
describe the issue and the steps to reproduce it. To expedite the resolution of issues that you
find in the service, Oracle recommends that you add multiple screenshots to your feedback
submissions. Adding a succession of screenshots that show your progress through a task
enables you to create a storyboard that shows Oracle how to recreate your issue.
Each time a user submits feedback to Oracle, a feedback notification, a subset of the
information that a user submits using the Provide Feedback function, is sent to Service
Administrators and to the user who submits the feedback. These notifications enable Service
Administrators to review submitted issues and suggest corrective actions. Feedback
notification is enabled by default. Each Service Administrator can turn off the notification by
clicking the Unsubscribe link embedded in the email. See Disabling Feedback Notification.
Regardless of the subscription status, a notification is always sent to the user who submits
the feedback. Before providing feedback, ensure that you are at the stage in the process
when the problem was observed.
1-7
Chapter 1
Accessibility Settings
Note:
Using this option to provide feedback sends your submission to Oracle but
does not create a service request. If a Service Administrator cannot resolve
the issue, then you can create a service request using the information that
you submit.
1. From any page, select Send Diagnostics To Oracle.
2. In Feedback, describe the issue that you encountered.
3. Optional: Select an option to highlight or darken areas of the screen in
the next two steps:
a. Select Highlight, and then click and drag on the screen to highlight
portions of the screen, for example, to highlight errors or issues.
b. Select Darken, and then click and drag on the screen to hide
portions of the screen. Use this option to hide sensitive data in the
screenshot.
Accessibility Settings
Use this for accessibility.
To access accessibility settings, click the Accessibility icon at the upper right of
the Home page.
1-8
Chapter 1
Welcome Panel
• Screen Reader Mode – Enables a screen reader to read the text on the screen.
• High contrast – Sharpens screen contrast.
Note: To increase the font size, use your browser settings.
Welcome Panel
Quickly displays your status, create, open, or take a tour.
The Welcome Panel gives you access to key areas while you use Narrative Reporting and
helps you see your pending workload at a glance. Click the arrow to access each option.
1-9
Chapter 1
Welcome Panel
Upload Photo
Select the picture to upload a photo of yourself.
Incomplete Tasks
Shows the number of assigned tasks that have not been completed yet.
New Messages
Displays the number of unread messages.
Flagged Messages
Displays the number of flagged messages.
1-10
Chapter 1
Welcome Panel
Create
Depending on your permissions, lets you create a report, book, report package or system
audit file.
Open
Opens the recently used list.
Tour
Takes you to the Oracle Cloud Help Center to access videos and documentation.
Messages
When you select Messages from either the Welcome Panel or the Messages icon, you will
see items such as confirmation of an action or a notification that you’re assigned a task. Click
the blue text to perform the action that you need to take.
Tasks
You can access your incomplete tasks from the Welcome Panel or all of your tasks (current,
future, completed) from the Tasks icon. Click either the icon or the blue text link to access
additional task details.
1-11
Chapter 1
Conventions Used
Conventions Used
These are the most popular icons used in Narrative Reporting.
Conventions used in Narrative Reporting:
In addition, a person indicates that you can get help from either the Oracle Cloud
Help Center, Oracle Support site, or Provide Feedback. You can also access Oracle
Customer Cloud Connect, a community gathering place for members to interact and
collaborate on common goals and objectives, from this icon.
All Narrative Reporting icons have tooltips. Hover your cursor over tooltips for
information about icons.
1-12
Chapter 1
Which Tasks Should I Do First?
Secured access to Narrative Reporting is established by the roles that you have been
provisioned within Oracle Cloud User Management Console, and access permissions that
have been granted to you from within the service. Because the functionality is restricted to
only the users who can perform a task, security is enforced. For example, look at the Home
Page. A service administrator has access to all the functionality available within the service,
but a reviewer only sees some of these tasks. If your roles and access grants are more
restrictive, then you will only see a subset of the functionality.
All Users
• Learn about Narrative Reporting in Learn about Narrative Reporting .
• See which tasks you should start with in Which Tasks Should I Do First?
• Find out about browser requirements as well as other requirements in Prerequisites.
• Find out how to access an instance of Narrative Reporting in Accessing EPM Cloud.
• Upload your photo, check the language and time zone, and set any other preferences
listed in Managing User Preferences.
Administrators
• Learn about Narrative Reporting in Learn about Narrative Reporting .
• See which tasks you should start with in Which Tasks Should I Do First?
• Get familiar with these additional features by watching these videos: Learn about
working with applications, models, and dimensions and Learn about Security.
1-13
Chapter 1
How Do I Get Additional Help
Note:
Depending on your browser, the screenshots and procedures shown may
look slightly different from what you see on screen. For example, a browse
button may be presented as "choose file" in Chrome.
Using Translations
This tells you the languages translated for Narrative Reporting.
The following items are translated for Narrative Reporting:
• The User Interface (UI) is translated into Arabic, Danish, German, Spanish,
Finnish, French, Italian, Japanese, Korean, Dutch, Norwegian, Polish, Portuguese
(Brazilian), Russian, Swedish, Turkish, Simplified Chinese, Traditional Chinese,
and Canadian French.
1-14
Chapter 1
Using Translations
Note:
Tutorial video closed captions are not translated.
The online Help and guides are translated into French, German, Italian, Spanish,
Brazilian Portuguese, Japanese, Korean, Traditional Chinese, and Simplified Chinese.
Additionally, theOracle Smart View for Office User's online Help and guide is translated to
Dutch. See the Oracle Cloud Help Center Translated Books tab at Oracle Cloud Help
Center.
Note:
The Sample Application and the contents are in English only.
The translated documentation covers all features up to August 28, 2017, except
for Working with Smart View for Enterprise Performance Management Cloud
which covers features up to August 7, 2017.
1-15
2
Overview of Report Packages
Related Topics
• Learning About Report Packages
Report packages provide a secure, collaborative, and process driven approach for
defining, authoring, reviewing and publishing financial, management and regulatory
reports.
• Why Use a Report Package?
Report packages enables you manage the lifecycle of your deliverable, such as:
Gathering information, reviewing it for accuracy, and Presenting it are key to business.
• What is a Report Package?
With report packages, you can structure the content of your report, assign responsibilities
to content creators and reviewers, and manage their collaboration and workflow to
produce a unified document.
• Report Package Components
A report package is made up of several components:
2-1
Chapter 2
What is a Report Package?
statutory, regulatory, filing, or annual reports. For any report, gathering information,
reviewing it for accuracy, and presenting it are key to businesses.
Creating reports is easy with one author and no review, but having multiple authors
working on a report can be more complicated. Do all of the authors have the current
version? How do you merge changes from multiple authors into a single document?
As you add content creators, keeping everyone organized becomes more challenging.
The situation becomes even more difficult with several authors, multiple reviewers—
each of whom might be responsible for different sections, and multiple signers who
provides final sign off on the whole report. How do you keep all of your authors,
approvers, reviewers, and signers organized? How do you handle versioning and
manage workflow? Coordinating stakeholders by email can be daunting.
A better way to organize and produce a collaborative report is by using a report
package.
Report packages help you manage the lifecycle of your deliverables. With them, you
can:
• Assign content to multiple authors, who each contribute individual pieces of the
report
• Gather comments from multiple reviewers
2-2
Chapter 2
Report Package Components
- Complete this Learning Path for a hands-on Narrative Reporting Basics: Report
Packages and Doclets.
Doclets
A core feature of report packages is the ability to break down a report into subcomponents
called doclets. What makes up a doclet varies, depending on the type of report that you are
creating. For example, a sales report might have separate doclets for each geographical
region, and a financial disclosure might have doclets for each of the various financial
statements, tax statements, and notes.
Alternatively, if one person is responsible for all of the income statement information in a
report, for example, those income statement documents can be all classified as a single
doclet. How you define a doclet is completely up to you. See "Identifying Doclets" in Report
Package Design Considerations.
2-3
Chapter 2
Report Package Components
After you identify the doclets in a report, you assign them to authors, who provide
content. For example, in a report that breaks down revenue by categories, you can
have doclets for services, hardware, and software licenses. Then, you could assign
each doclet to the management team in charge of that category.
Supplemental Doclets
Supplemental documents such as procedures, instructions, reference material, and so
on, can be uploaded into a report package as a supplemental doclet. Supplemental
documents can be any type of document file (for example, PDF, Excel, Word, and so
on). As the content for supplemental doclets is not included within the merged report,
these doclets are excluded from the review and sign off processes. The supplemental
doclet contents cannot be viewed online, but users can download and use native
programs to open the supplemental doclet in the same way that you can work with
third party artifacts in the library.
Reference Doclets
A Reference doclet can be used as a container to store contents such as named
ranges from an Excel file or charts and graphs created from Reports, see Adding a
Management Report to a Reference Doclet and consumed by one or more regular
doclets (non-supplemental).
The file content for Reference doclets is not directly included in any report package
outputs, such as preview, publish, review instances or signoff instances. However,
embedded content within a consuming doclet is displayed as part of the report
package outputs - even though the actual reference doclet is not directly merged in the
outputs. Reference doclets can participate in the author phase, but not in the review or
signoff phases.
Sections
Sections enable you to group doclets for organization, or to keep doclets together that
have a common format or are intended for a common viewership. For example, you
can group all financial statements in a financial disclosure report into one section.
2-4
Chapter 2
Report Package Components
Doing so provides a filtered view of only those doclets to the reviewers assigned to that
section.
Development Phases
Report package development occurs in three phases:
• Author phase—Compile the various report content and supporting details together into a
cohesive report package.
• Review phase—Gather commentary on multiple draft versions and revise the report
content accordingly.
• Sign Off phase—Gather electronic signatures from key constituents and secure report
contents to prevent modifications.
You decide which development phases your report requires. If the report content is going to
be provided primarily by one or two people, then you may not need an author phase. If your
report is being developed for a small group of internal stakeholders and not a public
audience, then you may not need a review phase. You can tailor the development phases to
the type of report that you need. See "Determining Development Phases" in Report Package
Design Considerations.
Lets’s look at these development phases in a little more detail.
Author Phase
2-5
Chapter 2
Report Package Components
In the author phase, authors and approvers work with doclets to add content to a
report package. Authors provide content, and approvers review and edit the content.
Benefits of the author phase include:
Content Management
Content management allows users to check doclets in and out of a central repository,
ensuring that only one user at a time is updating a doclet. It also provides for version
control. When a user checks in an updated version of a doclet, the previous version is
automatically stored. Previous versions can be easily accessed for comparison. Users
can store versions that they're still working on and can check versions in when they're
ready for others to access them.
Note:
Doclet versioning has been optimized to minimize the impact of multiple
automated check-ins. When multiple automated check-ins are performed on
the doclet due to variable or embedded content changes, the system will
update the doclet contents but will not generate a new version.
Flexible Workflow
Workflow enables doclet content to be developed collaboratively. An author can
update the doclet, and an approver can review and edit the content. You can set up
multiple levels of approvals, and the number of approval levels can vary per doclet.
For example, a doclet containing an introductory statement may not require an
approval, and a doclet containing revenue information may require multiple approval
levels.
Using workflow, users scheduled for later in the review process can take control of a
doclet sooner. For example, if a doclet is assigned to an author, an approver or the
owner of the report package can take action on the doclet without waiting for the doclet
author. This flexibility eliminates bottlenecks and speeds up content development.
2-6
Chapter 2
Report Package Components
Process Reporting
Process reporting enables you to view the author phase status on two levels:
• Summary level—Provides statuses for the entire author phase, such as the overall
completion percentage of the author phase, a summary of the status of all the doclets,
and the due date and time remaining for the author phase.
• Doclet level—Provides the status for each individual doclet, the current responsibility,
and whether the doclet is checked in or out. You can also tell at a glance the workflow
level of the doclets, including the user assignments and the due dates by user.
Review Phase
In the review phase, reviewers provide feedback, ask questions, and recommend changes.
Benefits of the review phase include:
Threaded Commentary
Reviewers provide feedback by commenting on different areas of the report. These
comments are threaded so other reviewers can participate in the discussion. Reviewers can
provide attachments or links to their comments to provide supporting details. Reviewers can
close comments after the outstanding issue is addressed.
2-7
Chapter 2
Report Package Components
Note:
Comments persist across review cycles in context, so that reviewers can see
how comments are addressed in subsequent drafts.
Multiple Platforms
You can comment on reports in these ways:
• Desktop or mobile web browser
• Microsoft Office, through Oracle Smart View for Office
Process Reporting
Process reporting enables the report package owner to view the review phase status
on two levels:
• Summary level—Provides statuses for the entire review phase, such as the
overall completion percentage of the review phase, the number and percentage of
reviews completed, the number of open comments, and the due date and time
remaining for the review phase.
• Doclet level—Provides review status for each doclet, such as the reviews
completed per doclet and the number of open and closed comments raised for
each doclet.
The Sign Off phase enables you to finalize your report content and get sign off from
your key stakeholders.
Benefits of the sign off phase include:
2-8
Chapter 2
Report Package Components
Locked Content
In the sign off phase, you lock your report to prevent changes. The report signers review the
final report and either sign off or reject the report content. If the report is rejected, the report
package owner can unlock and correct the report content. If the report is signed off, the
process is complete, and the report is ready for publication.
Multiple Platforms
You can provide sign off in these ways:
• Desktop or mobile web browser
• Microsoft Office, through Oracle Smart View for Office
Process Reporting
Report package owners can view a summary of the sign off phase. The summary can include
completion percentage, number of sign offs and rejections, due date, and days remaining, as
well as who signed off and any sign off notes.
2-9
3
Overview of an Application
Related Topics
• Learning About an Narrative Reporting Application
An application is a storage container for data.
• What is an Narrative Reporting Application?
An application is a storage container for data that you want to centrally store in the Cloud.
• Working with Data
To work with data in the Cloud, you need to set up an application, model, and dimensions
and then load your data.
• Reasons to Create an Application
There are two main reasons to create an application.
• Using the Sample or Custom Application
You can have only one application per environment (for example, one in Test and one in
Production) and have a choice between creating a sample or custom application.
• Creating Your Custom Application
Before creating your custom application, determine what type of application you need to
create by knowing what data you need to work with, where that data resides now, what
dimensions you need to include, and the formatting necessary for load.
• Artifact Locking
To prevent concurrent editing of application and model artifacts, simultaneous operations
on the same artifact are not permitted.
• Dimension Basics
Here’s some basic information about dimensions and dimension types:
• Security
There are different levels of security in an application. Security on the data level is
achieved through data grants that provide access to individual or the combinations/
intersections of dimensions.
3-1
Chapter 3
What is an Narrative Reporting Application?
Note:
The Narrative Reporting application will no longer be available to Oracle
Enterprise Performance Management Cloud Narrative Reporting customers
under the Standard and Enterprise licensing. (starting in June 2019). Legacy
customers, pre-June 2019 licensing of Narrative Reporting (previously known
as Enterprise Performance Reporting Cloud) will still have access to the
application.
This is due to EPM Cloud introducing Free Form Applications, which provide
dimensional models without dimension type restrictions as well as fast performance
and support for large dimensions. Free Form Applications provide significantly more
robust functionality than the legacy Narrative Reporting application and models,
including read or write member formula, and procedural logic capabilities. Because of
these new powerful capabilities, the Narrative Reporting application will no longer be
available to new EPM Cloud Narrative Reporting customers. Free Form Applications
with its enhanced functionality can be used for custom cubes.
For Standard and Enterprise licensing customers, the Sample Application and Model
will still be available for use with the report package and Management Reporting
samples, however, the Application card will not be available for viewing or modifying
the Application and Model. The Sample Application is deployed behind-the-scenes
when performing a Get Sample Content action from the user, using the Download
menu.
3-2
Chapter 3
Working with Data
You can also work with Smart View to access data in an existing on-premise Enterprise
Performance Management or Business Intelligence product such as Planning, or Essbase as
well as other Cloud services that Smart View supports such as Planning. This method does
not require an Narrative Reporting application to be set up.
3-3
Chapter 3
Reasons to Create an Application
Both methods of working with data allow you to perform interactive analysis and easily
refresh updated data into a report package. See Learn About Smart View and
Example: Work with Narrative Reporting data in Smart View .
3-4
Chapter 3
Creating Your Custom Application
When you first get started, you can use the sample application to see a finished application
with its dimensional hierarchies in a model, and use Smart View to interact with data in a
doclet in a sample report package. Once you are familiar with the sample application
functionality, you can create your custom application. See Working with the Sample
Application and Creating a Custom Application.
Artifact Locking
To prevent concurrent editing of application and model artifacts, simultaneous operations on
the same artifact are not permitted.
This locking feature ensures the integrity of data and the model. The lock is applied during
either a bulk operation or a dimension edit, and it is unlocked upon completion. If another
user attempts to access an artifact that has already been locked, an error message is
displayed. For example, you cannot delete a model while another user is deploying that
model.
3-5
Chapter 3
Dimension Basics
Dimension Basics
Here’s some basic information about dimensions and dimension types:
3-6
Chapter 3
Security
• Account* (required)
• Time* (required)
• Currency
• Entity
• Scenario
• Year
• Generic
You can enable up to 20 dimensions per model.
• Each model must have one Account and one Time dimension
• For Currency, Entity, Scenario, and Year, you can have either zero or one dimension
• You are allowed up to 18 Generic dimensions.
When you create dimensions using the standard dimension types, you can create them by
using either predefined properties for that type or load dimension properties of your own.
See "Creating Dimensions" in Create a Custom Application for more details.
Security
There are different levels of security in an application. Security on the data level is achieved
through data grants that provide access to individual or the combinations/intersections of
dimensions.
For more information, see Learn About Security, Grant Access, and Set Up Data Grants. See
the following video as well on security Understanding Security.
3-7
4
Overview of Smart View
Related Topics
• Learning About Smart View
You can learn how to work with Oracle Smart View for Office and then try to interact with
Narrative Reporting data and report packages.
In Excel, Smart View allows you to perform ad hoc queries on Narrative Reporting data and
other EPM and BI data sources. You can easily embed data points from ad hoc queries into
your report narratives in Narrative Reporting. The data points in your narratives are
refreshable, meaning the data will always be the latest.
4-1
Chapter 4
Learning About Smart View
When you work with doclets in Word or PowerPoint, you can use Smart View to
include data from Narrative Reporting data sources and other EPM System data
sources, including on-premises and cloud data sources. For example, you can
incorporate data from a profit and loss statement in Oracle Essbase Studio and an
income statement from a Planning source. The data points for the areas that you copy
remain in Word or PowerPoint, and you can refresh the doclet to see the latest data
values.
For more information about working with Smart View in Narrative Reporting, see this
4-2
5
Overview of the Library
Related Topics
• Learning About the Library
The library is the Narrative Reporting artifact repository.
users access to them. Learn more about the library from this video Learning About the
Narrative Reporting Library.
Users with the library administrator role can:
• Create folders and see all child folders and folder contents however, they cannot open
and view the contents of folders unless they have the appropriate permissions.
• Create shortcuts in any folder where they have write permissions.
5-1
Chapter 5
Learning About the Library
A user with the service administrator role has the complete ability to perform any of the
actions or tasks to any artifact or folder in the library. The service administrator can see
each users My Library folder and has unrestricted access to the service. However,
they cannot see other users Favorites or Recent folders since these only contain
shortcuts.
The library provides these benefits:
Migrating
You can migrate folders, Report Packages, Reports, Books, Bursting Definitions, Data
sources, Notes, Fonts, Third-party files, and Applications (where applicable) between
environments and within them. You can migrate artifacts using the export, download,
and import functionality in the library or by using the EPM Automate Commands. For
migrating Notes artifacts, you use the Notes Manager. See Migrating Notes Artifacts
from One Environment to Another, Notes Manager Migrate Artifacts, and EPM
Automate Commands.
Auditing
An administrator of an artifact can run audit reports for their artifact. The service
administrator can run additional audit reports for the entire system. Additional
information on audits:
• Actions in the system are captured in a running system audit.
• You can extract audit entries for folders or artifacts to which you have administrator
permissions.
• An extract file is created from the running system audit that falls within the time
frame that you entered in Create Audit File and is saved in the Audit Logs folder in
the library.
For more information on audits, see Using Audits.
Built-In Intelligence
The library is role-based, and a user is either shown content that they have been given
explicit access to, or content that has been made available to them from the report
package workflow. For example, a doclet author cannot see a report package in the
library until the author phase has started. See Creating Artifacts in the Library.
5-2
Chapter 5
Learning About the Library
5-3
Chapter 5
Learning About the Library
Note:
The menus and actions available for the following are role based.
Recent
Contains shortcuts to recently accessed content. The number of recent shortcuts
retained is set in preferences, see the Library tab in Managing User Preferences. You
can inspect shortcuts, which are read only, to view artifact properties. Refresh to
update the contents. See Inspect. See the Using the Action Menus for more
information on how to access the action menus to select these options. Additional
rules for this folder are:
• Only the given user can see the shortcuts in this folder.
• The user cannot copy, move, or rename the shortcuts in this folder.
• The user can delete shortcuts in this folder.
• If the name of the artifact to which the Recent shortcut points to is changed, the
name of the shortcut is also changed.
• If the source artifact is deleted, the recent shortcut is deleted.
5-4
Chapter 5
Learning About the Library
• The ability of the given user to access the artifact that the Recent shortcut points to is
governed by the user’s permissions on the base artifact, not the shortcut.
• The artifact properties shown in the Inspect dialog for a recent artifact are from the
source artifact.
Favorites
Contains shortcuts to artifacts marked as favorites. Includes the same options available as
the Recent folder. Additional rules for this folder are:
• Only the given user can see the shortcuts in this folder.
• The user can rename and delete shortcuts in this folder, and add or change a
description.
• The user can move a sub-folder or shortcut contained in this folder only within the
Favorites folder or its children.
• The user cannot copy or move artifacts to or from outside the Favorites folder, this
includes the copy and move of shortcuts.
• The name of the favorite shortcut does not need to match the source artifact, and if the
source artifacts name changes, the name of the shortcut contained in the Favorites does
not change.
• If the source artifact is deleted, the favorite artifact is deleted.
• The artifact properties shown in the Inspect dialog for a Favorites artifact (shortcut or
folder) are from the favorites artifact.
My Library
Personal artifacts such as Excel spreadsheets, Word documents, shortcuts, and folders.
Includes the same options as the Recent and Favorites folders, plus adds auditing. You
cannot give another user access to the content in My Library. The audit type artifact file is
created in the Audit Logs folder and audit is added to the artifact name, for example Audit
— reportpackageRP1. Additional rules for this folder are:
• Only the service administrator or given user can see the artifacts in this folder.
• You can't create report packages in the My Library folder, or move or copy report
packages to it. However, you can use shortcuts to report packages in the My Library
folder.
• Other artifacts can be copied or moved into or out-of this folder.
5-5
Chapter 5
Learning About the Library
— Contain Books that reside elsewhere in the folders of the library, where they are
created.
• Bursting Definitions — Contain Bursting Definitions that reside elsewhere in the
folders of the library, where they are created.
5-6
Chapter 5
Learning About the Library
3. Select an existing folder or create a new one using the for where you would like to
place the copied report package.
Note:
If copying to an existing folder, you must have write-access to the folder where
you are placing the copied report package.
Note:
This topic also applies to other artifacts in the library you have access to, for
example reports.
3. Select an existing folder or create a new one using the for where you would like to
move the report package.
Note:
When moving to an existing folder, you must have write-access to the folder
where the report package is being moved to.
Note:
This topic also applies to other artifacts in the library you have access to, for
example reports.
5-7
Chapter 5
Learning About the Library
Note:
When selecting the option to create report packages, the Create Report
Package wizard is displayed. See Create Report Packages.
Note:
Data source artifacts in the Library can still optionally be used to
maintain connections to cubes; however this can also be done in
Connections.
5-8
Chapter 5
Learning About the Library
• EPM Cloud Platform Connections: You can access cubes for reporting and Remote
Libraries.
• Essbase, Fusion ERP, Profitability and Cost Management (PCM) Connections: You can
access cubes for reporting only.
When creating a Connection, you select the connection type (based on the data source type)
and enter the Server Name and Admin Credentials, as well as other fields, depending on
the data source. You can also optionally select cubes to be added as data sources. The data
source artifacts in the Library use the Connections as parent artifact "containers", where
you can select a Connection to use and select a cube from that connection.
For EPM Cloud Platform connections, you can optionally enable a Remote Library for users
to access reporting content from these connections in Narrative Reporting.
The Connection dialog, where you can create and edit Connections. For the EPM Cloud
Platform connection, you can Enable Library to expose a Remote Library to the end-users.
Under Manage Data Sources, you can create and manage data sources for Reports.
5-9
Chapter 5
Learning About the Library
The Data Source dialog, where you can alternately create Connections to specific
cubes. Cube connections can also be defined in the Connections dialog.
5-10
Chapter 5
Learning About the Library
1. On the Narrative Reporting Home page, under the Tools icon, you can select
Connections.
3. In Name, enter a descriptive identifier for the connection, such as a combination of the
data source and server.
4. In Type, select the type of data source:
• Oracle Enterprise Performance Management Cloud, used for:
– Enterprise Profitability and Cost Management
– FreeForm
– Planning and Planning Modules
– Financial Consolidation and Close
– Tax Reporting
5-11
Chapter 5
Learning About the Library
Note:
8. Enter the administrator User ID and Password. The administrator User ID needs to
be a Service/System Administrator role at the data source level, BI Administrator
role for Fusion Applications.
Note:
You must log in to Narrative Reporting with the administrator credentials
for the data source that you want to create a connection to. For example,
if your Planning Modules administrator is PlanAdmin, you must log in to
Narrative Reporting with the PlanAdmin credentials to create a data
source connection to the Planning Modules data source. Enter User ID
and Password credentials used for native authentication at the source.
Single Sign-on with Identity Assertion technologies is not supported.
5-12
Chapter 5
Learning About the Library
(Oracle Essbase Cloud only): Click Yes on the dialog box to trust the connection. This
setting is stored so that you do not have to answer the question again.
10. For EPM Cloud connections, optionally select Enable Library to expose a Remote
Library.
11. To select cubes to be added as data sources:
• Under Manage Data Sources, click Add Data Sources to add one or more
cubes to connect Reports to.
• For each cube, enter a Data Source Name, select the Application and Cube
names.
After selecting a cube, you can click on to preview the dimension list.
5-13
Chapter 5
Learning About the Library
• In the Manage Data Sources toolbar, you can: Edit an existing data source,
create a New data source, Delete a data source and Refresh the view.
• Click OK to add the Connection. The connection will appear in the list under
the Manage Connections.
To Edit a Connection:
In Manage Connections, select the Connection, and then select Edit from the
Actions menu. When you edit a connection, you can change the Connection Name
and Server, as well as the Application and Cube names.
Note:
• Changing the Connection Name does not affect any report objects that
use the connection.
• Changing the Server, Application, or Cube names causes any report
objects that use the connection to point to the new destination.
• For security purposes, you must re-enter the administrator credentials
when editing the connection.
5-14
Chapter 5
Learning About the Library
For information on granting access to library artifacts, see this video Granting Access
to Library Artifacts.
Note:
The list of column names that are displayed for the View menu are determined by
artifact, folder type, and a user’s privilege.
5-15
Chapter 5
Learning About the Library
cursor in the header title areas and selecting sort ascending or descending
icons.
Using Audits
Audits are stored in the system-generated Audit Logs folder. It contains system-
generated audits for the entire system and audit reports that were run on specific
artifacts. Audit-type extracts that can be run on library artifacts and folders by a service
administrator. An audit extract allows you to view who made changes to an artifact or
folder, when it was changed, and what was changed.
Considerations and actions for audits:
• Actions in the system are captured in a running system audit.
• Users can extract audit entries for folders or artifacts to which they have
administrator permissions.
• Only audit log type artifacts are allowed in this folder.
• All users can view this folder, but are only allowed to view audit log artifacts that
they created.
• Users with the Service Administrator role can view any audit log artifact.
• Users can’t copy or move any artifacts into or out of this folder.
• Users can download an audit log artifact and delete an audit log artifact.
For more information, see Perform an Audit.
5-16
Chapter 5
Learning About the Library
For example, you can create a personal folder to organize artifacts in the library. Click in
the navigation pane or content pane. If you create a folder in the navigation area, the folder is
added after the system generated folders but not within. In the content area, you can create a
personal folder within any of the following folders that have been selected in the navigation
pane to help with organization:
• Favorites
• My Library
• Application
• Any personal folder that you created or can access
Depending on the folder type selected in the navigation pane, you might have more options.
For example, if the My Library folder is selected, you can inspect and audit.
Note:
For localized versions of Narrative Reporting, you should not create custom folders
spelled the same as a translated system folder. This is due to certain implications
when opening the same localized version of Narrative Reporting in English.
5-17
Chapter 5
Learning About the Library
Note:
Some of the following actions might not apply to system-generated personal
folders or system personal folders.
5-18
Chapter 5
Learning About the Library
Note:
When an artifact is selected from the content pane of the library, it automatically
opens the artifact in its native environment. For example, when you select a report
package it opens in the report center. You are prompted to open or save third-party
documents, such as XLSX files.
Report Package
When you select a report package from the Report Packages folder of the library, it opens in
the report center. The actions that you can take depends on your role and the status of the
report package. See Create Report Packages. Available actions for report packages from the
content pane:
• Open—Open a Report Package.
• Edit—Edit report package in the report center.
• Inspect—View and change; properties and view access, and view the history.
• Copy—Make a copy of a Report Package.
• Copy URL to Clipboard—Provides a direct URL to open a Library Artifact such as a
Report Package, Report, Snapshot Report, Book, or a third-party file.
• Move—Move a Report Package to a different folder you have access to.
• Audit—Extract audit entries for a report package. See Perform an Audit.
• Export—Makes a ZIP file of a folder and its contents and saves it where you choose.
See Migrate Artifacts.
• View in Library Folder —See the report package in its library location.
Note:
Available only when Report Packages folder is selected.
5-19
Chapter 5
Learning About the Library
• Inspect—View and change; properties and view access, and view the history.
• Copy—Make a copy of a report.
• Copy URL to Clipboard—Provides a direct URL to open a Library Artifact such
as a Report Package, Report, Snapshot Report, Book, or a third-party file.
• Move—Move a report to a different folder you have access to.
• Audit—Extract audit entries for a report . See Perform an Audit.
• Export—Makes a ZIP file of a folder and its contents and saves it where you
choose. See Migrate Artifacts.
• View in Library Folder —See the report in its library folder location.
Note:
Available only when Reports folder is selected.
Bursting Definitions
When you select a bursting definition from the Bursting Definition folder in the library, it
opens the bursting definition for editing. Some of the available actions from the content
pane:
• Edit—Edit Bursting Definition from the library.
• Inspect—View and change; properties and view access, and view the history.
• Copy—Make a copy of a bursting definition.
• Move—Move a bursting definition to a different folder you have access to.
• Audit—Extract audit entries for a bursting definition. See Perform an Audit.
• Export—Makes a ZIP file of a folder and its contents and saves it where you
choose. See Migrate Artifacts.
• View in Library Folder —See the Bursting Definition in its library location.
Data Sources
When you select a data source from the Data Sources folder of the library, it opens the
data source for editing. Some of the available actions from the content pane:
• Edit—Edit a data source.
• Inspect—View and change; properties and view access, and view the history.
• Export—Makes a ZIP file of a folder and its contents and saves it where you
choose. See Migrate Artifacts.
Application
When you select the application from the Application folder of the library, it opens in
the application center. The actions that you can take on the application depend on
your role and permissions. Some actions that you can take from the content pane:
5-20
Chapter 5
Learning About the Library
• Inspect—View and change; properties and view access, and view history from the
Inspect dialog.
• Audit—Extract audit entries for a Library Artifact such as a Report Package, Report,
Snapshot Report, Book, or a third-party file. See Perform an Audit.
• Export—Makes a ZIP file of a folder and its contents and saves it where you choose, see
Migrate Artifacts.
Rules for this folder are as follows:
• Only the application artifact resides in this folder. Other child folders and artifacts are also
allowed.
• All system users can see the folder and have read access. Additional access to its
content is through access security.
• Service administrators, application administrator, and library administrator (specifically for
creating child folders) have write access to this folder.
For more information on applications and tasks, see Learn About an Narrative Reporting
Application.
Note:
To perform a successful folder export, the user must have administer access to
all artifacts in the folder.
• Import—used as part of the migration process to import a file either from the library or
locally, see Migrating Folders and Artifacts for more information on how to complete this
task from the library.
Note:
You can also migrate Note Templates, Notes, and Note Formats via the Notes
Manager. For more information, see Migrating Notes Artifacts from One
Environment to Another.
5-21
Chapter 5
Learning About the Library
You can access Inspect from the navigation and content panes for folders and
artifacts. From the navigation pane, you can review and inspect the properties tab for
the following:
• System-generated personal folders:
– Recent
– Favorites
– My Library
• System-generated folders:
– Audit Logs
– Report Packages
– Application
5-22
Chapter 5
Learning About the Library
Note:
For the Application folder, you can also review the Access and History tabs.
In Properties ,you can edit names and descriptions of personal folders and folders that
you created. You can also view properties related to a folder or artifact.
To assign or view access permissions for a folder or artifact and manage security for a folder
or artifact, use the Access tab . The Access tab is available only for folders and artifacts
that you have been given permission. For more information on the Access tab, see Granting
Access.
In History , you can view the history for a folder or an artifact. If you selected inspect for
a folder from either the navigation or content panes, the history tab displays the results for the
folder. Only administrators see history for all of the artifacts in a folder.
Note:
• This feature is not available for multiple selections, only a single selected
artifact.
• This feature does not apply to folders.
• The user launching the copied URL will need at least View access to the
artifact.
5-23
Chapter 5
Learning About the Library
3. Paste the URL where needed. Upon clicking on the URL, the Library artifact will be
launched in a browser window.
5-24
6
Using the Appearance Icon
Change the theme of your display or add your company logo or a background image to the
Home page.
On the Appearance page, you can change the general look and feel of your Oracle
Enterprise Performance Management Cloud environment. Enabling the Redwood Experience
not only provides a new application look and feel, but it also includes certain features, such
as dynamic tabs, that are not available in the other themes. If you opt not to use the
Redwood Experience, you can choose instead from a list of predefined classic themes with
different background colors, icon styles, and so on. You can also add a branding logo and
background images to the Home page and hide the business process name. For general
information about using the Home page, see About the Home Page.
Note:
You can set your profile picture to display at the top of the Announcements panel of
the Home page in User Preferences. Click Tools, and then User Preferences. For
more information, see Using the General Tab.
6-1
Chapter 6
Note:
6-2
7
Managing User Preferences
Manage your user badge photo, notifications, and other display items by modifying your
personal preferences.
To modify User Preferences settings:
7-1
Chapter 7
User Preferences Icon
Use the Zoom control slide to size the image. Then, drag the highlighted square
area to crop the image for best display or use the
7-2
Chapter 7
Using the General Tab
• Under Locale, the default language for your browser is selected. Text, buttons, and
messages are displayed in the selected language. You can select another language, if
desired. If you do so, you must sign out and sign in again for the language setting to take
effect. Select a time zone that you want to use for displaying time. The current date and
time are displayed.
Note:
If you do not set your language in the Preferences - General tab, then the
language displayed for the user interface is derived from your Browser settings.
For email notifications, the default language is English. If you would like to
receive notifications in a language other than English, select the specific
language from the Language drop down menu (not Default - " Language ")
from the Preferences - General tab. For example, if you want Spanish to be
your default language, select Spanish from the Language drop down menu.
The time zone you select can be different than the time zone you are in.
7-3
Chapter 7
Using the Notification Tab
• Under Show Confirmation Messages, if you have turned off the feature to
display system confirmation messages, you can turn system confirmation
messages on again by selecting Show Messages.
Note:
Although you have set the Date and Time format in the Preferences –
Formatting tab, notifications that you receive may have a different format due
to internal architectural constraints.
7-4
Chapter 7
Using the Formatting Tab
Use the Format Locale menu to select default values for numbers, dates, and times for your
location. For example, the "English (United States)" locale formats the thousands separator
with a comma, the decimal separator with a period, and the date with the three-letter
abbreviation for month, followed by the day and year.
You can either change these settings manually, or you can use the Format Locale menu to
select the default values for a different locale. For example, the "Spanish (Spain)" locale
formats the thousands separator with a period, the decimal with a comma, and the date with
the day, month, and year.
The following commonly used formats are available for thousands and decimals separators:
• Default is the value provided from your operating system.
• Comma (for example, 100,000 or 95,91).
• Period (for example, 100.000 or 95.91).
• Space (for example, 100 000 or 95 91).
• Apostrophe (for example, 100'000 or 95'91).
Similarly, for Date and Time, select the format that you want to use for display purposes.
Note:
You can customize your time formats, using the Customize option which presents a
text box to enter a custom sequence for your unique requirements using standard
time formats.
Date formats:
• M—Month
• d—Day
• y—Year
7-5
Chapter 7
Using the Library Tab
Resetting Preferences
To restore your preferences to the default values, select and use one of
the following options:
• Reset name of tab, in this example Reset General to undo any modifications that
were applied and restore default values on the Preferences tab.
• Reset All Tabs to Default option from any Preferences tab to reset every
preference value on all tabs of the Preference dialog box to the original default
values from initial use.
Caution:
All changes, whether applied or not, are removed.
7-6
Chapter 7
Previewing a Report POV
Note:
The default option for the Preview POV preference is disabled
7-7
Chapter 7
Previewing a Report POV
7-8
8
Uploading Additional Fonts
Oracle recommends that as an initial startup task, the service administrator uploads the
TrueType fonts that your company uses to produce reports. This will ensure the most
accurate rendering of the documents when viewing on the web.
Without these uploaded fonts, Narrative Reporting uses a font mapping utility that attempts to
properly render the report on the web. However, this mapping may introduce variances in the
report layout when displayed on the web. Therefore, we highly recommend that you upload
your TrueType fonts when you set up the service.
Note:
The system is not redefining or changing the fonts leveraged in the report, the font
mapping only applies to the document rendered on the web.
The service administrator can upload individual font files or zipped files containing multiple
TrueType fonts to the Fonts folder in the library. You can also organize your font files by
creating sub-folders in the Fonts directory.
The font file must be a TrueType font and cannot already exist in the font folder structure. If
you do upload a duplicate font, you will receive an error message indicating the duplicate (or
invalid) font file. If you uploaded multiple fonts in a zip file, all other valid files will be loaded.
Note:
You can migrate font files like any other artifact from one environment to another or
within the same environment. You can migrate using the export, download, and
import functionality in the library. See Migrate Artifacts.
Note:
When uploading additional fonts to Narrative Reporting, you are responsible for the
proper licensing of the fonts from the font vendor. For example, if you upload the
Microsoft font "Times New Roman," you must obtain the licensing from Microsoft to
do so. Uploading a Microsoft font sourced from a Windows machine is not typically
covered by the legal use agreement from Microsoft.
1. Locate your additional TrueType fonts. If more than one is to be uploaded, create a zip
file.
8-1
Chapter 8
Note:
Be aware that it may take some time to perform the upload depending on
the size of the font file.
8-2
Chapter 8
The zip file is unzipped, and all the uploaded fonts are automatically extracted to the
Fonts folder. These fonts are now available when displaying your documents. Any
custom fonts uploaded also appear in the font list for management reports. See the
Designing With Management Reporting for Oracle Enterprise Performance Management
Cloud and Working with Management Reporting for Oracle Enterprise Performance
Management Cloud Guides.
Note:
For PowerPoint report package types, custom fonts take effect after the next
scheduled daily maintenance. See Setting Service Maintenance Time.
8-3
9
Installing Samples
Narrative Reporting provides samples to help you learn how to use report packages,
applications, and management reports. You can use:
• Sample Report Packages, with MS Word, PowerPoint and PDF report package types,
can help you become familiar with the report package functionality and content such as
the report center, doclets, phases, embedded content and variables, where applicable.
For all three sample report packages types, phases and user assignments have not been
enabled and defined, however after importing the sample files, a report administrator can
enable phases, define dates and assign users. To learn more how to use the sample
report package, see Working with the Sample Report Package.
• Sample Reports can help you become familiar with the functionality of Reports.
• Sample Books can help you become familiar with the book functionality.
• Sample Bursting Definitions can help you become familiar with the bursting
functionality.
Upon installation, all sample content will be automatically deployed and imported when you
perform a Get Sample Content action from the Downloads menu. The Samples folder will
be organized with subfolders for each artifact type (Report Packages, Reports, Snapshot
Reports, Books, and Bursting definitions).
9-1
Chapter 9
Installing samples
To work with sample files, a service administrator must install the samples from the
User Menu.
To install samples:
1. On the Narrative Reporting Home page, access Settings and Actions by clicking
your user name at the top right corner of the screen.
2. Select Downloads.
Note:
The sample application will be loaded and deployed and all sample
library artifacts will automatically imported behind-the-scenes.
9-2
Chapter 9
For Standard and Enterprise licenses, a sample application is generated and is populated
with one model, seven dimensions, and corresponding data, upon installing samples. The
sample application is a source for reports and report package reference doclets. It can also
be queried in Oracle Smart View for Office. The sample application is automatically deployed
while performing a Get Sample Content action.
For old Enterprise Performance Reporting SKUs (pre-June 2019), if you have deployed a
custom application, the sample application will not be deployed. In this case, the reports and
report package reference doclets will not be refreshable, since the sample application will not
exist. If a custom application does not exist, the sample application will be deployed.
Note:
Sample content for deprecated functionality, such as the Disclosure Management
samples or the sample application load files, is no longer included.
9-3
10
Learning About Security
In this topic, you will gain a high-level understanding of the layers of security that you can
implement in Oracle Narrative Reporting Cloud Service to ensure that each user has the
appropriate access to information and system administration. The three layers of security:
• System Level Security
• Artifact Level Security
• Data Level Security
Levels of Security
Oracle Narrative Reporting Cloud Service security is achieved through a combination of
system level roles, corresponding artifact level permissions, and data security:
• System Level security – Restricts Oracle Narrative Reporting Cloud Service to users that
are created by the Identity Domain Administrator in Oracle Cloud, My Services and
assigned at least one role.
• Artifact Level security – Restricts access to report packages, third-party documents,
folders, and the application by granting permissions to users and groups.
• Data Level security – Identifies the users and groups that have specified access to data.
10-1
Chapter 10
Levels of Security
Service Administrator
Performs all functional activities, including granting predefined roles to Narrative
Reporting users.
Power User
Creates report packages, management reporting definitions, and Disclosure
Management documents.
Creates folders, including root-level folders.
Creates and maintains all artifacts, such as models, dimensions, and data grants.
User
Views Narrative Reporting artifacts to which the user has access.
Viewer
Views reports and other artifacts to which the user has access. This is the minimum
role required to sign in to and use an environment.
10-2
Chapter 10
Levels of Security
Service Administrators
Create and maintain all aspects of the system, except for user management
Reports Administrators
Create report packages, management reporting definitions and Disclosure Management
documents
Application Administrators
Create and maintain all application artifacts, such as applications, models, dimensions, and
data grants
Library Administrators
Create folders, including root-level folders
Users
The minimum role required to log in to and use the service, and to view artifacts to which the
user has access
10-3
Chapter 10
Levels of Security
When you see the keys in Oracle Narrative Reporting Cloud Service, you can grant
access to users, groups, or users and groups.
When you create an artifact (report package, folder, application), you automatically
have permission to edit, delete, and maintain that artifact. In addition, you can give
other users, groups, or users and groups the ability to maintain or view that artifact by
granting access to those users. Users who do not have access cannot see or access
that artifact.
The permissions you can grant on an artifact depend on the artifact. For example, you
can grant "Administer" or "View" permissions to Third-Party artifacts in a folder,
whereas you can grant "Administer", "Write", or "View" permissions on a folder in a
library. For an application, you can grant "ADMINISTER" or "USE" permissions. See
Learning About Security for details on all the permissions.
10-4
Chapter 10
Levels of Security
You can grant permissions to artifacts in the library using the concept of "inherited
permissions". This gives you the ability to easily grant the same permissions that you set at a
parent folder to the child folder(s) and artifacts underneath it. By default, folders are created
with the Inherit Permissions box checked by default, but you can clear it if you wish. And, you
may also individually override the inherited permissions for certain users and/or groups by
directly assigning or revoking a permission. Note that the inherited permission check box is
not the default for a report package, since granting access allows other users to view it
immediately. A report package owner usually waits until a more appropriate time in the report
package lifecycle rather than granting access at creation time.
See Granting Access for more details.
Reports Permissions
1. In order to run a management report, the user must have at least the "View" permission
on the artifact.
2. In order to save a management report as a snapshot the user must have "View"
permission on the artifact. Saved management reports can only be written to folders to
which a viewer has "Write" access.
3. When a management report snapshot is created, the system grants that user with the
Report Administrator permission on the snapshot.
4. When a management report snapshot is created from the definition, the snapshot does
not get the permissions applied to the management report definition.
10-5
Chapter 10
Levels of Security
10-6
Chapter 10
Levels of Security
The rows within a data grant determine the security outcome (effective permissions). The top
row (base layer) is evaluated first. Some best practice ideas:
• Apply broad rules for the majority of cases, and then create exceptions. You can either
grant the greatest access in the base layer, or start with a restrictive base layer and then
grant greater access.
• Try to create security in the data grant in the fewest steps to simplify maintenance.
The key to creating data grants is to understand how the order of the rows affects the
effective permissions and steering clear of creating conflicting rules between rows. In cases
of conflict, the least restrictive access rules takes precedence. See Setting Up Data Grants
for more details on the rules and logic applied to creating data grants in Oracle Narrative
Reporting Cloud Service, The chapter includes sample data grants to increase your
understanding of them.
10-7
11
Granting Access
To control which users can access content within Narrative Reporting, you must grant access
to users for the following artifacts:
• Report Packages
• Folders
• Reports reports
• Third-party Artifacts, such as MS Office documents, PDFs, and images
• Dimensions
• An Application (includes the application artifact, dimensions, and data grants)
Note:
Access to models and data is granted through Data Grants . See Set Up Data
Grants. For System audit logs, no access can be granted to other users. Only the
Service Administrator and the creator of the System audit log can view them.
Watch this tutorial video, you’ll learn how service administrators grant access to library
artifacts in Narrative Reporting. You can grant access to folders; third-party artifacts such as
Microsoft Office documents, PDFs, and images; report packages, and applications.
11-1
Chapter 11
As a best practice, to minimize maintenance, you can group users who have the same
access level. Permission is then assigned to the group rather than each individual
user.
Types of Permission
The following types of permission may be granted on different artifact types:
users and groups. Click the check box on the Access tab of the associated
Inspect dialog box to add or remove that permission for the selected user or group.
When you hover over the selected permission, it is identified as "Direct
Permission."
11-2
Chapter 11
• Inherited permissions are used to assign the permissions granted to a parent level
artifact to all its children to avoid having to set individual user permissions for each
artifact. The permissions applied to the parent flow down to all child artifacts for that
parent. You can adjust the inherited permissions by revoking permission for a particular
user or group, for example, if you have confidential data that you do not want everyone to
see.
You can assign both Administer and View permissions at the folder level and the objects in
the folder will inherit those permissions if Inherit permissions from parent folder is turned
on.
By default, inheritance is turned on for folders and third-party artifacts. Inheritance is turned
off by default for report packages and reports so users are granted appropriate access to the
report package and reports during the development of the report.
The inheritance icon is displayed beside users with inherited permissions. Hovering over
a permission displays the path to the location of the permission.
If you add or remove an inherited default permission on the Access tab, a new icon is
displayed beside the modified permission to indicate the change. Click again to revert to the
original inherited permission, if required.
11-3
Chapter 11
Granting Access to Report Packages
Caution:
As a best practice, Report Package Owners and Viewers should be assigned
in the Report Package rather than the Library.
The report package owner can assign access to the report package, using one of the
following methods:
• When creating the report package, select and assign users, as described in
Create Report Packages.
• Through the Library, using the Inspect dialog box, as described in this document.
Available Permissions
Only Administer and View (report package viewer) permissions can be assigned
through the Library. Report package authors, approvers, and reviewers must be
assigned from the report package itself. See Create Report Packages for additional
information.
The following permissions are available for the Report Package:
• Administer—Enables the user or group to edit, delete, and import or export the
artifact to which the permission has been applied for that user or group. The
Administrator user in the Report Package is displayed in the Library and the
Access tab with direct Administer permission. If you assign other users the
Administer permission on a report package, then they are also displayed as report
package owners.
• View—Enables the user or group to see the report package. The View user in the
Report Package is displayed in the Library, and from Inspect on the Access tabs of
the report package as having direct View permissions.
To grant access to report packages:
1. From the Home page, select an option to access the report package:
• Report Packages on the Home Page
• Library, and then Report Packages
• Library, and then Folder
Caution:
As a best practice, Report Package Owners and Viewers should be
assigned in the Report Package rather than the Library.
11-4
Chapter 11
Granting Access to Report Packages
11-5
Chapter 11
Granting Access to Report Packages
Note:
To remove the original administrator, you must assign the
administrator permission to another user, who can then remove the
original Administrator.
11-6
Chapter 11
Granting Access to Folders and Third-party Documents
The icon indicates inherited permission. When you hover over the inherited
permission, the complete path to the original artifact is displayed.
7. Click Close.
Available Permissions
The following permissions are available for the folders and third-party content:
• Administer – Enable the user or group to read, edit and delete artifacts.
• Write – For folders only, enable the user to import third-party content or other artifacts as
a new file into the parent container or folder.
• View — Enables the user or group to see all authorized folder artifacts within the
application. The View permission may be applied directly to the artifact or inherited from a
parent folder hierarchy.
• Remove – Allows the user to delete a selected user or group from the list. Highlight the
name, and then click X to remove the name and any associated permissions.
To grant access to folders and third-party content:
1. From the Home page, select Library.
2. In the Library, select the folder or artifact for which you want to assign access.
3. Under Actions, select Inspect, and then Access.
11-7
Chapter 11
Granting Access to Folders and Third-party Documents
Users or groups who are inheriting permissions from the parent folder are
indicated by the inheritance icon .
11-8
Chapter 11
Granting Access to an Application
• Select View to enable the user or group to see all authorized folder artifacts
within the application. The View permission may be applied directly to the artifact,
or inherited from a parent folder hierarchy.
• Select Remove to delete a user or group from the list. Highlight the name, and
then click X to remove the name and any associated permissions immediately.
b. Optional: To inherit the same permissions that have been assigned to a parent
artifact, click Inherit permissions from parent folder. Inherited permission is
indicated by the icon . When you hover over the inherited permission, the
complete path to the original artifact is displayed
6. Click Close.
Caution:
If you apply access to the Application system folder listed under the left column of
the Library using the Inspect option without opening the application, the associated
permission is applied to the system folder and not to the application itself.
Available Permissions
The following permissions are available for the application:
• Administer—Allows the user or group to perform the following tasks within the
application, to enable the ongoing management of all application artifacts:
– See and manage all models in the application
– Edit and delete any artifact in the application
– Import and export all application artifacts (models, dimensions, and data grants)
– Add, edit, and remove users and groups
• Use—Allows a user to see the Application in the Library. The level of access which the
user is allowed is also governed by any additional permissions restricting the user, such
as:
– View permissions applied to any artifact
– Write permissions applied to a folder artifact
– Additional permissions applied to the model, data and metadata
11-9
Chapter 11
Granting Access to an Application
4. From Access , click the check box under the appropriate columns, or select
Grant Permission from User or Group Actions to assign the level of access
for each user or group:
11-10
Chapter 11
Granting Access to an Application
• Select Administer to enable the user or group to perform ongoing management of all
application artifacts.
• Select Use to allow a user to see the Application in the Library. The level of access
which the user is allowed is also governed by any additional permissions restricting
the user.
5. Optional: Select Remove to delete the selected user or group from the list. Highlight the
name, and then click X to remove the name and any associated permissions:
6. Click Close.
4. Click and select the users to which you want to assign access, as
follows:
a. Select the user type:
• Users
• Groups
11-11
Chapter 11
Granting Access to Dimensions
5. From the Access tab , assign the level of access for each user or group by
clicking the check box under the appropriate columns, or select Grant Permission
from User or Group Actions :
• Select Administer to enable the user or group to perform ongoing
management of application artifacts.
• Select Use to allow a user to see the Application in the Library. The level of
access which the user is allowed is also governed by any additional
permissions restricting the user.
6. Optional: Select Remove to delete the selected user or group from the list.
Highlight the name, and then click X to remove the name and any associated
permissions.
7. Click Close.
Note:
In addition to applying access to specific dimensions through the application
as described in this document, you can also control access using data
grants:
• Create data grants that restrict which portions of a model can be accessed.
• Set Default Access when you create or modify a dimension to READ from the
Default NONE to enable all users to view but not modify the dimension.
For more information on data grants, see Set Up Data Grants.
To grant access to dimensions:
1. On the Home page, select Application, and then click the application name to
display the Application Overview.
2. From the application Overview screen, select Dimensions and Models.
11-12
Chapter 11
Granting Access to Dimensions
3. Click the name of the dimension for which you want to grant access.
4. From the Dimension Overview screen, select Access. The name of the selected
dimension is displayed at the top of the screen.
5. Click and select the users to which you want to assign access, as
follows:
a. Select the user type:
• Users
• Groups
• Users and Groups
11-13
Chapter 11
Granting Access to Dimensions
b. On the Select User dialog box, enter the first few letters for the user name in
the text box, and then click Search to populate the list of names. To
display all users and groups, enter an asterisk "*" as a wildcard in the Search
field.
c. Select the users and groups to which you want to assign access, and then
click OK.
6. From the Access tab , select Administer to enable the user or group to view,
modify, or delete the dimension.
7. Optional: Select Remove to delete the selected user or group from the list.
Highlight the name, and then click X to remove the name and any associated
permissions.
8. Click Close.
11-14
12
Setting Up Data Grants
Data grants enable you to apply a level of security to the data stored in a model and to
control who can access sensitive or confidential information. You can create data grants for
dimension intersections that identify users or groups who are allowed to access that data. At
least one model must exist before you can apply a data grant.
Usually, you create data grants only for dimensions to which you need to allow or restrict
access; otherwise, you can use the Default Access to set the access for the entire dimension.
For example, in the Sample Application, you can set the Default Access to Read for the
dimensions that do not need access restriction, and then set your specific data grants on the
remaining dimensions, where Default Access is None, to grant access as required.
Carefully constructed data grants can ease security maintenance by adapting automatically
to changes in your application, such as members being added or dropped.
See these sections for more information:
• Understanding How Data Grants Work
• Selecting Member Functions
• Data Grants Processing and Conflict Resolution Rules
• Creating Data Grants
• Sample Data Grant
Watch this tutorial video, you'll learn how to create data grants for Oracle Enterprise
Performance Reporting Cloud. As an application administrator you create data grants to
enable access to portions of data for users and groups. You create data grants in layers.
Each layer refines access.
12-1
Chapter 12
Understanding How Data Grants Work
• Default Access for the Scenario dimension has been set to None, so we are
setting individual permissions from that baseline.
• The Accounting Manager is also part of the Accounting Group.
The rows are read in sequence, from the top down, and the results for each row
culminate in the effective permission for the selected data. For more information on
processing data grants, see Data Grants Processing and Conflict Resolution Rules.
Note:
In the first row of the data grant, Actual and Plan are used in a single row
because they have the same criteria. Alternatively, you can create two rows
instead; however, combining members minimizes the number of rows in the
data grant.
After the data grant is created, it is recommended that you validate the data grant. The
Validate operation checks the data grants to determine whether member names used
in the data grant are still valid. For example, if a member that was selected for a data
grant is removed from a dimension, that data grant becomes invalid. If the data grant
is not valid, an alert icon is displayed for the data grant and the data intersection row
inside the data grant. Open the data grant to see the affected model, and correct the
situation.
Caution:
The Validate operation does not automatically change any data grants.
After validating the data grant, review the assigned permissions on the Data Grants
Access screen. Select each individual user or group, and verify that the data grants
reflect the restrictions that you require. If you created multiple data grants, then
conflicting rows likely exist. The background resolution of multiple competing or
conflicting data grants may not create the final result that you expect, so you might
need to refine your data grants to ensure the proper access.
Best practice suggestions:
12-2
Chapter 12
Selecting Member Functions
• Grant the broadest rules that apply to the most people in your base layer for first row of
the data grant, and then add exception rows to reduce access.
• Try to create your security model in the fewest possible steps, to ease maintenance.
For more details on the rules and logic applied to creating data grants in Narrative Reporting,
see Data Grants Processing and Conflict Resolution Rules.
The function icon in the Select Members dialog box is available for every member level
in the hierarchy, and offers the following member functions to select the members to be
included in a data grant:
• Member —Assign the data grant to the selected member only.
• Children—Assign the data grant to the children of the member only. The member is not
included.
• IChildren (Inclusive Children) —Assign the data grant to the target member and its
children.
• Descendants —Assign the data grant to the entire tree under the selected member. The
member is not included.
12-3
Chapter 12
Data Grants Processing and Conflict Resolution Rules
12-4
Chapter 12
Creating Data Grants
2. From the Overview screen in Application, select Dimensions and Models , and then
click the name of the dimension to which you want to assign the data grant.
3. On the Dimension Overview for the selected dimension, under Default Access,
check the default access setting for the baseline access for this dimension for all users
because it may affect how you set the data grant:
• If the default dimension access is set to None, you might need to allow permissions
to Read in your data grant.
• If the default dimension access is set to Read, you may need to restrict access to
members in the dimension by setting the permissions to None.
Determining the default access ensures a common starting point for all users, easing
construction of the data grant. If your company prefers a most restrictive environment,
create no more than one data grant per dimension and ensure all None rows are at the
bottom or lower rows of the data grant.
12-5
Chapter 12
Creating Data Grants
6. Enter a name for the new data grant, and then click Access to set the
permissions for the new data grant.
7. Under Models, select at least one model that contains the dimension for which
you want to set the data grant. The screen is activated when the model is
selected.
12-6
Chapter 12
Creating Data Grants
9. Under the dimension name (for example, Fiscal Calendar), click Select Members to
display the Select Members dialog box.
10. Under All Members, click the member name to expand the list of members to the
required level.
12-7
Chapter 12
Creating Data Grants
11. Click the function icon beside the required level of member to select the
functions for the members to be included in the data grant. The selections are
automatically moved to the Selections column. For a list of member functions, see
Selecting Member Functions.
To redisplay any members, click the previous level in the navigation.
12. Optional: On the Select Members dialog box, click Actions to select one or
more display options for the dimension and its members:
• Show Alias Instead of Name
• Show Member Counts
• Sort Alphabetically
13. Click Close.
14. Under Users, click Add to select the users and groups that you want to include in
the data grant on the Select User dialog box.
15. Optional: Under Users, click the number of users to view all selected users in a
list, or add another user.
12-8
Chapter 12
Creating Data Grants
16. Under Permission, click Select Permission to display the Permissions dialog box, and
then select the appropriate permission for the selected users:
• None – The selected user cannot view or modify the specified member for the
dimension.
• Read – The selected user can view, but not modify the specified member for the
dimension.
• Delete Permission – Click to remove the entire permission from the Permissions
table.
17. Optional: From the drop-down arrow beside each row in the data grant, select from the
available options to perform other actions for permissions for the row:
• Add Another Permission–Enables you to add another permission for the selected
row, without re-entering the member details.
• Move Up or Move Down–Moves the selected row up or down in the table rows.
Because rows are evaluated from top to bottom to determine the data available to
12-9
Chapter 12
Sample Data Grant
users and groups, you should be aware that any moves to the rows will affect
the effective permissions.
• Add Row–Use to add another row to the data grant.
• Duplicate-Use to add another row with the same criteria to the data grant.
• Delete-Use to delete the row for the data grant.
18. After all rows for the selected data grant are added, click Save, and then Close.
Caution:
The Validate operation does not automatically change any data grants.
20. From the list of users on the Data Grants Access tab , select the user or
group that is assigned to this data grant, and verify that the assigned permissions
are correct.
Although the data grant may be valid, it might not accurately represent the access
that you intended to assign. Review all data grants for the selected user or group
to refine the access and ensure only the authorized user or group can access the
required data.
12-10
Chapter 12
Sample Data Grant
1. Because the access restrictions will be set across only three dimensions, from the
Overview for each dimension, set the Default Access for Entities, Scenarios, and Fiscal
Calendar dimensions to None.
2. Set the Default Access for the remaining dimensions (Accounts, Years, Currencies, and
Segments) to Read.
3. Set the access permissions for each user and dimension to Read, as follows:
12-11
Chapter 12
Sample Data Grant
When logged in as Rodney, notice how the data grant is applied in an ad-hoc query in
Smart View.
12-12
Chapter 12
Setting Up Data Grants
When logged in as Oceana, notice how the data grant is applied in an ad-hoc query in Smart
View.
12-13
Chapter 12
Setting Up Data Grants
12-14
13
Performing an Audit
Maintenance actions performed on artifacts and folders are tracked in a running system audit
that details who modified an artifact or folder and which action was taken.
Report package maintenance and modifications, such as doclet check-in/out and Review
phase initiation, are tracked in an artifact log for the report package, which details the actions
taken, user id, time/date stamp, etc.
Report execution is also tracked in an artifact log. The log includes the report name, user id,
time/date stamp, POV selections, and elapsed time.
The following artifacts and actions are not supported by the audit framework:
• Book preview and editing
• Bursting definition editing and execution
• Report design changes and saving
Two types of files can be generated for audits based on your role or permission:
• System Audit File—Only the Service Administrator can generate a System Audit File to
capture all entries between the default first timestamp (date and time) for the system log
and a selected end timestamp. The starting timestamp of the records cannot be edited.
• Artifact or Folder Audit File—Can be generated for selected artifacts or folders by the
user who has Administer permission for the artifact or folder, or the Service Administrator.
This audit file provides an extract of the transactions, based on a selected date range. An
audit file can be created for the following system generated and system personal folders
and user created folders:
– My Library
– Report Packages
– Reports
– Folders
Note:
You cannot create an audit log for the system generated Recent or Favorites
folders.
The audit logs are stored in the system-generated Audit Logs folder in the library. All users
can view the Audit Logs folder, but they can view only the audit files that they created. Users
cannot copy or move artifacts into or out of this folder. You cannot grant access to audit logs
to another user. Only the Service Administrator and the creator of an audit log can view them.
After you create the audit files, you can download them to your local file system for review.
13-1
Chapter 13
Creating a System Audit
Caution:
When creating the system audit file, you can choose an option to remove all
entries for the selected system audit file from the audit logs after they have
been extracted. Because the entries have been removed, the new From
timestamp for all entries changes to the first timestamp after the removed
entries. For example, if you remove all entries up to Mar 16th, the new From
timestamp becomes March 17.
13-2
Chapter 13
Creating a System Audit
• On the Welcome Panel, select Create , and then select System Audit File.
• From the Library, select Audit Logs in the left pane, and click Create in the right
pane, and then select System Audit.
13-3
Chapter 13
Creating a System Audit
2. From the Create System Audit File dialog box, use the calendar icon to
select the To timestamp for the end of the range for the audit file.
Note:
By default, From displays the earliest timestamp in the audit log and
cannot be changed.
3. Enter the name for the audit file that will be automatically stored in the Audit Logs
folder in the Library.
4. Optional: Select Remove extracted entries from the active system audit log to
clear the entries in the audit log after the audit file has been created.
13-4
Chapter 13
Creating a System Audit
Caution:
If you remove extracted entries, the From entry in the System Audit file changes
to reflect the next timestamp. For example, if the range for the audit extract that
was removed covered the period from March 15th to March 31st, then the new
From timestamp will be April 1st.
The System Audit Log contains details for each transaction, including the following:
• Timestamp
• User and IP Address
Note:
In most instances, the IP address displayed may not be the user’s actual IP
address.
13-5
Chapter 13
Creating an Artifact or Folder Audit
• Select Inspect to review the audit log Properties and the History for the file.
• Select Delete to remove the system audit file. A confirmation dialog box
confirms the deletion.
• Click Rename to enter a new name for the audit log file.
Note:
You cannot create an audit log for the system-generated Recent or Favorites
folders.
13-6
Chapter 13
Creating an Artifact or Folder Audit
1. On the Home Page, select Library, and then, in the left pane, select the artifact for which
you want to create an audit log.
2. For the chosen artifact, select Actions, and then select Audit.
3. From the Create Audit File dialog box, use the calendar icon to select the From and
To timestamp range for the audit file.
4. Enter the name for the audit file that will be automatically stored in the Audit Logs folder
in the Library, and then click OK.
5. Click OK.
6. Click OK to dismiss the confirmation message. The audit file is created in the
background, and a notification is posted when the audit log is complete.
7. Optional: On the Home page, select Messages to verify that the audit is complete.
13-7
Chapter 13
Creating an Artifact or Folder Audit
10. Navigate to the audit file on your local File System to review the results.
The System Audit Log contains details for each transaction, including the
following:
• Timestamp
• User and IP Address
Note:
In most instances, the IP address displayed may not be the user’s
actual IP address.
• Select Inspect to review the audit log Properties and the History for the file.
• Select Delete to remove the system audit file. A confirmation dialog is
displayed to confirm the deletion.
• Click Rename to enter a new name for the audit log file.
13-8
14
Migrating Artifacts
In Narrative Reporting, you can migrate Folders, Report Packages, Reports, Books, Bursting
Definitions, Data sources, Notes, Fonts, Third-party files, and Applications (where applicable)
between environments and within them. You can migrate artifacts using the export, download,
and import functionality in the library or by using the EPM Automate Commands. For
migrating Notes artifacts, you use the Notes Manager.
• Migrating Artifacts within the Same Environment
• Migrating Artifacts from One Environment to Another Environment
• Importing Artifacts into the New Environment Using the Library
• Exporting and Downloading Artifacts Using the Library
• Migrating Notes, see Migrating Notes Artifacts from One Environment to Another.
Watch this tutorial video, you’ll learn how administrators migrate Oracle Narrative Reporting
Cloud applications from one environment to another.
-- Migrating Applications.
Note:
Importing an application in the library replaces the exiting application in the library.
• Export the artifact from the current environment and download the export file to your local
file
• Log into the new environment where you already have activated your service
• Import the downloaded export file from your local file into the new environment
• Optionally, move data from your application by extracting from the current environment
and loading into the new environment or just reload data from the source.
14-1
Chapter 14
Exporting and Downloading Artifacts Using the Library
Note:
Comments and statuses in a report package are not migrated with the report
package.
Note:
Oracle recommends that you use the EPM Automate Commands for export if
the size of your artifacts (including folders) is larger than 256 MB.
a. For a root level folder, in the navigation pane, select the folder, then click ,
then click Export
b. For other artifacts (folder, report package, or application), in the right pane,
14-2
Chapter 14
Migrating Artifacts within the Same Environment
4. Select the menu in the upper right corner of the Library and then Import.
5. Select Local and browse to the export zip file you want to import.
6. Select Overwrite Existing Objects to replace any existing artifact with the new imported
artifact.
7. Select Include Access Permissions to include the already defined access permissions
on the imported artifact to the existing one.
8. Select OK. The import process runs in the background.
9. Check Messages to view the notification once the import is complete.
10. Check in the library folder you specified to verify that the file has been imported.
11. Optionally: If you extracted data from an application in your current environment, you
can now load the data into your new environment.
a. For a root level folder, in the navigation pane, select the folder, then click , then
click Export.
b. For other artifacts (folder, report package, or application), in the right pane, select the
14-3
Chapter 14
Migrating Artifacts within the Same Environment
6. To import the artifact to a different location than the export file, navigate to that
folder location. Otherwise, skip this step.
7. Select the menu in the upper right corner of the Library and then select
Import.
8. Select Library and browse to the export zip file you want to import.
9. Select Overwrite Existing Objects to replace any existing artifact with the new
imported artifact.
10. Select Include Access Permissions to include the already defined access
permissions on the imported artifact to the existing one. Then select OK.
11. The import process runs in the background.
12. Check Messages to view the notification once the import is complete.
13. Check in the library folder you specified to verify that the file has been imported.
14-4
15
Performing Backup and Restore (System
Clone)
Every day, during the operational maintenance of the service, Oracle backs up the content of
your service instance to create a complete backup snapshot of existing artifacts and data.
Backup snapshots are created for use in the event that you ever want to restore your service
to a prior known state.
Note:
Before attempting to restore your service from a backup snapshot, make sure the
destination service is the same release or newer. You cannot restore a backup
snapshot into a service that has an older release. You can confirm release numbers
by selecting the User menu from the Home page, About, and then selecting
Version.
Backup
Oracle recommends that you download the backup snapshots regularly to a local file system,
using the EPM Automate Commands, so you have them available in case you wish to restore
your service to a saved, prior snapshot. See Saving Backup Snapshots.
Note:
During Daily Maintenance, the service automatically creates a backup snapshot of
data and artifacts. When Daily Maintenance executes, it replaces the prior backup
snapshot with a new backup snapshot. You should schedule the execution EPM
Automate Commands on a daily basis to download the backup snapshot to a local
computer.
Restore
Restore can be done either through the Settings on the Home Page or by using the EPM
Automate Commands. When you restore a backup snapshot, your system will return to that
15-1
Chapter 15
Saving Backup Snapshots
prior state. Any changes that may have occurred subsequent to the time of the
backup, will not be reflected in the restored system. You can perform the following
tasks:
• Restore using the most recent daily backup snapshot Restore Using the Most
Recent Daily Backup Snapshot.
• Restore using a saved backup snapshot from your local file system Restore Using
a Saved Backup Snapshot.
Note:
The backup snapshots should be managed on the Service Administrator’s
local file system as part of the regular backup plan.
Note:
You must be a Service Administrator to access this.
Note:
The most recent snapshot from the last maintenance window is always
available.
15-2
Chapter 15
Restore Using a Saved Backup Snapshot
Note:
A message indicates that the snapshot will be restored at the next daily
maintenance time. If you need to cancel the scheduled restore, see Cancel a
Scheduled Restore.
Note:
You must be a Service Administrator to access this.
15-3
Chapter 15
Cloning Environments
Cloning Environments
The backup and restore procedures in this topic also serve as a way to clone from one
service instance to another.
To clone environments:
1. On the source instance, download the backup snapshot as outlined in Saving
Backup Snapshots.
2. On the target instance, restore the backup snapshot that you downloaded to your
local file system. See Restore Using the Most Recent Daily Backup Snapshot or
Restore Using a Saved Backup Snapshot.
3. Verify and adjust the daily maintenance time on the target instance, if necessary.
15-4