The Applications form lists the Isah applications for which you can build a flexible search path. These applications are predefined and cannot be changed.
To define a flexible search path for one of the applications, use the Operational applications form.
Fields
Application |
Explanation |
Form in which the application can be used |
1 |
When using cost-plus invoicing, you can use this application to define a search path for sales prices of hours worked by employees. You have the option to make prices dependent on the time worked. Where appropriate, an hour posting will automatically be split up into components if the components have different rates based on the search path. When using the 'TIME' variable, please make sure to define a contiguous time range: 00:00 - 07:00 07:00 - 20:00 20:00 - 23:59:59 If you were to define the times as follows, the system will revert to a lower search path level from the time of the interruption: 00:00 - 07:00 07:00 - 16:00 (break) 20:00 - 23:59:59 |
|
2 |
When using cost-plus invoicing, you can use this application to define a search path for sales prices of hours during which a machine (or machine group) was employed. |
|
3 |
When using cost-plus invoicing, you can use this application to define a search path for sales prices of equipment pieces. |
|
4 |
When using cost-plus invoicing, you can use this application to define a search path for sales prices of purchased external operations. |
|
5 |
You can use this application in combination with application 6 to define a search path that is the first part of the maintenance model. Use this application to determine the required service types and the frequency with which these types of services are to be performed. The frequency you enter matches the number of times (records) the service type is included in the Preventive maintenance schedule. |
|
6 |
You can use this application in combination with application 5 to define a search path for the preventive maintenance. This application is used to determine the other data entered on the Preventive maintenance form (by record), including part numberart, supplier, and prices. This procedure allows you to specify a different part for each service type/object combination. The part allows you to include different materials and operations for each service type/object combination. By selecting a part with a 'Purchase' order code, and entering a supplier other than '99999', you can specify that you want to outsource the maintenance concerned. The sales line created based on the subsequent preventive maintenance schedule will have a 'Purchase' origin, specifying the relevant supplier. |
|
7 |
You can use this application to define a search path for sums relating to objects included in service contracts that also involve corrective maintenance. |
|
8 |
You can use this application to define a search path for assigning service engineers to failures. |
Calendar form, when you choose the 'Default engineers' or 'Default engineers by district' preset |
9 |
You can use this application to define a search path for equipment sales prices when using cost-plus invoicing. These are the equipment prices per hour. In order to be able to use this functionality, you need to link equipment to operations in the calculations. When the hours are registered, also the equipment hours are registered. |
|
10 |
You can use this application to define a search path for equipment sales prices when using cost-plus invoicing. These are the equipment prices per quantity produced (for example, using molds). In order to be able to use this functionality, you need to link equipment to operations in the calculations. When registering hours, you can enter the quantity produced in the Quantity field. |
|
11 |
You can use this application to define a search path for order discounts based on pricing scales. The output data allow you to choose from the following: - Adding a sales (sub)line containing the part and the price based on a percentage of the total order value (yes/no=yes) - Adding a sales (sub)line containing the part and a fixed price (of the part (yes/no=no)) |
This application is not used yet, but it can be called inside a script. |
This field shows whether the user is required to specify one or more currency codes when he creates an operational application for this application. Examples are applications for which prices can be registered.
This field shows whether the user can register one or more rows of the same data in the operational application.
An example of an application that can have only one row of data is an application in which prices are registered. The reason for this limitation is that in any given situation, only one price can be valid at the same time.
An example of an application that can have multiple rows of data is an application in which a default engineer is registered, as more than one engineer may be qualified for a particular job. Where multiple options are available, the user will have to choose.