Viewing history data from the RMA

The FTM SWIFT Relationship Management Application (RMA) records all changes that are made to each RMA authorisation, query, or answer. These changes can be viewed using the views described in Table 1 and Table 2.

Table 1. Fields of the view DNF_RMAUTH_ou. History data for authorisations.
Field name	Data type	Mandatory	Description
OWN_BIC	CHAR(8)	Yes	The BIC8 of your financial institution. This is the local counterpart of the authorisation.
COR_BIC	CHAR(8)	Yes	The BIC8 of the correspondent. This is the remote counterpart of the authorisation.
SERVICE	CHAR(30)	Yes	The name of the SWIFT service to which the authorisation refers, for example: swift.fin For a FIN live destination. swift.fin!p For a FIN test and training (T&T) destination. swift.ia For the InterAct service. swift.fa For the FileAct service.
RMAUT_TYPE	CHAR(5)	Yes	The type of authorisation: toSnd This authorisation enables your institution to send messages to the correspondent. toRcv This authorisation enables your institution to receive messages from the correspondent.
ACTION_UTS	TIMESTAMP	Yes	The date and time when an action was performed.
ACTION	VARCHAR (32)	Yes	The action that was performed: accept An authorisation to send (or an update for an authorisation to send) was accepted. approve A change for an authorisation was approved. breakLock A lock for an authorisation was broken. create An authorisation was created. delete An authorisation to send was deleted. deleteBootstrap A bootstrap authorisation was deleted. deleteImport An authorisation was deleted during an RM import operation. deleteStale A stale authorisation was deleted. discard A change for an authorisation was refused. enable An authorisation to receive was enabled. ignore An RMA message was ignored. import An authorisation was imported. receive An RMA message was received from the correspondent. refuse A change for an authorisation was refused. reject An authorisation to send (or an update for an authorisation to send) or an RMA message was rejected. resend An RMA message for an authorisation was resent. revoke An authorisation to receive was revoked. send An RMA message was sent to the correspondent. setMasterBics The master BICs were set for an authorisation. update A bootstrap authorisation or an authorisation to receive was updated.
OBJECT	VARCHAR (16)	Yes	The object to which the action refers: Authorisation The action refers to an authorisation or an RMA message for an authorisation. Revocation The action refers to an RMA message for a revocation. Rejection The action refers to an RMA message for a rejection. Response The action refers to the response for an RMA message. DeliveryNotif The action refers to an delivery notification.
USER_ID	VARCHAR (100)	Yes	The user ID that performed the action.
RMAUT_STATUS	CHAR(8)	No	The status of the authorisation. Which statuses an authorisation can have depends on its type: toSnd An authorisation to send can have one of the following statuses: PendAcc You received an authorisation to send (or an update for an authorisation to send) but did not yet accept or reject it. Enabled You accepted the authorisation to send and it is now active. Rejected The authorisation to send is inactive because you rejected it. Revoked The authorisation to send is inactive because the correspondent revoked it. Deleted The authorisation to send is inactive because you deleted it. PendDel The delete operation is pending. toRcv An authorisation to receive can have one of the following statuses: Enabled The authorisation to receive is active. Rejected The authorisation to receive is inactive because the correspondent rejected it. Revoked The authorisation to receive is inactive because you revoked it. PendDel The delete operation is pending.
CHANGE_STATUS	VARCHAR (8)	No	The change status of the authorisation: Draft The authorisation was saved as a draft, but not yet submitted. PendApp1 The pending version requires approval by a relationship approver. PendApp2 The pending version was approved, but requires additional approval by a second relationship approver. Refused The pending version was refused by a relationship approver.
NETWORK_STATUS	VARCHAR (10)	No	The network status of the authorisation: InProgress The processing of the RMA message is in progress, that is, the RMA message was sent to the correspondent, but the Relationship Management Application did not yet receive confirmation that the message transfer is complete: If a delivery notification was not requested, the Relationship Management Application did not yet receive the response message that indicates that SWIFT received the RMA message. If a delivery notification was requested, the Relationship Management Application did not yet receive the delivery notification that indicates that the correspondent received the RMA message. Finished The processing of the RMA message is finished, that is, the Relationship Management Application received confirmation that the RMA message was sent to the correspondent. This value is also displayed for an authorisation to send that was received from a correspondent and for which no RMA message has yet been sent to the correspondent. Error An error occurred during an attempt to send the RMA message to the correspondent.
BOOTSTRAP	CHAR(1)	No	If the authorisation was created or updated, whether the authorisation is a bootstrap authorisation: Y The authorisation is a bootstrap authorisation. N The authorisation is not a bootstrap authorisation.
ISSUED_UTS	TIMESTAMP	No	If the authorisation was created or updated, the date and time when the authorisation was created or updated last.
VALIDITY_START	DATE	No	If the date from which the authorisation is valid was updated, the date from which the authorisation is valid after the update.
VALIDITY_END	DATE	No	If the date up to which the authorisation is valid was updated, the date up to which the authorisation is valid.
REJECT_CODE	CHAR(11)	No	If the reject or delete code of the authorisation was updated, the reject or delete code after the update.
REJECT_REASON	VARCHAR (512) FOR BIT DATA	No	If the reject or delete reason of the authorisation was updated, the reject or delete reason after the update.
PERMISSIONS	VARCHAR (10000) FOR BIT DATA	No	If the permissions of the authorisation were updated, the permissions of the authorisation (in XML format) after the update.
SIGNATURE	VARCHAR (2048) FOR BIT DATA	No	If the signature of the authorisation was updated, the signature of the authorisation after the update.
OWN_MASTER_BIC	CHAR(8)	No	If the master BIC8 for the BIC8 of your financial was updated, the master BIC8 after the update.
COR_MASTER_BIC	CHAR(8)	No	If the master BIC8 for the BIC8 of the correspondent was updated, the master BIC8 after the update.
MSIF_REFERENCE	CHAR(24) FOR BIT DATA	No	If the MSIF reference of the authorisation was updated, the MSIF reference of the authorisation after the update.
MSG_GRP	VARCHAR (50)	No	If the message group of the authorisation was updated, the message group of the authorisation after the update.

