OFTP Authentication (EDI Codes)

The term “EDI code” should be used carefully as it could cover one (or more) of the 3 codes used in OFTP to identify a given party.

SSID Code/Network Node

The SSID code is sent to a trading partner at the start of an OFTP communication session. It informs them who the sender is, as a company. The SSID command includes the SSID code and also an OFTP password. The recipient then sends back their SSID code and OFTP password in another SSID command. Either party can terminate the session if they do not recognise the contents of an SSID command.

SFID Code/File Node

Once the session is established, an SFID command is sent. This is a request for permission to send a file. It includes the SFID code of the origin and the destination. In the most simple case the SFID code will be the same as the SSID code, but if a company has multiple entities, they may have a different SFID for each entity within the company. The recipient of the SFID can then either accept the file (send back an SFPA command), or reject it (send back an SFNA command) if they do not recognise the origin or destination.

Message Level EDI Code/Message Node

Inside each EDI message is yet another EDI Code. The first record in each EDI message contains the origin and destination of the message. Depending on the format of the file this could be referred to as something else, such as ANA number for ANSI X12, or UNB code for EDIFACT/ODETTE. Again, this often refers to an entity within an organisation, although it could be the same as the SFID code, if a company has a different SFID code for each entity.