Basic header block (block 1) for SR 2017

Table 1. SWIFT inbound basic header block (block 1) - Transformation Extender map
	SOURCE PAYMENT STANDARD - MT/MX SWIFT Messages						TARGET = ISF Version 3
##	Tag or field name	Mandatory / Optional	Semantic	Content / Options	Sample Example	Mapping rules	ISF field path	Database
1	AppID	M	The Application Identifier identifies the application within which the message is being sent or received. The available options are: F = FIN All user-to-user, FIN system and FIN service messages A = GPA (General Purpose Application) Most GPA system and service messages L = GPA Certain GPA service messages, for example, LOGIN, LAKs, ABORT These values are automatically assigned by the SWIFT system and the user's CBT	1a	F	Extract the value from the source if it is not blank and map it directly to the target as it is	FinMessage:Block1:ApplicationIdentifier	--
2	ServiceID	M	The Service Identifier consists of two numeric characters. It identifies the type of data that is being sent or received and, in doing so, whether the message which follows is one of the following: a user-to-user message a system message a service message, for example, a session control command, such as SELECT, or a logical acknowledgment, such as ACK/SAK/UAK	2n	01	Extract the value from the source and map it directly to the target as it is	FinMessage:Block1:ServiceIdentifier	--
3	LTAddress	M	This 12-character FIN address, given in the Basic Header Block, is the address of the sending LT for input messages or of the receiving LT for output messages, and includes the Branch Code. In the Basic Header, the LT Code within the LT Identifier is specific to the LT that has established the session in which the message is being transmitted, that is the sending LT for input messages or the receiving LT for output messages.	12x	BANKBEBBAXXX	If the field Input/Output Identifier in Application Header Block is 'I' it is input message, if the value is 'O' the message is output message. Depending on if it is input/output message below rules should be applied: 1.If it is input message, map the address of sending LT OR 2. If it is output message, it is address of the receiving LT	For Sending LT and Receiving LT: FinMessage:Block1:LogicalTerminalAddress Sending LT only: ISFMessage:header:Sender Receving LT only: ISFMessage:header:Receiver	Sending LT only: TRANSMISSION_V.Sender TXN_PAYMENT_V. Sender Receving LT only: TRANSMISSION_V.Receiver TXN_PAYMENT_V.Receiver Note: Refer to "High Level Rules" tab - Rule No. 8 The name of view TXN_PAYMENT_V will depend on the "MessageType".
4	SessionNumber	M	The Session Number identifies the session in which the message was transmitted. Within the Basic Header, the 4-digit Session Number is the user's current GPA or FIN Session Number.	4n	2222	Extract the value from the source and map it directly to the target as it is	FinMessage:Block1:SessionNumber	--
5	Sequence Number (ISN or OSN)	M	The sequence number always consists of six digits. It is the ISN of the sender's current input session or the OSN of the receiver's current output session. Required only in the following instances: For all GPA messages/service messages with the following Service Identifiers, the Sequence Number must be equal to the next expected number: 01 (user-to-user messages) 03 (SELECT) 06 (LOGOUT) For all GPA messages with the following Service Identifiers, the Sequence Number must be equal to that of the acknowledged service message: 21 (ACK/NAK/UAK/UNK) 23 (SELECT ACK (SAK)) 26 (LOGOUT ACK) 43 (SELECT NAK (SNK)) For all FIN messages/service messages with the following Service Identifiers, the Sequence Number must be equal to the next expected number: 01 (user-to-user messages) 05 (QUIT) For all FIN messages with the following Service Identifiers, the Sequence Number must be equal to that of the acknowledged service message: 21 (ACK/NAK/UAK/UNK) 25 (QUIT ACK)	6n	123456}	Extract the value from the source and map it directly to the target as it is	FinMessage:Block1:SequenceNumber	--