This chapter describes what happens if both parties in the supply chain have an SCSN interface installed by Isah. If one of both parties works with another ERP application, this means their interface may work slightly differently. As long as their interface complies with SCSN standards, there should be no problems exchanging electronic messages.
The electronic message is sent to the URL through an ID. If this fails, Isah returns an Internal Server Error. If everything checks out, the message is placed in the Outgoing Queue and the electronic message's delivery status is changed to 'Ready to send'.
On the Interface Service, there is a process that runs every minute to check if there are any new messages, and to process the messages it finds. The message that was sent in step 1 will be found by this process. The Interface Service will pick up the message and try to send it to the receiver's SCSN interface. It does this by sending a PUT to the relevant URL:
The Interface Service will get a return message from the receiver. The nature of this message will determine if the status is updated to 'Sent' or 'Failed to send'. Any additional messages will be logged in the Logs folder in ProgramData.
The process that runs every minute to check if there are any new messages will find and process the message. It sends it to the Message Service by executing a POST to the URL.
The Message Service receives the POST from the Interface Service. The Message Service now imports the message into the Isah database. This works in the same way as manual importing into the database would work (for instance by using Importing order message or Importing purchase invoice in Isah). If importing the message does not succeed, you will see this on the Electronic messages form. If it does succeed, the order, order response or invoice is now visible in Isah.
1. A message is offered to the Supply Chain Message Service