Skip to content Skip to main navigation Skip to footer

Prelude Desktop Data Configuration

Create a folder named “Automation” in the Prelude Root folder (referred to as ), in which we will maintain the tables required for integration and to which we will require all files/tables for Prelude integration to be saved. This folder will contain the following sub-folders:

  • Control files required to control automation operations, mappings etc.
  • FTP/Pending – all outgoing files to be saved to this folder, e.g. synchronisation
  • FTP/Processed – outgoing files are moved to this folder after being processed
  • Pending – all incoming files to be saved to this folder
  • Stock Maintenance – YYYYMMDDHHMMSSMMM-CC-STK.CSV
  • Customer Maintenance – YYYYMMDDHHMMSSMMM-CC-SLM.CSV
  • Customer Address Maintenance – YYYYMMDDHHMMSSMMM-CC-SLA.CSV
  • Sales Rep Code Maintenance – YYYYMMDDHHMMSSMMM-CC-SRC.CSV
  • Supplier Maintenance – YYYYMMDDHHMMSSMMM-CC-PLM.CSV
  • Sales Orders – YYYYMMDDHHMMSSMMM-CC-SOP.CSV
  • Sales Invoices – YYYYMMDDHHMMSSMMM-CC-SLI.CSV
  • Sales Credit Notes – YYYYMMDDHHMMSSMMM-CC-SLC.CSV
  • Sales Receipts – YYYYMMDDHHMMSSMMM-CC-SLR.CSV
  • Sales Payments – YYYYMMDDHHMMSSMMM-CC-SLP.CSV
  • Purchase Orders – YYYYMMDDHHMMSSMMM-CC-POP.CSV
  • Purchase Invoices – YYYYMMDDHHMMSSMMM-CC-PLI.CSV
  • Purchase Credit Notes – YYYYMMDDHHMMSSMMM-CC-PLC.CSV
  • Purchase Payments – YYYYMMDDHHMMSSMMM-CC-PLP.CSV
  • Purchase Receipts – YYYYMMDDHHMMSSMMM-CC-PLR.CSV
  • Journals – Not yet used
  • Payroll – Not yet used
  • Reports – Process report files will be maintained in this folder
  • Logs – Process log files will be maintained in this folder
  • Quarantine – all files that cannot be processed will be moved to this folder

Under certain circumstances – i.e for inter company transactions where the same electronic statement/remittance is used the following two may also be used

Sales Transaction Matching – YYYYMMDDHHMMSSMMM-CC-STM.CSV
Purchase Transaction Matching – YYYYMMDDHHMMSSMMM-CC-PTM.CSV

Licence activation must be updated to enable Automation, after which Automation parameters must be set in Company 00 > Parameters > General > Automation tab. Automation applies to all Prelude Desktop companies, so its control parameters are only available in the root Prelude Desktop company 00.

Process: DIAMOND.INI must include the item AUTOMATION=Y. INI hierarchy applies, so Automation can be enabled/disabled at the Workstation|Root|Database level with DIAMOND.INI\AUTOMATION=N at the appropriate level.
For group networks, Prelude Desktop company 01 (data folder name DATA.001) is the Parent business. Prelude Desktop company NN (data folder name DATA.0NN), where NN is a two-alphanumeric code, is the subsidiary business.
CSV Files will now include a header row.
Individual Customer, Customer Address, Supplier, Stock Maintenance files may contain details of multiple records.
Individual transaction files must contain details of only one transaction.
Text (Char) field sizes are maximums (i.e. actual content can have fewer characters) unless the required field contents are specified in the definition.
Date fields will be in the format “DD/MM/YY” or “DD/MM/YYYY”.
Incoming files are to be saved to the Automation/Pending folder for processing.
If YYYYMMDDHHMMSSMMM-CC-TTT.CSV would overwrite an existing file of the same name in Pending, the file name will be appended with a, b, c etc. qualifying character.
Files that fail data validation will be moved to Quarantine for review and amendment and can be moved to Pending to be processed again. Fields in the files that require validation are identified in the file specifications below by the bold text in brackets. A file will not be processed at all if any field fails validation.
Files that pass data validation but fail to be processed at the time (e.g. because the destination database is locked for access by another user) will remain in Pending to be processed at the next attempt.
In order processing, for files submitted by Flightdeck, NUMBER field will be blank and REF field will include a unique ID which will be used to identify the order and the associated b2b internal orders for future amendment and processing.
When processed successfully, files will be moved to an archive folder relevant to the processed event.