Differences between revisions 1 and 3 (spanning 2 versions)
⇤ ← Revision 1 as of 2008-09-18 07:42:52 →
Size: 1734
Editor: DannyCheung
Comment:
← Revision 3 as of 2009-01-19 03:52:29 → ⇥
Size: 3110
Editor: DannyCheung
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
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. 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.
Line 6: Line 6:
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.		 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 their EDI.
Line 9: Line 8:
== General Overview ==
=== Outgoing Files ===
 1. Setup creditor to generate EDI files
 1. (Optional) Setup EDI email alerts (gencont -> EDI Manager Email)
 1. User creates a PO
 1. stpost runs spporep
 1. spporep creates file in /u/cc/
 1. spporep calls the script edi_commit.sh
 1. edi_commit.sh moves newly generated file into the appropriate directory		 == Outgoing Files ==

=== Setup ===
 1. Control allows auto-generated POs to be Emailed or Printed. You will need to choose one of these methods as the method for creating EDI files. That is, you need to choose from one of the following statements:
  1. "When I print out an auto-generated PO for a creditor, I want CONTROL to create an EDI file instead"
  1. "When I email an auto-generated PO for a creditor, I want CONTROL to create an EDI file instead"
 1. Set the appropriate creditors to email/print auto-generated POs as per you choice above
  1. {{{craad}}}->Purchase Order (Email/Print)
   1. E => I want to email auto-generated POs for this creditor
   1. P => I want to printout auto-generated POs for this creditor
   1. <BLANK> => Not sure what this does !!
 1. Specify the customised spporep to use for generating EDI files
  1. If using emails as the method to create EDI files {{{
ln -s /u/cc/std/binl/B2BEspporep /u/cc/std/binl/<CRED_CODE>spporepE}}}
  1. If using printouts as the method to create EDI files {{{
ln -s /u/cc/std/binl/B2BEspporep /u/cc/std/binl/<CRED_CODE>spporepP}}}
  1. If you want to always create EDI files for this creditor {{{
ln -s /u/cc/std/binl/B2BEspporep /u/cc/std/binl/<CRED_CODE>spporep }}}
 1. (Optional) Setup EDI email alerts ({{{gencont}}} -> EDI Manager Email)
 1. Ensure that {{{edi_commit.sh}}} moves the EDI files to a folder that the EDI vendor's software can access

=== How it works ===

 1. PO is generated{{{spporep}}} is run via sieat/stpost/steat/aleat
 1. {{{spporep}}} creates file in /u/cc/
 1. {{{spporep}}} calls the script {{{edi_commit.sh}}}
 1. {{{edi_commit.sh}}} moves newly generated file into the appropriate directory
Line 19: Line 36:
=== Incoming Files (Allphones only) ===
== Incoming Files (Allphones only) ==
Line 21: Line 39:
 1. crontab schedules edi_import.sh to run periodically
 1. edi_import.sh processes file to create order/invoice		  1. crontab schedules {{{edi_import.sh}}} to run periodically
 1. {{{edi_import.sh}}} processes file to create order/invoice
Line 31: Line 49:

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 their EDI.

Outgoing Files

Setup

  1. Control allows auto-generated POs to be Emailed or Printed. You will need to choose one of these methods as the method for creating EDI files. That is, you need to choose from one of the following statements:
    1. "When I print out an auto-generated PO for a creditor, I want CONTROL to create an EDI file instead"
    2. "When I email an auto-generated PO for a creditor, I want CONTROL to create an EDI file instead"
  2. Set the appropriate creditors to email/print auto-generated POs as per you choice above

    1. craad->Purchase Order (Email/Print)

      1. E => I want to email auto-generated POs for this creditor

      2. P => I want to printout auto-generated POs for this creditor

      3. <BLANK> => Not sure what this does !!

  3. Specify the customised spporep to use for generating EDI files

    1. If using emails as the method to create EDI files 

      ln -s /u/cc/std/binl/B2BEspporep /u/cc/std/binl/<CRED_CODE>spporepE

    2. If using printouts as the method to create EDI files 

      ln -s /u/cc/std/binl/B2BEspporep /u/cc/std/binl/<CRED_CODE>spporepP

    3. If you want to always create EDI files for this creditor 

      ln -s /u/cc/std/binl/B2BEspporep /u/cc/std/binl/<CRED_CODE>spporep

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

  5. Ensure that edi_commit.sh moves the EDI files to a folder that the EDI vendor's software can access

How it works

  1. PO is generatedspporep is run via sieat/stpost/steat/aleat

  2. spporep creates file in /u/cc/

  3. spporep calls the script edi_commit.sh

  4. edi_commit.sh moves newly generated file into the appropriate directory

  5. 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

EDI (last edited 2013-09-18 06:09:33 by localhost)