Applix TM1 Client 2.6 PDF

Applix TM1 Client
Applix, Inc. 1997. All Rights Reserved. Applix TM1 Client - Version 2.6 Part # TM1CLNT2.6 Applix, Inc. prepared the information contained in this document for use by Applix personnel, customers, and prospects. Applix reserves the right to change the information in this document without prior notice. The contents herein should not be construed as a representation or warranty by Applix. Applix assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used only in accordance with the terms of such license. Data Control for TM1, TM1 and Perspectives are trademarks of Applix Inc. IBM is a trademark of International Business Machines Corporation. Microsoft is a registered trademark and Windows is a trademark of Microsoft Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraphs (c) (1) (ii) of SFARS 252.277-7013, or in FAR 52.227-19, as applicable.
Print Date: 6/97
Contents
Preface
Client PC Hardware Requirements........................................... ix Client PC Software Requirements ...............................................x About This Manual.......................................................................x Conventions Used in This Manual ............................................ xi How This Manual is Organized................................................ xii Applix TM1 Documentation .................................................... xiii Support Services ....................................................................... xiv
Chapter 1
Basic Concepts
The TM1 Client Approach ....................................................... 1-1 The Cube.................................................................................... 1-2 Reference By Name............................................................ 1-3 Multiple Dimensions ......................................................... 1-4 Automatic Consolidation .................................................. 1-5 The Slice: From Many Dimensions to Two............................. 1-6 Client/Server Architecture ...................................................... 1-8 Client and Server................................................................ 1-8 TM1 Client Administration...................................................... 1-9 Privileges ...........................................................................1-10
iii
Transaction Logging ............................................................... 1-11
iv
Applix TM1 Client
Chapter 2
Tutorial
Loading TM1 in Excel............................................................... 2-1 Turning Off Automatic Recalculation..................................... 2-2 Setting the Reference Style ....................................................... 2-2 Loading TM1 in Lotus 1-2-3..................................................... 2-3 Turning Off Automatic Recalculation..................................... 2-3 Logging On................................................................................ 2-4 Changing Your Password ........................................................ 2-5 Viewing Cube Data................................................................... 2-6 The Default View ............................................................... 2-7 The Browse Dialog Box ..................................................... 2-7 Changing Elements Displayed.......................................... 2-8 Double-Click Drill Down .................................................. 2-8 Displaying Consolidated Values....................................... 2-9 Changing Perspectives......................................................2-10 Entering Data ...........................................................................2-11 Privileges and Entering Data ...........................................2-13 The CALC Flag..................................................................2-13 Creating a Slice Worksheet .....................................................2-14 Changing Elements Used to Retrieve Data.....................2-15 Changing the Cube Reference in a Slice Worksheet.......2-17 Saving the Slice Worksheet .....................................................2-18 Cube References.......................................................................2-18 Writing a Cube Reference.................................................2-20 Reserving and Locking Values in the Database ....................2-23
Contents
Setting Network Options........................................................ 2-26 Connecting to Multiple Servers ............................................. 2-27 Disconnecting From All TM1 Servers ................................... 2-27
Chapter 3
Worksheet Functions
DBGEN(Type,Value,Cube,K1,K2[,K8]) ............................... 3-2 Arguments .......................................................................... 3-2 Example............................................................................... 3-2 DBGEN16(Type,Value,Cube,K1,K2[,K16]).......................... 3-3 Arguments .......................................................................... 3-3 Example............................................................................... 3-3 DBRn(Cube,K1,K2[,...Kn])........................................................ 3-4 Arguments .......................................................................... 3-4 Example............................................................................... 3-4 DBRWn(Cube,K1,K2[,...Kn]) .................................................... 3-5 Arguments .......................................................................... 3-5 Example............................................................................... 3-5 DBRX(Handle,Cube,K1,K2[,...Kn]) .......................................... 3-6 Arguments .......................................................................... 3-6 Example............................................................................... 3-6 DBSn(Value,Cube,K1,K2[,...Kn]).............................................. 3-7 Arguments .......................................................................... 3-7 Example............................................................................... 3-8 DBSSn(String,Cube,K1,K2,...Kn).............................................. 3-8 Arguments .......................................................................... 3-8 Example............................................................................... 3-9
vi
Applix TM1 Client
DBSWn(Cube,K1,K2[,...Kn])..................................................... 3-9 Arguments .......................................................................... 3-9 Example .............................................................................3-10 DFRST(Dimension)..................................................................3-10 Argument...........................................................................3-10 Example .............................................................................3-10 DIMIX(Dimension,Element) ...................................................3-11 Arguments .........................................................................3-11 Example .............................................................................3-11 DIMNM(Dimension,Index).....................................................3-11 Arguments .........................................................................3-12 Example .............................................................................3-12 DIMSIZ(Dimension) ................................................................3-12 Argument...........................................................................3-12 Example .............................................................................3-12 DNEXT(Dimension,Element)..................................................3-13 Arguments .........................................................................3-13 Example .............................................................................3-13 DNLEV(Dimension) ................................................................3-13 Argument...........................................................................3-13 Example .............................................................................3-14 DTYPE(Dimension, Element) .................................................3-14 Arguments .........................................................................3-15 Example .............................................................................3-15 ELCOMP(Dimension,Element,Index) ....................................3-15
Contents
vii
Arguments ........................................................................ 3-15 Example............................................................................. 3-16 ELCOMPN(Dimension,Element)........................................... 3-16 Arguments ........................................................................ 3-16 Example............................................................................. 3-16 ELISCOMP(Dimension,Element1,Element2)........................ 3-17 Arguments ........................................................................ 3-17 Example............................................................................. 3-17 ELISPAR(Dimension,Element1,Element2)............................ 3-18 Arguments ........................................................................ 3-18 Example............................................................................. 3-18 ELLEV(Dimension,Element) .................................................. 3-19 Arguments ........................................................................ 3-19 Example............................................................................. 3-19 ELPAR(Dimension,Element,Index) ....................................... 3-20 Arguments ........................................................................ 3-20 Example............................................................................. 3-20 ELPARN(Dimension,Element)............................................... 3-21 Arguments ........................................................................ 3-21 Example............................................................................. 3-21 ELSLEN(Dimension,Element)................................................ 3-21 Arguments ........................................................................ 3-21 Example............................................................................. 3-22 ELWEIGHT(Dimension,Element,Component)..................... 3-22 Arguments ........................................................................ 3-22
viii
Applix TM1 Client
Example .............................................................................3-22 SUBNM(Dimension,Subset,Index) .........................................3-23 Arguments .........................................................................3-23 Example .............................................................................3-23 SUBSIZ(Dimension,Subset).....................................................3-24 Arguments .........................................................................3-24 Example .............................................................................3-24 TABDIM(Cube,Index) .............................................................3-24 Arguments .........................................................................3-25 Example .............................................................................3-25 VIEW(Cube,K1,K2,......Kn,) .....................................................3-25 Arguments .........................................................................3-26 Example .............................................................................3-26
Chapter 4
Macro Functions
Accessing Macro Functions...................................................... 4-2 Accessing Macro Functions from Excel Versions 5 and 74-2 Accessing Macro Functions from Excel Version 8 .......... 4-3 Accessing Macro Functions from VBA ............................ 4-4 Accessing Macro Functions from Lotus 1-2-3.................. 4-4 Function Descriptions............................................................... 4-5
Appendix A
Error Messages
General Errors .......................................................................... A-1 Dimension Error Messages ..................................................... A-5 Network Error Messages ........................................................ A-9
Contents
ix
Rules Error Messages............................................................. A-16 System Error Messages.......................................................... A-18 Cube Error Messages ............................................................. A-19
Index
Applix TM1 Client
Preface
TM1 Client enables you to integrate the popular Microsoft Excel or Lotus 1-2-3 spreadsheets with the powerful TM1 Server multidimensional On-Line Analytical Processing (OLAP) engine. This structure forms the ideal client/server architecture for planning, analysis, reporting, budgeting and other decision support tasks. TM1 Client lets you access the shared on-line analytical server with full security to use and/or create multi-dimensional spreadsheets, and to conduct extensive analyses with the TM1 Browse feature.
Client PC Hardware Requirements

In determining the hardware requirements for the client PC, you should adhere to the requirements set forth by Lotus and Microsoft for their spreadsheets. Minimum hardware configurations to run TM1 Client on Excel Version 5.x or 7.x and Lotus 1-2-3 Release 5 are a 386 or greater microprocessor and 8Mb of RAM. Minimum hardware configurations to run TM1 Client on Excel Version 8.0 are a 386 or greater microprocessor and 16Mb of RAM. See the Applix TM1 Server manual for information about server requirements.
ix
Client PC Software Requirements
Client PC Software Requirements

TM1 Client runs on Windows 95, NT 3.51, and NT 4.0. TM1 Client Version 2.6 supports Microsoft Excel Versions 5, 7, and 8, as well as Lotus 1-2-3 Release 5.
About This Manual

This guide is written for people who will be using Applix TM1 Client to access data on a TM1 Server. It explains how to connect to TM1 Servers, and provides descriptions and explanations of all TM1 Client features.
Applix TM1 Client
Conventions Used in This Manual
Conventions Used in This Manual

The following typeface conventions are used throughout this manual: Helvetica Helvetica text indicates that this option or object appears in the document window. For example, Type the name of the document in the File name entry area. File names, keys, directories, functions, and formulas/functions are also indicated by Helvetica text. Helvetica Bold Bold Helvetica text indicates an option to chose or text to type. It usually appears in numbered steps. Words are italicized for emphasis or to draw your attention to a new term. For example, Do not press the RETURN key, or This action is called word wrapping. Whenever you see a reference to a menu option, the option is identified using the following notation: Menu Name Option Name For example, "Choose File Save."
Italics
Menu Name Option Name
Preface
xi
How This Manual is Organized
Certain actions require you to select cells in a worksheet. This guide uses the term click-select for this operation. To click-select: In Excel, double click on the cell.
In 1-2-3, click once on the cell and press <Ins>.
How This Manual is Organized

Chapter 1 Basic Concepts provides an overview of TM1 Client and explains basic concepts you need to know to use TM1 effectively. Tutorial provides step-by-step instructions for using the TM1 Client with Excel or Lotus 1-2-3. Worksheet Functions provides descriptions of all worksheet functions. Macro Functions provides descriptions of all macro functions. Error Messages describes TM1 error messages.
Chapter 2 Chapter 3 Chapter 4 Appendix A
xii
Applix TM1 Client
Applix TM1 Documentation
Applix TM1 Documentation

