Privacy Notice
Disclaimer
Software Disclaimer

MOSS IFTMBF 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: IFTMBF
     BGM: MessageBGM+335:::Firm Booking Message+19296+9'
     DTM: DischargeDateDTM+96:20070809120000:204'
     DTM: LatestDeliveryDateDTM+128:20070812120000:204'
     DTM: MessageDateDTM+137:20070710120000:204'
     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'
     SG 1: BillOfLading
     SG 1: CountryOfDestination
     SG 1: CountryOfOrigin
     SG 1: LocationOfFreightPayment
     SG 3: BookingNumber
     SG 3: ConsigneeFileNumber
     SG 3: ConsigneesShipmentReferenceNumber
     SG 3: ContractNumber
     SG 3: DeliveryOrderNumber
     SG 3: FreightForwardersShipmentRefrenceNumber
     SG 3: OrderNumber
     SG 3: SID
     SG 3: TransportReference
     SG 3: UniqueConsignmentReference
     SG 7: MainCarriageTransport
     SG 10: CarrierParty
     SG 10: FreightForwarderParty
     SG 10: MaterialReleaseParty
     SG 10: SellerParty
     SG 10: ShipFromParty
     SG 10: ShipToParty
     SG 16: ItemDescription
     SG 32: TransportEquipment




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