MODTRS - TRANSIT CONTROLS USING ASYCUDA++ Ó UNCTAD – SITE (V1.15) 7.26 The Voyage number of the generated manifest takes on the following structure: FIP + Year of FIP + “-“ + Registration no. of FIP where the Year and Registration number come from the first FIP tagged in the list. The Bill of Lading number follows the following structure: FIP + Year of FIP + “-“ + Registration no. of FIP / 1 where the final number is incremented for each Bill of Lading. In all cases, when a Manifest is generated from a FIP, the type of Bill of Lading code is 950 according to International coding standards. The status of the Bills of Lading will be ‘REGISTERED’ and the operation will be ‘FROM FIP’. Status At any time when a FIP is on the screen, the Local Menu contains a  ‘Status’  option that will give the ‘CURRENT’ status of the FIP.  The status of an FIP can be: - ·     New FIP ·     Stored ·     Registered ·     Validated ·     Under customs control The status box gives the name of the user who carried out the action, and the date and time if Registered, Validated or under Customs control. Technical details of status can be found in Section V of the New Technical Features of Version 1.15a document. Details of the structure of the ASYCUDA++ database tables (as they relate to FIP) are given in Section III of the New Technical Features of Version 1.15a document. Details on standard communication DIAMs, provided for FIP message transfer are in the A++ Gate documentation Version 1.4 in the section entitled  ‘Standard DIAM documentation’.