In addition to this manual, there are several other manuals to which you may want to refer. TM1 Perspectives Describes the powerful TM1 Perspectives Online Analytic Processing (OLAP) product for Microsoft Excel. This product allows you to quickly retrieve and analyze multidimensional data from the TM1 database. Describes the TM1 Server, which services requests for data from TM1 client programs such as TM1 Perspectives. The server stores and maintains data, and acts as a bridge between the client software and your data warehouse. Data Control is a powerful program for managing the data processing activities of an Applix TM1 application. Data Control combines TM1s multidimensional database engine, direct ODBC access to source data, and the richness of the Microsoft Excel environment to give the developer control and flexibility to manage the back-end functions of a TM1 application. This manual describes all the functions and features of the TM1 API 2.0. The API provides complete access to all the features and functionality of the TM1 OLAP engine. The API is designed for use with C, C++, and Microsoft Visual Basic.
TM1 Server
TM1 Data Control
TM1 API 2.0
Preface
xiii
Support Services
Support Services
Applix, Inc. provides a wide range of support services, including: Training classes Consulting Services Held at local sites, at the Applix corporate headquarters, or at your facility. To cover issues such as application design, performance tuning and site-specific requirements. Several different service programs are available. (Please contact your account manager.)
Technical Services
Applix also sponsors local and national user group meetings, a periodic newsletter, and the hosting of customer advisory committees. For more information about these services, please contact us via telephone at (508) 870-0300, via fax at (508) 366-0995, or via electronic mail at support@applix.com.
xiv
Applix TM1 Client
Basic Concepts
The TM1 Client Approach
With traditional spreadsheets, data is tied to the spreadsheet. New data requires a new spreadsheet, and common data must be entered separately into each spreadsheet. TM1 Client solves these problems by storing data not in the spreadsheet, but in separate database files called cubes. Cubes reside on a separate computer called the TM1 Server. Client spreadsheets on the network read and write cube values by communicating with this server. Each piece of data is stored only once in the database cube and can be accessed simultaneously by any number of Client computers and spreadsheets connected to the TM1 Server.
The Cube
The following figure shows the client/server architecture.
The Cube
A TM1 cube is a type of database. However, unlike other databases you may be familiar with, it is specially designed for the operations that spreadsheet applications typically need. Like a spreadsheet, a cube is an array of values; unlike a spreadsheet, a cube references data by name, is multidimensional, and provides automatic consolidation.
Applix TM1 Client
The Cube
Reference By Name
A TM1 cube is made up of dimensions. A dimension is a list of labels or elements. To identify a value in a cube, TM1 Client uses element names (for example, California, Telephone, and March). Values from cubes are retrieved by a series of functions provided with TM1 Client. For example, to retrieve the amount budgeted in California for telephone expenses in March from the xbudget cube, you could write: =DBR(xbudget, California, Telephone, March) When this function is executed, the spreadsheet client sends a message requesting data from the TM1 Server using these names, and the TM1 Server responds by returning the value. The value returned becomes the value of the function. The following figure illustrates this concept.
This and other functions are covered in more detail in later chapters and in Appendix A.
Basic Concepts
The Cube
Multiple Dimensions
A cell in most stand-alone spreadsheets is identified by a row and a column. A single spreadsheet, much like a report, is twodimensional. Most current spreadsheet products support three-dimensional spreadsheets or workbooks, where cells are identified by a row, a column, and a page. Such spreadsheets can be useful when similar spreadsheets need to be linked together. For example, if divisions in a company each make an expense report in identical form, the reports can be stored behind one another, like pages in a book, rather than in separate files. You need three dimensions to compare data in three different ways. In the example stated above, you have three dimensions, or aspects of comparison: LOCATION EXPENSE MONTH to compare expenses in different regions. to compare different categories of expenses. to compare expenses from month to month.
Applix TM1 Client
The Cube
As long as you want to compare data in only three ways, three dimensions are sufficient. However, analysts often break up data in four ways or more. For example, you may also want to look at data by division. In this case, you introduce a fourth aspect of comparison the data becomes four-dimensional. It is easy to imagine the need to compare budgeted numbers to actual numbers, resulting in a fifth dimension. Although you cannot visualize an object with more than three physical dimensions, its not necessary to visualize the data in order to work with it. Analysts work with multidimensional data all the time. No three-dimensional spreadsheet can handle such a situation. However, a TM1 cube can be created with up to 16 dimensions, allowing a wide variety of possible analyses.
Automatic Consolidation
TM1 lets you define some dimension elements as calculated elements, which are totals of other elements. Thus, a dimension for months could be arranged with calculated elements as shown in the following illustration.
Basic Concepts
The Slice: From Many Dimensions to Two
When a spreadsheet calls for a value using the name Second Qtr, the TM1 server automatically adds up the corresponding values for April, May, and June. If the spreadsheet calls for a value using the name Total Year, the TM1 server adds up the values for all quarters. The TM1 database is specially designed to do this type of calculation at high speed.

Multiple dimensions are essential for analysis. However, to write reports or to display data in a spreadsheet, you must represent data in a two-dimensional model a paper report or a spreadsheet.
Applix TM1 Client
The most common way to select two-dimensional data from a TM1 cube is by slicing the cube. Slicing a cube assigns the elements of one dimension to the rows of a spreadsheet and the elements of another dimension to the columns of the spreadsheet. Other dimensions are held constant for some selected elements. For example, if you have a three-dimensional cube comprised of the dimensions Months, Accounts, and Locations, some possible slices of this cube are: Columns MONTHS, rows ACCOUNTS, displaying data for a selected location. This is the normal format of an income statement. Columns MONTHS, rows LOCATIONS, displaying data for a selected account. This might be used, for example, to compare sales at each location. Columns LOCATIONS, rows ACCOUNTS, displaying data for a selected month. This might be used to compare entire income statements for a month.
The principle remains the same for a four-dimensional cube. Two dimensions are laid out along the rows and columns, and each of the other two is held constant for selected element. If the cube also has a DIVISION dimension, some possible slices might be: Columns MONTHS, rows LOCATIONS, displaying data for one division and one account. Columns DIVISIONS, rows LOCATIONS, displaying data for one account and one month. Columns MONTHS, row DIVISIONS, displaying data for one location and one account.
Basic Concepts
Client/Server Architecture
If you do financial reporting, you have probably learned the hard way that management often asks for reports not accommodated by your applications. Very often, these reports are different slices of the same data. Using TM1 Client, such reports are easy to produce.
Client/Server Architecture
TM1 Client is designed with a client/server architecture. This architecture allows for a much more efficient use of computer resources. Operations such as the management of large amounts of data and the complex handling of millions of numbers requires high computing speed and large amounts of memory. These operations are assigned to a central, more powerful server computer. In turn, operations such as reporting and analysis require less computing power and can be assigned to less powerful client computers. In effect, the less powerful client computers share the resources of a more powerful server across a network.
Client and Server

As the term client/server implies, two different types of software are required to run the TM1 Client: the server and the client software.
The TM1 Server

The TM1 Server allows a client to access shared cube data. The server, when running, loads all cubes and dimensions specified by the administrator into memory. TM1 Server software performs three basic functions:
Applix TM1 Client
TM1 Client Administration
It manages data and consolidations in RAM (and on paging drives) and responds to data requests from clients. It manages security, granting or denying access to database values. It maintains a log of changes (transaction log) to the database.
The Client
As a client, you interact with the TM1 Server through a spreadsheet program. TM1 Client comes with add-in modules that work with industry-standard spreadsheet products. TM1 Clients capabilities are fully integrated with the spreadsheet interface with which you are most familiar. When you invoke the TM1 Client, a TM1.ADM file returns a list of available TM1 Servers on the network. With the correct server name, user ID, and password, TM1 Client allows you to log on to the server and access the data in its memory. A single TM1 Client can simultaneously log on to up to nine servers on a network.

An administrator manages the TM1 Client installation. Before you can use TM1 Client, the administrator must set you up as a client. TM1 Client cubes are loaded into the memory of the TM1 server computer. This provides instant access to the data. The server must be up and running before you can access cubes. The administrator determines which cubes are loaded on the server. The administrator also defines which cubes individual clients can read or update. Read and update privileges can also be assigned by dimension element. These and other administration functions are fully described in the Applix TM1 Server manual.
Basic Concepts
Privileges
The TM1 Server provides a multi-user environment, and must therefor provide strict security access to its data. When you log on to a TM1 Server, TM1 Client determines your ability to read or update data in cubes based on privileges assigned by the administrator. The following levels of privileges can be assigned to a cube or dimension element: NONE Client cannot view or update values. Viewing a cube with values to which you have no access will display N/A for those values. Client can view values but not change them. Client can view and change values. Client can view and change values. In addition, Client can temporarily reserve values so that no one else can work with them. Client can view, change, and reserve values. In addition, Client can permanently lock values so that they can no longer be changed.
READ WRITE RESERVE
LOCK
There is no UNLOCK privilege. Values can be unlocked only by the administrator.
10
Applix TM1 Client
Transaction Logging
Transaction Logging
TM1 Client provides backup, recovery, and control capabilities by means of the transaction log. Whenever a value in a cube is changed, TM1 Client writes a record to a log file stating: the time of the change the client performing the change the value before the change the value after the change the name of the cube and dimension elements that identify the value
The administrator uses this log file to recover the database in the event of computer failure. Also, the administrator can selectively undo changes made by one client or a group of clients. If you need to revert changes you have made, see your administrator.
Basic Concepts
11
Transaction Logging
12
Applix TM1 Client
2 - Tutorial
TM1 Client lets you connect to the TM1 Server using Excel or Lotus 1-2-3. This chapter takes you step-by-step through the basic features of TM1 Client. It assumes that the administrator has set you up to use TM1 Client. TM1 Client includes a subset of the functions of TM1 Perspectives. The Client version has the capability to work with cubes that reside on the TM1 Server. TM1 Perspectives has the additional capability of creating and updating dimensions, creating and working with your own cubes, and importing and exporting ASCII files.
Loading TM1 in Excel

To load TM1 in Excel, simply start Excel as you normally would. The TM1 add-in is automatically loaded and placed on the menu bar as TM1.
If TM1 does not appear, contact your administrator.
2-1
Turning Off Automatic Recalculation

Excel has automatic recalculation set as a default. This means that every time you change a number or formula, all calculations in the worksheet are performed. If you work with large spreadsheets, you have already discovered that this feature can slow your work substantially. Applix recommends that you turn automatic recalculation off and manually recalculate worksheets by pressing F9. Follow these steps to turn off automatic recalculation: 1. 2. Choose Tools Options. Click the Calculation tab. The Calculation dialog box appears. 3. 4. Click Manual. Click OK.
Setting the Reference Style

Excel lets you select from two different reference styles, A1 and R1C1, for displaying and referring to cells. The instructions in this manual use the A1 reference style where worksheet columns are labeled with letters and rows are labeled with numbers. TM1 Client accepts both the A1 and the R1C1 reference styles. Look at the worksheet on your screen. If the columns are labeled with letters, the worksheet is set to use the A1 reference style.
2-2
Applix TM1 Client
Loading TM1 in Lotus 1-2-3
If the columns are labeled with numbers, you can follow these steps to change the reference style: 1. 2. 3. 4. Choose Tools Options. Click the General tab. In the Reference Style panel, choose the A1 option. Click OK.
Your Excel interface now corresponds to the examples provided in this manual.
Loading TM1 in Lotus 1-2-3

To load TM1 in Lotus 1-2-3, simply start 1-2-3 as you normally would. The TM1 add-in is automatically loaded and placed on the menu bar as TM1.
If TM1 does not appear, contact your administrator.

Lotus 1-2-3 has automatic recalculation set as a default. This means that every time you change a number or formula, all calculations in the worksheet are performed. If you work with large spreadsheets, you have already discovered that this feature can slow your work substantially. It is recommended that you
Tutorial
2-3
Logging On
turn off automatic recalculation and manually recalculate worksheets by pressing F9. Follow these steps to turn off automatic recalculation in Lotus 1-23: 1. Choose Tools User Setup. The Tools User Setup dialog box appears. 2. 3. 4. Click Recalculation. Click Manual. Click OK.
You are now ready to use TM1 Client with Lotus 1-2-3.
Logging On
Before you can log on to a server, you must set the Server Definition directory in TM1 Options to point to the TM1.ADM file that contains the list of active network servers. The administrator can tell you where the TM1.ADM file is located. The default location used in the setup is x:\TM1\PROGRAMS, where x is the network drive letter. The log on procedure asks for a server ID, a user ID, and a password. Obtain these from your administrator. A special user ID (USR2) and password (RED) is available for training purposes. To log on to a TM1 Server: 1. Choose TM1 Network Connect.
2-4
Applix TM1 Client
Changing Your Password
The Connect to TM1 Server dialog box appears.
2. 3. 4.
Select a Server ID from the drop-down list. Enter USR2 or the user ID assigned to you in the Client ID field. Enter RED or the password assigned to you in the Password field. A message appears confirming that you are logged on to the server.
Changing Your Password

When logging on to a server, you can change your password by entering CHANGE in the Password field. You will be prompted for your current password and then for the new password you wish to use. To confirm the new password you entered, you will be prompted to re-enter the password. The password is then changed.
Tutorial
2-5
Viewing Cube Data
You can change your password only when logging on. If you are already logged on to a server, you must first disconnect and then log on again to change your password.
Viewing Cube Data

TM1 Client allows you to look directly into the database cubes with the Browse option. The Browse option lets you display and update data in the database cubes. The examples in this section access TM1 Server files. To access these files, you must be connected to the TM1 Server. To browse a cube: 1. Choose TM1 Browse Cubes. A list of available cubes appears. Cube names are preceded by the TM1 Server name and a colon (:). 2. Select the desired cube and click Show.
For example, if you select the cube xbudget, the following information appears in your spreadsheet window. This information includes data for the xbudget cube, as well as the Browse dialog box, which lets you navigate through the cube
2-6
Applix TM1 Client
Viewing Cube Data
The Default View

When you initially open a cube, the Browse option displays the default view of the cube as follows: the last dimension as columns the next-to-last dimension as rows the data for the first element of all other dimensions
In the previous example, the Browse option displays 1991 California data, with the elements of xaccount as row headings, and the elements of xmonth as column headings.
The Browse Dialog Box

The Browse dialog box includes the following items: The name of the view, if applicable, represented by the configuration of the buttons on the Browse dialog box
Tutorial
2-7
Viewing Cube Data
The name of the cube you are browsing One button per dimension in the cube Option buttons: File, Options, Show, Close, and Help
The Browse dialog box also allows you to change the view of a cube. You can: Change elements displayed. For example, you can change a year from 1992 to 1993. You can also change a simple element, such as California, to a consolidated element, such as Total U.S. Change perspectives. For example, you can change the dimensions used as rows or columns.
Changing Elements Displayed

In the example, you can change the elements displayed by following these steps: 1. Click the xregion button on the Browse dialog box.
2-8
Applix TM1 Client
Viewing Cube Data
The Dimension dialog box appears, displaying a list of the elements contained in the xregion dimension. 2. Double-click Oregon. Oregon replaces California in the worksheet, and the values in the spreadsheet change to reflect the budget for Oregon.
Double-Click Drill Down

