ASCII and Text TurboIntegrator Functions:
These functions pertain to ASCII and Text.

ASCIIDelete:
This is a TM1 TurboIntegrator function, valid only in TurboIntegrator processes.
This function deletes an ASCII file.

Syntax:
ASCIIDelete(FileName);

Arguments:

Argument	Description
FileName	The name of the ASCII file you want to delete. If a full parth is not specified, TM1 searches for the file in the server data directory.

Example:
ASCIIDelete('C:\exported_data\2002Q1Results.cma');
This example deletes the ASCII file named 2002Q1Results.cma from the C:\exported_data directory.

ASCIIOutput:
This is a TM1 TurboIntegrator function, valid only in TurboIntegrator processes.
This function writes a comma-delimited record to an ASCII file.
The ASCII file is opened when the first record is written, and is closed when the TurboIntegrator procedure (Prolog, Metadata, Data, or Epilog) containing the ASCIIIOutput function finishes processing.

Important: If you use the ASCIIOutput function to write to the same file in multiple procedures (tabs) of a TurboIntegrator process, the file will be overwritten each time it is opened for a new procedure.

Syntax:
ASCIIOutput(FileName, String 1, String 2, ...String n);

Arguments:

Argument	Description
FileName	A full path to the ASCII file to which you want to write the record. Path must include a file extension.
String1...Stringn	A string that corresponds to each field you want to create in the ASCII file. This argument can be a string or a TurboIntegrator variable for a string.

Example:
ASCIIOutput('NewCube.cma', V1, V2, V3, V4, V5 );
This example writes a record to the NewCube.cma ASCII file. Each field in the record corresponds to a variable assigned by TurboIntegrator to a column in your data source.

SetInputCharacterSet:
This is a TM1 TurboIntegrator function, valid only in TurboIntegrator processes.
When a TurboIntegrator process reads an external file as input, it needs to know the character set in which that external file was written. If the file contains a valid byte-order-mark, TM1 functions will correctly convert the file to UTF-8 if required.

For formats lacking a valid byte-order-mark, the characters must be converted from some other encoding to UTF-8. The SetInputCharacterSet function lets you specify the character set used in a TurboIntegrator data source. If the proper converters are present on the machine hosting the TM1 server, the input file will be converted to the Unicode character set required by TM1.

Syntax:
SetInputCharacterSet (CharacterSet);

Arguments:

Argument	Description
CharacterSet	The character encoding in the input file to be used by the TurboIntegrator process. If the CharacterSet argument is not a known character type, the type defaults to the system locale.

Example:
SetInputCharacterSet('TM1CS_ISO_8859_11');
This example specifies that the input character set for the TurboIntegrator data source is ISO-8859-11 Latin/Thai.

SetOutputCharacterSet:
This is a TM1 TurboIntegrator function, valid only in TurboIntegrator processes.
The SetOutputCharacterSet function lets you specify the character set to be used when writing to a text file with the TextOutput function.
SetOutputCharacterSet should immediately precede TextOutput in a TurboIntegrator process.

Syntax:
SetOutputCharacterSet( FileName, CharacterSet );

Arguments:

Argument	Description
FileName	A full path to the text file for which you want to specify a character set. The path must include a file extension. This argument should be indentical to the FileName argument for the TextOutput function.
CharacterSet	The character encoding to use when writing to the output file.

TextOutput:
This is a TM1 TurboIntegrator function, valid only in TurboIntegrator processes.
This function writes a comma-delimited record to a text file. By default TextOutput writes characters in the locale character set of the TM1 server machine. To create a file in a different character set, call the function SetOutputCharacterSetbefore calling TextOutput.
The text file is opened when the first record is written, and is closed when the TurboIntegrator procedure (Prolog, Metadata, Data, or Epilog) containing the TextOutput function finishes processing.

Important: If you use the TextOutput function to write to the same file in multiple procedures (tabs) of a TurboIntegrator process, the file will be overwritten each time it is opened for a new procedure.

Syntax:
TextOutput(FileName, String 1, String 2, ...String n);

Arguments:

Argument	Description
FileName	A full path to the ASCII file to which you want to write the record. Path must include a file extension.
String1...Stringn	A string that corresponds to each field you want to create in the ASCII file. This argument can be a string or a TurboIntegrator variable for a string.

