FTM SWIFT processing database

FTM SWIFT stores all the data it uses in its processing database:

• Each message sent by local applications (called an ISN message, because it has an input sequence number) and its acknowledgment message (ISN ACK) are stored in the Outbound Application Message Store (OAMS), which is implemented as the database table DNF_OAMS. The processing state of each message in the OAMS is represented by a state indicator:

  o

  The message is to be sent or replayed (that is, resent as a result of RP User Synchronization), but was not yet assigned a session and sequence number.

  s

  The message was assigned a session and sequence number.

  a

  The message was acknowledged.

  c

  The message is not a valid SWIFT APDU.

• Each messages received from a remote application (called an OSN message, because it has an output sequence number) is stored in the Inbound Application Message Store (IAMS), which is implemented as the database table DNF_IAMS.
• The configuration parameters for each LT and information about the status of each session are stored in the LT Status Store (LTSS), which is implemented by the table DNF_LTSS. Each LT updates its status in the LTSS as this status changes during a session.
• Information collected for audit and evaluation purposes (see Storing messages) is stored in special tables.
• Data about authorisations is stored in the Relationship Management Data Store (RMDS), which is described in Relationship Management Data Store.
• FINCopy Authorisation (FCA) data, which is used by central institutions when processing FINCopy messages (that is, Message Types 096 and 097). This data is stored in tables with names of the form DNF_FCA_ou.
• Application service profile (ASP) data.
• Configuration data (see System configuration concepts)