oracle hyperion planning обучение

На протяжении многих лет интернет-магазин предлагает товары и услуги, ориентированные на бизнес-пользователей и специалистов по информационным технологиям.

Хорошие отзывы постоянных клиентов и высокий уровень специалистов позволяет получить наивысший результат при совместной работе.

Источник

Oracle Hyperion Planning 11.1.2 for Interactive Users

Описание курса

Аннотация:

В данном курсе слушатели обучаются использованию Planning. Курс включает обзор особенностей и возможностей Planning и его связи с Essbase. Слушатели учатся создавать формы данных, списки заданий, осуществлять ввод и настройку данных, настраивать вычисления с помощью Calculation Manager, а также move a plan through the budget review and approval process. Помимо работы с формами данных Planning в Smart View, слушатели обучаются открытию текущей формы данных в Smart View из меню Planning путем настройки автоматического подключения к Planning провайдеру. Изучается также создание настраиваемых отчетов с помощью Financial Reporting. Полученные навыки закрепляются на практических занятиях.

Цель курса:

Аудитория:

Требования к подготовке слушателей:

Программа:

Обзор Planning

Управление Workspace

Измерения, данные и безопасность Planning

Создание форм данных и папок

Настройка форм данных

Ввод данных в Planning

Сверка и аннотирование данных

Управление Smart View

Выполнение заданий в Smart View

Создание бизнес-правил в Calculation Manager

Работа с шаблонами бизнес-правил

Настройка бизнес-правил

Настройка процесса подтверждения

Управление процессом подтверждения

Создание списков заданий

Financial Reporting

Создание базовых отчетов

Поддержка деталей и сеток

Форматирование ячеек и сеток

Создание объектов отчета

Добавление текстовых функций

Создание книг

Источник

18 Oracle Hyperion Planning

This chapter describes how to work with Oracle Hyperion Planning in Oracle Data Integrator.

This chapter includes the following sections:

18.1 Introduction

Oracle Data Integrator Adapter for Hyperion Planning enables you to connect and integrate Oracle’s Hyperion Planning with any database through Oracle Data Integrator. The adapter provides a set of Oracle Data Integrator Knowledge Modules (KMs) for loading metadata and data into Planning, Oracle’s Hyperion Workforce Planning, and Oracle’s Hyperion Capital Expense Planning applications.

18.1.1 Integration Process

Loading a Planning application with metadata and data using Oracle Data Integrator Adapter for Hyperion Planning involves these tasks:

Setting up an environment: Defining data servers and schemas

Reverse-engineering a Planning application using the adapter’s Reverse-engineering Knowledge Module (RKM)

Loading metadata and data into the Planning application using the adapter’s Integration Knowledge Module (IKM)

18.1.2 Knowledge Modules

Oracle Data Integrator provides the Knowledge Modules (KM) listed in Table 18-1 for handling Hyperion Planning data. These KMs use Hyperion Planning specific features. It is also possible to use the generic SQL KMs with the Hyperion Planning database.

Table 18-1 Hyperion Planning Knowledge Modules

RKM Hyperion Planning

Reverse-engineers Planning applications and creates data models to use as targets in Oracle Data Integrator mappings.

Each dimension (standard dimension and attribute dimension) is reversed as a datastore with the same name as the dimension with appropriate columns. Creates a datastore named «UDA» for loading UDA’s.

IKM SQL to Hyperion Planning

Loads metadata and data into Planning applications.

18.2 Installation and Configuration

Make sure you have read the information in this section before you start using the Oracle Data Integrator Adapter for Planning:

18.2.1 System Requirements and Certifications

Before performing any installation you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the products you are installing.

The list of supported platforms and versions is available on Oracle Technical Network (OTN):

18.2.2 Technology Specific Requirements

There are no technology-specifc requirements for using the Oracle Data Integrator Adapter for Planning.

18.2.3 Connectivity Requirements

There are no connectivity-specific requirements for using the Oracle Data Integrator Adapter for Planning.

18.3 Setting up Hyperion Planning Adapter

The following sections explain how to set up Hyperion Planning Adapter for ODI Studio and ODI standalone agent.

18.3.1 Setting up Adapter for ODI Studio

Exit from ODI Studio before setting up Hyperion Planning Adapter.

In Oracle Hyperion Planning directory, locate HspJS.jar

If HspJS.jar is not directly accessible by ODI, copy it to a location that allows ODI access.

