In this release, Import Metadata functionality is extended to Microsoft Word.
The Import Metadata command gives you the ability to reuse Oracle Smart View for Office content in Word documents, content that has already been formatted and customized for Word. You can use the copy and paste commands in Word to retain the customized formatting of a Smart View object, such as a table or graph, and the use Import Metadata to bring the metadata into the copied object.
For example, suppose you have a Word document containing a highly-formatted table with Smart View data points, and you would like to reuse the table in a different Word document. Instead of recreating the table from scratch, you can reuse the work that is already available with the new Import Metadata command on the Smart View ribbon.
Using the Word copy and paste commands to copy the table from one Word document to another, only the data is copied; the metadata is not copied. After the copy and paste, use the Import Metadata command on the Smart View ribbon to import the metadata from the original document into the new document. You can copy and paste within the same Word document or to a different Word document.
In the Oracle Smart View for Office User's Guide, see “Importing Metadata into Copied Word Documents.”
In a multiple-grid worksheet, you can now rename named ranges in Excel from a new option in the Document Contents pane, Rename Ranges. Using the Rename Ranges option enables Smart View to track the metadata associated with each range on a multiple-grid worksheet.
Multiple-grid worksheets are supported with Oracle Essbase data sources only.
In this release, Smart View extends support to Oracle Financial Consolidation and Close Cloud.
Oracle Financial Consolidation and Close Cloud is a subscription-based consolidation and reporting solution built for and deployed on Oracle Cloud. From Smart View, you can access Oracle Financial Consolidation and Close Cloud functionality in forms and ad hoc grids.
In this release, Smart View extends support to Oracle Enterprise Planning and Budgeting Cloud. Features that are already supported in Oracle Planning and Budgeting Cloud are also supported in Oracle Enterprise Planning and Budgeting Cloud.
In Oracle Smart View for Office User's Guide, if a feature or functionality is supported by Oracle Planning and Budgeting Cloud, then it is also supported by Oracle Enterprise Planning and Budgeting Cloud.
See the Oracle Enterprise Planning and Budgeting Cloud documentation for more information on this new service offering.
You can now quickly add attribute dimensions to an ad hoc sheet using the new Insert Attributes button available in the Planning Ad Hoc ribbon.
Click Insert Attributes to launch the Insert Attributes dialog box, where you can select the attribute members to add to the POV. When the attribute dimensions are in the POV, you can pivot or drag them to the grid as required. Once on the grid, you can use the Remove Only command to remove any unwanted attribute dimension or members.
You can add attribute dimensions at any time during the ad hoc session.
If the grid already contains some, but not all, attribute dimensions in the database, you can click Insert Attributes to select any of the remaining attributes to the POV.
Note that you can still use Member Selection to add specific attribute dimensions as required.
In the Oracle Smart View for Office User's Guide, see “Inserting Attribute Dimensions on the Sheet.”
The usability and readability of forms and ad hoc grids in Oracle Planning and Budgeting Cloud is increased with support for duplicate aliases for members from different dimensions and for members within dimensions.
In brief, the guidelines are:
Duplicate aliases are supported across dimensions and within dimensions.
Aliases can have the same name as a member.
Member names are still required to be unique so that they can be used in rules and form designs to avoid name collisions.
In free-form mode, when referencing an alias that resolves to multiple members, an error is returned noting that the alias cannot be resolved to a single member. You can resolve the alias to the correct member either by using the Member Selector to select the correct alias name or by hand-typing the qualified name. Using the parent member name as a qualifier should be sufficient in most cases, given that only duplicate alias names are supported, not duplicate member names. In the Oracle Smart View for Office User's Guide, see “Duplicate Aliases in Free-Form Mode” for more information.
To use the duplicate alias feature, you must have Smart View 18.104.22.168.600 and you must be connected to Oracle Planning and Budgeting Cloud version 16.06 or later.
In the Planning Admin Extension, you can now work with attribute dimensions and the Time Period dimension. Just as with regular dimensions, you can use the Planning Admin Extension in the Smart View application to quickly import and edit attribute and time dimension application metadata.
For information on using the Planning Admin Extension, see Administering Planning for Oracle Planning and Budgeting Cloud Service on the Oracle Help Center.
To use the features listed here, you will need to install Smart View 22.214.171.124.600 or later, and the updated Oracle Enterprise Performance Reporting Cloud extension for Smart View.
See the Oracle Smart View for Office User's Guide for more information on these features.
Report package variables provide centralized maintenance of common text, numbers and dates that are displayed in doclets throughout a report package. Variables can also be used to reference content between doclets, such as inserting Excel data from a reference doclet into a Word doclet paragraph.
The variables can be created by any report package owner or doclet author, using either Enterprise Performance Reporting Cloud on the web, or the Enterprise Performance Reporting Cloud Extension for Smart View. Smart View is required to define a reference variable value. After the variables are created, use the Variables option in Smart View to insert the variables into a Word doclet (in headers, tables, cells or paragraphs) and Excel doclet cells.
Two types of variables are available:
Static variables use static input that is defined by the user, such as a date label or a set value, which can be used throughout the report package. These static variables can be easily updated, and all inserted instances of the variable value in the doclet reflect the change.
Reference variables are created by referencing another doclet within the report package as the source, and selecting a value for the variable, such as text in a Word paragraph or an Excel cell value. If the source doclet is subsequently updated, those changes are automatically updated in the inserted instances of the variable in the report package.
Reference variables can be used in a number of ways. For example:
Insert Excel cell values into a Word paragraph, such as a Revenue total
Create Excel formulas to implement cross-footing rules for increased data accuracy
Create directional words for the report narrative, such as “an increase” or “a decrease”
After the variables are inserted, view the doclet to ensure all your variables are correctly displayed. There is no indication of the variable location in the final review or signoff document. The variables are displayed in the appropriate text size and font to match the surrounding text.
A doclet author can create their own stylized Microsoft Office Excel reports and then link to the report content in a Word doclet, without adding the file to the report package. In Enterprise Performance Reporting Cloud, this source Excel file is known as a reference file.
A reference file is an Excel file that a doclet author created and saved to a location where they can retrieve it. The reference file contains report content that the author has identified as named ranges using Excel’s Name Manager. The named ranges can then be embedded in a Word doclet. The reference file is attached to a regular doclet and is associated with only that doclet.
To summarize, a doclet author can:
Develop stylized reports within Excel, using Oracle Smart View for Office or other data access methods, and define named ranges on content to be used in a Word doclet
Integrate named ranges within the associated doclet
Easily update the source reference file in Excel and push the updates to the doclet
Incorporate multiple ranges, from the same or different reference files, in the doclet
Embedded content provides an easy way to add stylized content in your published reports.
Using reference doclets as the container where certain types of reporting content is created, authors can then embed that content in their assigned areas of the report package. You can design content such as highly formatted reports, ad hoc grids, and text within an Excel spreadsheet, and add that spreadsheet to the report package as a reference doclet. The available content in a reference doclet becomes common report content that can be embedded in doclets by assigned authors. Embedded content can be reused as required throughout the report package, and is refreshable, so the content will always reflect the latest data.
When connected to Oracle Enterprise Performance Reporting Cloud, you can now import metadata in Word documents, as described in Import Metadata Available for Word.
Use the Cumulative Feature Overview tool to create reports of new features added in prior releases. This tool enables you to identify your current products, your current release version, and your target implementation release version. With a single click, the tool quickly produces a customized set of high-level descriptions of the product features developed between your current and target releases. This tool is available here: