EDI & Flat File Processing at AFS

Overview

Processing methods vary by system and location, and may include:

• Direct EDI creation and loading
• Flat file loading
• Translation via Sterling Integrator
• In-house custom-built loaders and file creators

This article provides an overview of where and how EDI and flat files are processed, as well as supported inbound and outbound document types.

Systems & Platforms Used at AFS

Accuterm (SHV FAP)

• Files load directly from EDI and flat files
• Uses in-house custom-built loaders

Excellence TMS (SHV)

• EDI files written directly to EDI format using an in-house custom-built file creator
• Files load directly using an in-house custom-built EDI loader

Analytics (SLC FAP)

• Files load directly from EDI and flat files via in-house custom-built loaders
• Some flat files are translated in Sterling Integrator before loading

Kansas City FAP

• Files load directly from EDI
• Uses in-house custom-built loaders

AFS TMS / Smart TMS

• EDI files written directly to EDI format using an in-house custom-built file creator
• Files load directly using an in-house custom-built EDI loader

Greenville (GVL) FAP

• Sterling Integrator used for:
  • Translation of EDI
  • Translation of some flat files
• Files load via in-house custom-built loaders

BBA FAP

• Sterling Integrator used for translation of some EDI files
• Files load via in-house custom-built loaders

SSI FAP

• Sterling Integrator used for translation of:
  • EDI
  • Some flat files
• Files load via in-house custom-built loaders

DTA FAP

• Select clients’ files are forwarded to also be entered in:
  • GVL FAP
  • PAQ

PAQ

• Sterling Integrator used for translation of:
  • EDI
  • Some flat files
• Files load via in-house custom-built loaders

P44

• 214 Shipment Status files are forwarded from:
  • Excellence
  • AFS TMS / Smart TMS
  • GVL FAP

SmartAudit

• Sterling Integrator used for translation of:
  • EDI
  • Flat files
• Files load via in-house custom-built loaders

Document Types Supported by AFS

AFS processes both EDI and non-EDI document types.

Inbound Documents (Received by AFS)

Invoice Documents

• 110 – Air Freight Details and Invoice
• 210 – Motor Carrier Freight Details and Invoice
• 310 – Ocean Freight Details and Invoice
• 410 – Rail Carrier Freight Details and Invoice
• 810 – Invoice (Generic goods and services format)
• Ebill – CSV files pulled from the UPS website
• FBO – CSV files pulled from the FedEx website
• Various flat files

Shipment Status Documents

• 214 – Transportation Carrier Shipment Status Message
  • Delivery confirmation
  • Package movements
• 240 – Motor Carrier Package Status
  • Used by UPS for delivery confirmation and package movements
• 990 – Response to a Load Tender
  • Sent as confirmation to a load requested through a 204
• 997 – Functional Acknowledgement
  • Confirms receipt of a document received

Bill of Lading / Matching Documents

• 858 – Shipment Information
  • Bill of Lading (BOL) files sent by clients for matching purposes
• Various flat files

Outbound Documents (Sent by AFS)

Invoice Documents

• 210 – Motor Carrier Freight Details and Invoice
  • Used to send weekly carrier invoice data to clients for processing in their systems

Shipment Documents

• 204 – Motor Carrier Load Tender
  • Used to book shipments with carriers

Reporting Documents

• 820 – Payment Order / Remittance Advice
  • Electronic remittance information for applying received funds (Check or ACH Wire Transfer)
  • Can also be used to initiate a payment
• 820 (Dispute)
  • FedEx Parcel uses a version for disputing certain charge types
• 997 – Functional Acknowledgement

Additional Outbound Formats

• Flat files
• Spreadsheets
• CSV files

Notes & Best Practices

• Sterling Integrator is primarily used for EDI and flat file translation, not loading.
• Most loading activities rely on AFS in-house custom-built loaders.
• Processing paths may vary by client, location, and document type.