Modify /odi/studio/bin/odi.conf file to include HspJS.jar.

18.3.2 Setting up Adapter for ODI Standalone Agent

Stop ODI Agent before setting up Hyperion Planning Adapter.

In Oracle Hyperion Planning directory, locate HspJS.jar

Copy it into /lib directory.

For more information, see «Configuring the Domain for the Standalone Collocated Agent» in Oracle® Fusion Middleware Installing and Configuring Oracle Data Integrator

18.4 Setting up the Topology

Setting up the Topology consists of:

18.4.1 Creating an Hyperion Planning Data Server

In the Definition tab:

Name: Enter a name for the data server definition.

Server (Data Server): Enter the Planning application host name and RMI port number in this format: :

Under Connection, enter a user name and password for connecting to the Planning server.

The Test button does not work for a Hyperion Planning data server connection. This button works only for relational technologies that have a JDBC Driver.

18.4.2 Creating an Hyperion Planning Physical Schema

Under a data server, you can define a physical schema corresponding to an application and the logical schemas on which models are based.

Create for this physical schema a logical schema using the standard procedure, as described in «Creating a Logical Schema» of the Oracle Fusion Middleware Developer’s Guide for Oracle Data Integrator and associate it in a given context.

18.5 Creating and Reverse-Engineering a Planning Model

This section contains the following topics:

18.5.1 Create a Planning Model

Create a Planning Model using the standard procedure, as described in «Creating a Model» of the Oracle Fusion Middleware Developer’s Guide for Oracle Data Integrator

18.5.2 Reverse-engineer a Planning Model

Reverse-engineering a Planning application creates an Oracle Data Integrator model that includes a datastore for each dimension in the application. Note that the Year/Period/Version/Scenario are not reverse-engineered.

In the Reverse tab of the Planning Model, select the RKM Hyperion Planning.

The RKM connects to the application (which is determined by the logical schema and the context) and imports the following items:

A datastore for each dimension in the application, with the same name as the dimension

A datastore called UDA, for UDA loading

18.6 Designing a Mapping

After reverse-engineering a Planning application as a model, you can use the datastores in this model as targets of mappings for loading data and metadata into the application.

The KM choice for a mapping determines the abilities and performance of this mapping. The recommendations in this section help in the selection of the KM for different situations concerning Hyperion Planning.

This section contains the following topics:

18.6.1 Loading Metadata

Oracle Data Integrator provides the IKM SQL to Hyperion Planning for loading metadata into a Planning application.

Metadata consists of dimension members. You must load members, or metadata, before you load data values for the members. For example, before loading salary data for five new employees, you load the employees (as members) to the Planning relational database before you load the data to the Oracle’s Hyperion Essbase database.

You can load members only to dimensions that exist in Planning. You must use a separate mapping for each dimension that you load. You can chain mappings to load metadata into several dimensions at once.

Please note the following:

You must refresh the Essbase database after loading the dimension members in the application. The Essbase database is refreshed if you set the REFRESH_DATABASE option in IKM SQL to Hyperion Planning to Yes. See «Load Options» on page 18.

If the REFRESH_DATABASE option in IKM SQL to Hyperion is set to Yes and refresh Essbase database operation fails with an error, the execution is still shown as successful in the Operator tab. However, the errors are reported in the log file. In situations when the Essbase database is not refreshed and the execution is successful in the Operator tab, check the log file for errors.

To load metadata into a Planning application:

Create a mapping. Make sure that you select the IKM SQL to Hyperion Planning on the Flow tab.

Specify the load options as described in Section 18.6.3, «Load Options».

Run the mapping to load the metadata into the application

Validate the dimension:

Log on to Planning Web.

18.6.2 Loading Data

Oracle Data Integrator provides the IKM SQL to Hyperion Planning for loading data into a Planning application.

You can load data into selected dimension members that are already created in Planning. You must set up the Planning, Workforce Planning, or Capital Expense Planning application before you can load data into it.

Before loading data, ensure that the members (metadata) exist in the Planning relational database and the Essbase database. A data load fails if the members do not exist. (This includes the driver member and the members specified in the point of view.) If necessary, load metadata and refresh the Essbase database to synchronize the members.

Before loading data into a Planning, Workforce Planning, or Capital Expense Planning application, you must set up the relevant data load and driver dimensions in Planning. After you set up the data load and driver dimensions in Planning, you must determine the point of view for the members whose data you are loading.

To load data into a Planning application:

