Export and Import of AXIS table values
in
AXIS Users Guide - Import Export Options
You may export the contents of AXIS tables to the Import/Export
Database for further analysis or reporting, and for modification
and importing back into AXIS. You may also use the
Import/export database to assist in the initial definition of large
numbers of tables to be imported from an external source.
Table values imported from the Import/Export Database are
validated field by field and row by row and only valid values are
used to either update existing AXIS tables or to create new
tables. Table rows and columns not specified by an import
process are left untouched in existing objects or set to zero for
new tables. If problems are encountered with data during the Import
process, then diagnostic messages will be stored in the System Log
file.
You may export Table values to the Import/Export Database
directly from the viewed list of tables, just like Cells and other
objects. You may choose to export values for the current
table in the list, or for a group of selected tables. You may
also choose to export various Tables as part of the selected output
options in a Batch recalculation using the Report Pack wizard
options.
When importing Tables from the Import/export database into AXIS
based on externally defined data, it is important to know the
mandatory and optional fields available for use, and their
respective purposes and valid values.
Mandatory fields in the Import/export table
containing AXIS table values ("Tables" type)
1. TableName
This text field contains the name of the table as used in
AXIS. For tables other than vendor-defined tables, the Table
name is selected by the user, and must be unique within the section
selected.
2. Section
This field identifies which section the table belongs to.
The section identifies the type of usage normally associated with
the table according to the specific field or fields in which the
table can be selected. When tables are listed in the table
view list in AXIS, the section name is shown along with the Table
Name. However, for purposes of defining tables in the
Import/export database, you must use the correct AXIS literal for
that section, which you can determine by exporting a sample table
from AXIS to the Import/export database and viewing it there.
3. Shape
This field identifies the specific structure of the table, such
as By Annual Duration only (a single column table), or All Issue
Ages by 100 Years (a 100 X 100 table). Some tables such as
mortality rates support multiple shapes of table. For
purposes of defining tables in the Import/export database, you must
use the correct AXIS literal for that shape, which you can
determine by exporting a sample table of the appropriate shape from
AXIS to the Import/export database and viewing it there.
4. Row
The Row number is necessary when table data is imported and used
to update table contents on a row by row basis. You only need
to have values defined for the rows you wish to update in the AXIS
table, but there must be one record per row in this Table, the
exception being row -1 (see Op field description below for
more information), which can be defined through multiple records
all with row -1 and with different Op values. Note that rows
with numbers below zero are used to specify various table
attributes such as table definitions and column header options,
which may be a necessary part of the table definition and update
process, depending on the specific table being imported.
5. Op (Operation Column Code)
This is a text field is used to indicate and identify additional
table data, including Table definitions and expandable column
data. Each of these uses is explained below with the relevant
coding rules for Import/export table and some examples.
For all other tables, this field is not used and should be left
undefined.
a) Expandable column data
Some column-specific AXIS tables support additional expandable
columns of two dimensional data which is connected to a specific
column in the main table. Refer to the User's Guide topic on
Tables with Expandable Columns for more
information.
To clear all additional data for an expandable column,
only one row is needed in the Import/export table, coded as
follows:
Row = 0
Op = “Cnnn_NONE”, where
'nnn' is the expandable column number to be cleared
Example: To clear all additional data in the
expandable column 1 of a Required Surplus factor table, add a
single record with Row = 0 and Op field = "C001_NONE") which will
appear as follows in the Import/export database table view:
To define additional age and duration based
data for an expandable column, define this data in an
additional set of 100 rows x 100 columns, coded:
Row = 1 to 100
Op =
"Cnnn_DATA", where 'nnn' is the expandable column number to
which this data applies.
Example: Using the same example
as above, the resulting additional data for expandable column 1
will appear after the rows of the basic table data in the
Import/export database table view:
b) Table definition data
Table definitions specify how the numeric values stored in the
table are interpreted and applied. Different table sections
have different sets of definitions.
When Table values are exported to or imported from an
Import/export database table, each definition is specified in a
separate row, coded as follows:
Row = -1
Op = <option pseudonym>
(this is a short but meaningful internal name for the
definition)
C1 = option value
When you edit the table in AXIS, you can view and edit table
definitions, if they apply, by clicking the Define
button. You can also view the pseudonyms and current values
for each definition in the table by next clicking the View
Import/export Values button, which will result in a display
such as this:
The actual contents of the Import/export table corresponding to
this example would look like this:
1. C1 to C100
There are 100 optional fields to support up to 100 different
columns of data within the AXIS Tables. You only need to use
as many column fields as you have columns of data to feed.
2. LnkSection and LnkTable
These two optional fields are used for storing additional Link
information that is only required for Composite Tables. Rows
in Composite tables may be used to store links to other AXIS tables
of various types, shapes and sizes, as well as scalar values such
as Flat or Multiple factors. The LnkTable field stores
the actual Table name which is linked in each row, and the
LnkSection stores the internal AXIS literal for the Section
in which this Table is found.
3. Formula
This optional field is used for storing the text of formula that
is only required for Formula Tables.
Notes
1. Set tables have multiple objects defined in each row. Each
object may have values, such as Flat and Mult, attached to it. When
a Set table is exported, only these values are stored in the
Import/export table. You need to export table links to send the
names and types of the objects inside the Set table to the
Import/export database.
2. Starting from version 11.3.01.001, AXIS exports table
definitions as described above in the Op column explanation - one
row per definition. Old-style Import/export tables, i.e. those that
have all definitions in a single row (-1) are still supported for
import.