Functionality to add a Name (Description) and a Short Name to non-standard Sage 200 Modules/Sources
When importing Sage 200 Customer or Supplier transactions, it is possible to specify a Source (Module) number in the 16-90 range to the Excel import file. At present, when the transactions have been imported, the description of Sources 16-90 will ...
This will assist support on the product, I needed to on several occasions try to find how data has got into the system when a customer is sure the data was not imported. It would be great if when a item is imported into sage via one of the standar...
Guest
over 10 years ago
in Database
0
Idea Accepted - Gauging Support
Import Customer Transactions - Sales Receipts - Allow Bank Account to be specified
When using the Import Customer Transactions routine to import sales receipts, there is no option to specify which bank account should be used. The default bank account is used. When you enter a sales receipt via the Enter Customer Receipt routine,...
Sales and Purchase Transaction Imports should prevent Fx Rate lt; 1.000000 if the Customer or Supplier Account is Base Currency
It is possible to upload transactions with FX rate of lt; 1.00000 even the account you importing into is base currency, thus potentially putting the Control A/C out of balance.
Allow Imported Transactions to be Pre-Authorised if PL Invoice Authorisation is Enabled
On all Sage 200 versions prior to 2011 if purchase ledger invoice authorisation was enabled for all (£0.00). Imported invoices were not looked at and were imported as Authorised. On version 2013 onwards this core functionality changed and if PL in...
Narrative field to exist in trader ledger transaction tables
To display the narrative on reports and layouts, e.g. Purchase Remittance, requires the inclusion of the NLPostedNominalTran/NLDeferred NominalTran/NLPendNominalTran table(s) (depending on system configuration) by joining on the UniqueReferenceNum...
Guest
almost 8 years ago
in Database
0
Idea Accepted - Gauging Support
Expand SYSNominalAuditTrail table to Include SYSAccountingPeriodID
Expand SYSNominalAuditTrail table to Include SYSAccountingPeriodID as this would allow us to determine what Period a transaction was posted to which currently isn't possible in this area.
Andrew Siddles
over 8 years ago
in Database
0
Idea Accepted - Gauging Support
Improve traceability in SYSFeatureErrorLogging when deleting a bin location
When a bin location is created against a stock item, SQL SYSFeatureErrorLogging shows &Add New Location for item: ABBuiltIn/15/0/2& If you amend the name of the bin, SQL SYSFeatureErrorLogging shows &Edit Location for item: ABBuiltIn/1...
Guest
almost 11 years ago
in Database
0
Idea Accepted - Gauging Support
