Databases Reference
In-Depth Information
In the final part of the subjob, the dataflows of FAB merchandise SKUs and FAB
delivery SKUs are merged back into a single flow:
The data is sorted so that it is in the order ID , line ID sequence, passed through
a tMap component to strip out the SKU prefix, and written to a delimited file.
After this integration, our supplier systems now have order data and they can now
dispatch orders to customers. Our next integration will look at a typical next step in
the process, the supplier/fulfillment systems advise which items from the original
order have actually been shipped.
Order status updates
Once the orders have been processed by the suppliers, they will send back an order
status update to the website system, confirming fulfillment. Here are the key features
of this process:
1. The suppliers FTP files to a directory on the website server. All suppliers
follow the same format and the filenames' convention is [supplier code]_
shipped_[timestamp].csv , for example fab_shipped_201206060900.csv .
2. The suppliers can supply these files many times per day on a schedule that is
not predetermined.
3. Once processed, the output file needs to be moved to the website's order
status import directory.
4. The file required by the website is in XML format and is to be named
orderstatus_update.xml .
 
Search WWH ::




Custom Search