While browsing Cubes, TM1 Client allows you to double-click drill down on consolidated elements. This means that while you browse, double-clicking on a consolidated element causes TM1 to automatically show the components of that consolidation.
Double-Click on "Europe".
Components of "Europe" are displayed.
Tutorial
2-9
Viewing Cube Data
Displaying Consolidated Values

To display consolidated values, select a consolidated element from the list of dimension elements. For example, in the cube xbudget, the xregion dimension defines the element Total U.S. as the sum of all other regions. Follow these steps to view the consolidated value for Total U.S. 1. Click xregion on the Browse dialog box. The Dimension dialog box displays a list of the elements contained in the xregion dimension. 2. Select Total U.S. 3. Click OK.
Notice that it takes slightly longer to display the Total U.S. data than it does to display any of the individual regions. This is because calculated values are not stored in the cubes, but are produced as needed. This ensures that the most current calculated values are always available.
Changing Perspectives
Follow these steps to change dimensions used as rows (or columns): 1. Click and hold down xregion on the Browse dialog box. A white box appears in place of the dimension button. This box acts as a placeholder for the button as you reconfigure the dialog box.
2-10
Applix TM1 Client
Viewing Cube Data
2. 3. 4.
Drag the box over the xmonth button and release the mouse button. Move xmonth back to the top of the dialog box by dragging it over the xyear button. Click OK. You now have a side-by-side comparison of personnel expense costs for 1991, by month, and for every region in your database. The Browse dialog box appears as follows.
The Browse view appears as shown below.
Tutorial
2-11
Entering Data
Entering Data
The Browse option lets you directly enter or change cube values. To change a value, position the cursor in a Browse worksheet cell and type the new value. Changes are immediately stored in the cube on the TM1 Server. You cannot change values that are calculated or values that you are not authorized to change. Your ability to update cube values is determined by the privileges set by your administrator. Depending on how your system is set up, you can have rights to read but not to write certain values. You can only change cube values for which you have WRITE privileges. If TM1 returns the error message Value Cannot be Updated, one of the following conditions exist: You do no have WRITE privileges for that value. The cell contains a reference to a calculated cube value.
As USR2, you have rights to update Washington for 1993 in the xbudget cube. Create another Browse view of the xbudget cube as follows: 1. 2. 3. 4. If the Browse dialog box is open, click Close to close it. Choose TM1 Browse Cubes. Click xbudget. Click the xregion button in the Browse dialog box. The Dimension dialog box displays a list of the elements contained in the xregion dimension. 5. Select Washington and click OK.
2-12
Applix TM1 Client
Entering Data
6.
Click xyear in the Browse dialog box. The Dimension dialog box displays a list of elements contained in the xyear dimension.
7. 8. 9.
Select 1993 and click OK. Click Show in the Browse dialog box. Position the cursor in the cell at the intersection of January and Personnel Expense and type a new number.
10. Press Enter. The value in the cell at the intersection of January and Personnel Expense is sent to the cube on the server.
Tutorial
2-13
Entering Data
Privileges and Entering Data

Access to data is controlled by the privileges assigned to you. Return to the Browse view of the xbudget cube and perform these steps: 1. Click xyear in the Browse dialog box. The Dimension dialog box displays a list of the elements contained in the xyear dimension. 2. 3. 4. 5. Select 1991 and click OK. Click Show. Move to the cell at the intersection of January and Personnel Expense and type a new number. Press Enter. This time, the error message Write Access Denied appears. This is because you do not have WRITE privileges to region Washington for the year 1991. 6. Click OK.
The CALC Flag

Because TM1 Client operates in a shared environment, other users may simultaneously be working with the same cube data that you have updated. They may be viewing the same value you have changed, or they may be viewing a consolidation that depends on the value you changed. If this happens, the CALC flag, or recalculation indicator, appears on the worksheet to indicate that their data is not current. When the other users recalculate their worksheets, the most recent values display. To recalculate a worksheet, press F9.
2-14
Applix TM1 Client
Creating a Slice Worksheet

TM1 Client allows you to create Slice worksheets. A Slice worksheet is a standard Excel or Lotus 1-2-3 worksheet that corresponds to a two-dimensional view of a cube. Slice worksheets are connected to the TM1 database by means of formulas, and provide a powerful and flexible means of producing analyses and reports from the database. To create a Slice worksheet, configure the Browse dialog box for the perspective you want to show and then choose File Slice. TM1 Client automatically generates the worksheet. For example, to create a Slice worksheet from the xbudget cube: 1. Choose TM1 Browse Cubes. A list of all available cubes appears. 2. Select xbudget and click OK. The Browse dialog box for xbudget displays in default configuration. 3. Click File. The Browse File Menu dialog box appears.
Tutorial
2-15
4.
Click Slice.
A Slice worksheet is generated based on the default view of the xbudget cube. You can use this worksheet exactly as you would any other Excel or Lotus 1-2-3 worksheet. The Slice worksheet generated from the default view of xbudget appears as follows.
The top of the Slice worksheet lists the TM1 Server and cube name, as well as the elements used to retrieve the values in the worksheet. Although you cannot, at this time, change the dimensions used for rows and columns, you can change the cube and the elements used to retrieve the data in the worksheet.
Changing Elements Used to Retrieve Data

To change the dimension elements used to retrieve the data in the worksheet:
2-16
Applix TM1 Client
1.
Position the cursor on the dimension element you want to change and click-select the cell. The Dimension dialog box displays a list of all elements from that dimension.
2. 3. 4.
Select the desired element. Click OK. Press F9 to recalculate the worksheet.
The new element replaces the old element, and the worksheet recalculates to reflect the correct values associated with that element. Follow these steps to change the elements used to return data in the example Slice worksheet shown above: 1. Click-select cell B2. The Dimension dialog box for the xregion dimension appears.
2.
Select Florida.
Tutorial
2-17
3. 4.
Click OK. Press F9 to recalculate the worksheet.
You can use the same procedure to pick an element from the dimension xyear. Your ability to view Slice worksheet data depends upon the privileges you have been granted. NOTE: The process that creates a Slice worksheet uses the function DIMNM to retrieve an element name from a dimension. When you click-select a cell containing a DIMNM formula, TM1 Client automatically displays the Dimension dialog box for the associated dimension.
Changing the Cube Reference in a Slice Worksheet

To change the cube from which data is retrieved, follow these steps: 1. Move the cursor to cell B1.
2-18
Applix TM1 Client
Saving the Slice Worksheet
2.
Choose TM1 Pick Cube. A list of all available cubes appears in a dialog box.
3. 4. 5.
Select xactual. Click OK. Press F9 to recalculate the worksheet.
NOTE: The cube you select must have the same structure as the one that was used to create the Slice worksheet; all dimensions and elements must appear in the same order in both cubes. Choosing a cube with a different structure produces an error message.
Saving the Slice Worksheet

To save a Slice worksheet, choose File Save or File Save As from your spreadsheet menubar. A Slice worksheet, though it looks like a standard worksheet, reactivates the link to the database whenever it is opened. Save the Slice worksheet for xbudget under the name xslice.
Cube References
All values in a Slice worksheet are the result of cube reference functions that retrieve values from a database cube. To illustrate this, open the Slice worksheet you just created.
Tutorial
2-19
Cube References
1. 2. 3.
If the xslice worksheet is not displayed, choose File Open and select xslice. Position the cursor on cell B6. Examine the edit line.
As you can see, the number in cell B6 is the result of a formula that uses the cube reference function DBR4. (DBR4 is one of a series of cube reference functions provided by TM1 Client. Additional functions are explained in Chapter 4.) The cell addresses in the formula are pointing to database cells, the intersection of which defines a value in the xbudget cube. The first argument of the function points to cell B1($B$1), which contains the name of the server cube tm1serv:xbudget. The rest of the arguments point to cells B2, B3, A6, and B5, which contain the names California, 1991, Personnel Expenses, and January, respectively.
2-20
Applix TM1 Client
Cube References
The formula DBR4($B$1,$B$3,$B$2,$A6,B$5) can also be written as: DBR4(,tm1serv:xbudget,California,1991,Personnel Expenses, January) You obtain two key advantages when you write formulas using references to labels in the Slice worksheet: The same formula can be copied to retrieve a whole slice of data, which saves much work. The data is guaranteed to correspond to the label being used, which greatly reduces the possibility of error.
NOTE: Excel puts an equal sign (=) in front of every formula, and Lotus 1-2-3 precedes the functions provided by TM1 Client with @<<TM1>>.
Writing a Cube Reference

TM1 Client provides an option for building cube reference functions. 1. 2. 3. 4. 5. 6. Choose File Open from your spreadsheet File menu. Select xslice and click Open. Select the range B8 to R30. Press Delete to erase all existing cube references. Position the cursor on cell B8. Choose TM1 Edit Formula. The Edit Formula dialog box appears.
Tutorial
2-21
Cube References
7.
Click DB Ref. TM1 prompts you to select the cell containing the cube name.
8.
Clickselect cell B1. The Select Type of Cell Reference dialog box appears.
This dialog box lets you specify how the DBR formula references the cell containing the cube name: Click Absolute to use an absolute ($A$1) reference in the DBR formula. Click Column Rel to use a column relative (A$1) reference in the DBR formula. Click Row Rel to use a row relative ($A1) reference in the DBR formula. Click Relative to use a relative (A1) reference in the DBR formula.
2-22
Applix TM1 Client
Cube References
In this example, the cube name appears in the Sheet Titles area and should be referenced with an absolute cell reference. 9. Click Absolute.
TM1 makes a best guess at building the rest of the formula for you. It searches through the worksheet to identify the various cells that will make up the arguments of your formula. It also identifies the reference types automatically (row relative, column relative) so that you can later copy the formula throughout the sheet. Examine the choices that TM1 makes. It looks at cell B3 for the element from the xregion dimension. It correctly identifies the position of this cell and assigns it an absolute reference ($B$3). It looks to cell A6 for the element from the xaccount dimension and correctly identifies the reference to this cell as row relative ($A6). Examine the other references. Note that in all three cases, TM1 correctly identifies the type of cell referencing to use. 10. Click OK.
Tutorial
2-23
Reserving and Locking Values in the Database
The Edit Formula dialog box appears with the completed DBR formula.
11. Click OK to store the formula in cell B6. 12. Position the cursor in B6. Cell B6 displays the value retrieved by the DBR formula. To complete the report, you must copy and paste the formula in cell B6 to the range B6:R30. 13. Choose Edit Copy to copy the formula. 14. Select the range B6:R30. 15. Choose Edit Paste to insert the formula into all of the cells in the range. The value in B6 appears in all cells in the range. 16. Press F9 to recalculate the worksheet and update all values in the range

TM1 Client assigns each user to a group. The server in turn defines which groups can read or write which cubes. The administrator can also choose to assign group privileges by dimension element.
2-24
Applix TM1 Client
A user can have any one of five privileges to a cube or dimension element. See Chapter 1 "Basic Concepts," for more information on privileges. The administrator assigns privileges when setting up the TM1 Server. If you are assigned LOCK privileges, you can also RESERVE, READ, and WRITE. If you have Reserve and/or Lock privileges, you can temporarily reserve or permanently lock data resources. For example, to reserve the xbudget cube: 1. Choose TM1 Network Security. The following dialog box appears.
2.
Click Reserve. A dialog box prompts you to select the type of resource (i.e., cube or element) you want to reserve.
3.
Click Cube. A dialog box containing a list of all cubes on the TM1 Server appears.
4.
Select xbudget and click OK.
Tutorial
2-25
The RESERVE option temporarily holds a cube or dimension element. When data is reserved, other users can view it, but they cannot update it until you release the resource or log out. To release the xbudget cube: 1. 2. 3. 4. Choose TM1 Network Security. Click Release. Click Cube. Select xbudget and click OK.
The LOCK command permanently freezes a cube or dimension element. No one can change locked data. Once a resource is locked, only the system administrator can release the resource. Locked cubes are usually used to store historical data that should not be updated. If you have LOCK privileges, you automatically have RESERVE privileges. See your administrator to have privileges assigned.
2-26
Applix TM1 Client
Setting Network Options
Setting Network Options

The dialog box shown below allows you to change a number of default settings that govern the operation of TM1 Client.
TM1 Client does not allow access to the Database Directory. The Server Definition Directory field defines the directory that contains the TM1.ADM file. This file contains a list of all available network servers and routing information for those servers. You can enter the path to the directory directly in the entry field, or you can click on the browse button to navigate to the directory. Consult your system administrator for the correct Server Definition Directory. If Poll for Cube Changes is checked, TM1 Client polls the TM1 Server to check if any other users have changed values in shared cubes. If a shared cube has changed, the calculate flag at the bottom left of the screen flashes. If Advanced Mode is checked, the Advanced mode of the dimension dialog box is set as a default. Advanced mode provides
Tutorial
2-27
Connecting to Multiple Servers
complex query and navigation options for manipulating dimensions and elements. When you are finished making network option changes, click OK. You will then be prompted to save the file called TM1.INI. The TM1.INI file is used by TM1 Client to store default options. Saving this file sets the options you have selected as default options. The options will then be set to these new values the next time you access TM1 Client. If you choose not to update this file, your network options changes will not be implemented. NOTE: TM1.INI is saved to the Windows directory.
Connecting to Multiple Servers

