Load Options Click Sav
22.6 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: ■ Accounts ■ Employee ■ Entities ■ User-Defined Dimensions ■ Attribute Dimensions ■ UDA Data Load Columns are columns used for loading data into dimensions.22.6.1 Accounts
Table 22–2 describes the columns of the Accounts table. See Section 22.6.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 22–2 Accounts Column Description Account 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: ■ Unique ■ Alphanumeric ■ Not more than 80 characters ■ Member name cannot contain tabs, double quotation marks , or backslash \ characters. ■ Member name cannot start with any of these characters: \ | , = _ + - { } . ■ Value must not be an Essbase reserved word such as Children, Parent, UNIVERSE , MISSING, or MI. For more information about reserved words in Essbase, see the Hyperion Essbase - System 9 Database Administrators Guide or Essbase online help. This value is passed as a string. 22-8 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator Parent 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. Default Alias 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 NONE or none 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: ■ Unique ■ Alphanumeric ■ Not more than 80 characters ■ Member name cannot contain tabs, double quotation marks , or backslash \ characters. ■ Member name cannot start with any of these characters: \ | , = _ + - { } . ■ Value must not be an Essbase reserved word such as Children, Parent, UNIVERSE , MISSING, or MI. For more information about reserved words in Essbase, see the Hyperion Essbase - System 9 Database Administrators Guide or Essbase online help. This value is passed as a string; default value: a null string. Additional Alias 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. Data Storage Takes the storage attribute for the member being loaded. Valid values: ■ Store ■ Dynamic Calc ■ Dynamic Calc and Store ■ Shared ■ Never Share default ■ Label Only This value is passed as a string. Table 22–2 Cont. Accounts Column Description Oracle Hyperion Planning 22-9 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. Account Type 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. Time Balance 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: ■ Revenue-Flow ■ Expense-Flow ■ Asset-Balance ■ Liability-Balance ■ Equity-Balance Note: When Time Balance is Flow, records with any valid Skip Values are loaded, but Skip Value is disabled for all account types. Skip Value 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. Table 22–2 Cont. Accounts Column DescriptionParts
» Oracle Fusion Middleware Online Documentation Library
» Terminology Using This Guide
» Concepts Knowledge Modules Introduction
» System Requirements and Certifications
» Using External Tables Technology Specific Requirements
» Using Oracle Streams Technology Specific Requirements
» Connectivity Requirements Installation and Configuration
» Creating an Oracle Physical Schema
» Setting Up an Integration Project
» Reverse-engineer an Oracle Model
» Setting up Changed Data Capture
» Designing an ETL-Style Interface
» Troubleshooting Oracle Database Errors Common Problems and Solutions
» System Requirements and Certifications Technology Specific Requirements
» Creating a File Physical Schema
» In the Models accordion, right click your File Model and select New Datastore.
» In the editor toolbar, click Reverse-Engineer.The Columns Setup Wizard is
» Click OK when the columns definition is complete. From the File main menu, select Save.
» In the Definition Tab, enter the following fields:
» Go to the Files tab to describe the type of file. Set the fields as follows:
» In the toolbar menu, click Reverse Engineer COBOL CopyBook.
» Click OK. COBOL Copybook reverse-engineering
» Create an ODBC Datasource for the Excel Spreadsheet
» Define the Data Server, Physical and Logical Schema for the Microsoft Excel
» Run the customized reverse-engineering
» Select the Microsoft Excel Driver .xls driver.
» Name the data source: ODI_EXCEL_FILE_REPO and select the file
» In Topology Navigator, add a Microsoft Excel data server with the following
» From the File main menu, select Save.
» Add a physical schema to this data server. Leave the default values in the
» In the Context tab of the physical schema, click Add.
» In the new line, select the context that will be used for reverse engineering and
» In the Reverse-Engineer Tab, set the following parameters:
» In the toolbar menu, click Reverse-Engineer.
» Technology-Specific Requirements Installation and Configuration
» Reverse-engineer a Data Model
» Loading Data from an ANSI SQL-92 Compliant Technology
» Loading Data to an ANSI SQL-92 Compliant Technology
» Integrating Data in an ANSI SQL-92 Compliant Technology
» System Requirements Installation and Configuration
» Technologic Specific Requirements Installation and Configuration
» Creating a Physical Schema for XML
» Reverse-Engineering an XML Model
» Synchronizing XML File and Schema
» Loading Data from an XML Schema
» Loading Data to an XML Schema
» Detect the Errors Coming from XML Common Errors
» Creating a Complex File Physical Schema
» Designing an Interface Oracle Fusion Middleware Online Documentation Library
» Using the BULK INSERT Command
» Using Linked Servers Technology Specific Requirements
» Creating a Microsoft SQL Server Physical Schema
» Create a Microsoft SQL Server Model
» Reverse-engineer a Microsoft SQL Server Model
» Loading Data from Microsoft SQL Server
» Integrating Data in Microsoft SQL Server
» Creating a Microsoft Excel Data Server
» Creating a Microsoft Excel Physical Schema
» Setting up Data Quality Setting Up an Integration Project
» Create a Microsoft Excel Model
» Reverse-engineer a Microsoft Excel Model
» Loading Data from Microsoft Excel
» Loading Data to Microsoft Excel
» Decoding Error Messages Common Problems and Solutions
» Specific Requirements Oracle Fusion Middleware Online Documentation Library
» Creating a Netezza Physical Schema
» Reverse-engineer a Netezza Model
» Loading Data from Netezza Loading Data to Netezza
» Creating a Teradata Physical Schema
» Reverse-engineer a Teradata Model
» Loading Data from Teradata Loading Data to Teradata
» Integrating Data in Teradata
» Primary Indexes and Statistics
» Support for Teradata Utilities Support for Named Pipes Optimized Management of Temporary Tables
» Creating a Hypersonic SQL Data Server
» Creating a Hypersonic SQL Physical Schema
» Setting up Changed Data Capture Setting up Data Quality Designing an Interface
» Introduction Oracle Fusion Middleware Online Documentation Library
» Concepts Knowledge Modules Oracle Fusion Middleware Online Documentation Library
» Creating a DB2400 Physical Schema
» Reverse-engineer an IBM DB2400 Model
» Setting up Trigger-Based CDC
» CDCRTVJRN Program Details Setting up Log-Based CDC
» Using the CDC with the Native Journals
» Problems While Reading Journals
» Loading Data from IBM DB2 for iSeries
» Loading Data to IBM DB2 for iSeries
» Integrating Data in IBM DB2 for iSeries
» Installing the Run-Time Agent on iSeries
» Using Client Access Alternative Connectivity Methods for iSeries
» Change the driver and URL to your AS400 server with the following information:
» Set the following java properties for the java machine the run-time agent deployed
» Troubleshooting Error messages Troubleshooting
» Connection Errors Common Problems and Solutions
» Integrating Data in Oracle BI
» Extracts the OBIEE Metadata from a OBIEE Instance
» Using the Lineage Lineage Lifecycle
» Installation Overview Installing the Lineage in an OBIEE Server
» Requirements Installing the Lineage in an OBIEE Server
» Post-Installation Tasks Installing the Lineage in an OBIEE Server
» Exporting the OBIEE Repository Documentation to a Text File
» Exporting the OBIEE Web Catalog Report to a Text File
» Refreshing the OBIEE Lineage From Existing Exports
» Configuring the Scripts Automating the Lineage Tasks
» Automating Lineage Deployment Automating Lineage Refresh
» Viewing Execution Statistics Viewing and Filtering Lineage Data
» Using the Dashboard Using the Lineage in OBIEE Dashboards
» Using Lineage and Hierarchy Using Contextual Lineage
» Reverse-engineer an Essbase Model
» Loading Metadata Designing an Interface
» Loading Data Designing an Interface
» Data Extraction Methods for Essbase
» Extracting Essbase Data Extracting Data
» Extracting Members from Metadata
» Creating an Hyperion Financial Management Data Server
» Creating an Hyperion Financial Management Physical Schema
» Create an Financial Management Model
» Reverse-Engineer an Financial Management Model
» Extracting Financial Management Data
» Extracting Members from Member Lists
» Data Store Tables Oracle Fusion Middleware Online Documentation Library
» Creating an Hyperion Planning Data Server
» Creating an Hyperion Planning Physical Schema
» Reverse-engineer a Planning Model
» Log on to Planning Web. Select Administration Data Load Administration.
» Accounts Datastore Tables and Data Load Columns
» Employee Datastore Tables and Data Load Columns
» Entities Datastore Tables and Data Load Columns
» User-Defined Dimensions Datastore Tables and Data Load Columns
» Attribute Dimensions Datastore Tables and Data Load Columns
» JMS Message Structure Concepts
» Creating a JMS Physical Schema
» Create a JMS Model Defining the JMS Datastores
» Loading Data from a JMS Source Integrating Data in a JMS Target
» Declaring JMS Properties Using JMS Properties
» Using Property Values as Source Data
» Setting Properties when Sending a Message
» Creating a JMS XML Physical Schema
» Reverse-Engineering a JMS XML Model
» Loading Data from a JMS XML Source Integrating Data in a JMS XML Target
» Creating a Physical Schema for LDAP
» Reverse-Engineering an LDAP Model
» Loading Data from an LDAP Directory
» Loading Data to an LDAP Directory
» Integrating Data in an LDAP Directory
» Setting Up an Integration Project Troubleshooting
» Creating a TimesTen Physical Schema
» Reverse-engineer a TimesTen Model
» Setting Up an Integration Project Setting up Data Quality
» Integrating Data in TimesTen
» Create an Attunity Stream Model Reverse-engineer an Attunity Stream Model
» Setting Up an Integration Project Designing an Interface Using the LKM Attunity to SQL
» Overview of the GoldeGate CDC Process
» Create the Staging Physical Schema
» Define the Source Data Server
» Create the Source Physical Schema
» Create the Replicated Tables
» Set Up an Integration Project
» Configure CDC for the Replicated Tables
» Configure and Start Oracle GoldenGate Processes
» Design Interfaces Using Replicated Data
» Initial Load Method Advanced Configuration
» Tuning Replication Performances Advanced Configuration
» One Source Multiple Staging Configuration
» Cross Reference Table Structures
» Loading Phase LKM Overview of the SOA XREF KM Process
» Defining the Topology Working with XREF using the SOA Cross References KMs
Show more