Lookup Record

You can use Lookup records to cross-reference any identifying number to the Account record.

This document contains the field name, field description, field number, mnemonic, data type, and default information for each field. Other pertinent information includes:

Source

Indicates where the data in the field comes from:

User-entered
The user creates the information in this field.

System-entered
A system process populates the value for the field. This value can include data transmitted by the ATM network, when applicable.

System-calculated
The system calculates but does not store the value of the field each time the field appears on an inquiry or file maintenance screen.

The Lookup record includes the following fields:

Lookup Type

This field stores a credit union-defined code that identifies the type of Lookup record.

Enter a credit union-defined code (00-99) to identify the type of Lookup record.

Tip: You can use the Lookup Type Names parameters to set the descriptions for the value in this field.

Lookup

This field stores the value used to look up the account.

Enter information (up to 20 characters) that can be used to look up the account. You can enter any information (such as a credit card number or employee number) to be used as a cross-reference to the account number. For example, if you enter a credit card number, you can access the account by typing @ followed by the credit card number at any Account prompt.

If you do not make an entry, the system displays the following message and you remain in this field:

Cannot be blank

You must enter a lookup number to proceed.

If you create a Lookup record and enter a lookup number that has already been used in another Lookup record, the system displays one of the following messages:

Duplicate Lookup Number with Type # on Same Account
Duplicate Lookup Number with Type # on Account #

You can still approve the Lookup record if you intend to use the same lookup value for different lookup types or for different accounts.

Reference ID Type

This field stores a code that indicates if the lookup refers to a specific Share or Loan record.

Data Type Descriptions

(0) Share
The lookup refers to a specific Share record in the member’s account.

(1) Loan
The lookup refers to a specific Loan record in the member’s account.

(2) None
The lookup does not refer to a specific Share or Loan record in the member’s account, but to the entire account.

Reference ID

This field stores the ID of the Share or Loan record this lookup refers to.

• If you select (0) Share at the Reference ID Type field, enter the ID of the Share record this lookup refers to. You can type * to display and choose from a list of all Share records in the account.
• If you select (1) Loan at the Reference ID Type field, enter the ID of the Loan record this lookup refers to. You can type * to display and choose from a list of all Loan records in the account.
• If you select (2) None at the Reference ID Type field, leave this field blank.

Record Change Date

The system stores the system date in this field when you create, change, or save the Lookup record. Sometimes the system updates this field because the record was saved, even though there may not be any actual changes in the record.

Note: The system does not change the Record Change Date when a calculated field changes.

You cannot change the value of this field.

Non-Displayed Fields

These Lookup fields do not appear in the system and are only accessed by PowerOn specfiles or SymConnect.

Note: As of Symitar Release 2025.00, the SymConnect API is fully decommissioned. All clients and vendors are required to transition to SymXchange.

Locator

This field stores a unique number within each member account that can be used as a unique identification of this record.

The system automatically assigns the value in this field when the record is created, and you cannot change it. The value is a positive number greater than zero and up to about two billion.

This field can be used during PowerOn file maintenance (both on demand and batch) to uniquely identify a record. Using this field is recommended since a record’s ordinal sequence number may change if someone else inserts or deletes a record with a lower ordinal sequence number just before you post your file maintenance.