You can connect to as many as nine (9) TM1 Servers simultaneously. To connect to other TM1 Servers, use the same process you used to connect to the primary TM1 Server. See Logging On earlier in this chapter for details.
Disconnecting From All TM1 Servers

To disconnect from all TM1 Servers: 1. Choose TM1 Network Disconnect. A dialog box prompts you to confirm the disconnection. 2. Click Yes to disconnect from all the TM1 Server(s) to which you are currently connected. You cannot selectively disconnect from individual servers.
2-28
Applix TM1 Client
NOTE: You are automatically disconnected from all TM1 Servers when you exit Excel or Lotus 1-2-3.
Tutorial
2-29
2-30
Applix TM1 Client
Worksheet Functions
Worksheet functions return a numeric or string value, and can be used anywhere within an Excel or 123 worksheet. These functions are available using the Insert Function option in Excel, and through the @ List All option in Lotus 1-2-3. You must adhere to the function format conventions for your worksheet environment when using TM1 functions. In Excel, you must prefix all functions with an equal symbol (=). In 1-2-3, you must prefix all functions with the string @<<TM1>>. TM1 worksheet functions accept strings, values, or cell references as arguments. Strings must be enclosed in quotation marks, and cell references must refer to valid arguments for a given function. You can use Excel and 1-2-3 conventions for absolute and relative cell references in worksheet functions. Formulas written with cell references for their arguments present significant advantages over formulas written with strings. The strings in the various cells referred to can be changed, thus changing the intersection in the database to which the formula refers. Formulas written with cell references also have the advantage of being copyable.
DBGEN(Type,Value,Cube,K1,K2[,K8])
DBGEN(Type,Value,Cube,K1,K2[,K8])
DBGEN sends numeric or string values to cubes containing up to eight dimensions. This function restores cubes with the Transaction Log, and is a generic version of the DB Send functions (DBSn and DBSSn).
Arguments
Type Indicates whether the value being sent is numeric, string, or calculated. Specify N for numeric, S for string, or C for calculated. The value being sent. The cube to which the value is sent. The names of elements defining the intersection in the cube to which the value is sent. Arguments K1 through K8 are sequencesensitive. K1 must be an element from the first dimension of the cube, K2 must be an element from the second dimension of the cube, and so on.
Value Cube K1, ...K8
Example
DBGEN(N,5342,92act4d,California,3.5 Diskettes, Net Sales,January)
Applix TM1 Client
DBGEN16(Type,Value,Cube,K1,K2[,K16])
This example sends the value numeric value 5342 to the cube 92act4d at the intersection of California, 3.5 Diskettes, Net Sales, and January.
DBGEN16(Type,Value,Cube,K1,K2[,K16])
DBGEN sends numeric or string values to cubes containing more than eight dimensions. This function restores cubes with the Transaction Log, and is a generic version of the DB Send functions (DBSn and DBSSn).
Arguments
Type Indicates whether the value being sent is numeric, string, or calculated. Specify N for numeric, S for string, or C for calculated. The value being sent. The cube to which the value is sent. The names of elements defining the intersection in the cube to which the value is sent. Arguments K1 through K8 are sequencesensitive. K1 must be an element from the first dimension of the cube, K2 must be an element from the second dimension of the cube, and so on.
Value Cube K1, ...K8
Worksheet Functions
DBRn(Cube,K1,K2[,...Kn])
Example
DBGEN16(78365,91accounting,California,Track1,3.5Dis kettes, Wholesale,"Actual,Net Sales,External,Code2, January) This example sends the value 78365 to the cube 91accounting at the intersection of California, Track1, 3.5 Diskettes, Wholesale, Actual, Net Sales, External, Code2, and January.
This function retrieves a value from a cube of n dimensions.
Arguments
Cube K1,Kn The name of the database cube from which to retrieve the value. Dimension element names that define the intersection of the cube containing the value to be retrieved. Arguments K1 through Kn are sequencesensitive. K1 must be an element from the first dimension of the cube, K2 must be an element from the second dimension, and so on.
Applix TM1 Client
Example
DBR4(92act4d, California, 3.5 Diskettes, Net Sales, January) In this case, 92act4d is the cube name, and the function returns the value at the intersection of California, 3.5 Diskettes, Net Sales, and January.
Worksheet Functions
DBRWn(Cube,K1,K2[,...Kn])
DBRWn(Cube,K1,K2[,...Kn])
This function works exactly the same as the DBRn function described above with one major difference; DBRWn reduces network traffic and may improve performance on wide area networks. In cubes with a large number of cube references, DBRWn forces TM1 Client to send references in bundles rather than individually. Normal TM1 Client DB references are updated individually during a recalculation. DBRW references force TM1 Client to execute two passes over the worksheet. In the first pass, the function reads all changes to values and sends them in a single bundle to the cube. In the second pass, the function reads the values in the cube and sends them in a single bundle back to the worksheet. As a result, the worksheet recalculates twice when the function is executed.
Arguments
Cube K1,Kn The name of the database cube from which to retrieve the value. Dimension element names that define the intersection of the cube containing the value to be retrieved. Arguments K1 through Kn are sequence-sensitive. K1 must be an element from the first dimension of the cube, K2 must be an element from the second dimension, and so on.
Example
DBRW4(92act4d, California, 3.5 Diskettes, Net Sales, January)
Applix TM1 Client
DBRX(Handle,Cube,K1,K2[,...Kn])
In this example, the function returns the value at the intersection of California, 3.5 Diskettes, Net Sales, and January in the 92act4d cube.
DBRX(Handle,Cube,K1,K2[,...Kn])
The DBRX function retrieves a value from a places the value in a slice worksheet. This function works only with slices created from a cube browse. It is optimized to work within the slice, and performs better than the standard DBRn function. In Lotus 1-2-3, this function requires that you specify the number of dimension in the cube. For example, use DBRX3 to retrieve a value from a cube containing 3 dimensions.
Arguments
Handle Cube K1,Kn A reference to a cell containing a Slice function. The name of the database cube from which to retrieve the value. Dimension element names that define the intersection of the cube containing the value to be retrieved. Arguments K1 through Kn are sequencesensitive. K1 must be an element from the first dimension of the cube, K2 must be an element from the second dimension, and so on.
Worksheet Functions
DBSn(Value,Cube,K1,K2[,...Kn])
Example
DBRX(A5,92act4d,California,3.5 Diskettes, NetSales,January)
DBRX4(A5,92act4d,California,3.5 Diskettes, NetSales,January) In this example, cell A5 contains a Slice function which points the DBRX function to a model in memory and 92act4d is the cube name. The function returns the value at the intersection of California, 3.5 Diskettes, Net Sales, and January.
DBSn(Value,Cube,K1,K2[,...Kn])
DBSn sends a numeric value to a cube of n dimensions. This function cannot send a string to a string cube (see DBSSn function below). When you build a DBSn function with the Edit Formula option, the Edit Formula dialog box prompts you through a series of steps to build each function argument in the correct sequence.
Arguments
Value Cube The value being sent. The cube to which the value is sent.
Applix TM1 Client
DBSSn(String,Cube,K1,K2,...Kn)
K1, ...K8
The names of elements defining the intersection in the cube to which the value is sent. Arguments K1 through K8 are sequence-sensitive. K1 must be an element from the first dimension of the cube, K2 must be an element from the second dimension of the cube, and so on.
If the cube does not exist or one of the arguments does not occur in the corresponding dimension, the function returns KEY ERROR.
Example
DBS4(5342,92act4d,California,3.5 Diskettes, Net Sales, January) In this example, the function sends the value 5342 into the cube 92act4d at the intersection of California, 3.5 Diskettes, Net Sales, and January.
DBSSn(String,Cube,K1,K2,...Kn)
DBSSn sends a string to a string cube of n dimensions. This function cannot send a value to a numeric cube (see DBSn function above). When you build a DBSSn function with the Edit Formula option, the Edit Formula dialog box prompts you through a series of steps to build each function argument in the correct sequence.
Worksheet Functions
DBSWn(Cube,K1,K2[,...Kn])
Arguments
String Cube K1, ...K8 The string being sent. The cube to which the string is sent. The names of elements defining the intersection in the cube to which the string is sent. Arguments K1 through K8 are sequence-sensitive. K1 must be an element from the first dimension of the cube, K2 must be an element from the second dimension of the cube, and so on. If the cube does not exist or one of the arguments does not occur in the corresponding dimension, the function returns KEY ERROR.
Example
DBSS2(Smith,Info,California,Last Name) In this example, the formula sends the string Smith to the cube Info at the intersection of California and Last Name.
This function works exactly the same as the DBSn function described above with one major difference; DBSWn reduces network traffic and may improve performance on wide area networks.
10
Applix TM1 Client
In cubes with a large number of cube references, DBSWn forces TM1 Client to send references in bundles rather than individually. Normal TM1 Client DB references are updated individually during a recalculation. DBSW references force TM1 Client to execute two passes over the worksheet. In the first pass, the function reads all changes to values and sends them in a single bundle to the cube. In the second pass, the function reads the values in the cube and sends them in a single bundle back to the worksheet. As a result, the worksheet recalculates twice when the function is executed.
Arguments
Value Cube K1, ...K8 The value being sent. The cube to which the value is sent. The names of elements defining the intersection in the cube to which the value is sent. Arguments K1 through K8 are sequence-sensitive. K1 must be an element from the first dimension of the cube, K2 must be an element from the second dimension of the cube, and so on.
Example
DBSW4(5342,92act4d,California,3.5 Diskettes, Net Sales, January) In this example, the function sends the value 5342 into the cube 92act4d at the intersection of California, 3.5 Diskettes, Net Sales, and January.
Worksheet Functions
11
DFRST(Dimension)
DFRST(Dimension)
DFIRST returns the first element of a specified dimension.
Argument
Dimension A valid dimension name.
Example
DFRST(Locations) If the dimension Locations contains the elements California, Oregon, and Washington, the example returns California.
DIMIX(Dimension,Element)
DIMIX returns the index number of an element within a dimension.
Arguments
Dimension Element A valid dimension name. The name of an element within the dimension.
12
Applix TM1 Client
DIMNM(Dimension,Index)
If the element is not a member of the dimension specified, the function returns 0.
Example
DIMIX(Locations,Washington) If the dimension Locations contains the elements California, Oregon, and Washington, the example returns the value 3, as Washington is the third element of the dimension.
DIMNM(Dimension,Index)
DIMNM returns the element of a dimension that corresponds to the Index argument. When you click select a cell containing a DIMNM function, the Dimension dialog box appears. You can then select a new element to place in your worksheet.
Arguments
Dimension Index A valid dimension name. A value less than or equal to the number of elements in the dimension.
NOTE: To maintain functionality of the DIMNN function, do not use cell references as arguments to the function.
Worksheet Functions
13
DIMSIZ(Dimension)
Example
DIMNM(Locations,2) If the Region dimension contains the elements California, Oregon, and Washington, the example returns Oregon.
DIMSIZ(Dimension)
DIMSIZ returns the number of elements within a specified dimension.
Argument
Example
DIMSIZ(Region) If the dimension Region contains 19 elements, the example returns the value 19.
DNEXT(Dimension,Element)
DNEXT returns the element name that follows the element specified as an argument to the function.
14
Applix TM1 Client
DNLEV(Dimension)
Arguments
Example
DNEXT(Locations,Oregon) If the Locations dimension contains the elements California, Oregon, and Washington, the example returns Washington.
DNLEV(Dimension)
DNLEV returns the level number of the highest hierarchy level in a dimension.
Argument
Example
DNLEV(Region)
Worksheet Functions
15
DTYPE(Dimension, Element)
In the Region dimension, the various countries (Level 0) add up to regions (Level 1). The regions then add up to super-regions (Level 2), which in turn add up to the world (Level 3).
In the Region dimension, World is an element of the highest hierarchy level, Level 3. Therefore, the example returns the value 3.
DTYPE(Dimension, Element)
DTYPE returns information about the element type of a specified element. Specifically, it returns N if the element is a numeric element, S if the element is a string element, and C if the element is a calculated element.
Arguments
16
Applix TM1 Client
ELCOMP(Dimension,Element,Index)
Element
The name of an element within the dimension.
Example
DTYPE(Region,Europe) The element Europe in the dimension Region is a calculated element, so the example returns C.
ELCOMP(Dimension,Element,Index)
This function returns a component of a consolidated element in a specified dimension.
Arguments
Dimension Element Index A valid dimension name. The name of an element within the dimension. A positive value less than or equal to the total number of components in the specified element.
Example
ELCOMP(Region,Central Europe,2)
Worksheet Functions
17
ELCOMPN(Dimension,Element)
In the dimension Region, the consolidated element Central Europe is a consolidation of the components Germany and France. Accordingly, the example returns France.
ELCOMPN(Dimension,Element)
ELCOMPN returns the number of components in a specified element.
Arguments
Dimension Element A valid dimension name. The name of an element within the dimension. If the Element argument is an N element, the function returns 0.
Example
ELCOMPN(Region,Scandanavia) In the dimension Region, the C element Scandanavia is a consolidation of three elements. The example returns 3.
18
Applix TM1 Client
ELISCOMP(Dimension,Element1,Element2)
ELISCOMP(Dimension,Element1,Element2)
This function determines whether Element1 is a component of Element2 in the specified dimension. The function returns TRUE if Element1 is a component of Element2, otherwise the function returns FALSE.
Arguments
Dimension Element1 Element2 A valid dimension name. The name of an element within the dimension. The name of an element within the dimension.
Example
ELISCOMP(Region,Germany,Central Europe) In the dimension Region, the C element Central Europe is a consolidation of two elements, Germany and France. The example returns TRUE. Note that this function returns TRUE only for immediate components. In the above example, Germany is a component of Central Europe. Further, Central Europe is a component of Europe. However, since the function returns TRUE only for immediate components, the following example returns FALSE. ELISCOMP (Region,Germany,Europe)
Worksheet Functions
19
ELISPAR(Dimension,Element1,Element2)
ELISPAR(Dimension,Element1,Element2)
This function determines whether Element1 is a parent of Element2 in the specified dimension. The function returns TRUE if Element1 is a parent of Element2, otherwise the function returns FALSE.
Arguments
Dimension Element1 Element2 A valid dimension name. The name of an element within the dimension. The name of an element within the dimension.
Example
ELISPAR(Region,Central Europe,Germany) In the dimension Region, the C element Central Europe is the parent of both Germany and France. The example returns TRUE. Note that this function returns TRUE only for immediate parents. In the above example, Europe is a parent of Central Europe. Further, Central Europe is a parent of Germany. However, because Europe is not an immediate parent of Germany, the following example returns FALSE. ELISPAR(Region,Europe,Germany)
20
Applix TM1 Client
ELLEV(Dimension,Element)
ELLEV(Dimension,Element)
ELLEV returns the level of an element within a dimension.
Arguments
Example
ELLEV(Region,Europe) In the Region dimension, individual countries (Level 0) add up to regions (Level 1). The regions then add up to super-regions (Level 2), which in turn add up to the world (Level 3).
Worksheet Functions
21
ELPAR(Dimension,Element,Index)
The example returns 2, as Europe is a Level 2 element.
ELPAR(Dimension,Element,Index)
This function returns the parent of an element in a specified dimension. The parent of an element is any element that uses it as a component.
Arguments
Dimension Element Index A valid dimension name. The name of an element within the dimension. A positive value less than or equal to the total number of consolidated elements (parents) that use the Element argument as a component.
Example
ELPAR(Model,Wagon 4WD,2) In the dimension Model, the element Wagon 4WD is a component of both Total Wagons and Total 4WD. Therefore, both Total Wagons and Total 4WD are parents of Wagon 4WD. In the structure of the Model dimension, Total Wagons is defined first, Total 4WD is defined second.
22
Applix TM1 Client
ELPARN(Dimension,Element)
The example returns Total 4WD, as this is the second instance of a parent to Wagon 4WD within the Model dimension.
ELPARN(Dimension,Element)
ELPARN returns the number of parents of an element in a specified dimension.
Arguments
Example
ELPARN(Model,Wagon 4WD) In the dimension Model, the element Wagon 4WD is a component of both Total Wagons and Total 4WD. Therefore, both Total Wagons and Total 4WD are parents of Wagon 4WD. The formula returns 2.
ELSLEN(Dimension,Element)
ELSLEN returns the length of a string element within a dimension.
Worksheet Functions
23
ELWEIGHT(Dimension,Element,Component)
Arguments
Dimension Element A valid dimension name. The name of an element within the dimension. If the element specified is not a member of the dimension specified, or is not a string element, the function returns 0.
Example
ELSLEN(Region,Washington) The element Washington is a string element 10 characters in length. The example returns 10.
ELWEIGHT(Dimension,Element,Component)
This function returns the weight of a component in a consolidated element. The weight of a component is defined in column C of the dimension spreadsheet.
Arguments
Dimension Element A valid dimension name. The name of a consolidated element within the dimension.
24
Applix TM1 Client
SUBNM(Dimension,Subset,Index)
Component
The name of a component of the consolidated element.
Example
ELWEIGHT(Account1,Gross Margin,Variable Costs) In the following figure, the component Variable Costs has a weight of 1.
The example returns 1.
SUBNM(Dimension,Subset,Index)
This function is analogous to the DIMNM function, with the exception that it returns the nth element of a dimension subset instead of the dimension. When you click select a cell containing a SUBNM function, the Dimension dialog box appears. You can then select a new element to place in your worksheet.
Arguments
Dimension Subset A valid dimension name. The name of a subset within the dimension.
Worksheet Functions
25
SUBSIZ(Dimension,Subset)
Index
A positive value less than or equal to the total number of elements in the specified subset.
Example
SUBNM(Region,Americas,2) The subset Americas of the dimension Region contains the following elements in this order: North America, South America, and Central America. The example returns South America. NOTE: To maintain functionality of the SUBNM function, do not use cell references as arguments to the function.
SUBSIZ(Dimension,Subset)
This function returns the number of elements in a dimension subset.
Arguments
Dimension Subset A valid dimension name. The name of a subset within the dimension
Example
SUBSIZ (Region,Americas)
26
Applix TM1 Client
TABDIM(Cube,Index)
The subset Americas of the dimension Region contains three elements: North America, South America, and Central America. The example returns 3.
TABDIM(Cube,Index)
TABDIM provides information on the dimension structure of a cube. Specifically, it returns the dimension name that corresponds to the Index argument.
Arguments
Cube Index A valid cube name. A positive value less than or equal to the total number of dimensions in the cube.
Example
TABDIM(92act4d,3) The cube 92act4d is made up of the four dimensions: Region, Products, Account, and Month. The example returns Account, the third dimension of 92act4d.
VIEW(Cube,K1,K2,......Kn,)
A single VIEW function is created when you slice a view from a cube browse.
Worksheet Functions
27
VIEW(Cube,K1,K2,......Kn,)
This function creates an optimized view of the cube specified by the cube parameter. All DBR and DBRW formulas that refer to the View function can then access this optimized view. In this way, results are returned much faster. Multiple View functions can reside in the same spreadsheet if you have blocks of DBR formulas that refer to different TM1 views and/or cubes.
Arguments
Cube K1,Kn The name of the cube from which to retrieve data. Either specific elements in the slice to be used as titles, or the string ! which indicates that the corresponding dimension is a row or column in the view.
Example
VIEW(93sales,$B$2,$B$3,$B$4,!,!)
28
Applix TM1 Client
Macro Functions
In addition to providing functions for writing formulas in worksheets, TM1 Client also provides a series of Excel and Lotus 1-2-3 functions that can be incorporated into macros. These functions let you write macros and turnkey systems that take advantage of TM1 Client's powerful database capabilities. Most of these additional functions provided by TM1 Client are command-equivalent functionsthat is, they replicate the commands you invoke from the TM1 menu.
EXCEL_FUNCTION (Arguments)
Accessing Macro Functions

There are several ways to access the TM1 macro functions. The procedure you use varies according to spreadsheet product and version.
Accessing Macro Functions from Excel Versions 5 and 7

To access macro functions from Excel Version 7 and earlier: 1. 2. Choose Insert Macro MS Excel 4.0 Macro. Choose Insert Function. The Function Wizard dialog box appears. 3. 4. 5. 6. Select TM1 from the Function Category list box. Double-click the function you want to insert in the Function Name list box. Enter the appropriate arguments in the Function Wizard dialog box. Click Finish to complete the function and return the function to your macro.
Applix TM1 Client
Accessing Macro Functions from Excel Version 8

To access macro functions from Excel Version 8: 1. Right-click the sheet tab of the active worksheet. A pop-up menu appears. 2. Click Insert. The Insert dialog box appears. 3. 4. 5. Click the General tab. Click MS Excel 4.0 Macro. Choose Insert Function. The Paste Function dialog box appears. 6. 7. 8. 9. Select TM1 from the Function Category list box. Double-click the function you want to insert in the Function Name list box. Enter the appropriate arguments in the Arguments dialog box. Click OK to complete the function and return the function to your macro.
Macros
Accessing Macro Functions from VBA

To access macro functions from VBA, use the Run function as follows: Run (Function, arg1, ...) For example: =N_CONNECT(Demo, USR2, Swordfish) becomes: Run (N_CONNECT, Demo, USR2, Swordfish) in VBA.
Accessing Macro Functions from Lotus 1-2-3

To access macro functions from Lotus 1-2-3: 1. 2. Type { (open brace) in the cell to contain the macro function. Press F3. The Macro Keywords dialog box appears. 3. 4. Select the desired function from the Macro Keywords list box. Click OK to return the function to your macro.
Applix TM1 Client
Function Descriptions
Each section in this chapter describes a macro function. The following format is used:
EXCEL_FUNCTION (Arguments) {LOTUS_1-2-3_FUNCTION Arguments} D_FSAVE(SourceFile) {D_FSAVE SourceFile}

This function lets you save very large dimensions. TM1 supports up to 32,000 lines in dimension definitions. However, Excel allows a maximum of 16,384 lines in its worksheets, making it impossible to use Excel as an editor to define dimensions with more than 16,384 lines. In cases where you need to define dimensions with more than 16,384 lines, the D_FSAVE function reads a simple comma- (or semicolon-) delimited text file and generates a .dim dimension file. The source file must be a simple text file with three fields per line. The fields must be separated with the delimiter defined in International under the Windows control panel. The structure of the source file is the same as a TM1 .xdi or .ldi file. The first field contains the element type (C, N, S or blank for calculation component), the second field contains the element name and the third field contains the weight for a calculation component. The source file specified as an argument must have the name of the dimension to be created and the extension .dit. The extension should not be included in the SourceFile argument. The following is an example of a typical .xdi or .ldi file and its equivalent in text form:
Macros
{D_FSAVE SourceFile}
N,United States, N,Canada, N,Mexico, C,North America, ,United States, ,Canada, ,Mexico, C,North America less US, ,North America, ,United States,-1 The macro command
=D_FSAVE(Region)
= {D_FSAVE Region} creates a region .dim file from this region.dit file. If there are errors in the structure of the text file, such as misplaced or undefined elements, the .dim is not created. Rather, a tm1erlog.cma file is generated. The first field contains the
Applix TM1 Client
D PICK( )
offending record number and the second field contains the text of the error message.
D PICK( ) {D_PICK Target}

This function calls a dialog box that shows all available dimensions in the current data directory or on an active TM1 Server. There are no arguments to the D_PICK function. When you select a dimension name from the dialog box, this name becomes the value of the function.
The above macro displays a dialog box showing the dimensions available in the default data directory or in a cube server. Once a dimension name has been selected, the formula in A1 returns the dimension name selected from the dialog box. The macro then selects the first cell in the active worksheet and writes the value of the D_PICK formula (which is the selected dimension name) to that cell. When the user selects a dimension name from the dialog box, that name is stored in the range specified by the Target argument. The argument can be either a cell address or a range name. {D_PICK B1} When the macro encounters the above formula, it displays a dialog box showing the dimensions available in the default data
Macros
D SAVE( )
directory or on a cube server. After a dimension is selected from the dialog box, D_PICK places the dimension name in cell B1 of the worksheet.
D SAVE( ) {D_SAVE}
This function saves the active worksheet as an .xdi or .ldi file and then creates or updates a .dim file with the contents. The .dim file created carries the same name as the active worksheet. If there are errors in the structure of the active worksheet, such as misplaced or undefined elements, the .dim is not created. In case of errors, a tm1erlog.cma file is generated with two fields. The first field contains the offending record number and the second field contains the text of the error message.
E_PICK(Dimension) {E_PICK Dimension,Target}

This function calls a dialog box that displays all elements in the dimension specified by the Dimension argument. The dimension specified must be in the default data directory or on an active TM1 Server. When you select an element name from the dialog box, this name becomes the value of the function.
Applix TM1 Client
I EXPORT(Tab,File,Z,C)
The above macro displays a dialog box showing the elements of the Region dimension. When you select an element from the dialog box, the formula in cell A1 returns the element name you selected. The macro then selects the first cell in the active worksheet and writes the value of the D_PICK formula (which is the selected element name) to that cell.
When you select an element name from the dialog box, the selected name is stored in the range specified by the Target argument. The Target argument can be either a cell address or a range name. The Dimension argument must specify a dimension in the default data directory or on an active TM1 Server. {E_PICK Region,B1} When a macro encounters this formula, it displays a dialog box showing the elements of the Region dimension. When you select a element name from the dialog box E_PICK places the element name in cell B1 of the worksheet.
I EXPORT(Tab,File,Z,C) {I_EXPORT Tab,File,Z,C}

This function exports the data in a specified cube to a commadelimited ASCII file with the file extension .cma. The name of the cube from which the data is to be exported is specified by the string argument Tab. The cube specified must be in the default data directory or on an active cube server. The file to be written is specified by the File argument. The comma-delimited ASCII file is written to the default data directory. When specifying the Tab and File arguments, do not use file extensions. The function automatically assumes a file extension of .tab for the cube name and .cma for the file name.
Macros
{I_EXPORT Tab,File,Z,C}
The Boolean argument Z specifies whether or not zeroes should be suppressed. That is, it specifies whether the function writes a record for each possible intersection in the cube or only for those intersections that contain values other than zero. If this argument is FALSE, the function does not write records for zero values. If it is TRUE, all intersections are written as records. If this argument is 0, the function does not write records for zero values. If it is 1, all intersections are written as records. The Boolean argument C specifies whether or not values calculated by the cube are written as records. If this argument is FALSE, calculated values are not written. If this argument is TRUE, all values, both calculated and non-calculated, are written. If this argument is 0, calculated values are not be written. If this argument is 1, all values, both calculated and non-calculated, are written.
=I_EXPORT(92sales, Download,FALSE, TRUE) {I_EXPORT 92sales,Download,0,1} In the above example, the macro function takes the values in the cube 92sales and write a comma-delimited ASCII file named Download.cma. The function does not write records for cube
10
Applix TM1 Client
I NAMES(File,Column)
intersections that contain zero values, but it does write records for values that are calculated by the cube.
I NAMES(File,Column) {I_NAMES File,Column}

This function reads through a comma-delimited (.cma) ASCII file and writes a list of all labels that occur within a specific field in the ASCII file. The .cma file to be read is specified by the File argument. When specifying a .cma file, do not include an extension. The I_NAMES function reads only files with the .cma extension. The numeric argument Column specifies both the number of the field that is read and the number of the column of the worksheet to which the list of unique names is written. If you specify a 2 for this argument, the function reads the unique names in the second field of the .cma file and places them in column B (the second column) of the active worksheet.
=I_NAMES(93sales,3)
{I_NAMES 93sales,3} In the above example, the function reads through the commadelimited ASCII file 93sales.cma, records all the unique names in the third field of that file, and writes those names in column C (the third column) of the active worksheet.
Macros
11
I PROCESS(File)
I PROCESS(File) {I_PROCESS File}

This function converts information from standard ASCII file format into TM1 Client format. The function sequentially reads the records of a comma-delimited ASCII file into the first row of the active worksheet and recalculates the worksheet after each record is read. Each field of a record is read into a separate cell. Typically, you write DBSn formulas in the worksheet into which the records are being read. This DBSn formula reads the values in the record and sends them to the appropriate intersection in the database as defined by the labels in the various fields of the record. While reading the records into the active sheet, TM1 Client displays the following dialog box.
Pressing the Escape key during processing returns control to the macro at the cell following the location from which I_PROCESS was invoked. The .cma file to be read is specified by the File argument. When specifying a .cma file, do not include an extension. The I_PROCESS function reads only files with the .cma extension.
=I_PROCESS(95sales)
{I_PROCESS 95sales}
12
Applix TM1 Client
N_CONNECT(Server,Client,Password)
In this example, the function reads each record of the commadelimited ASCII file 95sales.cma into the first row of the active spreadsheet and recalculates the active worksheet after reading each record.
N_CONNECT(Server,Client,Password) {N_CONNECT Server,Client,Password,Target}

This function connects you to a network cube server. The argument Server specifies the name of the cube server to which you will connect. The argument Client specifies the client name under which you will be connected. The string argument Password specifies the password for the specified client. This function returns the value of any error messages returned by TM1 Client. If log-on is successful, the function does not return a value.
=N_CONNECT(Demo,USR2,Swordfish)
{N_CONNECT Demo,USR2,Swordfish,B1} In the example, TM1 Client searches for and attempts to log on to the Server named Demo as the client USR2. The formula will supply the password Swordfish when the Server requests a password. If the log-on attempt fails: The function returns the value of any error message.
The error message is sent to cell B1.
Macros
13
N_DISCONNECT( )
N_DISCONNECT( ) {N_DISCONNECT}
This function disconnects you from all cube servers to which you are currently connected. There are no arguments to this function. When you disconnect from servers with N_DISCONNECT, you are not prompted to confirm the action, as you are when disconnecting with the TM1 Network Disconnect option.
OPTGET(Option) {OPTGET Option,Target}

This function returns the current value of an option in the TM1 Client options setting. The argument Option is one of the option names used in the TM1.INI file. For example, if the database directory is set to C:\TM1DATA, the following function returns C:\TM1DATA. In Excel, the function returns the value of the specified option. In 1-2-3, the function stores the value of the option in the location specified by the Target argument.
= OPTGET(DataBaseDirectory)
{OPTGET DataBaseDirectory,B1} The following are valid arguments to the OPTGET function. AdminDirectory AdvancedMode Returns the current directory containing the TM1.ADM file. Returns T if Advanced Mode is activated; otherwise, returns F.
14
Applix TM1 Client
OPTSET(Option,Value)
AnsiFiles
Returns T if options are set to use the ANSI character set for processing text files; otherwise, returns F. Returns the current database directory. Returns F if the cube slice returns DBR formulas; returns T if the cube slide returns DBRW formulas in the spreadsheet. Returns T if the NetBIOS reset parameter is turned on; returns F if the parameter is turned off. Returns T if options are set so that TM1 Client displays the message NO CHANGE when a DB Send formula points to a C level cell. Returns F if this message is deactivated. Returns F if network polling is turned off; otherwise, returns T. (Refer to the Applix TM1 Server manual for more information.) Returns the number of Kbytes set for storing TM1 views. Note that numeric values are returned as strings.
DataBaseDirectory GenDBRW
NBReset
NoChangeMessage
PollingOn
ViewMaxMemory
OPTSET(Option,Value) {OPTSET Option,Value}

This function sets the TM1 Client option specified by the Option argument to the value specified by the Value argument. Both arguments must be strings or references to cells containing strings.
Macros
15
{OPTSET Option,Value}
Following is the list of valid Option arguments for the OPTSET function. Note that many of these parameters cannot be set in the normal TM1 Options dialog box. AdminDirectory Sets the directory containing the TM1.ADM file. The accompanying Value argument must be a complete path to the directory containing TM1.ADM. When the Value argument is T, activates TM1 Clients advanced mode. TM1 Client then always shows the advanced functions in the dimension dialog box. When the Value argument is F, TM1 Client displays the simplified version of the dimension dialog box. Determines whether or not TM1 uses the ANSI character set when importing files. If the Value argument is T, TM1 uses the ANSI character set. When Value is set to F, TM1 uses the ASCII character set. Sets the database directory to the directory specified by the Value argument. Switches from DBR to DBRW formulas when you create a cube slice. Set Value argument to F to return DBR formulas; set to T to return DBRW formulas in the spreadsheet. Lets you specify whether TM1 Client displays the message NO CHANGE when a DB Send formula points to a C level cell. When the Value argument is T, TM1 Client displays NO CHANGE when DB Send formulas point to consolidated values.
AdvancedMode
AnsiFiles
DataBaseDirectory GenDBRW
NoChangeMessage
16
Applix TM1 Client
QUDEFINE(Cube,Query,Range,Low,Hi,SkpZeroes,SkpCalcs)
When the Value argument is F, TM1 Client displays the value sent by the DB Send formula. NBReset Turns NetBIOS reset on and off. Set the Value argument to F to turn NBReset off; set to T to turn it back on. Turns the network polling on and off. When the Value argument is set to T, network polling is turned on. When Value is set to F, network polling is turned off. (Refer to the Applix TM1 Server manual for more information on this option.) Sets the number of Kbytes set for storing TM1 views. Sets the limit of time in seconds to trigger the algorithm that stores TM1 views in memory.
PollingOn
ViewMaxMemory ViewMinTime
QUDEFINE(Cube,Query,Range,Low,Hi,SkpZeroes,SkpCalcs) {QUDEFINE Cube,Query,Range,Low,Hi,SkpZeroes,SkpCalcs}

This function specifies all the parameters for a TM1 Client query set. It is the equivalent of opening the Query dialog box, specifying parameters and saving the query for future use. Once you create and save a query with this function, the query is available from the Query button in the Query dialog box. The query can also be executed by one of the three functions (QUEXPORT, QULOOP, and QUSUBSET) described below. The following list describes the arguments to QUDEFINE. Cube The name of the cube to be queried.
Macros
17
{QUDEFINECube,Query,Range,Low,Hi,SkpZeroes,SkpCalcs}
Query
The name of the query set to be saved for future use.
18
Applix TM1 Client
{QUDEFINECube,Query,Range,Low,Hi,SkpZeroes,SkpCalcs}
Range
The name of a range of cells used to specify the elements to be selected from each dimension. This range must contain as many columns as there are dimensions in the cube. Each column corresponds to a dimension in the cube. The order of the columns must be the same as the order of the dimensions in the cube. In each column, the elements to be included in the query are listed. You can specify a named subset by writing the name of the subset preceded by the character \. Leaving a column blank indicates that the currently selected subset for that dimension is to be used. If a column of the range is empty, the function queries the ALL subset of the corresponding dimension.
The following is an example of a QUDEFINE range for the 5dimensional cube 93sales provided with the examples installed with TM1 Client.
In this example, the actual range is comprised of those cells within the heavy border. The column titles are not necessary and are included for purposes of clarity. A QUDEFINE function using this range would specify Actual as the query elements for the Actvsbud dimension; Germany, France, or Spain, as the query elements for the Region dimension; Units as the query elements for the Account1 dimension; and Jan, Feb, and Mar as the query
Macros
19
QUEXPORT(Cube,Query,File)
elements for the Month dimension. Since no elements are specified under the Model column, the subset ALL is used. Hi and Low The Selection Range for the query set is specified using the Hi and Low arguments. When executing the query, TM1 Client considers only cells containing values less than or equal to the value specified by the Hi argument and greater than or equal to the value specified with the Low argument. Sets the Skip Calculated Values option. Set this argument to TRUE to ignore calculated values in the query. Set this argument to FALSE to consider all values in the query. Sets the Skip Zero/Blank Values option. Set this argument to TRUE to ignore zero or blank values in the query. Set this argument to FALSE to consider all values in the query.
SkpCalcs
SkpZeroes
The QUDEFINE function returns TRUE if the query is successful, FALSE if TM1 is unable to execute the query.
QUEXPORT(Cube,Query,File) {QUEXPORT Cube,Query,File}

This function exports an ASCII representation of the query set specified by the Query argument (see QUDEFINE above) from the cube specified by the Cube argument. The name of the file created upon export is specified with the File argument. The File argument must not include a file extension. The cube specified must be in the default data directory or on a cube server. The comma-delimited ASCII file is written to the directory to which Excel is currently looking.
20
Applix TM1 Client
QULOOP(Cube,Query)
The form of the exported ASCII file is completely normalized, with the cube name in the first field, the elements specifying a specific cell address in the next fields, and the value contained in the cell in the last field.
QULOOP(Cube,Query) {QULOOP Cube,Query}

This function is the equivalent of the TM1 Import/Export Process Cube option. QULOOP creates a record for each cell in the cube specified by the Cube argument that meets the parameters of the query set specified by the Query argument (see QUDEFINE above). The function then reads the record into line 1 of the active worksheet and recalculates the worksheet. The cube specified must be in the default data directory or on a cube server. The form of the record written is completely normalized, with the cube name in the first field, the elements specifying a specific cell address in the next fields, and the value contained in the cell in the last field. Thus, a 5-dimensional cube would create a record with 7 fields: the first containing the cube name, the second through sixth containing the cell address, and the seventh containing the value in the cell.
QUSUBSET(Cube,Query,Dimension,Subset) {QUSUBSET Cube,Query,Dimension,Subset}

This function is the equivalent of executing a previously defined query from the Dimension dialog box and saving the result of the query as a subset. The following list describes the arguments to QUSUBSET. Cube The name of the cube containing the dimension you want to query.
Macros
21
R_SAVE( )
Query Dimension Subset
The name of the query you want to execute. The name of the dimension against which you want to execute the query. The name to assign to the subset defined by the query result.
R_SAVE( ) {R_SAVE}
This function saves the active worksheet as a Rules worksheet and compiles it into a .rux file. The worksheet must have the same name as the cube for which the rule is being compiled. If the function is not successful, no .rux file is created and the tm1erlog file indicates the line that prevented the rule from being compiled.
SUBDEFINE(Dimension,Subset,Range) {SUBDEFINE Dimension,Subset,Range}

This function creates a dimension subset with the name specified by the Subset argument for the dimension specified by the Dimension argument. The subset contains the elements in the cells specified by the Range argument.
SUBPICK(Dimension, Subset, Vertical) {SUBPICK Dimension, Subset, Vertical}

This function calls a dialog box that shows all elements in a specified dimension subset. The Dimension argument specifies the dimension containing the desired subset. The Subset argument is the name of the desired subset. When you select one or more element names from the dialog box, the selected names
22
Applix TM1 Client
T_CLEAR( )
are returned to the current worksheet starting at the current cursor position. The Vertical argument determines the orientation of the element names in the worksheet. In Excel, specify True to orient element names vertically from the current cursor position. In Lotus 1-2-3, specify 1 to orient names vertically. If you do not supply a Vertical argument, element names are oriented horizontally from the current cursor position.
T_CLEAR( ) {T_CLEAR}
This function clears all cubes that are currently in RAM from the computers memory. There are no arguments to this function. It is important to note that if this function is used in a macro, TM1 does not prompt you to save any unsaved cubes. It is important to ensure that the macro saves all relevant cubes with the T_SAVE function before invoking T_CLEAR.
T_CREATE(Cube,D1,D2[,D3,...,D8]) {T CREATE Cube,D1,D2[,D3,...,D8]}

This function creates a cube of up to eight dimensions. T_CREATE provides the same functionality as T_CREATE16, but provides compatibility with older versions of TM1, where cubes could not exceed eight dimensions. The name of the cube to be created is specified by the Cube argument. The names of the dimensions that define the cube are specified in string arguments D1 through D8. A minimum of two dimensions must be specified.
Macros
23
T_CREATE16(Cube,D1,D2[,D3,...,D16])
The cube created is placed in the default data directory. The dimensions specified must also be in the default data directory or on a TM1 server. NOTE: Exercise caution when executing this function within a macro. If a cube already exists with the cube name specified, that cube is overwritten and all data in the cube is lost.
=T_CREATE(Example,Region,Products)
{T_CREATE Example,Region,Products,Month} In the example, TM1 creates a cube named Example. This new cube is made up of the dimensions Region, Products, and Month, in that order.
T_CREATE16(Cube,D1,D2[,D3,...,D16]) {T CREATE16 Cube,D1,D2[,D3,...,D16]}

This function creates a cube with up to 16 dimensions. The name of the cube to be created is specified by the Cube argument. The names of the dimensions that define the cube are specified in arguments D1 through D16. A minimum of two dimensions must be specified. The cube created is placed in the default data directory. The dimensions specified must also be in the default data directory or in a server. NOTE: Exercise caution when executing this function within a macro. If a cube already exists with the cube name specified, that cube is overwritten and all data in the cube is lost.
24
Applix TM1 Client
{T CREATE16 Cube,D1,D2[,D3,...,D16]}
=T_CREATE16(Example,Region,Products,Month)
{T_CREATE16 Example,Region,Products,Month} In the above example, TM1 creates cube named Example. This new cube is made up of the dimensions Region, Products, and Month, in that order.
Macros
25
T_PICK( )
T_PICK( ) {T_PICK Target}

This function calls a dialog box that shows all available cubes in the default data directory or on a cube server. When you select a cube name from the dialog box, T_PICK returns the cube name.. There are no arguments to this function.
This macro displays a dialog box showing the cubes available in the default data directory or on a cube server. When you select a cube name, the name becomes the value of the formula in cell A1. The macro then selects the first cell in the active worksheet and writes the value of the T_PICK formula (which is the selected cube name) in that cell.
When you select a cube name from the dialog box, the selected name is stored in the location specified by the Target argument. The argument can be either a cell address or a range name. {T_PICK B1}
26
Applix TM1 Client
T_SAVE( )
T_SAVE( ) {T_SAVE}
This function saves to disk all cubes currently in RAM. There are no arguments to this function. Note that if this function is invoked in a macro, TM1 does not prompt you for confirmation.
VUSLICE(Cube,View) {VUSLICE Cube,View}

This function creates a spreadsheet slice from a saved view for a given cube. The Cube argument is the name of the cube from which the view is sliced. The View argument is the name of the saved view you ant to slice from the cube. The slice generated begins at the current cursor position, and takes the format of a standard slice created from browse.
W_CALC( ) {W_CALC}
This function forces a recalculation of the active worksheet, and is the equivalent of pressing SHIFT F9. There are no arguments to this function.
Macros
27
W_DBSENABLE(Logical )
W_DBSENABLE(Logical ) {W_DBSENABLE Logical }

This function determines the manner in which the active worksheet executes DBS functions. W_DBSENABLE accepts a single argument, Logical. In Excel, the values for Logical are TRUE or FALSE. In 1-2-3, the values for Logical are 1 or 0. Specify TRUE or 1 to execute each DBS function individually as it is encountered in a worksheet. Specify FALSE or 0 to store the value of all DBS functions in a buffer, and execute the DBS functions in a single block when the worksheet is recalculated. =W_DBSENABLE(TRUE)
{W_DBSENABLE 1}
28
Applix TM1 Client
Error Messages
General Errors
C2 Menu not available while browsing. You have selected a TM1 help menu option that is not available during browsing. You must close the Browse dialog box to select this option. C6 Could not start timer. The Windows timer is currently not available. C5 Invalid Number. You have entered a string of characters that does not correspond to a number. C7 TM1S.LOG exists. See Backup and Recovery. The TM1 Server was not brought down correctly and there are changes to cubes that are not saved. You should check the TM1S.LOG to determine if a Restore Procedure will be required before bringing the TM1 Server back up. See Chapter 5, Backup and Recovery.
General Errors
C8
Error in Formula. You have written a worksheet formula that contains syntax errors. Examine the formula and correct the syntax errors.
C9
Errors Occurred, Please Examine TM1ERLOG.CMA. While processing a file, TM1 help encountered records it could not correctly process. The records that were not processed are written onto TM1ERLOG.CMA.
C11
Formula is too long. You have written a rule or worksheet formula that is longer than 256 characters and therefore cannot be stored in a worksheet cell. Rule formulas may be split and stored in two consecutive cells.
C12
Memory too low to hold Cube. The memory requirements of the cubes and dimensions you have loaded exceed the available memory. You may increase the amount of virtual memory available to Windows using the Control Panel / 386 enhanced facility.
C13
Memory is Low.
Applix TM1 Client
General Errors
System memory is low. You should shut down any extra programs and save your work. If the problem persists, you should increase the memory for the system. C14 No Item was Selected. You attempted to save a subset, query or view without selecting a name. Select or type the name and retry saving. C15 Only One Element May Be Selected. When selecting elements to be used as titles in a browse view, you may only select only one. C16 Path is too long. You have specified a path that is longer than 256 characters. C17 Query Resulted in Empty Subset. You have executed a query for a dimension subset that resulted in no elements. C18 Cant Update Changes. Browse order has been changed, cannot update cube changes. C19 Invalid License for this Release. Your TM1.LIC file is a license for an older version of the software. C20 Feature is not Available in this Version.
Error Messages
General Errors
This version of the software does not support the feature invoked. *NET_ERR A transmission error was detected.
Applix TM1 Client
*KEY_LONG
The Combined key (length of cube name plus length of names of each element) exceeds the maximum message length of 540 bytes. An incorrect cube name or dimension element name has been used to store or retrieve a value from the cube. You have referred to a value on a cube server to which you have no READ or WRITE privileges.
*KEY_ERR
*N/A
Error Messages
Dimension Error Messages

D2 String length not numeric. When an S or string dimension is defined, a string length must be defined in the third column of the dimension worksheet. This string length must be an integer number. This error message appears if the third column cell to the right of a string element is left blank or contains a non-integer number. D3 Calculation component out of place. TM1 help has detected an ename in column 2 that has no element type defined (N, C, or S) to the left of it in column 1 and is not preceded by a C type element or another calculation component. Either move this element name beneath a C type element or another calculation component or place an X to the left of it in column 1. Placing an X in column 1 causes TM1 help to ignore this element. D4 Circular reference in: XXXX. A calculated element forms part of its own definition, directly or indirectly. For example, if X1 is defined as the sum of X2 and X3, and X3 is defined as the sum of X1 and X4, this message will result.
Applix TM1 Client
D5
Duplicate Element: XXXX. Two elements with the same name have been defined in the dimension. One of them must be removed or have its name changed.
D6
Element name is blank. A C, N, or S has been placed in a cell in column 1 with no corresponding element name to the left of it in column 2.
D7
Element not defined: XXXX. An element has been included as a component of a calculated element but has not been defined as an N element elsewhere in the dimension worksheet.
D8
Invalid Element type. A letter other than C, N, S, or X has been placed in a cell in column 1.
D9
Maximum number of Elements exceeded. The number of elements in the dimension exceeds the limits established for your version.
D10
No Elements in Dimension. An attempt has been made to save a dimension worksheet that contains no elements. At least one dimension element must be defined to eliminate this message.
Error Messages
D12
Invalid DD4 File. Index file for the dimension does not have the expected format. Re-save the dimension to recreate the index file.
D13
Invalid DIM File. Index file for the dimension does not have the expected format. Re-save the dimension to recreate the index file.
D15
Element has more than 72 Characters truncating. You have specified an element with more than 72 characters. The name will be truncated down to 72 characters.
D16
Dimension already exists. You have attempted to create a new dimension where one already exists by the same name.
D17
Dimension does not occur in query cube. Dimension DIM file could not be found.
D18
Unrecognized statement. When compiling a dimension, valid statements are N, C, X, S, or !.
D19
Type of Element may not be changed. Cannot change type of element when
Applix TM1 Client
reloading dimension on active TM1 Server. D20 Calculation Component Defined as Simple Element. Error occurs when ! syntax is used to define consolidations, and consolidation and component are mismatched
D22
String Status of Dimension cannot be changed. You cannot add string fields to dimension that does not already have any when reloading dimension to an active TM1 Server.
Error Messages
Network Error Messages

N1 Network Busy. One of the servers that you are using is busy. It may be calculating a large consolidation. Wait a few minutes and then press Yes to try again. If problem persists, a network error may be the cause. N3 Already Connected to Server XXXX. You have attempted to connect to a server to which you are already connected. N4 TM1 Server Not Active. An attempt has been made to log into a nonactive server. Check the server name used during log-in. N5 Request Was Not Successful. You have issued a RESERVE, UNRESERVE, or LOCK request for an item that someone else has already placed a LOCK or RESERVEon, or one for which you have no Lock or Reserve privileges. Have the work group administrator check your privileges for the elements and cubes for which the request was issued.
10
Applix TM1 Client
N6
Client Not Registered. You have attempted to log on with a user name that is not listed in the }CLI_LST dimension on the server. Check the user name with which you logged on to insure that it matches the }CLI_LST dimension.
N7
Write Access Denied. You have attempted to either update a number that is calculated by the cube or, in the case of network cubes, have attempted to update a number for which you do not have WRITE privileges.
N8
Invalid Server Name XXXX. Server name contained illegal characters or server name was greater than eight characters.
N10
Invalid Password. You have attempted to log on with an invalid password. Check the password and try again.
N11
Maximum Number of Clients Reached. More clients than allowed by the servers license have attempted to log on.
N12
Incorrect TM1 Server License. TM1.LIC is either out of date of for the wrong software version.
Error Messages
11
N19
NETBIOS Subsystem Not Active. The NetBIOS protocol must be loaded on your computer.
N20
Not Connected to Server XXXX. Client is not currently connected to the TM1 Server.
N21
Connection Failed. Connection to TM1 Server failed. Check that the TM1 Server is still active and the network connection is still working.
N28
Client Already Logged In. Do You Want To Force Client Off? You have attempted to log-in as a client already active on the server. By responding Yes to this question, the connection of the other client will be severed and your connection will be established.
N29
Maximum Number of Dimensions Exceeded. The license you have does not support the number of dimensions you have specified.
N33
Cant Update Administrator File. Server cannot add its name to TM1.ADM file.
12
Applix TM1 Client
N34
Network Subsystem Failed. Cannot open Network Subsystem, check network installation.
N36
Server Out of Memory. Cant Continue. The Server is out of memory. Increase the amount of RAM and Virtual memory. You should check the TM1S.LOG to determine if a restore procedure will be required before bringing the TM1 Server back up. See Chapter 5, Backup and Recovery.
N37
Parameter Error. See Log for More Information. Parameter error on the TM1 Server. Check the log window on the TM1 Server to determine the problem.
N38
Server Name Not Provided in Parameter List. With an IPX or NetBIOS TM1 Server, the server name is required in the parameter list.
N39
Cant Load XXXX or Windows Sockets not Installed. Cannot load WINSOCK.DLL or WINSOCK32.DLL.
N40
Cant Load Sockets Function. Windows Sockets error, cannot find the function address.
Error Messages
13
N41
Windows Sockets Subsystem Not Ready for Communication. Check Sockets Subsystem.
N42
Invalid Version of Windows Sockets. Version 1.1 or higher supported.
N43
Cant Find Remote XXXX. TM1 Server cannot find remote machine.
N44
Cant Open Socket. Cannot open socket. Check Windows Sockets installation.
N45
Connection to Server XXXX Failed. Unable to connect to TM1 Server. Possible network error.
N46
Connection Severed Sending. Communication with TM1 Server interrupted during send.
N47
Connection Severed Receiving. Communication with TM1 Server interrupted during receive.
N48
Remote Computer Disconnected. Connection Closed. Remote computer was disconnected, or TM1 application was closed.
14
Applix TM1 Client
N49
Listen Failed. TM1 Server listen failed, check installation.
N50
Maximum Number of Tasks Exceeded. Maximum number of tasks exceeded by API application
N51
NETBIOS Error: Code XXXX. NetBIOS internal error.
N52
Server XXXX Not Active or Connection Failed. Check TM1 Server and the network connection.
N53
Request Not completed. Connection Closed. Program timed out before request was completed.
N54
Version of Server not compatible with this Client. Client and TM1 Server are of different dates or versions.
N55
Reloading Failed. Dimension or cube failed to reload. Check files.
Error Messages
15
N56
Not Connected to any Server. Client is not currently connected to a TM1 Server.
N57
Cant Open More Connections. Client is connected to the Maximum number of TM1 Servers.
N58
Invalid parameter XXXX. Check parameter list on TM1 Server for errors.
N59
Cant Load XXXX Or Tli Not Installed. You have attempted to log on with an invalid password. Check the password and try again.
N62
Bind failed. Please check your network connections.
16
Applix TM1 Client
Rules Error Messages
Rules Error Messages

