Use this action to view properties for different objects. For each of the objects, you can view the logical unit name, the object key name, and the properties. You cannot enter new objects or change the properties of an object. The objects shown depend on which components are installed. All stated system parameters in the configuration for installed components are viewed.
Object properties can, for example, be different address types to customers and suppliers. Different address types are preinstalled when a new company is entered. Notice that the property named GROUPS is used as a link when, for example, a company is both a customer and a supplier.
Tasks described in this action are to be managed by a system manager or an equivalent person.
The following object properties can be configured for IFS Maintenance:
Object LU | Object Key | Property Name | Property Value | Explanation |
CcConfiguration | SystemParameter | AUTO_COM_TASK_CASE | TRUE or FALSE | The value defines what the status of the case task should be in order to change the status of a handover reference. A more detailed explanation is given below this table. |
CcConfiguration | SystemParameter | CASE_ID_PREFIX |
For example, GLB |
The prefix to be added to the generated sequence number of the case ID. There is no further logic behind the prefix. However, the use of a character part in the case ID (possible to modify before creation of the case) provides a way to build further customizations with logic for parts of the specific case ID. For example GLB for global cases and CUST for customer |
CcConfiguration | SystemParameter | DISABLE_EMPTY_TABS |
TRUE or FALSE |
If set to TRUE, the tabs in the View Customer’s Information window which have no data will be disabled. Since this window has quite a large number of tabs it will make it easier for the end user to see in which tabs there is information available. |
CcConfiguration | SystemParameter | DISPLAY_TIME | TRUE or FALSE | Used to configure whether to display time or not on the Focus Date, Expected Response Date and Task Due Date fields.) Value TRUE will display the date and time. Value FALSE will only display date. |
CcConfiguration | SystemParameter | LANGUAGE_CODE | For example, en |
The default language code for case descriptions and resolutions |
CcConfiguration | SystemParameter | NLS_LANG_VALIDATION |
ON or OFF |
When set to ON a warning message is shown when updating cases written using a different character set than the case was created with. Used to avoid users from overwriting/destroying information written in a different character set. However the validation only shows a warning message. It is still possible to update the record if desired. |
CcConfiguration | SystemParameter | REG_ASSIGNEE_ONLY |
YES or NO |
If set to YES, only the users defined as assignees, (Support Organization Basic Data/Assignee tab with the Assignee check box selected) are allowed to register cases. If they are not, they will get a warning message saying that cases cannot be created by users who are not assignees. |
CcConfiguration | SystemParameter | SERVER_TIME_ZONE | For example, Europe/Stockholm | Any Time Zone Code found in ISO Code Usage/Time Zone tab. Server time zone is used when displaying date/time values in Call Center. |
CcConfiguration | SystemParameter | SHOW_HANDOVER_WO |
TRUE or FALSE |
When using automatic handover
(i.e. when a task has been predefined in basic data as a handover to
work order), this parameter controls the behaviour of the handover
dialog: TRUE – The Handover Work Order dialog box is shown. FALSE – A service request will be created automatically without launching this dialog box. This system parameter makes it possible to create a work order from Call Center with a minimum effort. |
CcConfiguration | SystemParameter | USE_MAPI_FOR_EMAILS |
YES or NO | Used to select whether to use the MAPI or COMMAND_SYS API when sending e-mails from Call Center (EE client) Value YES will use MAPI. MAPI uses the user’s personal mail account and makes it possible to browse for attachments on the desktop instead of only shared file directories. On the other hand, using Mail API, the sender of the mail always becomes the user’s mail address instead of the generic support organization’s e-mail address. |
MaintenanceConfiguration | None (*) | AUTO_AUTH_SIGN_EXP | TRUE or FALSE | Set this parameter to TRUE if you would like all expense transactions to be authorized automatically (the signature in the DEF_AUTH_SIGN property will be used). This parameter is most often set to FALSE. Expense transactions on a work order will then have to be authorized by a user manually. |
MaintenanceConfiguration | None (*) | AUTO_AUTH_SIGN_EXT | TRUE or FALSE | Set this parameter to TRUE if you would like all external transactions to be authorized automatically (the signature in the DEF_AUTH_SIGN property will be used). This parameter is most often set to FALSE. External transactions on a work order will then have to be authorized by a user manually. |
MaintenanceConfiguration | None (*) | AUTO_AUTH_SIGN | TRUE or FALSE | Set this parameter to TRUE if you would like all time transactions to be authorized automatically (the signature in the DEF_AUTH_SIGN property will be used). This parameter is most often set to FALSE. Time transactions on a work order will then have to be authorized by a user manually. |
MaintenanceConfiguration | None (*) | AUTO_AUTH_SIGN_TOOL | TRUE or FALSE | Set this parameter to TRUE if you would like all tools and facilities transactions to be authorized automatically (the signature in the DEF_AUTH_SIGN property will be used). This parameter is most often set to FALSE. Tools and facilities transactions on a work order will then have to be authorized by a user manually. |
MaintenanceConfiguration | None (*) | AUTO_INHERIT_WO_SIGN | TRUE, FALSE or QUERY | This setting determines if
modifications in the work order's Executed By field should affect
existing jobs and operation lines. If this parameter is set to TRUE, all empty jobs and unallocated operation lines always inherit the value in the Executed By field and error messages are sent if the maintenance organization or craft ID is not valid for the signature. It also removes the value in the Executed By field from jobs and operation lines where an executor existed. If this parameter is set to FALSE, the change in the Executed By field does not affect any existing job and operation lines. If this parameter is set to QUERY, a query is sent to the user asking him or her if the modification should affect existing job and operation lines. The user can then select Yes or No (TRUE or FALSE). |
MaintenanceConfiguration | None (*) | CONNECTION_TYPE | EQUIPMENT or VIM | The default connection type used when creating a new work order or service request. Use EQUIPMENT if you mainly create work orders on equipment objects, and VIM if you mainly create work orders on VIM serials. |
MaintenanceConfiguration | None (*) | DEF_AUTH_SIGN | SYS | The default authorizer signature is used when generating work orders from preventive maintenance actions and when using the quick report in work order functions. If AUTO_AUTH_SIGN is set to TRUE, the signature is also used when the system automatically authorizes time transactions. The parameter value must be established before you create a company. When a company is created, a person is also created with this ID. It is recommended that you use the SYS value. |
MaintenanceConfiguration | None (*) | DIS_ALLOC_ON_GANTT | TRUE or FALSE | When this parameter setting is TRUE, only the allocation information on the upper Gantt is displayed. No rescheduling is possible on the upper Gantt. When the parameter setting is FALSE, the planning information on the upper Gantt is displayed and rescheduling is possible. |
MaintenanceConfiguration | None (*) | DIS_PLAN_SCH_WO | TRUE or FALSE | Set this parameter to TRUE if you would like all planning dates on a work order to be automatically calculated when a service contract is added. |
MaintenanceConfiguration | None (*) | ICON_DIRECTORY | For example, C:\IFSAPPL\runtime | The icon directory is the physical path to where icons (bitmap pictures) are kept. The icons can be connected to object groups. If an object group is then connected to an object, the icon is displayed when viewing an object structure in the graphical navigator (in Chart mode). The value should not be null. |
MaintenanceConfiguration | None (*) | INHERIT_OBJECT_ID | TRUE or FALSE | If you set the value to TRUE, when a new child object is created, the parent object ID will automatically be a part of the child object's ID. For example, if the parent object is B1-02, enter 03 as the new child object ID. When the object is saved, the object ID will be automatically set to B1-02-03. (The separator sign used is determined by the OBJECT_LEVEL_SEPARATOR parameter.) If the parameter is set to FALSE, the object ID will either be the value you define as object ID (for functional object), or part number - serial number (for serial object). |
MaintenanceConfiguration | None (*) | ISOLATION_CHANGEDATE | TRUE or FALSE | If you set this parameter to TRUE, you will be allowed to change the reestablishment period for a delimitation order. |
MaintenanceConfiguration | None (*) | MANUAL_EXPENSE | NO BOOKINGS, BOOKING, or NONE | If you set this parameter to NO BOOKINGS, no expense transactions are created, and this is also the value to which to upgrade. If you set this parameter to BOOKING, expense transactions are created. If you set this parameter to NONE, manual expense posting lines will not be allowed. This is the value for fresh installations. |
MaintenanceConfiguration | None (*) | MANUAL_EXTERNAL | NO BOOKINGS, BOOKING, or NONE | If you set this property to NO BOOKINGS, no external transactions are created, and this is also the value to which to upgrade. If you set this property to BOOKING, external transactions are created. If you set this property to NONE, manual external posting lines will not be allowed. This is the value for fresh installations. |
MaintenanceConfiguration | None (*) | MAX_SEARCH_RESULTS | A number | This setting determines the number of records that will be displayed in the Free Time Search window. |
MaintenanceConfiguration | None (*) | OBJECT_LEVEL_SEPARATOR | For example, - | This setting is used when serial object IDs are created to separate the part number from the serial number. It is also used for functional objects if the INHERIT_OBJECT_ID property is set to TRUE. |
MaintenanceConfiguration | None (*) | PARTIAL_WO_ON_GANTT | TRUE or FALSE | This setting determines if the Work Order Scheduling Gantt (the lower Gantt in Resource Allocation Gantt window), should display all work orders and PM actions having a planned date in the queried time interval or only work orders and PM actions that have been planned to be completed within the queried time frame. Set this property to TRUE if you would like to display all work orders and PM actions fully or partially planned within the search interval in lower Gantt. Set this property to FALSE, if you would like to display work orders and PM actions for which both the planned start and planned finish date/time need to be within the queried time interval. |
MaintenanceConfiguration | None (*) | PERIOD_DISTR_METHOD | Proportional, Even or Fixed. | This setting determines what method should be used for period allocations on service contracts. Use Proportional to allocate the amount according to the exact number of days that falls into each period within the date interval. Use Even to allocate the amount evenly between each period within the date interval, regardless of the number of days in each period. Use Mixed to allocate the amount according to the exact number of days that falls into each period which is not completely covered by the date interval, e.g. the first and last period. All periods completely included in the date interval are allocated evenly, regardless of the number of days in each period. |
MaintenanceConfiguration | None (*) | PERMIT_CHANGE_DATE | TRUE or FALSE | Set this property to TRUE if you would like to change the Valid To Date on a permit. This property is set to FALSE, by default, and the Valid To Date on a permit cannot be changed. If this property is set to TRUE, and the status of the permit is Approved or Released, the change is allowed provided that the Valid To Date is later than its previous value. If the change in the Valid To Date is to make it earlier than its previous value, an error message will be displayed informing you that you are not allowed to set an earlier Valid To Date for the particular state of the permit. If the change in the Valid To Date is allowed, the Approved By signature for the permit is set to the signature of the user logged in. |
MaintenanceConfiguration | None (*) | PM_PLAN_HORIZON | For example, 2005 | This setting determines how far ahead a calendar based preventive maintenance action should be generated. The horizon is defined by year. This property should be reviewed annually. |
MaintenanceConfiguration | None (*) | PM_PLAN_OPERATION | TRUE or FALSE | Set this property to TRUE to display preventive maintenance operations in the Free Time Search and Gantt windows. |
MaintenanceConfiguration | None (*) | PREDECESSOR_SEP | For example - | This separator is used in windows where several work order operations' predecessors are handled in the same field. |
MaintenanceConfiguration | None (*) | PROJ_UPDATE_METHOD | ONLINE or BATCH | This setting determines if the project cost should be updated directly (ONLINE) or in the batch (BATCH). |
MaintenanceConfiguration | None (*) | SEARCH_LIMIT_DAYS | A number | This setting determines the default number of days for Latest Date/Time field in the Free Time Search window. |
MaintenanceConfiguration | None (*) | SHOW_DONE_WO | TRUE or FALSE | Set this property to TRUE if work orders with the WorkDone, Reported, Finished and Canceled status should be shown in the Resource Load Graph window. |
MaintenanceConfiguration | None (*) | STRUCTURE_DATE_FROM | For example, 2010-01-01 12:00:00AM | If this property has a value, that date becomes the default value for Date From field for the date interval defined in the search criteria for the Equipment Object Cost/Revenue Analysis window. |
MaintenanceConfiguration | None (*) | STRUCTURE_DATE_TO | For example, 2010-01-02 12:00:00AM | If this property has a value, that date becomes the default value for Date To field for the date interval defined in the search criteria for the Equipment Object Cost/Revenue Analysis window. |
MaintenanceConfiguration | None (*) | STRUCTURE_SEL_TYPE | Exclude Project Cost/Revenue, Include Project Cost/Revenue or Show Project | This setting determines if the project cost should be included in selections for equipment object cost/revenue analysis and becomes the default value for the Selection field defined in the search criteria for the Equipment Object Cost/Revenue Analysis window. If you set this property to Exclude Project Cost/Revenue, the project cost is not included in the analysis. If you set this property to Include Project Cost/Revenue, the project cost is included. If you set this property to Show Project, the project costs of a project selected by you will be included. |
MaintenanceConfiguration | None (*) | SRVCON_DOC_OUTPUT | Any value. For example, SRVINV | If this property has a value
when trying to invoice a service contract the following message is
displayed: "System definition object property SRVCON_DOC_OUTPUT needs to be set to the value of an output type from Document Text Administration/Output Types. Do you want to set-up an Output Type?" Possible answers are Yes or No. If Yes is selected, the invoicing is aborted. If not, the invoicing is done. This message appears only after installation and when a value is set for the property. |
MaintenanceConfiguration | None (*) | SRVCON_PERIOD_ALLOC | TRUE or FALSE | Set this property to TRUE if periodic allocations should be enabled for service contracts. |
MaintenanceConfiguration | None (*) | SRVQUO_DOC_OUTPUT | Any value. For example, SRVQUO | This property needs to have a value in order to create document texts when creating revenue transactions for maintenance orders. On installation, this value will be set to SRVQUO, and the output type will automatically be created in Document Text Administration/Output Types. If for some reason this needs to be changed to another value, first enter the new document output type, and then change the property value to the new document output type. |
MaintenanceConfiguration | None (*) | WEEK_FORMAT | IYIW or IWIY | Used when defining a week to generate PM actions or defining a start week for a PM action. It is recommended to use week format IYIW. |
PartCertificate | DocumentClass | PART_CERT_DOC_CLASS | <Enter the valid document class> | The default document class to use when manually storing approved part certificates in IFS Document Management. |
The following object properties can be configured for the integration between 360 Scheduling and IFS Applications:
Object LU | Object Key | Property Name | Property Value | Explanation |
Sch360Configuration | SystemParameter | ACTWO_DEFAULT_STATE | E.g., Released | Makes it possible to set the lowest status from which work orders can be transferred for scheduling. |
Sch360Configuration | SystemParameter | LOAD_TRANSFER | 360_HTTP or 360_FILE | The default protocol that will be used to transfer all data to the Scheduling Engine. If the protocol is not defined on the scheduling task, this value will be used. |
Sch360Configuration | SystemParameter | CHANGE_TRANSFER | 360_HTTP or 360_FILE | The default protocol that will be used to transfer changes to the Scheduling Engine. If the protocol is not defined on the scheduling task, this value will be used. |
Sch360Configuration | SystemParameter | SCHEDULE_RECEIVER |
|
Makes it possible to define the data that should be included in application messages, i.e., the messages which are produced for the scheduled tasks used to transfer data to the Scheduling Engine. The data entered in the property value for this object parameter will be shown on the detail for each message. |
Sch360Configuration | SystemParameter | SCHEDULE_INFO |
|
Makes it possible to define the data that should be included in application messages, i.e., the messages which are produced for the scheduled tasks used to transfer data to the Scheduling Engine. The data entered in the property value for this object parameter will be shown in the overview for each message. |
Note:
When the AUTO_COM_TASK_CASE system parameter is set to FALSE:
When the AUTO_COM_TASK_CASE system parameter is set to TRUE:
For each component installed, a lot of system parameters have to be stated in the configuration. After installation, all stated system parameters can be viewed in the System Definitions/Object Property window.