MODCHQCF - NATIONAL CONFIGURATION Ó UNCTAD - SITE (V1.15) 8.10 Learning Modes for Suspense Regimes When a declaration is processed for temporary admission or temporary export, certain details of the declaration  (Commodity  Code,  Country  of  Origin  or  Destination,  Company  Code  etc)  are  written into the database as a means of identifying and controlling the declaration. When  processing  a  declaration  for  exit  from  temporary  admission  or,  for  re-import  of  temporary export goods, you must use a Customs Procedure Code with the previous procedure that activates the  capture  of  an  original  declaration  reference  data.  ASYCUDA++  then  checks  the  remaining stock  account  by  unit  of  quantity  (Supplementary  Units  of  Net  Mass)  and  will  write-off  the  stock account  by  the  amount  re-imported  or  exported.  Warehousing  declarations  are  controlled  in  a similar way but are additionally controlled by Warehouse Code. When  ‘Learning  Mode’ is set to  ‘YES’  for  temporary  admission,  the  import  declaration  will  be processed   as   described   above.   However,   when   a   declaration   for   ‘exit’   from   that   temporary admission is processed, you capture a previous procedure that has an action code of  ‘05' in order to  activate  the  capture  of  the  previous  declaration  reference.  However,  when  the  declaration  is assessed, the system will not write-off the stock account and not perform any further checks on the remaining stock account or the delay. When ‘Learning Mode’ is set to ‘YES’ for temporary exports or for warehousing declarations, any declarations for re-import of temporary export or for exit of goods from warehouse will be processed as described in the previous paragraph, i.e. the stock account will not be written off and the system will not perform any further checks on the remaining stock account or the delay. ‘Learning Mode’ is intended to assist countries where the original transaction under the suspense regime is not in the ASYCUDA++ database (the transaction is ‘pre-ASYCUDA’) and so cannot be matched. ‘Learning Mode’  should  be  an  interim  measure,  for  new  transactions  using  suspense regime codes will be in the database and eventually ‘Learning Mode’ can be deactivated. See    Section    3    of    this    Reference    Document    for    details    on    processing Declarations using Suspense  regimes.Section  10  of  this  Reference  Document explains ‘Customs Procedure Codes’, ‘Requested Procedures’, and ‘Action Codes’   and   how   they   are   used   to   manage   stock   controls   under   suspense regimes.  For  technical  details  on  the  effect  of  the    ‘Learning  Mode’  flags  on ASYCUDA++ transaction tables, see the Technical Documentation. Declaration Configuration The flexibility of the ASYCUDA++ system is one of its strongest points. The Declaration input fields can be configured to suit the needs of the particular country concerned. The on-screen descriptions of the fields, or ‘labels’, can also be altered to meet national  requirements.  See  the  Technical  Documentation  for  details  on  using the ASYCUDA++ language translation utility program ‘LTR’. The   declaration   fields   can   be   defined   as   ‘Mandatory’   -   must   be   completed,   ‘Optional’   -   not necessary   and   ‘Prohibited’   -   data   entry   prevented.   It   is   possible   to   decide   whether   validation controls on particular fields are activated or not. It is not possible to directly add validation controls, as they are ‘hard coded’ within the system, but some existing controls can be configured. Declaration Configuration Management Export  and  Import  Declarations  can  be  configured  separately  under  these  options.  The  method used is identical for both types of declaration.  After choosing the type of declaration to configure, select ‘Local menu’, ‘Field Panel’. The following screen will be displayed: