Transaction Register (Update Standard Rule)

Transaction register enables you to specify a field for which you want to check for duplicate data (using the Update standard rule Transaction Register function) and then invoke it (using the Select standard rule Transaction Register function) to verify whether the field contains duplicate data. Using the Update standard rule you can load document data into up to six fields in memory (Field1 through Field6).

Note: You must define the data for which the translator will check by adding a Transaction Register Update standard rule prior to the point in the map where you invoke the Transaction Register Select standard rule to check for duplicate data. The updates do not go directly to the database; they are kept in memory until the eventual select, and then they are checked against the database and inserted if necessary.

Then, using the Select standard rule Transaction Register function, you can invoke the check against the Transaction Register database table. If the data is validated as duplicate data, the translator notes the error in the translator report.

If there is no matching data already in the Transaction Register table, the content of Field1 through Field6 is inserted as a row in the table.

Note: If the document translation does not succeed, the field information (specified for duplicate verification) is not added to the Transaction Register database table.

The following list describes the fields on the Standard Rule tab with the Update standard rule selected and Transaction Register selected from the Table and key (or group) list:

Field: Description
Table (or group): Transaction Register. The translator updates the selected field repository with the data from a specified field (in the Column (or field) list) so that other fields may be later validated against that data to prevent duplicate items.
Column (or field): Column (or field) the translator will update with the information from the current map component. Valid values are Field1 through Field 6.