|
⇤ ← Revision 1 as of 2008-09-18 07:42:52
Size: 1734
Comment:
|
Size: 1930
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 12: | Line 11: |
| 1. (Optional) Setup EDI email alerts (gencont -> EDI Manager Email) | 1. {{{craad}}}->Purchase Order (Email/Print) = E 1. {{{ > ln -s /u/cc/std/binl/B2BEspporep /u/cc/std/binl/<CRED_CODE>spporepE}}} 1. (Optional) Setup EDI email alerts ({{{gencont}}} -> EDI Manager Email) |
| Line 14: | Line 16: |
| 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 |
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 |
| Line 21: | Line 23: |
| 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 |
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.
General Overview
Outgoing Files
- Setup creditor to generate EDI files
craad->Purchase Order (Email/Print) = E
> ln -s /u/cc/std/binl/B2BEspporep /u/cc/std/binl/<CRED_CODE>spporepE
(Optional) Setup EDI email alerts (gencont -> EDI Manager Email)
- User creates a PO
stpost runs spporep
spporep creates file in /u/cc/
spporep calls the script edi_commit.sh
edi_commit.sh moves newly generated file into the appropriate directory
- EDI vendor software retrieves file and imports into their system
Incoming Files (Allphones only)
- EDI vendor software creates file in appropriate directory
crontab schedules edi_import.sh to run periodically
edi_import.sh processes file to create order/invoice
- On success, file extension is changed to .success
- 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
- For "Soft Errors", leave file for processing at another time