After Installation Import Transaction Module Destroy FA

The Official Extensions repo has become a nightmare for some as they have not been updated properly by the respective authors / maintainers in recent times. Compounded with this is the fact that PHP/MySQL versions too have been rapidly evolving. Hence the onus is on the end user to take suitable precautions like this non exhaustive list:

1. Take backup before any new module installation
2. Read the module code if PHP savvy
3. Compare the code in the modules folder with those in the FA24Extensions repo and other repos and use your own judgement before relying on any source.
4. Search the forums and the wiki and other's weblogs for pertinent gotchas.
5. Rollback any bad extension install
6. Ensure that the FA DB schema is not changed on such roll back - a restore from backup is better and advised.
7. File additions/deletions and modifications especially in the various installed_extensions.php files need to be rolled back as well.
8. Many Charts of Accounts when taken from the official repo will not have their field name orders in synch with the default ones.

If you are dealing with a commercial / production installation, do not use FA (or for that matter any ERP) without professional assistance - smart people's time will need to be paid for well and are certainly worth much more than many dumb superior's salaries! Those who pretend to be "self-sufficient" IT heads responsible for FA in their organisations are actually doing a great disservice to their employers - all will be well till something goes wrong and then heads roll or a coverup occurs - either way FA gets a bad name!

It appears that you are using the dry run method which is used for checking. Try the actual run choice.

Logout, close all browser instances and then login. Check the db that the serial numbers of the vouchers do not already exist in your FA instance. Then try it again.

Check if the DB user in FA has the necessary permissions - use the debug feature in FA and check it out or take local professional assistance.

This occurs because your CSV file is not properly formatted.
The list() statements in the files import_transactions.php and includes/import_transactions.inc populate the $code_id variable.

The possibilities where it could go wrong are at:

ST_JOURNAL:
  list($reference, $date, $memo, $amt, $code_id, $taxtype, $dim1_ref, $dim2_ref, $person_type_id, $person_id, $comments)
ST_BANKPAYMENT:
  list($reference, $date, $memo, $amt, $ignore, $code_id, $taxtype, $dim1_ref, $dim2_ref, $person_type_id, $person_id, $BranchNo)
ST_BANKDEPOSIT:
  list($reference, $date, $memo, $ignore, $amt, $code_id, $taxtype, $dim1_ref, $dim2_ref, $person_type_id, $person_id, $BranchNo)
ST_BANKDEPOSIT / ST_BANKPAYMENT:
  list($reference, $date, $memo, $amt, $code_id, $taxtype, $dim1_ref, $dim2_ref, $person_type_id, $person_id, $BranchNo)
ST_SALESORDER / ST_SALESINVOICE:
  list($customer_id, $branchNo, $reference, $date, $payment_id, $sales_type_name, $dimension_id, $dimension2_id, $item_code, $item_description, $quantity, $unit, $price, $discountpercentage, $freightcost, $delfrom, $deldate, $delto, $deladdress, $contactphone, $email, $custref, $shipvia, $comments, $exrate)