EULANDA® ERP System Head Start thru Technology
Home Information PDF Documents EULANDA Handbooks Training Book's corner Download Contact us Table of Contents About us
Password needed Newsgroup
Determining Item Prices (SQL API)
In invoice items in the tables and views different price fields are offered. The meaning and connections of the fields experience here.
The computation sequence 
Basis x Multi = VkvRab - Rabatt = VkRab + VkNRab = Vk x Menge x
PreisEh = VkSum x VkAufschlagProzent + VkZuschlag = VkGes
Legende:
- User-capable for editing database field
- Data base field is changed automatically by the SQL server over triggers
- Computed field, which is produced by the SQL server
The accuracy is noted in the form Numeric(18,2). This means for example 18 places, of it 2 right-of-comma positions. The type of number Numeric is stored exactly, thus and/or computed without rounding errors.
Some fields contain Default values. These are used, if for the import this data field is not indicated. EULANDA® picks the default values out from the meta data SQL server and initializes thereby the input fields.
The storable fields are defined all with not NULL. An assignment as NULL-field is not permissible thereby. With the import the field can be omitted however, in this case the default value is used.
References with import from data
When importing data only the yellow marked fields are accepted. The yellow fields contain so-called default values. For the import if this field is not indicated, then the SQL server adds the field with the indicated default value. With the import the field may not be assigned the SQL value NULL.
The triggered fields are blocked over the authorization pattern against direct letter. A system administrator could however always access the right to each trigger field writing. For this reason an external program should never run on the administration authorization, but be maximum in the role of EUL_SuperUser. VkVRabVkRab
All computed fields are always write protected, since physically no value can be written here into the data base. Computed fields are produced automatically by the SQL server and to stand only for reading for order.
References with expression and evaluation
The calculation, offers and info systems the field VK position price per unit and VkGes should be always used as position total price. Consider with credit notes all price fields in the views PRINT_Rechnung and/or PRINT_RechnungPos are positivly used. Only in the table calculation and calculation pos as well as the views MASTER_Rechnung and MASTER_RechnungPos are negatively used the amounts.
Since calculations are headed for over the print views and the word Rechnung is exchanged there with credit notes against the word Gutschrift implies this already negative amounts. For this reason credit notes are printed out according to standard with positive totals.
Use with statistics, the prices therefore never add print views, but either the genuine tables, or the MASTER views.
Field description
Basis: Numeric(18,2), Default = 0, not NULL
This field is loaded when putting on a position according to standard from the EK field of the item stock and can be individually amended in the order entry. The field value can be changed, so that it is possible current market prices to enter here or to lead an individual calculation over the field Multi through.
To be let by changes in the SQL registry is it possible the load function for this field to be changed and so this field from other data fields or a SQL user function fill.
The multi is a field computed by the SQL server. This field can be changed in the position collection. Here the dependent VK fields are again computed. The value of the multi field is not stored, but only the yellow market price fields. The SQL server computes the multi-field on the basis the yellow fields independently.
By this procedure it is possible that foreign programs use the same central roundness pattern with the external creation of orders and thus always reproducible results are obtained. Only the yellow marked fields may be used from foreign applications to the letter.
VkvRab: Numeric(18,2), Default = 0, not NULL
This price field is capable for editing in the position mask and as entered in the data base is stored.
The discount field is a field computed by the SQL server.
This field can be changed in the position collection. Here the dependent VK fields are again computed. The value of the discount field is not stored, but only the yellow marked price fields. The SQL server computes the multi-field on the basis the yellow fields independently.
By this procedure it is possible that foreign programs use the same central roundness pattern with the external creation of orders and thus always reproducible results are obtained. Only the yellow marked fields may be used from foreign' s applications t the letter
VkRab: Numeric(18,2), Default = 0, not NULL
This price field is capable for editing in the position mask and as entered in the data base is stored. It contains the discounted "fast“-Vk. On this price only discountable additions over VkNRab is not added.
This field is stored automatically by triggers in the server. It contains one or more not discountable price positions. This field is for additions e.g. copper addition, gold addition intended and only connected in the craftsman version with the addition values such as DEL note. It is however already now linked with the computation logic. The addition is located in a separate table and causes with a change an actualization of this field.
Vk: Numeric(18,2), Default = 0
The VK is the price per unit of the position of inclusive all discounts and necessary the additions. The VK is a field computed by the SQL server. The field can be changed in the position mask, computed then however only the yellow marked fields.
Menge: Numeric(18,4), Default = 1, not NULL
The "Menge" field contains the quantity.
PriceEh: Numeric(9,2), Default = 1, not NULL
The price unit is taken over from the articles source data. Over the PreisEh the total price is formed, whereby the price unit affects the price per unit Vk already provided with the quantity. Thereby the biggest possibility accuracy during the total price determination will be reached.
The field VkSum is computed an intermediate value, by the SQL server.
VkAufschlagProzent: Numeric(9,4)
This file can obtain several proportional total impacts on the position. It is updated by the SQL server by triggers. The trigger is headed for, as soon as entries in the table are changed to this position. A position can process thus as many as desired proportional impacts. The field is used at present not actively and is intended for the craftsman.
This field can obtain several absolute total impacts on the position. It is updated by the SQL server by triggers. The trigger is headed for, as soon as entries in the addition table are changed to this position. A position can process thus as desired price additions. The field is used at present not actively and is intended for the craftsman version. An employment could achievements the buy item be accounted for, been.
This price is the actual position total price which is used also in the order forms. The field is computed automatically by the SQL server.