Example:
TextOutput('NewCube.cma', V1, V2, V3, V4, V5 );
This example writes a record to the NewCube.cma file. Each field in the record corresponds to a variable assigned by TurboIntegrator to a column in your data source.

Read this aritcle completely...

TM1 TurboIntegrator lets you manipulate TM1 data and metadata when you define a process.
This is accomplished through the use of functions in the Prolog, Metadata, Data, and Epilog subtabs within the Advanced tab of the TurboIntegrator window. These sub-tabs include generated statements based on settings and options you select when defining a TurboIntegrator process. Any functions you create must appear after the generated statements.

The TI functions in this chapter are sorted by category:

ASCII and Text Turbointegrator Functions:
ASCIIDelete
ASCIIOutput
SetInputCharacterSet
SetOutputCharacterSet
TextOutput

Attribute Manipulation TurboIntegrator Functions:
AttrDelete
AttrInsert
AttrPutN
AttrPutS

Chore Management TurboIntegrator Functions:
ChoreQuit
SetChoreVerboseMessages

Cube Manipulation TurboIntegrator Functions:
CellGetN
CubeCreate
CellGetS
CubeDestroy
CellIsUpdateable
CubeExists
CellPutN
CubeGetLogChanges
CellPutProportionalSpread
CubeSetLogChanges
CellPutS
CubeUnload

Dimension Manipulation TurboIntegrator Functions:
DimensionCreate
DimensionElementDelete
DimensionDeleteAllElements
DimensionElementInsert
DimensionDestroy
DimensionElementPrincipalName
DimensionElementComponentAdd
DimensionExists
DimensionElementComponentDelete
DimensionSortOrder

ODBC TurboIntegrator Functions:
ODBCClose
ODBCOutput
ODBCOpen

Process Control TurboIntegrator Functions:
ExecuteCommand
ItemSkip
ExecuteProcess
ProcessBreak
GetProcessErrorFileDirectory
ProcessError
GetProcessErrorFilename
ProcessQuit
If
While
ItemReject

Rules Management TurboIntegrator Functions:
CubeProcessFeeders
RuleLoadFromFile

Security TurboIntegrator Functions:
AddClient
DeleteGroup
AddGroup
ElementSecurityGet
AssignClientToGroup
ElementSecurityPut
AssignClientPassword
RemoveClientFromGroup
DeleteClient
SecurityRefresh

Server Manipulation TurboIntegrator Functions:
BatchUpdateFinish
SaveDataAll
BatchUpdateFinishWait
ServerShutdown
BatchUpdateStart

Subset Manipulation TurboIntegrator Functions:
SubsetAliasSet
SubsetExists
SubsetCreate
SubsetExpandAboveSet
SubsetCreateByMDX
SubsetFormatStyleSet
SubsetDeleteAllElements
SubsetGetElementName
SubsetDestroy
SubsetGetSize
SubsetElementDelete
SubsetIsAllSet
SubsetElementInsert

View Manipulation TurboIntegrator Functions:
PublishView
ViewExtractSkipCalcsSet
ViewColumnDimensionSet
ViewExtractSkipRuleValuesSet
ViewColumnSuppressZeroesSet
ViewExtractSkipZeroesSet
ViewConstruct
ViewRowDimensionSet
ViewCreate
ViewRowSuppressZeroesSet
ViewDestroy
ViewTitleDimensionSet
ViewExists
ViewTitleElementSet
ViewExtractSkipCalcsSet
ViewZeroOut
ViewExtractSkipRuleValuesSet

Miscellaneous TurboIntegrator Functions:
Expand
StringToNumber
FileExists
StringToNumberEx
NumberToString
WildcardFileSearch
NumberToStringEx
TM1ProcessError.log file

There is no interface to assist in the creation of TurboIntegrator functions. You must enter functions by hand directly in the appropriate sub-tab within the Advanced tab. String arguments to TurboIntegrator functions must be enclosed in single quotation marks. A semi-colon (;) must be included to indicate the end of each function in the TurboIntegrator window.

In addition to these TurboIntegrator functions, you can also incorporate all standard TM1 Rules functions in a process definition, with the exception of the STET function. Important: Each argument to TurboIntegrator functions is limited to 256 bytes. A TurboIntegrator function can accept multiple arguments, and each argument is limited to 256 bytes.

