SAS and Interfaces
Input and output SAS
This NETiKA tool is extremely developed. It enables data import (creation or modification), export and mass data changes.
The module includes all RI management rules as well as all of the client’s specific project management rules.
There is not development required for implementation, only SQL configuration, which is done by the NETiKA integration team.
The SAS has a workflow which secures the transactions. All errors are logged and clearly explained. The tool has a very useful functionality: data errors can be corrected via a MMI (man-machine interface) directly in the application without having to resubmit a data file. The MMI suggests lists of values to assist the user with input.
The SAS is therefore not a standard SAS which limits clients to a precise format. It is a solution which meets client needs, based on the expertise of the integrator to adapt the parameters to the fullest extent possible.
Asynchronous SAS input/output
The asynchronous version of the SAS described above is useful for long sessions to ensure their integrity and successful completion.
Our SAS include reconciliation functionality which ensure database consistency.
Since 2000, NETiKA has gained extensive experience interfacing its solution with various client IS’ during projects at major accounts (group inventories, financial ERP, purchasing ERP, schedule management, CMMS, etc.). We develop all types of interfaces in line with the practices, requirements and needs of our clients’ IT teams: web services, direct display reading, flat file background transfers (.csv, .xml) using different protocols (SFTP, etc.), inclusion of screens via URL links, Idocs, etc.
For NETiKA RI database imports (sites, third parties, leases, files, invoices, contracts, orders, etc.), NETiKA provides standard formats and a very simple procedure which makes clients autonomous. We also use proven procedures to import documents. We have two processing methods for flat files transmitted via FTP or another protocol:
- Manual handling via a sas (see above) which enables data correction on the screen
- Automatic ordered background processing. The benefit is that there is no human intervention required. The downside is the handling of errors when they occur: the user receives an alert via which they can review a log file then take the appropriate action.
We prefer an interactive SAS for the initial loading of databases, which requires special care.