Client
Description
This module is used for client management. A client represents the top level of the (DP-technical) organisation of company data and is the object which can be selected by a user when logging in. The information that a client holds is available system-wide.
Functionality
Input window
This window is used to maintain clients. You can select a client by entering the desired number in the Number field and confirming with RETURN. If you want to call up the list window, you can select the menu item "Search".
(If you are logging in for the first time in a completely new ClassiX® application, you have to confirm the login window empty, because no users have been created yet. Next you have to create the client master data, because all further data should be saved client-dependent.
| Menu item | Description |
|---|---|
| Edit | - |
| : Communication | - |
| : : Insert | - |
| : : : Street address | Insert street address |
| : : : P.O. Box address | Insert letterbox address |
| : : : Telephone | Insert phone number |
| : : : Mobile phone | Insert mobile phone number |
| : : : Fax | Inserting a fax number |
| Insert email address | |
| : : : WWW address | Insert website address |
| : : Edit | Edit selected communication object |
| : : Remove | Remove selected communication object |
| : : Contact | Contact selected communication object |
| Print selected communication object | |
| : : Representation | - |
| : : : Detailed | Display communication data in the detailed view |
| : : : List | Display communication data in the list view |
| : : Validity | Set validity |
| : Search terms | - |
| : : Insert | Insert search term |
| : : Remove | Remove selected search term |
| : Structures | Create evaluation groups |
| : Features | - |
| : : Presettable | Creating a presettable feature |
| : : Calculated | Create calculated characteristic |
| : : Conditional | Create conditional characteristic |
| : Operations | Operations of the client |
| : Document settings | Document settings of the client |
| : IV code | |
| : : edit | Instantview code can be defined client-dependent and is made available via the provider "virtual::". Define(Sonderaufschlag) 10% ;
And use it in report columns, documents, formulas and/or conditions with the call (virtual::Special mark-up). |
| : : Compile | Compiles the instantview code of the client. A message about the success or error is displayed. |
| Close | Close window |
| Search | Call up list window |
| Symbol | Description |
|---|---|
 | Create new client |
 | Save changes |
 | Delete client |
 | Print client |
 | Edit company data |
 | Transactions of the client |
 | Document settings of the client |
Master data
| Field | Description |
|---|---|
| Master data | (the fields in italics come from the company master, but can also be maintained here) |
| : Number | Client number |
| : Short name | Client short name |
| : Search terms | Labels that lead to the current data record during the client search |
| : Name | Name of the client |
| Legal form | Legal form |
| : Register | Commercial register number |
| Currency | Local currency (see also foreign currencies) |
| UStIdNr | Value added tax identification number |
| Tax no. | Domestic tax number of the client at the tax office |
| : Participant number | Participant number for the electronic submission of tax returns |
| Communication | Addresses of the client and telecommunication data |
In the client master data, it is important to define the field 'Number' unambiguously in order to functionally guarantee multi-client capability. Number' is the client number used in the system. Furthermore, it is essential to enter the currency (as local currency). Address data and telephone, etc. should also be entered because the program can then refer to these correctly if necessary. Finish each field entry with the 'Tab' key and do not forget to save your entries with 'OK'.
The client window contains several pages/tabs between which you can scroll by clicking on the title of the page. By clicking on e.g. 'Accounting' - or via the key combination 'Alt'-'R' - you can maintain the accounting functions of your company.
You can also edit the data at any time using the menu item 'Edit' and by clicking the right mouse button in the communication area in the lower part of the window. If you have previously selected an entry, you can edit it directly via 'Edit' or by double-clicking.
Sale
| Field | Description | ||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Disposition type text article | - | ||||||||||||||||||||||||||||||||||||||||||||||||
| : Standard setting | This setting controls whether order items with text articles are to be scheduled by default and consequently only then receive the scheduling status. Only order items with a disposition status are automatically procured when the order is technically released. As a rule, the default setting here should be "purchase requisition", as text articles are usually purchased from the supplier. | ||||||||||||||||||||||||||||||||||||||||||||||||
| Orders | |||||||||||||||||||||||||||||||||||||||||||||||||
| Automatic assignment of specification numbers in the order or in the quotation | This option can be used to activate the generation of a number for the specification (variant) when a quotation or order item is released by the sales department, provided that no variant number exists yet. | ||||||||||||||||||||||||||||||||||||||||||||||||
| : Indexing of offer or order items (item text + attributes) | If this option is set, a search term is built up via the item text, the attribute values and via a possibly existing specification number of an offer or order item. This enables the search for offers or orders based on the search term (item search). If this option is set subsequently, the system administrator should be prompted to perform subsequent indexing for the offer or order items already saved in the system (UpdateOrderItemIndex) | ||||||||||||||||||||||||||||||||||||||||||||||||
| Prescribed currency table for sales prices <->Calculation currency | This option makes it mandatory to have a currency table (SALESFX or local definition) if the pricing currency of an order or the currency of a sales price in a foreign currency is used. If a foreign currency occurs and a currency table is not available, an error message will be displayed due to the option set here. If this option is not set, the EUROFX table is automatically used for conversion in the above-mentioned cases if foreign currencies are present, and this can lead to currency fluctuations in the examples given in the documentation (foreign currencies). | ||||||||||||||||||||||||||||||||||||||||||||||||
| Calculate margin without freight and packaging | Setting this option will calculate the margin between the cost of the order and the order value. Freight and packaging costs are not included. | ||||||||||||||||||||||||||||||||||||||||||||||||
| : Log changes in price, quantity, costs and characteristics of quotation and order items | In order to document changes in quotations and orders for items or to make them subsequently checkable, you can activate a function here that doubles changes in quantity, sales price, purchase price and characteristics. You can display these changes via the context menu "Change history" of the item. If items are deleted, the change history of the item is moved up one level, i.e. it is saved in the group, sales set or document header. When the history is called up, all changes to the position and the positions below it are displayed. | ||||||||||||||||||||||||||||||||||||||||||||||||
| Delivery notes | - | ||||||||||||||||||||||||||||||||||||||||||||||||
| : Default quantity type | Determines the quantity which is to be offered as standard delivery quantity for the call-off of delivery notes from orders. | ||||||||||||||||||||||||||||||||||||||||||||||||
| Account assignment (outgoing invoices) | - | ||||||||||||||||||||||||||||||||||||||||||||||||
| : Account assignment | Outgoing invoices are assigned to an account when saved (recommended!) | ||||||||||||||||||||||||||||||||||||||||||||||||
| : Detailed account assignment | Takes into account any different cost elements of the invoice item | ||||||||||||||||||||||||||||||||||||||||||||||||
| Foreign currency exchange rate according to date of invoice | In the case of an invoice/credit note in foreign currency (i.e. not equal to the local currency), the exchange rate is frozen on the basis of the invoice date and not the current date/validity date when the invoice/credit note is registered . However, this is only done if the conversion rate has not already been fixed in advance | ||||||||||||||||||||||||||||||||||||||||||||||||
| : Cost calculation and sales statistics calculation | Set the time when the calculation is to be calculated. Real time - The calculation is performed directly when the document is booked. This method is more time-consuming, but has the advantage that the data is always up to date. Application calendar - performing calculations in the application calendar. The start of the calculation will preferably be carried out at night. | ||||||||||||||||||||||||||||||||||||||||||||||||
| : : Cost calculation | Calculation of the concurrent calculation, the following lines should be present in the application calendar entry when called up:
To speed up the night run, the following indexes should be created: | ||||||||||||||||||||||||||||||||||||||||||||||||
| : : : Offers : : : Orders : : : Invoices | Calculation of sales statistics, the following lines are necessary for the call in the application calendar :
To speed up the night run, the following indexes should be created: | ||||||||||||||||||||||||||||||||||||||||||||||||
| Calculation of marginal costs | - | ||||||||||||||||||||||||||||||||||||||||||||||||
| Activate detailed cost calculation in all order items | |||||||||||||||||||||||||||||||||||||||||||||||||
| Direct actual costs through groups of service providers | For the positions of service provider groups, the actual costs are automatically calculated as "direct costs". No additional time or stock bookings have to be entered. | ||||||||||||||||||||||||||||||||||||||||||||||||
| Activate for the following order types | see marginal cost calculation |
Purchasing
| Field | Description | ||||||
|---|---|---|---|---|---|---|---|
| Account assignment (incoming invoices) | The cost elements to be specified here are used for the initial account assignment of incoming invoices. | ||||||
| Account for ancillary delivery costs | Default cost element that is proposed for the account assignment of delivery costs for an incoming invoice. This can also be stored conditionally. | ||||||
| : Account text article | If a text article is used in a purchase order item, this cost element is proposed for initial account assignment in the incoming invoice. This can also be stored conditionally. | ||||||
| Foreign currency exchange rate according to date of invoice | In the case of an incoming invoice/credit note in a foreign currency (i.e. not equal to the local currency), the conversion rate is determined according to the invoice date and not the current date/validity date when the currency is changed in the incoming invoice mask | ||||||
| Release rule (incoming invoices) | The release rule determines up to which value an incoming invoice deviating from the purchase order is automatically released by the system. | ||||||
| : Value deviation | If the difference between the actual net value of the incoming invoice and the expected (ordered) net value is greater than this amount, the items of the incoming invoice must be checked. (see reasons for checking) | ||||||
| Percentage deviation | If the actual net value of the incoming invoice differs from the expected net value by more than the percentage specified here, the items of the incoming invoice must be checked. (see reasons for checking) | ||||||
| : Value deviation (position) | If the value of the difference between the expected (ordered) and the actual value of an A/P invoice line item is greater than the value specified in this field, the A/P invoice line item must be checked. (see reasons for checking) | ||||||
| Percentage deviation (position) | If the difference between the actual value of an incoming invoice item and the expected value differs by more than the percentage specified here, the item of the incoming invoice must be checked. (see reasons for checking) | ||||||
| : Recognition rule | Via the recognition rule, incoming invoices can be accepted (released) directly, even if they should have been checked on the basis of the normal release rules. For example, all incoming invoices with a net value of less than 100 EUR could always be released directly, as checking all these invoices would be too time-consuming. In this case, the formula to be entered would be as follows: If the rule applies to an incoming invoice, a checkbox "Accept invoice" appears in the incoming invoice mask, which is checked by default. If the invoice is to be checked despite the applicable recognition rule, this checkbox must be removed. | ||||||
| Signature rule | |||||||
| Activated | If this checkbox is set, the orders must pass the signature regulation. The minimum requirement is that the business process "PURCHASE_SIGNATURE" has been imorted. | If this checkbox is set, the orders must run through the signature regulation. The minimum requirement is that the business process "PURCHASE_SIGNATURE" has been imported and users for the 1st and 2nd signature have been stored.||||||
| Without signature regulation up to a yield of | Amount up to which an order can be created without signature regulation. As soon as the amount is exceeded, the order is activated for the signature regulation, i.e. if the value of an order exceeds the value after the order confirmation, the signature regulation is activated! | Amount up to which an order can be created without a signature rule. As soon as the amount is exceeded, the order must go through the signature regulation. If the value of an order exceeds the value after the order confirmation, the signature rule is also activated!||||||
| Permitted percentage deviation | After the orders have been digitally signed, the value may only be higher by this percentage than the original order value! | ||||||
| : Print only signed | Only orders that have already been signed can be printed or issued! | ||||||
| : for 1st/2nd signature | Users that may be used in the signature regime. You can enter a different list of users for each signature. Using the control, you can define a table for the users used for each signature. You can define a table for the users to be used for each signature via the regulation. If no regulation is stored, the users must be selected when entering the order.Examples of the conditions :
|
Logistics
| Field | Description |
|---|---|
| Stock statistics | - |
| : Valuation of stock receipts | Determine with which value the goods receipts for the warehouse are valued. This determines the basis with which the current average price is calculated or how the value of putaways is determined. The warehouse value is calculated with the average price in the warehouse statistics at the end of the month. ATTENTION ! |
| : : Average price according to roll price | The average price is based on the standard price of the corresponding partial roll |
| : : Average price according to document price | The average price is based on the price on the receipt. This setting is the default setting in the system, even if you had not previously selected either of the two options (see above "by roll price"). |
| Date of the first storage statistics | Start date for calculations of stock statistics. No stock statistics can be created before this date. Various options can be set for this first stock statistic, see |
| Automatic deployment | - |
| : Goods receipt | |
| : : Merchandise | When a goods receipt is posted for a purchase order relating to an order item, it immediately changes to the status "Ready" and does not need to be specially staged via staging from goods receipt |
| : : for production | When a goods receipt is posted for a production-related purchase order, it immediately changes to the status "Ready" and does not need to be staged separately via staging from goods receipt |
| : :Goods for cost centre | When a goods receipt is posted for a cost centre-related purchase order, it immediately changes to the status "Ready" and does not need to be made available via the staging from goods receipt |
| : Manufacturing | |
| : : : Order parts / Level 0 | If a production order is reported ready on level 0 (order item part), the production order immediately changes to the status "Ready" and does not need to be provided via the provision from production |
| : : Sub-assemblies / level > 0 | If a production order of sub-assemblies at level > 0 (not order item part!) is reported ready, the production order immediately changes to the status "Staged" and does not need to be staged separately via staging from production. |
| : : Kanban parts / level > 0 | If the stock reservations are created in the part request, the kanban parts do not get the status "stock reservation" but directly the status "ready". These parts do not appear in the staging list for the warehouse anymore. | If the stock reservations are created in the parts request, the Kanban parts do not receive the status "Stock reservation" but directly the status "Provided". As a result, they no longer appear in the staging list for the warehouse.
| Storage reservations | - |
| In case of reduced stock removal quantities - create remaining quantities as new document | If this option is set, a new retrieval document with all remaining quantities is automatically created after a query for retrievals whose order requirement quantity is greater than the quantities stored on the retrieval document. This document is not posted and serves as a reminder that there is still more material to be removed for this order. It is therefore to be understood as a missing parts list. |
| : System notification when outstanding stockouts are covered | If this option is set, a system message is sent if, according to the MRP account, there is a waiting requirement that could now be covered. In detail, this means that the system message is sent when...
|
| Capacity planning | - |
| : Workstations / Production | - |
| : : Bypass bottlenecks automatically | When scheduling work sequences, the remaining capacity on the required workstations is checked against the required capacity. If there is not enough capacity, the scheduling is postponed. The option "scheduling without idle times" or also called "gapless scheduling" is then important for postponing. ATTENTION: The check mark "Check / report bottlenecks" must also be set if this option is desired! |
| : : : Check / report bottlenecks | Bottlenecks on resources will be examined. A message is issued if a bottleneck is found during scheduling. If this bottleneck is to be bypassed automatically, the check mark "Bypass bottlenecks automatically" must also be set |
| : : Scheduling without waiting times | If a workstation has insufficient free capacity in the entire work process, the complete work at all workstations is shifted further into the future until all workstations have sufficient capacity for the planned work. If this checkbox is not ticked, in the event of a bottleneck at a workstation, the system simply waits for sufficient available capacity and still starts production on the desired start date. This can result in idle times between the individual workstations. |
| : Employees / Service | - |
| : : Daily employee planning | In capacity planning, dates of service provider groups and work orders are posted to employee accounts on a daily basis. If the checkbox is not set, the work is only posted to the employee's worklist. |
| : : Avoiding bottlenecks by postponing deadlines | If an employee has insufficient capacity for a project to be scheduled, the project date is automatically postponed until the work can be carried out. If this option is not set, the workload of an employee can be 200%. |
| : Scheduling | Defines whether scheduling should be automatic (graphical or non-graphical) or manual when generating part requests. Sets the default whether the scheduling should be done automatically (graphically or non-graphically) or manually when creating the parts requests. This setting sets the options in stock orders, preliminary requirements and parts planning. This setting sets the options in warehouse orders, preliminary requirements and parts scheduling. |
| : : automatic (graphic) | The scheduling of the creation of part requirements is carried out using the XGantt tool from Varchart, which is subject to a fee, in a graphic representation of the concatenation of all deadlines. | Scheduling when creating part requirements is done via the XGantt tool from the company Varchart, which is subject to a charge, in a graphical representation of the concatenation of all dates.
| : : automatic (not graphical) | The scheduling of the creation of part requirements is done automatically, without graphical display. No further licence is required. | Scheduling during the creation of part requests is done automatically, without graphic display. No further licence is required.
| : : manual | The scheduling of the creation of part requirements does not take place at all, but must be called up by the user via the menu of the part requirement mask. | Scheduling when creating parts requests does not take place at all, but must be called up by the user via the menu of the parts request screen.
| : Common variant sub-accounts | - |
| : : Activate possibility in the parts master | If this option is set, it can be determined on the processing mask of the variant parts per variant part whether the lower parts share the warehouse account and/or the MRP account of the variant part and therefore do not have their own accounts. |
| : Manufacturing | |
| : : : System notification when a production order level 0 with a sales order as predecessor is provided | A system message is created with the commercial clerk of the sales order as recipient. This informs the sales order clerk who can then create the shipping documents, for example. If no business administrator has been created in the order, no system message is created. |
| : : : Provision of a production order only possible if previous stage has been provided | The provision and storage of a production order is only possible if all production orders of the directly preceding production stage are provided. |
Accounting
| Field | Description |
|---|---|
| : Accounts | |
| : : : Basic chart of accounts (IKR, SKRxx, ...) | For example, IKR (for industrial charts of accounts) or SKR03 (for standard chart of accounts 03) can be entered as the basic chart of accounts. This information is required for the provision of electronic data within the framework of the GDPdU (IDEA) standard data exchange |
| : : Method of determining the profit | The method of determining the profit depends on the accounting obligation and the respective type of profit income. This information is required for the provision of electronic data in the context of the GDPdU (IDEA) standard data exchange |
| : : Standard accounts Discount | In this area you can define to which accounts tax-free cash discounts are booked. This means you do not need to create a tax rate for 0%, which is usually used to control these postings. The account allocations can only be made after they have been created. These standard settings can be manually overwritten later in the payment settings if required. |
| : : : Discount expense (without VAT) | Cash discount expense account for tax (key) unrestricted debit-side open items |
| : : : Discount income (without VAT) | Cash discount on income account for tax (key) unrestricted creditor open items |
| : : Standard accounts Currency differences | In this section, you can define the accounts to which any currency differences that may occur are to be posted. The account allocations can only be made after these have also been created. These accounts are also used for the automatic account assignment of clearing entries during the OP clearing, provided that open items were posted with foreign currencies. |
| : : : Exchange rate losses | Expense account for exchange losses |
| : : : Foreign exchange gains | Income account for currency gains |
| : Cost accounting | - |
| : : Cost type accounting | If this option is selected, costs are only entered and posted indirectly via cost element accounts and no longer directly via P&L G/L accounts | If this option is selected, costs are only entered and posted indirectly via cost type accounts and no longer directly via P&L G/L accounts.
| : : Cost centre accounting | If this option is selected, a cost centre can always be entered in the masks for expenses or revenues (depending on whether a cost element allows this or whether it is mandatory) |
| : : Standard cost centre Invoices | Specification of a standard cost centre, which is offered by default as main cost centre in the header of all outgoing and incoming invoices. This is also automatically preselected, e.g. during the payment run of the financial accounting as clearing cost centre for cash discount deduction. |
| : : Standard cost centre warehouse | Standard cost centre for items from internal orders, requisitions, purchase orders and/or purchase invoices intended for the warehouse |
| : : Billing cost type warehouse | For storage and retrieval for cost centres, this allocation cost element is automatically added to the corresponding postings. This enables you to determine these costs fairly for cost centres (and allocation cost elements) without influencing the profit and loss account. The profit and loss account is posted via outgoing invoices (revenue accounts), incoming invoices (expense accounts) and inventory changes. The evaluation of these costs is carried out by means of the cost centre evaluation per organisation chart. |
| : : Cost unit accounting | With this option the account assignment to cost objects can be activated. |
| : : Automatically use existing cost objects of the partner in the offer and order | This option can be selected if the option "Cost unit accounting" has been activated. This controls that when an offer or order is created, a new cost unit is not automatically created and assigned to the document. Instead, an existing cost object of the customer, interested party or operator role is taken over. The consequence and also the reason for this option is that only one cost unit is used for each partner and thus it is possible, among other things, to carry out a cost evaluation for a customer via the financial accounting. In the offer/order, the cost unit is determined in the following order: |
| : Booking screen | - |
| : : Delivery date for incoming invoices in booking mask | Allows you to enter a delivery date in the booking mask. The due date of an incoming invoice is then based on the most recent date from the invoice date, invoice receipt date or delivery date |
| : : Activate company codes | If this identifier is set, a company code can be specified in the booking mask for each individual booking. A cash register, customer invoice/credit memo and vendor invoice/credit memo can also be assigned to a company code | If this identifier is set, a company code can be specified in the booking mask for each individual booking. A company code can also be assigned to a cash register, customer invoice/credit note and supplier invoice/credit note.
| : : Control key constraint | If this identifier is set, a control key must always be entered for a posting where a control key may occur |
| : : Permitted tax account assignment deviation | In the case of incoming invoices, rounding differences may result in differences between the assigned and expected tax value. The amount of the permitted deviation can be defined here. |
| : Bank Clearing | - |
| : : Path for DTAUS + SEPA format | Specification of the standard path for the output of files in the German DTAUS format for domestic payments or in the European SEPA format for payments in the euro area |
| : : Path for DTAZV + MT101 format | Specification of the standard path for the output of files in German DTAZV format for foreign payments or in international S.W.I.F.T. MT101 format for payments in any currency |
| : : Path for bank statement files (MT940) | Path preset for reading bank statements in S.W.I.F.T. MT940 format |
| : : Archive of bank statement files (MT940) | Specifies the path to which bank statement files are moved after successful import. If the entry is missing here, the file is not moved |
| : : : Foreign exchange rate according to date of bank statement | When posting a bank statement in the financial accounting, the exchange rate is determined according to the date of the bank statement and not the current date/validity date |
| : Archiving associated documents | - |
| : : Filing directory | When posting a FiBu document with an assigned document, the document is moved to the directory defined here. The directory specification must end with a backslash. (e.g.: "Y:\classix\Archive-FiBu-Documents\" ) |
| : : Move archived documents to subfolders (year-month) | If the storage directory is set and this option is selected, subfolders in the format "YYYY-MM" are created on the basis of the document date of the financial accounting entry and the document is moved to these subfolders. |
| : : Incoming directory | The documents to be assigned to a financial accounting entry can be stored in the directory defined here. This has the advantage that the assignment (the file selection) is easier and the number of documents still to be assigned is displayed in the booking mask. |
Sets
| Field | Description |
|---|---|
| : Surcharge calculation | The specifications for overhead calculation determine where the overheads for material or labour costs are stored in the system. Global overhead costs (GMK) surcharges are stored directly at the client(data fields: material.primeOverheadRate and wages.primeOverheadRate), wage overheads can be stored either globally or at the cost centres. |
| : : Material GMK global | |
| : : Lohn GMK global | The global surcharge rates stored on the client's system are used to calculate the order costs. This applies, for example, to the wage overhead rate when calculating the BDE costs. |
| : : : Wage GMK cost centres related | In order cost calculation, the overhead rates stored at the cost centres are used. Thus, when calculating the PDC costs, the overhead rate stored at the cost centre of the workstation or machine is used. |
| : Sentences | In general, global data/cost records can be stored here, e.g.
As a rule, these global data/cost records should be newly created as local attributes in the client, e.g. to be able to define a time-limited validity of such a record. To do this, right-click on the attribute. A new window will open. The toolbar of the new window contains the validity symbol. Clicking on this symbol opens the validity window in which the validity can be set. |
| Annexes | - |
| : Reminder value | Indication of whether a reminder value should be offered in Asset Accounting. If the value here is zero, no reminder value can be entered in Asset Accounting |
| : formulary | Reference to a table of characteristics, in which certain calculations are stored. As a rule, this table is always available internally, e.g. to carry out generally valid conversions or to determine values from other data. If a collection of formulas is stored, you can navigate to it with the right mouse button |
WMS data
| Field | Description |
|---|---|
| Control system | - |
| : Supply depot | Listing of replenishment stocks. |
| Picklist sorting (priorities) ascending | |
| : Output the entire description when picking | |
| : Create goods receipts and issues during stock changes (scanner). | |
| : Prevent stock transfer of allocated individual parts | |
| SAP B1 form export directory | |
| SAP B1 form delivery note printing | |
| SAP B1 form invoice printing | |
| SAP data transfer | - | Definition of retrieval intervals for upload and download and their number of attempts (upload).
| : Upload Trigger Delivery Notes | |
| : Upload Trigger Outgoing invoices | |
| : Upload Trigger Goods Receipts | |
| : Upload Trigger Stock Transfers | |
| : Upload trigger goods receipts (stock increase). | |
| : Upload trigger goods issues (stock decrease). | |
| : Upload Trigger Inventories | |
| : Upload Trigger Picklists | |
| : Upload Trigger orders | |
| : Upload Trigger Goods Receipts | |
| : Upload Trigger Article | |
| : Upload Trigger Basic Data | |
| : Number of attempts Upload |
SAP® and SAP Business One® are trademarks or registered trademarks of SAP SE in Germany and other countries.
System
| Field | Description |
|---|---|
| Service provider | - |
| : ClassiX supplier | The supplier role of the ClassiX system provider can be stored here |
| Voice control | - |
| No. of languages | The number of languages can be limited for multilingual fields. If the descriptions, cover letters, etc. are only maintained in two languages (e.g. German and English), this can be used to prevent someone from getting lost in the third language (French). German and English are implemented as standard operating languages, further operating languages are maintained using the Text Literal Browser (AppsWH and System) |
| Preset language | The language that is preset is displayed here. The language is determined and set from the location-specific data, the location of the user. | The language is displayed here, which is preset. The language is determined and set from the location-specific data, the location of the user.
| : Fallback language | This sets the language to be used by this machine when a text is not available in the currently set language. (0 corresponds to German, 1 corresponds to English) |
| Directories | - |
| : General network drives | ClassiX refers to documents via document references. In order for all ClassiX users to be able to access these documents from ClassiX, they must be located in the intranet, in the ClassiX database or on a network drive accessible to all users. To distinguish the network drives from the local drives ("C:" etc.), they must be defined here in the client. The individual letters (as drive designations) must be separated by commas. If only one specific folder is shared on a network drive, the entire path (e.g.: "Y:\Sharing_Documents") can be entered here. (Please pay attention to upper and lower case) |
| : Price lists directory | |
| : Documents Directory | When creating document references with a reference to a file (directly or during Outlook import), this directory is proposed as default. |
| : Save emails in subfolder month | If an e-mail is to be imported as a document reference and saved in the "Document root", a monthly subfolder is created in the "Document root" on the basis of the date of the e-mail and this folder is suggested as the storage location. If a new Word document is created directly in the associations dialogue, a monthly subfolder is created in the "root directory for documents" based on the date of the object (if available) or the current date and the document is saved in it. This option only applies to the saving of emails and email attachments or new Word documents and a defined "root directory for documents". |
| : Data Directory | With interfaces or other processes, files are created for printing and export. These are written into a subdirectory of the data directory |
| : Save emails in subfolder month | If the files in the subdirectory are to be combined per month, this option can be selected! |
| Communication settings | - |
| : Fax identification | If you want to send a fax directly from a fax number, you can set the identification required for the fax machine here. If nothing is entered here, the word "FAX:" is placed before the fax number (e.g. " FAX:+49402056346 " |
| : Map URL | |
| SMTP server | The name by which the SMTP server in the network can be addressed is entered here. If emails can be sent anonymously via the SMTP server, it is sufficient to enter the server name. Via the button Also via the button |
| Interval checks | The interval checks and start scripts are inherited from top to bottom in the hierarchy. This means: If these settings are set in the client, they are valid for all users until the user's cost centre, a higher-level cost centre or the user himself has changed these settings on the corresponding editing masks. |
| : Check resubmissions | This allows you to check activity documents with the activity type "planning", which are created with a resubmission date with or without time. The resubmissions of the logged-in user can be queried in intervals. Messages which have an earlier or current date for resubmission and the status "Read" is not set are then automatically displayed on the screen. The setting is only used in the user if the checkbox "inherited" is selected in the user and the account! | This enables the checking of transaction documents with the transaction type "planning", which are created with a resubmission date with or without time. The resubmissions of the logged-in user can be queried on an interval-controlled basis. Messages that have an earlier or current resubmission date and the status "Read" is not set are then automatically displayed on the screen. The setting is only used in the user if the checkbox "Inherited" is selected in the user and the cost centre!
| : Interval | Time interval, at which intervals it should be checked whether resubmissions exist. |
| : Changeable by user | The user settings allow the user to change the values for the interval check continuously. |
| : Check system messages | The system messages of the logged-in user can be retrieved at intervals. If there are messages that have not yet been moved to the "Read" status or with a later date for resubmission, they are automatically displayed on the screen. This setting is only used if the check box "inherited" is selected in the user! |
| : Interval | Time interval at which the system checks whether system messages are available. |
| : Changeable by user | The user settings allow the user to change the values for the interval check continuously. |
| Start script | A start script that is to be executed once as soon as the user has logged in: InstantView® script that runs automatically immediately after login. |
| : Testing | The start script is called for testing purposes |
| : Changeable by user | The user settings allow the user to change the values for the interval check continuously. |
you can configure the logon to the SMTP server (refer to The interval checks and start scripts are inherited from top to bottom in the hierarchy. This means: If these settings are set in the client, they are valid for all users until the user's cost centre, a higher-level cost centre or the user himself has changed these settings on the corresponding editing masks.
On this tab you can enter your ClassiX® partner under "service provider". This data is used for direct programme support. Under "Language control" the handling of the multilingual functions of ClassiX® can be influenced, e.g. the default language can be changed here. Under "Directories" standard directories can be set, e.g. for document management. Under "Communication" the own fax identification is entered, for integration with a fax gateway. The multilingual field Map URL contains the internet address of a map service provider to display maps to addresses from ClassiX®. The URL can be arbitrary, when called up the following tokens are replaced with corresponding data: %CITY% for the city, %STREET% for street and house number, %ZIP% for postcode and %COUNTRY% for country.
Security
| Field | Description | ||||
|---|---|---|---|---|---|
| Password | The rules for setting passwords are only checked if the user changes his password via his personal settings. A free password can be set at any time via the editing mask of the user. Thus, the administrator can also assign simple passwords when setting new or resetting passwords. | ||||
| Specify minimum password length | The minimum length of the user's password is prescribed. | ||||
| : Specify a capital letter | User passwords must contain at least one capital letter. | ||||
| : Specify a lower case letter | Users' passwords must contain at least one lower case letter. | ||||
| : prescribe a number | Users' passwords must contain at least one number. | ||||
| : Require a special character | User passwords must contain at least one special character (characters other than A-Z and a-z). | ||||
| Can only be changed once a day | A user's password can only be changed once a day. | ||||
| : Passwords must be different | For a password change, the number of the last passwords from which the new password must differ can be entered here. It is fixed that a new password must be different from the last password, therefore a number entered here must be at least 2. | ||||
| : New password can be requested by e-mail from the user | A user can request a new password, which will be sent to him/her by e-mail from the machine. If the "NEW_PASSWORD_MAIL" form is not available, the machine uses a fixed format for the mail. An example of the form is in our sample database or you can ask our support. | ||||
| : Validity period of the password | Specifies the validity of a password in days. | ||||
| Registration | |||||
| Number of failed attempts to temporarily block a user ID | how often an incorrect password can be entered for a user ID Only when these values are set will the number of failed login attempts be recorded and processed. | ||||
| Temporary blocking time | After the above number of failed attempts is reached, a user ID lockout time can be specified in minutes. | If the document "NEW_PASSWORD_MAIL" is not present, the system uses a fixed format for the mail. An example of the document is in our example database or you can ask the support.||||
| Maximum number of temporary suspensions of a user ID | Specifies how often a user ID can be temporarily blocked by entering the wrong password until the user ID is permanently blocked. | ||||
| Automatic logoff after | Specifies the time in minutes after which a user is automatically logged off when the machine is not used. | ||||
| Close dialogues automatically after | If the value = zero or deactivated, the value from the automatic logoff is used. If this is also zero, dialogues are displayed indefinitely. Dialogues are error messages, file selection, questions etc. | ||||
| Maximum number of sessions per user |
|
Database
| Field | Description |
|---|---|
| DB layer | Specification for the physical differentiation of clients at database level (file level) |
| Domain Declarations | Here, objects within the database can be divided into domains using domain declarations. |
Once you have completed all the fields, you can use the 'Company' button to enter more company-related data, such as bank details on the 'Additional Data' tab of the new window. You will notice that overlapping information does not have to be re-entered because in ClassiX® all data is logically linked.
| button | Description |
|---|---|
| OK | Changes to the client are saved. If no changes have been made, the button is locked. |
| New | The input window is cleared. |
| Delete | The displayed client is deleted. |
| Close | The window is closed without saving changes. If you want to save the changes, you must press the "OK" button. |
List window
Serves to list the clients.
| Symbol | Description |
|---|---|
| Create new client |
 | Edit client |
| Delete client |
| Print client list |
 | Searchfor characteristics |
 | Search for objects that do not contain any of the characteristics to be specified (regardless of the value set) |
| Operations of the client | Transactions of the client
| Document settings of the client |
| button | Description |
|---|---|
| Edit | The current client is displayed in the input window. |
| New | An empty input window opens. |
| Delete | The selected client is deleted. |
| Close | The window is closed. |
Selection window
This window is used to select a client.
| button | Description |
|---|---|
| OK | The selected client is taken over. |
| Close | The selection is cancelled. |
SMTP settings
Use this window to configure access to the SMTP server.
| Field | Description |
|---|---|
| SMTP uses SSL to send messages | This check box must be selected if you want to log in to the SMTP server using a secure connection. (The setting of the option must depend on the settings set on the SMTP server). |
| Authentication | Here you can define whether ClassiX can send anonymous emails via the SMTP server (cdoAnonymous). In both other cases (cdoBasic and cdoNTLM) an authentication (login) on the server is required. |
| Free sender address allowed | If authentication is required, it may be that you can only send an e-mail using the authenticated address (user name then corresponds to the address). If this is not the case and any sender address may be specified via the authenticated SMTP account, this option must be set. |
| User+Password | If an authentication on the TAPI server must take place in order to send an e-mail, the accounts can be defined here. With these accounts ClassiX can log on to the TAPI server and send emails. If several accounts are created, the account can be selected in the print mask for sending e-mails. (In this case the account also corresponds to the sender address of the email). |
| button | Description |
|---|---|
| OK | The changes are saved. |
| Close | The window is closed without saving the changes. |
Related topics
Technical documentation
Overview
Client basic module
Module name
cyber.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| ADDRESS_CHANGED | Address object | Address has been changed | |
| ADDRESS_CREATED | Address object | Address was created | |
| ADDRESS_DELETED | Address object | Address was deleted | |
| CITY_BY_ZIP_CODE_SELECTED | |||
| CYBER_ENTERPRISE_CHANGED | Client object | Client has been changed | |
| CYBER_ENTERPRISE_CREATED | Client object | Client was created | |
| CYBER_ENTERPRISE_DELETED | Client object | Client was deleted |
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
| ADDRESS_DELETED | Address object | Address was deleted | |
| ASK_YES_NO | (Multilingual) character string | Question-dialogue | |
| DELETE_ACCESS | Communication object | Communication object was deleted | |
| EDIT_CYBER_ENTERPRISE | NULL or client object | Call up input window for client | Client editing module |
| EDIT_PO_BOX_ADDRESS | NULL or letterbox object | Open the input window for letterbox addresses | |
| EDIT_STREET_ADDRESS | NULL or street object | Open the input window for street addresses | |
| EDIT_VALIDITY_BY_DATE | Object | Edit the validity of the object | |
| SELECT_CITY_BY_ZIP_CODE | NULL or Collection postcode objects | Select postcode |
Client editing module
Module name
cyberedt.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| ADDRESS_CHANGED | Address object | Address has been changed | |
| ADDRESS_CREATED | Address object | Address was created | |
| ADDRESS_DELETED | Address object | Address was deleted | |
| CITY_BY_ZIP_CODE_SELECTED | |||
| CONDITION_SELECTED | |||
| CYBER_ENTERPRISE_CHANGED | Client object | Client has been changed | |
| CYBER_ENTERPRISE_CREATED | Client object | Client was created | |
| CYBER_ENTERPRISE_DELETED | Client object | Client was deleted | |
| EDIT_CYBER_ENTERPRISE | NULL or client object | Call up input window for client | |
| LIST_CYBER_ENTERPRISE | Collection client objects or NULL | Call up list window for client | |
| LOAD_CYBER_ENTERPRISE | Importing a client | ||
| SELECT_DEFAULT_TRANSACTION | |||
| TEXT_CONDITION_SELECTED |
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
| ADDRESS_DELETED | |||
| ASK_YES_NO | |||
| CYBER_ENTERPRISE_CHANGED | Client object | Client was changed | |
| CYBER_ENTERPRISE_CREATED | Client object | Client was created | |
| CYBER_ENTERPRISE_DELETED | Client object | Client was deleted | |
| CYBER_ENTERPRISE_SELECTED | Client object, recipient | Client was selected | |
| DEFAULT_TRANSACTION_SELECTED | |||
| DELETE_ACCESS | |||
| DELETE_CYBER_ENTERPRISE | |||
| EDIT_CYBER_ENTERPRISE | NULL or client object | Call up input window for client | Client editing module |
| EDIT_PO_BOX_ADDRESS | |||
| EDIT_PROCEEDINGS | |||
| EDIT_STREET_ADDRESS | |||
| EDIT_TEXT_CONDITION | |||
| EDIT_VALIDITY_BY_DATE | |||
| LIST_CYBER_ENTERPRISE | Call up list window for client | Client editing module | |
| LIST_STRUCTURE | |||
| SELECT_CITY_BY_ZIP_CODE | |||
| SELECT_SALES_CONDITION | |||
| SELECT_TEXT_CONDITION | |||
| SHOW_PREVIEW |
Client selection module
Module name
cybersel.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| ADDRESS_CHANGED | Address object | Address has been changed | |
| ADDRESS_CREATED | Address object | Address was created | |
| ADDRESS_DELETED | Address object | Address was deleted | |
| CITY_BY_ZIP_CODE_SELECTED | |||
| CYBER_ENTERPRISE_CHANGED | Client object | Client has been changed | |
| CYBER_ENTERPRISE_CREATED | Client object | Client was created | |
| CYBER_ENTERPRISE_DELETED | Client object | Client was deleted | |
| SELECT_CYBER_ENTERPRISE | Collection client objects or NULL, recipient of the response | Call up selection window for client |
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
| ADDRESS_DELETED | |||
| ASK_YES_NO | |||
| CYBER_ENTERPRISE_SELECTED | Client object, recipient | Client was selected | |
| DELETE_ACCESS | |||
| EDIT_CYBER_ENTERPRISE | NULL or client object | Call up input window for client | Client editing module |
| EDIT_PO_BOX_ADDRESS | |||
| EDIT_STREET_ADDRESS | |||
| EDIT_VALIDITY_BY_DATE | |||
| SELECT_CITY_BY_ZIP_CODE |
;){kind=link}
;){kind=link}
;){kind=link}