Differences between revisions 6 and 7
⇤ ← Revision 6 as of 2009-02-10 01:45:40 →
Size: 1430
Editor: DannyCheung
Comment:
← Revision 7 as of 2013-09-18 06:09:34 → ⇥
Size: 1430
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * See ["EDI"] for more details.  * See [[EDI]] for more details.

EDI for DIM Furniture

Setup

  • See EDI for more details.

  • HO needs to be running a FTP server

  • The stores need to be running a FTP client that understands .netrc files

At the store:

  1. EDI file is generated by DIMWAspporepE.

  2. DIMWAspporepE calls /u/cc/binl/edi_commit.sh

  3. /u/cc/binl/edi_commit.sh moves the EDI file from /u/cc/ to /u/cc/edi/outgoing/ and assigns it a random, unique filename

  4. /u/cc/binl/edi_upload_dim.sh is run (Scheduled to run every minute in cron)

  5. /u/cc/binl/edi_upload_dim.sh sends the EDI files to head office via FTP

  6. The FTP username, password and other settings are stored in ~ccc/.netrc. You should make sure that there is a blank line at the end of the file

At Head Office:

  1. EDI files are placed in /u/cc/edi/outgoing/

    1. spporep calls /u/cc/binl/edi_commit.sh, which places the locally generated EDI files here

    2. Files generated at the stores are placed here via FTP

  2. cron is scheduled to run /u/cc/binl/edi_upload_dim.sh every minute. NOTE: This script is different to the one at the stores

  3. /u/cc/binl/edi_upload.sh takes all EDI files in /u/cc/edi/outgoing/ and moves them to /u/cc/edi/outgoing/enabling/

  4. AccPack or Nexus (I can't remember which one) accesses the files via SMB

CategoryEdi

CategoryDim

DIM_EDI (last edited 2013-09-18 06:09:34 by localhost)