EDI

EDI is a system that allows businesses exchange and process documents via a third party with little or no human intervention.

For retailers, this means that purchase orders can be automatically sent to a supplier or customers orders can be received and processed.When generating purchase order, spporep can specify to generate a file and place it in the appropriate folder for sending by an external EDI vendor.

All files must follow the format specified by the vendor. The vendor checks the file, imports the file into its database and generates a corresponding file for the recipient. Allphones use B2BE as their EDI vendor. I am not sure who DIM use for there EDI.

General Overview

Outgoing Files

  1. Setup creditor to generate EDI files

  2. (Optional) Setup EDI email alerts (gencont -> EDI Manager Email)

  3. User creates a PO
  4. stpost runs spporep
  5. spporep creates file in /u/cc/
  6. spporep calls the script edi_commit.sh
  7. edi_commit.sh moves newly generated file into the appropriate directory
  8. EDI vendor software retrieves file and imports into their system

Incoming Files (Allphones only)

  1. EDI vendor software creates file in appropriate directory
  2. crontab schedules edi_import.sh to run periodically
  3. edi_import.sh processes file to create order/invoice
  4. On success, file extension is changed to .success
  5. On failure,
    • For "Soft Errors", leave file for processing at another time
      • Delivery docket not found
      • After 2-3 days, generate warnings
      • Later on, upgrade to "Hard Error" status
    • For "Hard Errors", file extension is changed to .err
      • Invoice references PO/stock/etc. that does not exist

CategoryAllphones