The Nominal Transaction table must have VAT Code/VAT Period ID fields against each NL Posting
When it comes to reconciling VAT Transactions for a submission period Vs Nominal posted transactions, there is no direct link between the two. It will be useful to have each transaction's VAT Code, VAT Type, VAT Period ID stored in Nominal Transac...
Rustum Khedkar
over 1 year ago
in Database
0
Idea Accepted - Gauging Support
The functionality whilst raising purchase orders directly from sales orders needs vast improvement overall. There are too many pitfalls. It would help the user by being able to raise PO directly from each specific product particularly where multip...
Thompson, Kevin
about 2 years ago
in Back to Back Orders
1
Idea Accepted - Gauging Support
On very rare occasions you may see duplicate URNs posted to the Sales Ledger due to environmental issues (deadlocks etc), this could possibly be prevented by setting a constraint on the SLPostedCustomerTran URN field field in the database to preve...
Tim Critchley
over 1 year ago
in Database
0
Idea Accepted - Gauging Support
When raising a Sales order have a tick box for if the products on the order need consolidating on a Purchase order (e.g. 1 weeks orders for a Supplier all on 1 PO). Have a similar system as Generate Orders but you can then select which suppliers c...
Guest
almost 6 years ago
in Back to Back Orders
0
Idea Accepted - Gauging Support
Ability to link Nominal SQL tables to POP and SOP transactions.
Currently there is no link between the Nominal Ledger and the POP and SOP transactions in the SQL database.This as I see it is a major weakness in the database design as there is no visibility of the nominal postings detail. This can easily cause ...
Guest
over 10 years ago
in Back to Back Orders
0
Idea Accepted - Gauging Support
DateTimeCreated field in SOPOrderReturn to match Application/Database Server timezone
In 200 when a new Sales Order is created and saved, the DateTimeCreated field in SOPOrderReturn is populated and is exactly one hour behind the actual time the Sales Order was created. Having spoken to 200 Tech Support, this is because the DateTim...
Guest
over 7 years ago
in Back to Back Orders
2
Idea Accepted - Gauging Support
We create a number of reports in Sage based on data directly from SQL. We use the DateTimeCreated field in a number of tables to provide KPIs and time triggered reports. DateTimeCreated has always been generated from the Server time that SQL is ru...
Guest
over 8 years ago
in Database
1
Idea Accepted - Gauging Support
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
Add a database transaction around the allocation/dispatch routines
There is not currently a database transaction around the allocation/dispatch routine, we have found that if a process gets interrupted for any reason (Sage/Network/Terminal issues) the process is not rolled back and this leaves corruption in the d...
Guest
over 8 years ago
in Back to Back Orders
0
Idea Accepted - Gauging Support
