Category: Sage Line 500/1000 ERP
V1 DBForm sniplets
In DBForms try where possible to use -E for Trusted Connections rather than hard coded usernames and passwords. Use dbsvpdf.exe to output V1 outputs to PDF For multi page, multi document outputs use a variable to control the end of page such as END_OF_DOC using a field you know will appear on the last page…
The Journal Listing Report on General Ledger produces lots of blank pages
Sage Line 500 V7.1 had an option added to not include blank lines between journals which lead to hundreds of pages of blank pages being printed. If not in your version ask your reseller referencing 58022 to obtain the latest binary version and system key file introducing this. NLJLISTBK1 = NO NLJLISTBK2 = NO Assembly…
Sage Line 500/1000 Period End Email Check
As part of Sage Line 500/1000 Period End we found it easier and more audit friendly to have an automated email fire via SQL. My colleague Jim wrote the below (Hey Bob!), I then changed it around to match the sections in which we ran period end. This made it easier to determine if period…
NL Batch processing states there is an error with a journal which does not show in list
In my experience this occurs on large Journals populated outside of Sage into Sage’s SQL database Record the errors or check the system.log file on the company for affected entries. Check if the entries actually exist with a TSQL statement select * from scheme.nljrnm(nolock) where journal_no IN (‘‘,’‘) order by journal_no,page_no Normally you will find…
Update Sage Line 500 Binaries
This should first be tested on a development system before being deployed to a live system. My steps may be incomplete, some binary upgrades will require new system keys or may require a utility to be run beforehand. Always test first! Ensure no-one is using the Binary being upgraded, it is recommended for all users…
Use TSQL to extract V1 DBArchive Blobs
Using TSQL it is very easy to automate extraction from Version One’s DBArchive product with its dbremoteblob program (It does require a username and password to access DBArchive and the program comes with DBArchive). With a 4 core CPU I extracted 72000 documents a day, a limitation found was the programs used did not return…
Check scheme.plitempm for any orphaned entries
Check scheme.plitempm for any orphaned entries against plpy tables, found to be caused by third party app not Sage Line 500.
V1 DBAuthorise grab a list of Purchase Orders
V1 DBAuthorise can be setup to have multiple Purchase orders, so I use a Common Table Expression in a view for any time I need to get a list of Purchase Orders and Sage Company that is not in ~Accepted and State OK (1024). user5 for us is the PO number and user7 the Sage…
Maximum History Reached in Code & Post Registered Invoices
Credit: Datel Code & Post Registered Invoices has a database limit on the plreghstm table and can hold 79 rows before displaying the error Maximum History Reached (Even though the field supports 4 characters). The last row holds a ~ (Tilda) in the page number field causing the error message and subsequently the automation routine…
Prevent Duplicate Audit Entry warnings on Sage Line 500 when migrating systems
The file .seqno in csmaster/master is used to maintain the current audit reference. Ensure its copied from the old server otherwise it will start from zero causing duplicates and failure to post audit entries to the database. System Keys which track the Sequence Number: CEAUSEQNO Errors: Auditing failed: xx_xxxx_xxx event C. Duplicate seq. no.nnnn?