Read this aritcle completely...

FEEDERS:
When you use a SKIPCHECK declaration to restore the sparse consolidation in a TM1 rule, you must also ensure that all rules-derived cells are identified by feeder statements. To do this, insert a FEEDERS declaration immediately following all rules statements:
FEEDERS;

Immediately following the FEEDERS declaration you should create feeders statements that identify the rules-derived cells in the cube.

FEEDSTRINGS:
Rule-generated string values are not displayed when a view is zero-suppressed unless the string resides in a cell that is fed.

To enable feeding of string cells, insert the FEEDSTRINGS declaration as the first line of your rule:
FEEDSTRINGS;

Once this declaration is in place, you can set up feeders for string cells in a cube view, and rely on the string to be available to other rules even if the view is zero-suppressed. Statements that define feeders for string cells should be created below the FEEDERS declaration in your rule.

As in the case of numeric feeders, a feed to a consolidated cell results in feeding of all components of the consolidation. Because you can store strings in consolidated cells, you must pay special attention if such cells are used to feed other cells.

Overuse of string feeders can result in calculation explosions and poor application performance.

Read this aritcle completely...

SKIPCHECK:

During consolidations, TM1 uses a sparse consolidation algorithm to skip over cells that contain zero or are empty. This algorithm speeds up consolidation calculations in cubes that are highly sparse. A sparse cube is a cube in which the number of populated cells as a percentage of total cells is low.

When consolidating data in cubes that have rules defined, TM1 turns off this sparse consolidation algorithm because one or more empty cells may in fact be calculated by a rule. (Skipping rules-calculated cells will cause consolidated totals to be incorrect). When the sparse consolidation algorithm is turned off, every cell is checked for a value during consolidation. This can slow down calculations in cubes that are very large and sparse.

You can restore sparse consolidation and improve performance by inserting a SKIPCHECK declaration at the beginning of a TM1 rule:
SKIPCHECK;

If your rule uses a FEEDSTRINGS statement, the SKIPCHECK statement should be the second statement in your rule. If your rule does not use a FEEDSTRINGS statement, the SKIPCHECK statement should be the first statement in your rule.

When you use SKIPCHECK to restore sparse consolidation, you must also ensure that your rule includes a FEEDERS declaration and that all rules-derived cells are identified by feeder statements.

Read this aritcle completely...

Element Information Rules Functions:

• DIMIX
• DTYPE
• ELCOMP
• ELCOMPN
• ELISANC
• ELISCOMP
• ELISPAR
• ELLEV
• ELPAR
• ELPARN
• ELWEIGHT

DIMIX:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
DIMIX returns the index number of an element within a dimension.

Syntax:
DIMIX(dimension, element)

Arguments:

Argument	Description
dimension	A valid dimension name.
element	The name of an element within the dimension. If the element is not a member of the dimension specified, the function returns 0.

Example:
DIMIX('Region','Brazil')
Brazil has an index value of three in the Region dimension. The example returns 3.

DTYPE:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
DTYPE returns information about the element type of a specified element. 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 consolidated element.

Syntax:
DTYPE(dimension, element)

Arguments:

Argument	Description
dimension	A valid dimension name.
element	The name of an element within the dimension.

Example:
DTYPE('Region','Europe')
The element Europe is a consolidated element of the Region dimension, so the example returns C.

ELCOMP:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
ELCOMP returns the name of a child of a consolidated element in a specified dimension. If the element argument is not a consolidated element, the function returns 0.

Syntax:
ELCOMP(dimension, element, position)

Arguments:

Argument	Description
dimension	A valid dimension name.
element	The name of a consolidated element within the dimension.
position	A positive value less than or equal to the total number of children in the specified element.

Example:
ELCOMP('Region','Central Europe',2)
In the dimension Region, the consolidated element Central Europe is a consolidation of the children France and Germany. Germany is in the second position in this consolidation. Accordingly, the example returns Germany.

ELCOMPN:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
ELCOMPN returns the number of components in a specified element. If the element argument is not a consolidated element, the function returns 0.

Syntax:
ELCOMPN(dimension, element)

Arguments:

