Hand placing the final block on a colourful tower

Back to Basics

DataRapt released the first sub-ledger control account bundle way back in February 2008.  We have come a long way since then and now cover 4 SYSPRO versions, 10 sub-ledgers and serve customers world-wide. It must be said that without our valued partners and customers, none of this would have been possible.

Looking at our growth between then and now, I have realised that it’s time to take out some of our older blogs and give them a good spring clean.

This, then, is our new, updated look at the basics.

Refreshing the Reconciliations

The Refresh function is the heart of the sub-ledger reconciliations. First, the opening and closing balances for the sub-ledger and control accounts are calculated from transaction level up. Then all transactions that make up the sub-ledger balance are compared to the relevant GL audit trail files. Finally, the audit trail files are compared to the entries posted to the control accounts in the Ledger.

Two very important notes about the Refresh:

  1. This function is performed only for the financial period or periods that you have selected. In order to refresh the data for any other period, you must select the required period before selecting this function. In addition, if any transactions have been posted back to a prior period, the refresh for that period must be performed again.
  2. DataRapt does not write any data to SYSPRO tables, but rather updates its own set of tables with the results of the refresh. This highlights the importance of re-refreshing the reconciliation(s) if changes have been made to the SYSPRO data.

‘Correcting’ the DataRapt Reconciliations

There is a misconception that the DataRapt reconciliations can, themselves, be adjusted to remove variances that have been corrected in the General Ledger by way of ledger journals.

There is no posting function in the DataRapt reconciliations. Every transaction that makes up the sub-ledger balance is drawn from the underlying SYSPRO tables. This means that the only way to ‘fix’ the DataRapt reconciliation is to correct the problem in the sub-ledger. The WhatNext? function that is available for every variance in the reconciliation attempts to address how the variance may have arisen, and suggested corrections are provided.

We do not ever suggest correcting or over-riding data in the SYSPRO tables, but are here to assist you in finding a solution to data inaccuracies.

Date changes

Whilst SYSPRO is a period driven system, there are some tables that use transaction dates to ascertain the timing of the transaction. This applies particularly to the Fixed Assets module, where the purchase date of the asset is key to all SYSPRO and, by extension, DataRapt calculations. The Work in Progress module also relies on dates for certain calculations in DataRapt.

Performing the Financial Year or Month change function in SYSPRO can, on occasion, cause timing difference between the sub-ledgers and the general ledger.

Please contact the DataRapt team if you find yourselves in this situation.

DataRapt Purge

There is some confusion regarding the purge function within DataRapt. We have been asked the question “Will the Purge Reconciliation Information function purge SYSPRO data?”

The answer is no, you cannot purge SYSPRO data through DataRapt.

The data you are being prompted to purge here is DataRapt data. The retention of this data influences how far back you can view previously refreshed periods in the recons without refreshing again. If you purge this data then you will have to refresh the periods again if you want to query them. Bear in mind that if you would like to view periods older than those that can be re-refreshed then this will no longer be possible if you have purged those periods.

DataRapt Releases and Builds

DataRapt’s ‘hotfix’ equivalent is the DataRapt Build. We have separate builds for the different SYSPRO versions we support and sometimes for different releases of those versions.

If you are experiencing problems with any DataRapt program, you should ensure that you are running the latest build for the version and release of SYSPRO that you are using.

You can get information on any program changes between the build of DataRapt you are currently running and the latest build by looking at the Change Notes on our support site.

DataRapt Licensing

This section covers quite a large topic, and might deserve a write-up of its own. Thus, instead of basics, I will cover some of the misconceptions regarding licensing.

DataRapt needs ‘Activation Keys’ in order to run. These keys are automatically issued on receipt of payment and should be valid for the entire license period. However, there are times when the keys become invalidated due to a change in user environment and will need to reissued. The most common reasons for this are:

  1. the server identifier against the licensed server has changed
  2. the number of licensed SYSPRO users has increased
  3. the SYSPRO company name has been altered or a new one has been added
  4. the version of SYSPRO has changed

If you add a new SYSPRO company name on the server, you’ll need a corresponding activation key for DataRapt. You will need to tell us how the company name is defined in SYSPRO as the DataRapt key needs to match the company name in SYSPRO exactly.

DataRapt licensing is based on the number of licensed SYSPRO users. If this changes, you may need to apply for new DataRapt Activation Keys. There may be license fees payable but we will advise you if this is the case.