Sending Business Documents To and From 1SYNC

Step	Action
1	Your enterprise (acting as a supplier or a retailer) submits an internal request business document from your back-end system to Integration Server. The request business document can be a Trading Networks document or an Integration Server publishable record, with a predefined ConversationID.
2	A custom defined outbound mapping service maps the internal information to the 1SYNC-specific request document.
3	The mapped request document is sent to wm.ip.sync.services:sendXXDocument service. The wm.ip.sync.services:sendXXDocument can be any one of the following services: wm.ip.sync.services:sendConfirmationDocument wm.ip.sync.services:sendSubscriptionDocument wm.ip.sync.services:sendRFCINDocument wm.ip.sync.services.sendCatalogueRequest These services in turn invoke the wm.ip.sync.services:sendRequests service.
4	The wm.ip.sync.services:sendRequests service invokes the EDIINT Send service to post the request business document to 1SYNC.
5	1SYNC receives the 1SYNC request business document.
6	1SYNC responds by sending a response business document to your enterprise (acting as a supplier or a retailer) by way of 1SYNC.
7	The EDIINT Receive service receives the response business document from 1SYNC and submits the response document to Trading Networks.
8	The response business document triggers a Trading Networks processing rule, which invokes the wm.ip.sync.rules:processResponse service. This service retrieves the request referenced by the response business document, copies the ConversationID from the request to the response business document, checks for any exception in the response business document, and updates the user status in Trading Networks.
9	A custom-defined inbound mapping service maps the 1SYNC-related information to internal information recognizable by your back-end system.
10	Your back-end system receives and processes the internal response business document.