Argument	Description
dimension	A valid dimension name.
element	The name of a consolidated element within the dimension.

Example:
ELCOMPN('Region','Scandanavia')
In the Region dimension, the element Scandanavia is a consolidation of three elements. The example returns 3.

ELISANC:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
ELISANC determines whether element1 is an ancestor of element2 in the specified dimension. The function returns 1 if element1 is an ancestor of element2, otherwise the function returns 0.

Syntax:
ELISANC(dimension, element1, element2)

Arguments:

Argument	Description
dimension	A valid dimension name.
element1	The name of an element within the dimension.
element2	The name of an element within the dimension.

Example:
ELISANC('Region', 'Europe', 'Germany')
In the dimension Region, the element Europe is an ancestor of Germany. The example returns 1.

ELISCOMP:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
ELISCOMP determines whether element1 is a child of element2 in the specified dimension. The function returns 1 if element1 is a child of element2, otherwise the function returns 0.

Syntax:
ELISCOMP(dimension, element1, element2)

Arguments:

Argument	Description
dimension	A valid dimension name.
element1	The name of an element within the dimension.
element2	The name of an element within the dimension.

Example:
ELISCOMP('Region','Germany','Central Europe')
In the dimension Region, the element Central Europe is a consolidation of two elements, Germany and France. The example returns 1.

Note: this function returns 1 only for immediate children. In the above example, Germany is a child of Central Europe. Further, Central Europe is a child of Europe. However, because the function returns 1 only for immediate children, the following example returns 0:
ELISCOMP('Region','Germany','Europe')

ELISPAR:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
ELISPAR determines whether element1 is a parent of element2 in the specified dimension. The function returns 1 if element1 is a parent of element2, otherwise the function returns 0.

Syntax:
ELISPAR(dimension, element1, element2)

Arguments:

Argument	Description
dimension	A valid dimension name.
element1	The name of an element within the dimension.
element2	The name of an element within the dimension.

Example:
ELISPAR('Region','Central Europe','Germany')
In the dimension Region, the consolidated element Central Europe is the parent of both Germany and France. Accordingly, the example returns 1.

Note: this function returns 1 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 0:
ELISPAR('Region','Europe','Germany')

ELLEV:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
ELLEV returns the level of an element within a dimension.

Syntax:
ELLEV(dimension, element)

Arguments:

Argument	Description
dimension	A valid dimension name.
element	The name of an element within the dimension.

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). The example returns 2, as Europe is a Level 2 element.

ELPAR:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
ELPAR returns the parent of an element in a specified dimension

Syntax:
ELPAR(dimension, element, index)

Arguments:

Argument	Description
dimension	A valid dimension name.
element	The name of an element within the dimension.
index	A positive value less than or equal to the total number of consolidated elements (parents) that use the element argument as a child.

Example:
ELPAR('Model','Wagon 4WD',2)
In the dimension Model, the element Wagon 4WD is a child 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.
The example returns Total 4WD, as this is the second instance of a parent to Wagon 4WD within the Model dimension.

ELPARN:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
ELPARN returns the number of parents of an element in a specified dimension.

Syntax:
ELPARN(dimension, element)

Arguments:

Argument	Description
dimension	A valid dimension name.
element	The name of a consolidated element within the dimension.

Example:
ELPARN('Model','Wagon 4WD')
In the Model dimension, the element Wagon 4WD is a child of both Total Wagons and Total 4WD. Therefore, both Total Wagons and Total 4WD are parents of Wagon 4WD. The function returns 2.

ELWEIGHT:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
ELWEIGHT returns the weight of a child in a consolidated element.

Syntax:
ELWEIGHT(dimension, element1, element2)

Arguments:

Argument	Description
dimension	A valid dimension name.
element1	The name of an element within the dimension.
element2	The name of an element within the dimension.

Example:
ELWEIGHT('Account1','Gross margin','Variable Costs')
The element Variable Costs, which is a child of Gross margin, has a weight of -1. The example returns -1.

Read this aritcle completely...

Privacy Policy:

WEBSITE OF DATAWAREHOUSING SUPPORT
This statement relates to our privacy practices in connection with this website. We are not responsible for the content or privacy practices of other websites. Any external links to other websites are clearly identifiable as such.

