| |
Project: EDI PHP Application
ID: 1219777141
| Status: |
Open
|
| Budget: |
N/A
|
| Created: |
8/26/2008 12:59
|
| Bidding Ends: |
11/24/2008 11:59 (90 days left)
|
| Project Creator: |
avarise
Rating:
(No Feedback Yet)
|
| Description: |
Avarise LLC is developing a PHP 4 oo application to handle Electronic Data Interchange (edi) documents 850's, 856's and 997's. The application is about 40% developed and is currently being worked on by two developers, a front end developer and myself.
EDI knowledge is preferred but not necessary.
The application is a purchase order system which has a front end that is almost completely developed. Once the purchase order is complete, there is an option to send via EDI, and an array full of params is sent to the base_mapping class, which determines how to map the edi document according to the vendor's rules and then uploads the document via FTP to the inovis VAN (company who transfers the documents between businesses).
The 850 purchase order is uploaded via ftp. The 850 is parsed by the VAN and sent to the company in the sender ID field. Once the company receives it, they parse it and upload to FTP a 997 acknowledgment document, which will be downloaded by our cronjob. The 997 states whether the 850 was correctly formatted or not.
The company now will internally process the purchase order and when they are ready to ship the good on the purchase order, they will send an 856 Shipping Notice edi document to the VAN, which our cronjob will process and our mapping class will parse the 856 into an object that can be used to send an email to the warehouse staff. Once we receive the 856, we upload a 997 acknowledgment to let them know if we properly received the 856. The 856 contains data such as shipping box sizes and what items are being shipped.
We are working with two mappings for two different companies, but both are using the ASC x12 standard so should be very similar.
All edi transactions are saved to a MySQL database.
---------------
Project has the frontend almost entirely completed and is being developed by another programmer.
Backend (this project specification) will be worked on by mainly yourself, and myself when I have the opportunity. I will be reviewing all code to make sure good standards and coding practices are implemented.
The backend already parses 850's for one company and inserts the records to MySQL and uploads the edi document to the server. There is a base class, extended to the company's particular rules, extended to the specific document (850,856,997). The process of retrieving the EDI documents from the server is currently being written, which will then have to be parsed and an object will be created and handled based on what is parsed.
You will be required to pick up additional tasks if necessary to complete this task. Bonuses will be considered in this case.
EDI Specifications:
http://eidx.comptia.org/guidelines/gs_document_index.aspx
Company 1 Mapping Specification:
850: http://eidx.comptia.org/guidelines/documents/gsdbo97.pdf
856: http://eidx.comptia.org/guidelines/documents/3020856.pdf
997: http://eidx.comptia.org/guidelines/documents/EIDX-X12-997-V4010.pdf
Company 2's Mapping Specification will be provided after acceptance of job but follows the same ASC x12 standards as above.
You will be working on our development platform via ftp and possibly SSH (we will be setting up an environment with SSH access for outside contractors soon).
SVN Knowledge is very much preferred. Linux and FTP knowledge is also very much preferred.
|
| Job Type: |
- Programming Services
- PHP
- Script Development
- Website Development
- Other
|
| Database System: |
MySQL |
Messages Posted: 0
|