In Planning, specify parameters for data to load:

For Available Driver Dimensions, select the dimension to which you are loading data in an Essbase database; for example, select the Account dimension.

Select the members of the driver dimension to load with data.

After the Hyperion Planning data load is set up, use Hyperion Planning RKM to perform the reverse-engineering process. Reverse-engineering retrieves and updates the datastore for the data load dimension with additional columns (fields) required for the data load.

In Oracle Data Integrator Studio, run a mapping for loading data.

You can use the same mapping for loading metadata and data. Section 18.6.3, «Load Options» lists the options of the IKM SQL to Hyperion Planning

Check the Operator log to see if the mapping ran successfully.

To validate the data load, use either method:

Create a Planning data form to retrieve data.

Check Oracle’s Essbase Administration Services to ensure that blocks were created in the appropriate cube.

18.6.3 Load Options

IKM SQL to Hyperion Planning supports these options for defining how Oracle Data Integrator Adapter for Hyperion Planning loads data:

Possible values: Yes or No; default: No If set to Yes, members are loaded in the same order as in the input records.

Possible values: Yes or No; default: No If set to Yes, incoming records are sorted so that all parents are inserted before children.

Possible values: Yes or No; default: No If set to Yes, logging is done during the load process to the file specified by the LOG_FILE_NAME option.

The name of the file where logs are saved; default value:Java temp folder/ dimension.log

Maximum number of errors before the load process is stopped; default value: 0

If set to 0 or a negative number, the load process is not stopped regardless of the number of errors.

Possible values: Yes or No; default: No

If set to Yes, error records are loggedto the file specified by the ERROR_LOG_FILE property.

The name of the file where error records are logged; default value: Java temp folder/ dimension.err

The column delimiter used for the error record file; default value: comma (,)

The row delimiter used for the error record file; default value: \r\n

Row and column delimiters values can also be specified in hexadecimal. A value that starts with 0x is treated as hexadecimal; for example, 0x0041 is treated as the letter A.

The text delimiter to be used for the column values in the error record file

Possible values: Yes or No; default: Yes

If set to Yes, the row header (with all column names) is logged in the error records file.

If set to Yes, completion of the load operation invokes a cube refresh.

Possible values: Yes or No; default: No

18.7 Datastore Tables and Data Load Columns

IKM SQL to Hyperion Planning loads columns in tables to create datastores. The following topics describe the columns in each datastore:

Data Load Columns are columns used for loading data into dimensions.

18.7.1 Accounts

Table 18-2 describes the columns of the Accounts table. See Section 18.7.7, «Data Load Columns» for descriptions of additional columns that are displayed for loading Account dimension data if the application has been set up for data load in Planning.

Table 18-2 Accounts

Takes the name of the account member you are loading. If this member exists, its properties are modified; otherwise, the record is added. This field is required.

The value for this field must meet these requirements:

Not more than 80 characters

Member name cannot contain tabs, double quotation marks («), or backslash (\) characters.

This value is passed as a string.

Takes the name of the parent of the member you are loading. It is used to create the hierarchy in the dimension.

When you load data for a member and specify a different parent member that from the parent member in the application, the member is updated with the parent value that you specify.

Example: If Member 1 has a parent value of Member A in your Planning application and you load Member 1 with a parent value of Member B, your application is updated, and Member B becomes the parent of Member 1. Member 1 and its descendants are moved from Member A to Member B. If the column is left blank, it is ignored during the load.

The record is not loaded if one of the following situations occurs:

The specified parent is a descendant of the member that you are loading.

The specified parent does not exist in the Planning application.

Takes an alternate name for the member being loaded. If you are modifying properties and do not specify a value, the alias is not changed in the Planning application. If you specify or as the value, the alias in the Planning application is deleted.

The value for this column must meet the following requirements for a successful load:

Not more than 80 characters

Member name cannot contain tabs, double quotation marks («), or backslash (\) characters.

This value is passed as a string; default value: a null string.

Can take an alternate name for the member being loaded. There will be as many Alias columns as there are Alias tables defined in Planning. The value for multiple alias columns must conform to the same requirements as those listed for the default alias column.

Takes the storage attribute for the member being loaded.

Dynamic Calc and Store

Never Share (default)

This value is passed as a string.

Two Pass Calculation

Boolean value to indicate whether the member being loaded has the Two-Pass Calculation associated attribute. Valid values: 0 for False (default), or any other number for True. Values are valid only when the Data Storage value is Dynamic Calc or Dynamic Calc and Store; otherwise, the record is rejected.