GENERAL STATEMENT
Budgeting Solutions fully respects your right to privacy, and will not collect any personal information about you on this website without your clear permission. Any personal information which you volunteer to Datawarehousing Support will be treated with the highest standards of security and confidentiality.

Collection and use of personal information
Datawarehousing Support does not collect any personal data about you on this website, apart from information which you volunteer (for example by e-mailing us). Any information which you provide in this way is not made available to any third parties, and is used by Budgeting Solutions only in line with the purpose for which you provided it.

COLLECTION & USE OF TECHNICAL INFORMATION
This website does not use cookies, apart from temporary "session" cookies which enable a visitor's web browser to remember which pages on this website have already been visited. Visitors can use this website with no loss of functionality if cookies are disabled from the web browser.
Technical details in connection with visits to this website are logged for statistical purposes. No information is collected that could be used by us to identify website visitors.

Read this aritcle completely...

Disclaimer:

NOTICE:
These are the terms and conditions ("the terms") governing the use of this website ("the Website") which is wholly owned by Datawarehousing Support. These terms apply to each user and/or visitor to the Website and are governed by Indian law.

PROPRIETOR AND PROPRIETARY INFORMATION
Information on this Website is the property of Datawarehousing Support. The materials contained in this site are protected by copyright law. The contents of the Website are available to any user and/or visitor for personal reference only and may not be reproduced in any manner whatsoever either in whole or in part without the prior permission of Datawarehousing Support, its authorised agents or representatives.Datawarehousing Support reserves the right in its absolute discretion:
(a) to add to or remove any material from the Website or to amend, alter, redesign or change anything contained in or on it at any time; and
(b) to monitor, suspend, revoke, or otherwise limit access to the Website at any time.

NO WARRANTIES
The use of this Website is at the visitor's or user's own personal risk. Datawarehousing Support does not warrant the content, accuracy or veracity of any material or other information on the Website nor does it warrant that the Website is free from errors, faults, viruses or other computer or data-corrupting or data-damaging material.

The Website contains links to other sites or addresses on the web. External sites are not part of the Website and do not belong to Datawarehousing Support. Datawarehousing Support does not approve or endorse other websites nor is it responsible for their contents.Descriptions of, or references to, products, services or publications within the Website do not constitute or imply their endorsement or recommendation in any way by Datawarehousing Support. No reference in the Website to any specific product, process, or service by trade name, trademark, manufacturer, or otherwise, shall be used for advertising or product endorsement purposes.

EXCLUSION OF LIABILITY
To the maximum extent permitted by law Datawarehousing Support excludes liability for any loss, claim, damages or any special, consequential, exemplary or punitive damages (whether direct or indirectly incurred) of any kind arising out of or in connection with any visitor's or user's access to, or use of the Website, or any material thereon, whether based in contract, tort or whether negligent or otherwise.

Read this aritcle completely...

Dimension Information Rules Functions:

• ATTRN
• ATTRS
• ConsolidateChildren
• DIMNM
• DIMSIZ
• DNEXT
• DNLEV
• TABDIM

ATTRN:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
ATTRN returns a numeric attribute for a specified element of a dimension.
Syntax:
ATTRN(dimension, element, attribute)

Arguments:

Argument	Description
dimension	A valid dimension name.
element	An element of the dimension.
attribute	The attribute for which you want to retrieve a value. This argument must be a valid attribute of the element.

Example:
ATTRN('Model', 'L Series 1.8L Sedan', 'Manufacture Code')
In this example, the function returns the numeric value of the Manufacture Code attribute of the L Series 1.8L Sedan element in the Model dimension.

ATTRS:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
ATTRS returns a string attribute for a specified element of a dimension.
Syntax:
ATTRS(dimension, element, attribute)

Arguments:

Argument	Description
dimension	A valid dimension name.
element	An element of the dimension.
attribute	The attribute for which you want to retrieve a value. This argument must be a valid attribute of the element.

Example:
ATTRS('Model', 'L Series 1.8L Sedan', 'Manufacture Code')
In this example, the function returns the string value of the Manufacture Code attribute of the L Series 1.8L Sedan element in the Model dimension.

ConsolidateChildren:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
This function forces consolidated values to be calculated by summing immediate children along a specified dimension. This is useful when intermediate consolidations are calculated by rules and you want a parent consolidation to be calculated by summing the intermediate consolidations rather than by summing the underlying leaf values.