R1 XXXX Not a Dimension of this CUBE. You have written an expression of the form !dimname or dimname:elname, where dimname is not a dimension of the cube for which the rules are being defined. R2 Element Name XXXX Ambiguous. You have referred to an element which occurs in more than one dimension. You must precede the element name with the name of the dimension as follows: dimname:elname. R3 Element Name XXXX Not Found. You have referred to an element that does not occur in the cube. R4 Error evaluating rule: possible circular reference. You have either written a set of rules with a circular reference, or you have exceeded the stack capacity of the rules processor. Please refer to Chapter 12, Technical Overview/ Performance Optimization, of the TM1 Perspectives Users Manual. R5 Formula Error On or Near This Line. The rules compiler has identified a syntax error in the statement that appears on this line.
Error Messages
17
R6
Maximum size of Rule reached. The size of a compiled rules file is limited to about 64k. You may need to simplify or combine rules if you get this message.
R8
Error Evaluating Rule. Contact your reseller or Applix, Inc. for support.
R9
Error Evaluating Rule: Invalid Key. Invalid name given in DB formula.
18
Applix TM1 Client
System Error Messages
System Error Messages

S3 File XXXX not found. You have specified a file that does not exist. S5 Out of Memory. Increase the amount of RAM and virtual memory. S6 Printer not ready. Check that the printer is ready to print. S7 File XXXX is Read-Only. Check network security rights for this file or its directory. S10 Record size too big. ASCII file records are limited to 2048 bytes in TM1 help. S15 Directory XXXX not found. You have specified a directory that does not exist.
Error Messages
19
Cube Error Messages
Cube Error Messages

