Privacy Notice
Disclaimer
Software Disclaimer

MOSS IFTMIN Message Structure

Note: The intent of this viewpoint is to illustrate message structure using example content. It provides content for many more segments than would typically be used in practice. Further, some shown may be mutually exclusive. It shows only one element of a type, even in situations where it is typical to have many (e.g. goods items, packaging). Example data may have (mistakenly) not been provided, in which case just the segment tag is shown.

Message ElementExample Content (from MOSS Data Matrix)
Message Type: IFTMIN
     BGM: MessageBGM+705:::Booking Instructions+19296+9'
     DTM: MessageDateDTM+137:20070709120000:204'
     TSR: TransportTSR+27+2:172++9'
     FTX: DeliveryTermsFTX+AAR+++This cargo is to be cleared at Charleston prior to movement to Spring Hill. GO date is 15 days from VSL ARR for CAD and 15 days FM ARR Inland for Inbond'
     FTX: GoodsDescriptionFTX+AAA+++auto parts'
     FTX: TransportAdditionalInformationFTX+'
     SG 1: BillOfLading
     SG 2: DeliveryTerms
     SG 3: BillOfLading
     SG 3: ContractNumber
     SG 3: DeliveryOrderNumber
     SG 3: OrderNumber
     SG 3: UniqueConsignmentReference
     SG 8: MainCarriageTransport
     SG 11: CarrierParty
     SG 11: ConsolidatorParty
     SG 11: CustomsBrokerParty
     SG 11: FreightForwarderParty
     SG 11: PayerParty
     SG 11: SellerParty
     SG 11: ShipFromParty
     SG 11: ShipToParty
     SG 11: UltimateConsigneeParty
     SG 18: ItemDescription
     SG 37: TransportEquipment




Send questions or comments to se-interop@nist.gov.
Date Created: April 24, 2006
Last Modified: September 23, 2009