This chapter describes what happens if only the sender of the message has an SCSN interface. Checks on the validity of the messages, as described in Both Parties With SCSN Interface, also take place here.
The order message is sent to an 'outbox', where the receiver can pick it up. Isah checks the message. If any of the checks fail, Isah returns an error. If all checks succeed, the message is placed in the outbox and the electronic message's delivery status is changed to 'Ready to be picked up'. The supplier receives a notification if this has been set up in Isah.
The receiving party has been notified of the order message and is now picking it up. They can do this via an automated process, or manually, by executing a GET:
URL: http://[address]/[orderid]
(GET) – Interface Service
The GET is expecting an XML SCSN message attachment. If the message cannot be found, the system returns a technical error message to the sender. If it is found, it can be processed further.
When the order message has been picked up, it can be imported into the ERP system. This can be done manually, in Isah, by selecting the import function Import order message.
The process of receiving the incoming message and importing it into the database is the same as described in step 3, 4 and 5 in Both Parties With SCSN Interface. The message is picked from the queue and imported with a POST.
The process of receiving the incoming message and importing it into the database is the same as described in step 3, 4 and 5 in Both Parties With SCSN Interface. The message is picked from the queue and imported with a POST.
1. The client generates an order message