EDI outgoing ack

EDI Outgoing Acknowledgements (POA)

Normal EDI terminology would make a distinction between Functional Acknowledgements (FA) and Purchase Order Acknowledgements (POA). An FA simply confirms that an EDI document has been received, while the POA provides a more detailed response for incoming POs to advise any issues with supply, pricing, invalid items, etc.

In IP1 we don’t really have a FA document, but we generally send a POA. ECN translate/forward onto the end customer (e.g. Bookseller) as a FA only if the end customer doesn’t support POAs.

POAs typically kicked off from EDI menu, but could be automated.

DSO374 was used to select POAs. It calls DSO375 for BISAC orders (EB source) or DSO378 for X12 orders (ED or EG source).

X12 menu simply has DSO378 – no real need to call via DSO374 anymore if all traffic in X12 format.

TMSDS/EDI-ALVL is key configuration control file for POAs. It dictates level of detail supplied back to customers (eg. Header only, all details, only details with price or supply issues, etc). This control file also allows for different timing of POA send for both initial order and backorder supply.

0 = Do not send

1 = Immediately send on receipt

2 = Only when processed

3 = Only when order rejected / cancelled.

Note that DSEAA00P contains both receiver (customer’s) TPID and sender TPID. ECN are also able to determine sender TPID based on ftp delivery into separate user id/folder (e.g. Pearson, Macmillan account have different user id in ftp script).