Documentation
Back to website >

Glossary [S]

Script A script is a text file in a programming language that is interpreted. A classic batch file can also be called a script. Scripts allow you to execute different instruction sequences based on conditions. For example, a data backup can always be executed if the day of the week is Monday and Thursday. EULANDA supports scripts in Java, Visualbasic, SQL and Pascal.
Servicepack Service pack is the term used to describe the aggregation of many individual program updates into a complete package for large software products. A typical example is the Windows operating system and Microsoft SQL Server. For example, the service pack reduces the effort involved in a new installation, since after the installation of the main product, many individual patches no longer have to be installed after the installation of the main product, but only the currently valid service pack.
SFTP SFTP is a file transfer protocol that, unlike FTP, provides a secure transmission. The connection and transmission is encrypted. Today it is especially important in the area of EDIFACT and is often used to exchange EDI files between partners. The disadvantage compared to AS2 is that no acknowledgement of receipt will be received and therefore it is not sure whether the partner has received the file without errors.
Sichten

Views are different ways to see on your data. Normally, the data is available in a fixed structure in the database server. With EULANDA®, for example, an article file consists of the article number, the matchcode, the texts, the prices and other fields. Another view of this table could, for example, consist of a subset of the actual fields - for example, only the article number and the sales price; a combination of different tables is also possible. A view can combine the VAT table, revenue table and article table and present them to the outside world as a common new table. All these combinations allow a flexible structure of the program.

In views, the SQL server does not store the original data or create a new file, but creates this view "on the fly" at the request of the client. EULANDA® or any other application such as Excel, Word or an external print generator can access views like "normal tables".

Since views in the SQL server are small programs that compile the data, a view can also contain additional fields, that is, fields that are not contained in the original data. These could be calculated fields, that is, fields that result from existing fields (total price = quantity x unit price), but can also come from completely different tables in the same database. One example are the "open items". Here, the information is compared from various tables and recompiled. An open item is an invoice to which all payments from the payment table of the relevant invoice are added up and brought into agreement with the invoice header record. If the total of all payments is not identical to the invoice amount, the invoice is open. In this case, the view creates a data record from all necessary fields, whereby the header record is supplemented by fields from the address master, the currency master and other tables. The view obtained in this way is sent to the client, i.e. the EULANDA®.

Views have the advantage that the client or the EULANDA® has easier access to data in a standardized way. This is the only way to make it easy for external applications to access prepared structures without knowledge of the internal complex interrelationships.

A major advantage of views is that they help to avoid redundancies. All required information exists only once in good systems and is collected via views according to requirements.

EULANDA® supports a layer model by different views. For original tables, such as articles, addresses, invoices, etc., there are MASTER views. These contain additional information that is calculated from frequently required fields and combined with information from other tables. The MASTER views are too complex and unwieldy for normal work. For this reason, soffits for the respective task are derived from them. One example is the PRINT views. These contain a subset of data from fields in the MASTER view. If you want to derive your own PRINT views, for example to include additional fields, or even to include data from external files, you should always derive the PRINT view. If possible, the PRINT view is kept compatible with updates, which will not always be the case with the complex MASTER views.

SNOM manufacturer of IP phones.
SQL Registry The central settings database of EULANDA. It is also stored in the respective SQL database, i. e. per client. It has a hierarchical structure similar to the Windows registry. The control is done via the editor integrated in EULANDA (under System administration/SQL Registry). Alternatively, there are also API procedures in the SQL server to change the SQL registry.
Stored Procedure These are programs created in the programming language SQL and stored in the database. These can be executed by the SQL server and are much faster than interpreted SQL source code. In addition, these programs can also be executed in server events, e. g. without EULANDA program.