MODTRS - TRANSIT CONTROLS USING ASYCUDA++ Ó UNCTAD – SITE (V1.15) 7.35 Message Transfer in a Multiple Office environment When transferring a TIR Carnet, FIP or T1 from one office to another, the transfer is normally carried out using A++ Gate. However, if the office to which the message is to be sent is on your current server, then the A++ Gate is not activated. You will receive the same message that your document has been transferred but no A++ Gate agent is created and no DIAM is activated on your server. ASYCUDA++ Technical Details on Transit The transit functions of ASYCUDA++ are a more recent development and were first introduced with ASYCUDA++ Version 1.15. The introduction of MODTRS and the Transit functions in MODBRK required changes in the system database tables and the writing of new standard messages and reports. Although this Reference Document is not intended as a reference to technical details many of the main changes are summarised below. Database Tables TIR Carnet Storage of TIRs in the ASYCUDA++ database is done with three tables: TIR_GEN: TIR Carnet details TIR_ITM: TIR - Voucher details TIR_MAN: TIR goods details FIP Storage of FIPs in the ASYCUDA++ database is done with five tables: FIP_GEN: FIP General segment FIP_ITM: FIP Items FIP_OCC_CNS: FIP Occasional consignee FIP_OCC_DEC: FIP Occasional declarants FIP_DEC_SER: FIP serial numbers T1s Storage of T1s in the ASYCUDA++ database is done with five tables: TRS_ITM: T1 Items TRS_OCC_CNS: T1 Occasional consignee TRS_OCC_EXP: T1 Occasional exporters TRS_DEC_SER: T1 serial numbers The structure of these tables is given in the document ‘New Technical Features of Version 1.15a’.