Process flow

1/ DSR110 manifest # allocation:

• Finds completed transactions for selected carrier/whs that don’t already have a manifest number.
• Assigns manifest number (TAMNFN) to these transactions.
• Con-note (TAPODR) already assigned at dispatch confirmation time (when transaction completed).
• Writes to DSR110W1 temporary work file
• Prints con-notes if selected to do so.
• Calls EDR615A to create download data (see next step).

2/ EDR615A create download:

• These programs read DSR110W1 temporary work file
• They use this data to print manifest document and create download information according to specific carrier specifications into EDCNN00P con-note file which has flat file format.
• Star track program is EDR645. It writes data into EDCNN00P with “STAR” in position 397 of each record.

3/ EDO110 Manifest data download:

• Checks if any data to send in EDCNN00P.
• Calls various EDO110x programs for each carrier. These programs take data from EDCNN00P for the particular carrier and write to specific work file.

• These programs then call EDO110E with TPID parameter (e.g. “STAR” or “VEXP”) to determine FTP, log file and archiving folder variables to be used for this carrier.
  • EDO110E looks up EDSAN00P trading partner id file to get FTP script member details and IP address if access method is FTP.
  • EDO110E looks up TMSDS/EDI-CONM to get IFS folder names for pickup and archive of carrier manifest files.
  • In 7.4 release, uses TMSDS/EDI-FTP for the pickup folder name instead of EDI-CONM (in line with other EDI documents)
  • EDO110E looks up TMSDS/EDI-FLOG to determine member to hold last ftp transmission log information.
• The EDO110x carrier program then copies the work file to nominated IFS folder/filename, calls EDO110B to send the data via FTP, then calls EDO110D to copy data to nominated archive folder.
  • Note that EDO110B also calls EDO110C to write FTP log information
• EDO110A then clears EDCNN00P data.