Frequently Asked Questions
The StockCode ProductClass Account Manipulation (SPAM) module steps through all the SYSPRO tables and any transaction that contains both the Stock Code and Product Class will be modified based on the Xref which will contain the OLD Product Class, Stock Code and NEW Product Class. On each relevant SYSPRO transaction, ONLY the OLD Product Class will be changed to the NEW Product Class.
This solution came about with our clients only needing to change the Product Class assigned to a specific Stock Code and also modify the historical transactions to reflect the NEW Product Class. Since there is no one-to-one relationship between OLD and NEW Product Class, the SPAM product does not make any changes to any table which contains ONLY the Product Class and the Product Class master is therefore not modified.
Some of our clients have then used our Product Class Account Manipulation (PCAM) to make the necessary modifications to the master tables etc after using the SPAM module to “clean up” but this is not an absolute requirement for our SPAM clients.
The Xref import file would therefore require three columns with the OLD Product Class in the first column, the Stock Code in the second column and the NEW Product Class in the third column:
For all the MAN modules simply requiring the OLD Code, NEW Code and optionally the NEW description, using a product such as Microsoft Excel (as per the below image), place:
– the OLD Codes in the first column
– the associated NEW Codes in the second column
– the optional NEW descriptions in the third column
and then save the spreadsheet as a CSV (Comma delimited) (*.csv) format which will be able to be imported into the required cross reference module.
The StockCode ProductClass Account Manipulation (SPAM) module requires OLD Product Class, Stock Code and NEW Product Class and would therefore require three columns with the OLD Product Class in the first column, the Stock Code in the second column and the NEW Product Class in the third column:
Saving this as a Comma Separated Value (.CSV) to be used by the MAN Xref import process would look like this:
As each of the Source IT packages shares the same configuration procedure (SITINI), each package installation and configuration needs to be handled separately.
For each package being installed, place the downloaded package executable into the SYSPRO\base\upgrade folder, login to SYSPRO as a SYSPRO Administrator and allow for server update to take place, log back in and run the configuration program (SITINI).
NOTE: The configuration program (SITINI) will only process the last package installation file updated onto the server.
Upgrading multiple Source IT packages to a newer SYSPRO version when they originally existed in the previous SYSPRO version does not require the configuration program (SITINI) to be run and the server update may be actioned using multiple package executables simultaneously by loading all of them into the SYSPRO\base\upgrade folder on the server and logging in as a SYSPRO Administrator .
Our packaged products include a 30 day test license allowing for them to be installed in SYSPRO and used to determine whether the included functionality is adequate.
Note that our MAN product test licenses are limited to a single code or single merge.
If extension license codes are required to complete testing, feel free to contact us to arrange associated licenses.
The BTS product allows for the associated Banking Institutions format to be linked to the relative SYSPRO Bank.
A list screen as below allows for the correct format to be selected.
The following BTS Bank formats are available per banking institution.
- Business Integrator
- NetBank Secure
First National Bank:
- AiDPS Swazi
- CITI Preformat
JP Morgan Bank:
- Global ACH GDFF
- FTI GMT
- Local Payment
Standard Chartered Bank:
Kenya Commercial Bank:
- KCB Quickpay
Commercial bank of Africa:
- Trade Payments CSV
ABN Amro Bank:
- BSI VDB
Fihrst Management Systems:
- BCI(Banco Commercial)
- Direct Entry Payments
HSBC Bank India:
When setting up Netbank “pre-format” and you get th “Import batch – error” message as per this image:
Using the CSV template (using beneficiary reference number) option as per the highlighted option the image below has been represented as correct.
The time required for each MAN module to complete is primarily based on the amount of data stored in the associated SYSPRO tables.
Other aspects such as the server processing capacity and network speeds will naturally influence run times.
Run times vary from literally seconds through to a few hours with our longest reported time at 7 hours for GLAM on a 130GB database back in 2009. Average reported run times have been between 1 and 2 hours.
The MAN modules processes each relevant table and compares the code on each transaction against the cross reference to verify if it is required to me modified.
Based on this solution, the impact of the number of cross reference entries has a minimal effect on the total run time.
If a single cross reference entry takes 2 hours to complete, using 2000 cross reference entries would add about 15 minutes onto the run time.
Aspects such as “summary audit” settings against the MAN module will also have a bearing. There is no practical reason why the “detailed audit” option would be specified but this setting would also have an implication on the run rime adding up to another 20 minutes to the total run time.
The MAN module “Monitor refresh delay period” value you have set to 1 hour does have an implication but nothing like the Tick Over. This value would have been fine at 1 minute to not have a huge implication on your volumes.
The “Tickover refreshes on reports/batches” value as defined against the SYSPRO user being used to run the MAN module must be set to at least “2 minutes” as this is CRITICAL for the optimal performance of our manipulation product.
If you are able to see values ticking over in the “Stock Code Replacement In Progress” window, the “Tickover refreshes on reports/batches” value is incorrect. This session should even indicate “Not responding” due to the 2 minute PLUS delay between refreshes. It is the primary reason we have the “Manipulation Module Status” tool to allow real time viewing of the modules progress.
To modify this “Tickover refreshes on reports/batches” value against the operator, use the SYSPRO “Operator Maintenance” program as follows:
Identifying specific versions of each product that is downloaded by our users allows us to proactively notify those users regarding any relevant upgrades or modifications which may effect their downloaded solutions.
All our data manipulation modules have been developed to handle merging of data within a single SYSPRO company where possible.
Due to the nature of differing rules associated to merging from business to business, it may be necessary to clarify these rules and even run conversions using live test data to confirm acceptance of merging rules.
If the table being altered has the Old Code as a key and the NEW code already exists in SYSPRO, the program will merge the records with the data of the existing master transaction along with quantities, balances, budgets etc. may need to be added together.
Code merging – When replacing a FROM code with a TO code that already exists in SYSPRO, the static information of the FROM record will be lost and this same information of the TO code will remain in SYSPRO. Examples of these are: Dates, Addresses, Names, Rates, Prices, Credit Limits etc. Other than this static information, where at all possible, the information from both records will be merged. It is therefore assumed that when a merge manipulation occurs, the two records being merged have the same unit of measure, rate, price, currency, etc.
Due to the fact that the SYSPRO EFT module is required to be generic, allowing it to be used anywhere in the world, it is not possible for the module to address the individual financial institution’s import formats as Source IT’s GEPS/CEPS modules have in the past.
In the case of GEPS\CEPS, Source IT has specifically written the associated bank format conversions as required. The EFT module outputs all the relevant payment information into an XML output file (see layout).
Using the available trigger points in the EFT module, it is possible to write routines to “massage” this XML file as required for the specific bank format required by the financial institution concerned.
Source IT has developed a new process BTS (Bank Translation System) which will handle the automatic formatting of the payment instructions into the required bank specific layout for the specific financial institutions currently being handled by GEPS\CEPS. See the BTS documentation for User and installation Manuals.
Source IT is in a position to handle the development of any additional formats as may be required by a specific financial institution and include in the BTS system. Contact Source IT should you have any queries