Current Edi Processing

Current EDI Processing

PHA currently processes EDI transactions for both of our container terminals: Bayport & Barbour’s Cut (BCT). We have an FTP server dedicated to the transmitting of EDI between our trading partners and PHA. The inbound transactions are pre-processed on the FTP server and then moved to the BCT or Bayport AIX Express servers. The outbound transactions are generated on the BCT and Bayport AIX Express servers and then moved to the FTP server to transmit to the trading partners.

We currently use VB and PERL programs on the FTP server to pre-process inbound transactions. We also use PERL programs to post-process the outbound transactions.

Automate6 is a utility that schedules and processes data on the FTP server. CRONTAB is the utility that schedules and processes data on the Express AIX servers.

309 & 350

We have a secure VPN connection to CBP to download "309 Manifest" and "350 Container Status" transactions. The VPN connection downloads these files to our AMS server. Every five minutes these transactions are moved to the FTP server to be pre-processed and then moved to the BCT or Bayport AIX Express servers.

301 & 315

Our trading partners send us "301 Booking" and "315 Container Status" transactions. Some of our partners deposit their EDI files on our FTP server in a secure folder for their Line. However, some of our partners require that we sign in to their FTP servers to download the inbound transactions. Once their transactions are on our FTP server, they are pre-processed and moved to the BCT or Bayport AIX Express servers.

997

A few of our trading partners require that we send them a “997 Confirmation” transaction after we receive an inbound transaction from them. This “997 Confirmation” transaction is generated