Takes the account type of the member that is being loaded. Valid values: Revenue, Expense, Asset, Liability, Equity, and Saved Assumption. The default is taken from the parent of the member that is being loaded, or it is Expense if the member is being added to the root dimension.

Takes a type for members with an account type of Saved Assumption only or when the record is rejected. Valid values: Flow, First, Balance, Average, and two averaging options, Actual_365 and Actual_Actual. (Actual_365 assumes the actual number of days in each month and 28 days in February; Actual_Actual accounts for 29 days in February during leap years.)

The default is taken from the parent of the member being loaded or is Flow if the member is being added to the root dimension. This value is passed as a string. Default values of Time Balance for Account types:

Note: When Time Balance is Flow, records with any valid Skip Values are loaded, but Skip Value is disabled for all account types.

Skip ValueTakes the skip option that is set for the Time Balance property. When the Time Balance property is set to First, Balance, or Average, these Skip options are available:

None-Indicates that zeros and #missing value are considered when the parent value is calculated

Missing-Excludes #missing values when calculating parent values

Zeros-Excludes zero values when calculating parent values

Missing and Zeros-Excludes #missing and zero values when calculating parent values

Note: When Time Balance is Flow, records with any valid Skip Values are loaded, but Skip Value is disabled for all Account types.

Takes the data storage value. Valid values:

Currency-Stores and displays the member’s data value in the default currency.

Non-currency-Stores and displays the member’s data value as a numeric value.

Percentage-Stores data values as a numeric value and displays the member’s data value as a percentage.

Smart list / enumeration-Stores data values as a numeric value and displays the member’s data value as a string.

Date-Stores and displays the member’s data value in the format mm/dd/yyyy or dd/ mm/yyyy

Text-Stores and displays the member’s data value as text.

Unspecified-Stores and displays the member’s data value as «unspecified.»

The default value is taken from the parent of the member being loaded or is Currency if the member is being added to the root dimension.

Exchange Rate Type

Takes the exchange rate. This column is dependent on the value specified for the Data Type column. Valid values:

Average, Ending, and Historical when Data Type is equal to Currency

None when Data Type is equal to Non-currency or Percentage

This value is passed as a string. The default value is taken from the parent of the member that is being loaded or, if the member is being added to the root dimension, is based on the account type and takes the following values:

Indicates the distribution selected in the Planning application. If the application has no distribution, this column is not displayed.

Valid values are 0 and 1 (or any number other than 0); default value: 1.

Takes a value for account members with an account type of Saved Assumption or if the record is rejected. Valid values:

Expense-designates the saved assumption as an expense. The actual amount is subtracted from the budgeted amount to determine the variance.

Non-Expense-designates the saved assumption as revenue. The budgeted amount is subtracted from the actual amount to determine the variance.

This value is passed as a string. The default value is taken from the parent of the member being loaded or, if the member is being added to the root dimension, is based on the value of the count type.

For Account types, the value is set to the following:

Takes a plan type name for the plan type assigned to the member being loaded. Valid values are any plan types specified in Planning application.

This value is passed as a string. The default is taken from the parent of the member being loaded. If the source plan of the parent is not valid for the member, the specified plan type is not selected for the member in the application, and the first plan type that the member is used in is used. If the member is being loaded to the root dimension, the first plan type the member is used in is used.

When you update or save the parent of a member, the system verifies if the Source Plan Type associated with the member being loaded is valid for the new parent. If the member’s source plan type is not a valid plan type of its parent member, you receive the error message, «The source plan type is not in the subset of valid plan types.»

If the source plan type of a member is valid for the parent member but not for the member itself, the member is saved but its source plan type is set to the first valid plan type (in the order Plan 1, Plan 2, Plan 3, Wrkforce, Capex).

Note: If a Source Plan Type is specified in the adapter but is not valid for the parent, the record is rejected.

Boolean value that indicates if the member being loaded is used in Plan1. Valid values are 0 for False and any other number for True. The default value is True. The name of the column varies depending on the name of the plan type in the Planning application.

Takes the aggregation option for the member being loaded as related to Plan1. This column is available only ifthe Planning application is valid for this plan type. The name of the column varies depending on the name of the plan type in the Planning application.

This value is passed as a string. Valid values:

Источник

• ← opigno система дистанционного обучения
• oracle pl sql обучение →