Hi @LRCDKORF,

I’m not sure I’m clear on the requirement.

Are you trying to implement EDI or utilize the Freight Booking functionality?  

The row you have highlighted in your screenshot is the DESADV message class which in IFS would be considered the Dispatch Advance or in EDI would be similar to an 856 message - Advanced Shipping Notice (ASN).

The Freight Booking message is intended to be an outbound message (visible in the Outbound Message Viewer) from the IFS Shipment record to a 3rd party Freight Carrier or Transportation Management System (TMS). 

The thought is you’d send data from the IFS Shipment (i.e. Receiver address, handling units, part information, etc.), then a user would process the Shipment in the 3rd party application. 

Once the transportation function is completed in the 3rd party software, this would execute a message back to IFS and write to the inbound message (FreightTrackChargeService - visible in the API explorer). 

The return values would be stored in a new tab called ‘Freight Information’ on the Shipment record assuming they are sent in the correct format. 

If you need a charge added to a Customer Order, you’d need to create a custom event or workflow to manage this requirement as that is not apart of core IFS.  

Dear astfarazt,

we are currently testing the freight Booking functionality and the screenshot we have posted was just an example to show which information we are looking for.

From our understanding we need at first the right API (for inbound FreightTrackChargeService, for outbound - what do we need to look for???). Which is the right message class and action?

Thanks a lot.

Kind regards