T1 Write Access Denied. You have attempted to update a number that is calculated by the cube or, in the case of network cubes, attempted to update a number for which you do not have WRITE privileges. T8 Not enough Dimensions specified. An attempt has been made to create a cube with less than two dimensions. At least two dimensions must be specified when creating a cube. T11 Bad CUBE XXXX. A cube (.tab) file has been read that does not conform to TM1 help format. The file may not be used. T12 Dimension other than last one contain strings. An attempt has been made to create a cube in which a dimension other than the last dimension has string elements. TM1 help allows string elements only in the last dimension of a cube.
20
Applix TM1 Client
Cube Error Messages
T14
Mismatch in number of Dimensions for CUBE: XXXX. The user has attempted to refer to a cube with a DB formula in which the number of dimensions defined in a formula is not the same as the number of dimensions contained in the cube. For example, if 92act4d.tab contains four dimensions and you write a DBS5 formula referring to 92act4d.tab, this message will be returned.
T17
Element XXXX not in Dimension XXXX. This element is not listed in the dimension.
T18
Saving Cubes Not Supported By Evaluation Version. The evaluation version does not support the saving of changes to local cubes.
Error Messages
21
Index
A
Access Privileges Definitions 1-10 Automatic Consolidation 1-5 Recalculation Turning Off in Excel 2-2 Turning Off in Lotus 2-3 from Queries 4-20 Cube Data Viewing 2-6 Cube Displayed Changing 2-17 Cube Reference 2-18 Writing 2-20 Cube(s) Defined 1-2 Cubes Clearing from Memory 4-22 Creating 4-22 Saving 4-25 Selecting 4-24
B
Browse Dialog Box 2-7
C
CALC Flag 2-13 Changing Elements Displayed 2-8, 2-15 Perspectives 2-10 The Cube Displayed 2-17 Checking Options 4-14 Clearing Cubes from Memory 4-22 Client 1-9 Client/Server Architecture 1-8 Connecting to Multiple Servers 2-27 Connecting to a Cube Server 4-13 Consolidated Values Displaying 2-9 Creating a Slice Worksheet 2-14 Cubes 4-22 Slice Worksheets 4-25 Subsets 4-21
D
D_FSAVE 4-5 D_PICK 4-7 D_SAVE 4-8 Data Identification By Name 1-3 Database Values Reserving and Locking 2-23 DBRn 3-4 DBRWn 3-5, 3-9 DBRXn 3-6 DBSn 3-7 Default View 2-7 Defining Queries 4-17 DFRST 3-10 dimension error messages A-5 Dimension(s) Multiple, General Information 1-4
DIMIX 3-11 DIMNM 3-11 DIMSIZ 3-12 Disconnecting from SERVERs 2-27 Disconnecting from Cube Servers 4-14 Displaying Consolidated Values 2-9 DNEXT 3-13 DNLEV 3-13 DTYPE 3-14
F
Functions Macro D_FSAVE 4-5 D_PICK 4-7 D_SAVE 4-8 E_PICK 19 4-8 I_EXPORT 4-9 I_NAMES 4-11 I_PROCESS 4-11 N_CONNECT 4-13 N_DISCONNECT 4-14 OPTGET 4-14 OPTSET 4-15 QUDEFINE 4-17 QUEXPORT 4-19 QULOOP 4-20 QUSUBSET 4-20 R_SAVE 4-21 SUBDEFINE 4-21 SUBPICK 4-21 T_CLEAR 4-22 T_CREATE 4-22 T_CREATE16 4-23 T_PICK 4-24 T_SAVE 4-25 VUSLICE 4-25 Worksheet DBGEN 3-2 DBGEN16 3-3 DBRn 3-4 DBRWn 3-5, 3-9 DBRXn 3-6 DBSn 3-7 DBSSn 3-8 DFRST 3-10
E
E_PICK 4-8 ELCOMP 3-15, 3-16 Elements Displayed Changing 2-8, 2-15 ELISCOMP 3-17 ELISPAR 3-18 ELLEV 3-19 ELPAR 3-20 ELPARN 3-21 ELSLEN 3-21 ELWEIGHT 3-22 Entering Data 2-11 error messages cube A-19 dimension A-5 general A-1, A-19 network A-9 rules A-16 system A-18 Excel Loading 2-1 Exporting based on Queries 4-19 Cube Data 4-9
Applix TM1 Client
DIMIX 3-11 DIMNM 3-11 DIMSIZ 3-12 DNEXT 3-13 DNLEV 3-13 DTYPE 3-14 ELCOMP 3-15 ELCOMPN 3-16 ELISCOMP 3-17 ELISPAR 3-18 ELLEV 3-19 ELPAR 3-20 ELPARN 3-21 ELSLEN 3-21 ELWEIGHT 3-22 SUBNM 3-23 SUBSIZ 3-24 TABDIM 3-24 VIEW 3-25
M
Macro Functions D_FSAVE 4-5 D_PICK 4-7 D_SAVE 4-8 E_PICK 4-8 I_EXPORT 4-9 I_NAMES 4-11 I_PROCESS 4-11 N_CONNECT 4-13 N_DISCONNECT 4-14 OPTGET 4-14 OPTSET 4-15 QUDEFINE 4-17 QUEXPORT 4-19 QULOOP 4-20 QUSUBSET 4-20 R_SAVE 4-21 SUBDEFINE 4-21 SUBPICK 4-21 T_CLEAR 4-22 T_CREATE 4-22 T_CREATE16 4-23 T_PICK 4-24 T_SAVE 4-25 VUSLICE 4-25 Multiple Servers Connecting To 2-27
I
I_EXPORT 4-9 I_NAMES 4-11 I_PROCESS 4-11
L
Loading Excel 2-1 Lotus 1-2-3 2-3 Locking and Reserving Database Values 2-23 Logging On TM1 CLIENT 2-4 Lotus 1-2-3 Loading 2-3
N
N_CONNECT 4-13 N_DISCONNECT 4-14 Network Options Setting 2-26
Index
O
Opening Dimension Dialog Box 4-7 OPTGET 4-14 OPTSET 4-15
P
Password(s) Changing 2-5 Perspectives Changing 2-10 Privileges Definitions 1-10 Processing from Cubes 4-20 Text Files 4-11
Q
QUDEFINE 4-17 Queries Defining 4-17 QUEXPORT 4-19 QULOOP 4-20 QUSUBSET 4-20
Highest Level of Elements 3-13 Index Number of a Dimension Element 3-11 Length of Element Names 3-21 Level of Elements 3-19 Next Element 3-13 Number of Components 3-16 Number of Elements 3-12 Number of Elements in a Subset 3-24 Number of Parent Elements 3-21 Parent Elements 3-18 Parents of Elements 3-20 Subset Element Names 3-23 Type of Elements 3-14 Unique Names 4-11 Weight of Elements 3-22 Rules Error Messages A-16
S
Saving Cube Rules 4-21 Cubes 4-25 Dimensions 4-8 Large Dimensions 4-5 the Slice Worksheet 2-18 Security Privileges Definitions 1-10 Selecting Cubes 4-24 Dimension Elements 4-8 Elements from Subsets 4-21 Sending Numeric Values to a Cube 3-7 String Values to a Cube 3-8 Setting
R
Reserving and Locking Database Values 2-23 Restoring Transaction Log 3-2, 3-3 Restoring Transaction Log17- 3-3 Retrieving Component Elements 3-17 Components of Elements 3-15 Cube Dimensions 3-24 Element Names 3-11 First Element of a Dimension 3-10
Applix TM1 Client
Network Options 2-26 Options 4-15 the Reference Style In Excel 2-2 Slice Worksheet Creating 2-14 Saving 2-18 Slice(s) Definition 1-6 Spreadsheet Connector Connecting 4-13 Disconnecting from 4-14 SUBDEFINE 4-21 SUBNM 3-23 SUBPICK 4-21 SUBSIZ 3-24 system error messages A-18
V
Viewing Cube Data 2-6 VUSLICE 4-25
W
Worksheet Functions DBGEN 3-2 DBGEN16 3-3 DBRn 3-4 DBRWn 3-5, 3-9 DBRXn 3-6 DBSn 3-7 DBSSn 3-8 DFRST 3-10 DIMIX 3-11 DIMNM 3-11 DIMSIZ 3-12 DNEXT 3-13 DNLEV 3-13 DTYPE 3-14 ELCOMP 3-15 ELCOMPN 3-16 ELISCOMP 3-17 ELISPAR 3-18 ELLEV 3-19 ELPAR 3-20 ELPARN 3-21 ELSLEN 3-21 ELWEIGHT 3-22 SUBNM 3-23 SUBSIZ 3-24 TABDIM 3-24 VIEW 3-25 Worksheet Slice Definition 1-6 Worksheets
T
T_CLEAR 4-22 T_CREATE 4-22 T_CREATE16 4-23 T_PICK 4-24 T_SAVE 4-25 TABDIM 3-24 TM1 Client Administration 1-9 General Information 1-1 Logging On 2-4 TM1 Server 1-1, 1-8 TM1 SERVERs Disconnecting from 2-27 Transaction Log 1-11 Turning Off Automatic Recalculation In Excel 2-2 In Lotus 2-3
Index
Creating from Cubes 4-25 Writing a Cube Reference 2-20
Applix TM1 Client
Index

Applix TM1 Client 2.6 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Applix TM1 Client 2.6 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Applix TM1 Client

Print Date: 6/97

Transaction Logging ............................................................... 1-11