Syntax:
ConsolidateChildren(DimName1, DimName2, ...)

Arguments:

Argument	Description
DimName1, DimName2, ...	Names of the dimensions along which consolidations will be performed. The function requires at least one DimName argument, and can accept as many DimName arguments as there are dimensions in the cube for which the rule is written.

Example:
Consider a cube named Sales composed of the dimensions ActVsBud, Region, Model, Account1, and Month.
In this example, the Month dimension is defined as follows: If no rule is in place for this cube, the value of the Year consolidation is calculated by summing all the underlying leaf values, in this case Jan through Dec.
The following figure illustrates this consolidation. Now, suppose you create the following rule for this cube, which indicates that all quarterly values should be 1:
[{'1 Quarter', '2 Quarter', '3 Quarter', '4 Quarter'}]=1;
The result is as follows: In the figure, you can see that quarterly values are indeed calculated by the rule, but the Year consolidation is still calculated by summing all underlying leaf values. If this is not your desired calculation path, you can use the ConsolidateChildren function to force TM1 to calculate the Year consolidation by summing its immediate children, specifically 1 Quarter, 2 Quarter, 3 Quarter, and 4 Quarter.
['Year']=ConsolidateChildren('Month');[{'1 Quarter', '2 Quarter', '3 Quarter', '4 Quarter'}]=1;
In the rule, the statement ['Year']=ConsolidateChildren('Month') says that the Year consolidation should be calculated by summing the immediate children of Year in the Month dimension.
The following figure shows the result of the ['Year']=ConsolidateChildren('Month') statement: Note that the Year consolidation is now calculated by summing its immediate children.
It's important to remember that for a given consolidation, the ConsolidateChildren function applies only to the immediate children of the consolidation.
The ConsolidateChildren function can also be used to specify how consolidations are calculated in multiple dimensions, as in the following example:

Arguments:

Argument	Description
['World','Year']= ConsolidateChildren(' Region','Month')	This statement applies the ConsolidateChildren function to both the World and Year consolidations. In this case, World is calculated by summing all its immediate children in the Region dimension, while Year is calculated by summing its immediate children in the Month dimension.

DIMNM:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes. DIMNM returns the element of a dimension that corresponds to the index argument.
Syntax:
DIMNM(dimension, index)

Arguments:

Argument	Description
dimension	A valid dimension name.
index	A value less than or equal to the number of elements in the dimension. If this argument is less than 1, or greater than the number of elements in the dimension, the function returns 0.

Example:
DIMNM('Region',2)
This example returns 'Belgium', which is the element within the Region dimension with an index value of 2.

DIMSIZ:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
DIMSIZ returns the number of elements within a specified dimension.
Syntax:
DIMSIZ(dimension)
Arguments:

Argument	Description
dimension	A valid dimension name.

Example:
DIMSIZ('Accounts')
If the dimension Accounts contains 19 elements, the example returns the value 19.

DNEXT:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes. DNEXT returns the element name that follows the element specified as an argument to the function.
Syntax:
DNEXT(dimension, element)

Arguments:

Argument	Description
dimension	A valid dimension name.
element	The name of an element within the dimension. This argument can also be the name of an alias for a dimension element.

Example:
DNEXT("Location","Oregon")
If the Location dimension contains the ordered elements California, Oregon, and Washington, the example returns Washington.

DNLEV:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
DNLEV returns the number levels in a dimension.
Syntax:
DNLEV(dimension)

Arguments:

Argument	Description
dimension	A valid dimension name.

Example:
DNLEV('Region')
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).
There are four levels in the Region dimension, so the example returns the value 4.

TABDIM:
This is a TM1 rules function, valid in both TM1 rules and TurboIntegrator processes.
TABDIM returns the dimension name that corresponds to the index argument.
Syntax:
TABDIM(cube, index)

Arguments:

Argument	Description
cube	A valid cube name.
index	A positive value less than or equal to the total number of dimensions in the cube.

Example:
TABDIM('SalesCube',3)
The cube SalesCube contains five dimensions: account1, actvsbud, model, month, and region. The example returns model, the third dimension of SalesCube.

Read this aritcle completely...