3.6.1 Maintain Static Data

This topic describes how to maintain static data.

Data that remains constant over a period of time is called static data. Usually, such data will be commonly accessed by more than one module. The following are some typical examples of static data:

• The details about the currencies that are used in your bank
• The details about the brokers with whom you may deal
• The details of End of Cycle functions that should be executed automatically.

Such data is maintained in tables. Once the data is entered in a table, it has to be authorized before it can be used by any function. Each item in a table is called a record. Each record has a key that uniquely identifies it.

For example, when you open a record for a broker, you should allot an identification code. This code, called the Broker ID is unique to the broker whose details you are defining and cannot be allotted to any other broker. Thus, the Broker ID identifies the broker for whom the details have been defined. In a similar fashion, you have to allot unique codes to each currency, dealer, etc.

While you are defining a record, you have to enter the key first and then go on to define the attributes for it. These attributes will automatically be picked up when the key of the record is involved in a transaction. For example, you define Alexander (with a Broker ID of Alex) as a broker and indicate that the brokerage should be booked in advance. Whenever Alexander is involved in a transaction, the brokerage will be booked in advance.