972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Transport

IFTSAI Forwarding and transport schedule and availability information

The UN/EDIFACT message used to request transport schedule or availability information and to answer such requests.

Sent by
Shipper, forwarder or carrier
Received by
Carrier or requesting party
Standard
UN/EDIFACT · Batch message
X12 equivalent
323 Vessel Schedule and Itinerary (Ocean)

What is the EDIFACT IFTSAI message?

IFTSAI is the UN/EDIFACT forwarding and transport schedule and availability information message. Its function, as defined in the directory, is to request transport schedule or availability information and to answer such a request.

Carriers use it to publish sailing schedules and capacity, and shippers and forwarders use it to ask what departures are available between two places. The answer lists the vessels or other means of transport, voyages, ports or terminals and the departure and arrival dates. Answers are usually returned as another IFTSAI.

How the EDIFACT IFTSAI message worksDiagram of the UN/EDIFACT IFTSAI Forwarding and transport schedule and availability information message. Shipper, forwarder or carrier sends it to carrier or requesting party. It usually starts the exchange. It is usually followed by IFTMBP and IFTMBF. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT IFTSAI message worksForwarding and transport schedule and availability information: who sends it, where it fits and what thedirectory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeIFTSAISENDERShipper, forwarder orcarrierRECEIVERCarrier or requestingpartyCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYIFTMBPProvisional bookingIFTMBFFirm booking2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage IFTSAIUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 6 conditional groups, starting with:RFFLOCEQDTDTNADGIDBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for IFTSAI. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT IFTSAI message worksDiagram of the UN/EDIFACT IFTSAI Forwarding and transport schedule and availability information message. Shipper, forwarder or carrier sends it to carrier or requesting party. It usually starts the exchange. It is usually followed by IFTMBP and IFTMBF. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT IFTSAImessage worksForwarding and transport schedule andavailability information: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeIFTSAISENDERShipper,forwarder orcarrierRECEIVERCarrier orrequesting partyCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYIFTMBPProvisional bookingIFTMBFFirm booking2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message IFTSAI (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 6 conditional groups, starting with:RFFLOCEQDTDTNADGIDBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for IFTSAI.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends IFTSAI, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around IFTSAI and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Requesting sailing schedules between two ports
  • Publishing vessel schedules to customers
  • Asking about available capacity before booking

Where it fits in the message flow

This message IFTSAI Forwarding and transport schedule and availability information
Usually followed by IFTMBP Provisional bookingIFTMBF Firm booking

Structure

Mandatory segments in IFTSAI (directory D.21A)

In UN/EDIFACT directory D.21A, the IFTSAI message has 55 segment positions arranged in 17 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • UNT

Practical example

IFTSAI in practice

A forwarder needs options for a shipment from Shanghai to Le Havre. Its booking tool sends carriers an IFTSAI request for departures in the next three weeks. Each carrier answers with an IFTSAI listing vessels, voyages, cut-offs and estimated transit times, and the forwarder books the best option with an IFTMBF.

Implementation

Implementation considerations for IFTSAI

  • Use UN/LOCODEs for ports and places, mapped to your own location codes.
  • Refresh schedules regularly, since they change often.
  • Distinguish requests from responses with the message function code.
  • Keep vessel and voyage identifiers consistent with bookings.

How ECOM helps

Automate IFTSAI with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

Industry

3PL and Warehousing

Warehouse orders, shipping advice, receipts and inventory reporting between brands, 3PLs, carriers and retailers.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related transport messages

All 36 transport messages

Need help with IFTSAI?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us