Relationship to the FTM data model

The FTM data model defines a number of tables to manage the operational data within an FTM solution.

For operational data, the data model has the following primary functions:
  • Store the details of the messages and transactions processed by system
  • Persist state and track progress
  • Manage relationships between objects
  • Storing information. For example, information for auditing, reporting, or billing.

Each business transaction is represented by records in the OBJ_BASE and TRANSACTION_BASE tables. These records serve to store the details of the business transaction and to persist and track the status of the business transaction.

For each business transaction, an ISF XML document contains the business data relating to that transaction. That ISF XML document is stored as part of the TRANSACTION_BASE record. Also, in order to optimize processing or retrieval requirements, for some key properties of the business transaction, the value may be stored directly within the TRANSACTION_BASE record, as well as within the ISF XML document. Other properties may be stored in additional tables (for example TXN_PAYMENT_BASE for payment transactions, or TXN_SECURITIES_BASE for securities base).

The value of OBJ_BASE.TYPE specifies the type of object (for example, TRANSMISSION, TRANSACTION, TXN_PAYMENT). The type of an object dictates the set of tables that are used to store the properties of the object. In the case of transaction objects (for example, TRANSACTION, TXN_PAYMENT, TXN_SECURITIES) OBJ_BASE.SUBTYPE specifies the business purpose of the transaction. This value will typically be the same as that stored in the BusinessConcept element of the header in the ISF XML transaction document.

Typically, a view (with a name that is derived from the object type) is used to provide a combined interface to the tables that are used to store the properties of an object.

The data model is also responsible for the management of relationships between transactions.

Therefore, an ISF XML document will contain the business data relating to a single business transaction. It will not contain data to manage the status of the business transaction, or the relationship to other transactions.

This separation of responsibilities between the data model and ISF allows for a general purpose data model that can manage a variety of different business transaction types. The extensible ISF takes care of the differing content requirements of the business transactions.