Table 2. Fields of the view DNF_RMQAH_ou. History data for queries and answers.
Field name	Data type	Mandatory	Description
RMQS_ID	DECIMAL (19,0)	Yes	A unique identifier of the related query or answer.
PARENT_ID	DECIMAL (19,0)	No	For RMA answers, the unique identifier of the related query.
OWN_BIC	CHAR(8)	Yes	The BIC8 of your financial institution. This is the local counterpart of the query or answer.
COR_BIC	CHAR(8)	Yes	The BIC8 of the correspondent. This is the remote counterpart of the query or answer.
SERVICE	CHAR(30)	Yes	The name of the SWIFT service to which the authorisation refers, for example: swift.fin For a FIN live destination. swift.fin!p For a FIN test and training (T&T) destination. swift.ia For the InterAct service. swift.fa For the FileAct service.
RMQA_TYPE	CHAR(4)	Yes	The type of query or answer: cvd The query or answer was received from the correspondent. sent The query or answer was sent to the correspondent.
RMAUT_TYPE	CHAR(5)	Yes	The type of authorisation: toSnd This authorisation enables your institution to send messages to the correspondent. toRcv This authorisation enables your institution to receive messages from the correspondent.
ACTION_UTS	TIMESTAMP	Yes	The date and time when an action was performed.
ACTION	VARCHAR (32)	Yes	The action that was performed: approve A change for a query or answer was approved. breakLock A lock for a query or answer was broken. create A query or answer was created. delete A query and all related answers were deleted. discard A change for a query or answer was discarded. ignore An RMA message was ignored. markAsAnswered A query was marked as answered. markAsRead An answer was marked as read. receive An RMA message was received from the correspondent. refuse A change for a query or answer was refused. resend An RMA message for a query or answer was resent. send An RMA message was sent to the correspondent. setMasterBics The master BICs were set for a query or answer. update A query or answer was updated.
OBJECT	VARCHAR (16)	Yes	The object to which the action refers: Query The action refers to a query or an RMA message for a query. Answer The action refers to an answer or an RMA message for an answer. Response The action refers to a response for an RMA message. DeliveryNotif The action refers to a delivery notification.
USER_ID	VARCHAR (100)	Yes	The user ID that performed the action.
CHANGE_STATUS	VARCHAR (8)	Yes	The change status of the query or answer: Draft The query or answer was saved as a draft, but not yet submitted. PendApp1 The pending version requires approval by a relationship approver. PendApp2 The pending version was approved, but requires additional approval by a second relationship approver. Refused The pending version was refused by a relationship approver.
NETWORK_STATUS	VARCHAR (10)	Yes	The network status of the query or answer: InProgress An RMA message was sent to the correspondent, but the Relationship Management Application did not yet receive confirmation that the message transfer is complete. Finished The Relationship Management Application received confirmation that the RMA message was sent to the correspondent. This symbol is also displayed for an authorisation to send that was received from a correspondent and for which an RMA message was not yet sent to the correspondent. Error An error occurred during an attempt to send the RMA message to the correspondent.
AUTH_ISSUED_UTS	TIMESTAMP	No	If the query or answer was created or updated, the date and time when the related authorisation was created or updated last.
TEXT	VARCHAR (10000) FOR BIT DATA	No	If the text of the query or answer was updated, this field contains the text of the query or answer after the update. The text in this field is coded in Unicode, but the SQL data type of the field is binary. To retrieve the data in this field in a readable format, in the select list of the SELECT statement, instead of the sheer column name, specify the following expression: `RTRIM( CAST( CAST( TEXT AS VARCHAR(1000) CCSID UNICODE ) AS VARCHAR(1000) CCSID EBCDIC) )` In this expression, the data of the column is cast to the EBCDIC character representation of your system.
SIGNATURE	VARCHAR (2048) FOR BIT DATA	No	If the signature of the query or answer was updated, the signature of the query or answer after the update.
OWN_MASTER_BIC	CHAR(8)	No	If the master BIC8 for the BIC8 of your financial institution was updated, the master BIC8 of the query or answer after the update.
COR_MASTER_BIC	CHAR(8)	No	If the master BIC8 for the BIC8 of the correspondent was updated, the master BIC8 of the query or answer after the update.
MSIF_REFERENCE	CHAR(24) FOR BIT DATA	No	If the MSIF reference of the query or answer was updated, the MSIF reference of the query or answer after the update.
MSG_GRP	VARCHAR (50)	No	If the message group of the query or answer was updated, the message group of the query or answer after the update.