A “table,” in this e-Biz Impact context, is a user-defined name that you specify in the arguments to db filters and functions. Each table name must be unique for each acquisition AIM, and a good suggestion is to make each table name similar to the reference name of the acquisition AIM. For example, for transactions sent by a general ledger application, use the table name “GENLEDGE.”
For the dbInsert, dbDiskList, dbSelect, and dbDelete built-in filter functions, you place this table name into the Table argument field in the Filter Information window. For the dbExist and dbNotExist built-in qualification functions, you place this table name into the Args argument field in the Qualification Object Information window.
When necessary, transaction production truncates the table’s name to meet your system’s file name limitations. Within the file name, transaction production maps all alpha characters to uppercase and converts \ . : / and space characters to % # ^ $ and _ respectively. Any character that is less than a space or greater than a tilde is mapped to a question mark.
WARNING! The table name must be unique enough to be truncated and mapped to a unique name. If two transactions with the same Key have different table names that map to the same table name, transaction production writes the second transaction’s data over the first transaction’s data in the collection file.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
