Verify or Adjust Default Object Properties

Explanation

This activity is used to verify or adjust object properties. Object properties are pre-defined settings that are imperative for the installation of Fleet and Asset Management. It is recommended to examine property values after the installation is complete and change the values if necessary. If validations are to be performed for a given object property value, select the Validations Enabled option and enter the relevant validation method. Note: The parameter list of the method that is to be called for validation must include the following:

Following is a list of all available properties in Fleet and Asset Management. 

Parameter Description Legal Values
DEFAULT_OWNER The default owner code to use,
  • when generating serial numbers for a structure that contains a vehicle part number.
  • (If IFS/Complex Assembly MRO is used) when creating vehicles due to DPF (different part found) Handling.
All legal owners defined in IFS/Enterprise are valid. The default value is 000.
UPD_VEH_COND_CODE This controls the automatic update of the condition code of a vehicle, when a maintenance event is distributed on a serial. TRUE (default value)
FALSE
ORDER_NO_PREFIX A prefix for the order number of a maintenance order. A combination of any two characters is valid. The default value is MO.
EVENT_DURATION_HOURS The default duration (in hours) of the maintenance event. This is used to display the default event date or time when an event is distributed. Any positive number is valid. The default value is 4.
EVENT_WARNING_DAYS The number of days a maintenance event is pending before it is considered old. A warning is displayed when an operational logging is performed. Any positive number is valid. The default value is 10.
OPER_EVENT_DELAY The number of days an operational event is to be retained after its completion. After this date, the operational event is removed by a batch job. Any positive number is valid. The default value is 14.
PLANNED_EVENT_WARN The warning percentage to use when a maintenance event is manually changed in PlannedEvent. Any number between 0 and 100 is valid. The default value is 50.
ERROR_LOG_CLEANUP The number of days before old items in the error log are to be removed. Any positive number is valid. The default value is 5.
MAINT_PLAN_HORIZON The horizon (in years) to allow maintenance planning on a maintenance plan. This is used to validate intervals in the maintenance plan. Any positive number is valid. The default value is 100.
FUNCTION_LEVEL_INSTR The number of levels to use in a function breakdown when a task card is registered for a serial that is not a vehicle. Any number between 0 and 3 is valid. The default value is 1.
FUNC_LEVEL_INSTR_VEH The number of levels to use in a function breakdown when a task card is registered for a vehicle. Any number between 0 and 3 is valid. The default value is 1.
TASK_CALC_EVENTS The number of events to create per maintenance code for a due calculation.  FIRST
SEVERAL (default value)
TASK_CALC_HORIZON The horizon (in years) for the planned events from due calculation. This requires the value SEVERAL in the TASK_CALC_EVENTS parameter to have an effect. Any positive number is valid. The default value is 5.
MIN_CONFIG_SETTING The default value for minimum configuration when an entry is created in the serial structure template. TRUE (default value)
FALSE
OPER_LOG_SEV_EVENTS Is it possible to perform an operational logging on an operational event more than once? No Requirements (default value)
Warning
Not Allowed
OPER_LOG_MAND_EVENTS Is it possible to perform an operational logging without entering an operational event? No Requirements (default value)
Warning
Mandatory
DEFAULT_LOCATION The default location code to use,
  • when serial numbers are generated for top serials that are not vehicle parts,
  • when serial numbers are generated for vehicle parts where a Vehicle ID is optional,
  • (If IFS/Complex MRO is used) when performing disassembly or assembly of an overhaul object structure during an MRO shop visit. Here, the default location is used for the structure transactions that take place through a background job.
All legal location codes are valid. The default value is 000.
FUNC_LEVEL_REPAIR The required number of levels to use in a function breakdown when a fault repair (finish maintenance event) is reported. Any number between 0 and 3 is valid. The default value is 1.
FROM_TO_SERIAL_RANGE The separator to use when assigning a serial number range (from - to) for a modification. Any character is valid. Note: The character cannot be identical to the other property values for the SERIAL_RANGE separator. The default value is ..
SEP_SERIAL_RANGE The character to use when assigning more than one serial number range for a modification. Any character is valid. Note: The character cannot be identical to the other property values for the SERIAL_RANGE separator. The default value is ;
ALL_SERIAL_RANGE The character to use when assigning all serials to a serial number range for a modification. Any character is valid. Note: The character cannot be identical to the other property values for the SERIAL_RANGE separator. The default value is %
VIM_CURRENCY The currency of all the Fleet and Asset Management costs. This is used to convert values if the work order currency is different, or when operating with several work order currencies.

NOTE: The purpose of this object property is to ensure cost is accumulated in one currency only. Accumulating costs in different currencies, is not supported.

Object property VIM_COMPANY has been replaced by this object property.
All legal currency codes defined in IFS/Accounting Rules are valid.
LAST_DATE_LIMIT The number of years (past) for which you are allowed to start operational loggings. Any positive number is valid. The default value is 2.
DEFAULT_HIST_LANG The default language for storing part descriptions in history records. All legal language codes defined in IFS/Application Services. The default value is en.
CONFIG_TEMPL_SETTING The default value for configured in separate template when an entry is created in the serial structure template. TRUE (default value)
FALSE
CREATE_WO_STRUCTURE This determines if the option to create a work order structure when distributing events on a maintenance order should be selected automatically. TRUE (default value)
FALSE
AUTO_FINISH_ORDER Indicates whether the maintenance order should be finished when the last event on the order is finished or canceled. FALSE (default value)
TRUE
CHUNK_SIZE The number of serials to be processed in one chunk when running the due calculation for the interval maintenance. Any positive number is valid. The default value is 1000.
CHUNKS_IN_PARALLEL The number of chunks to be process in parallel when running the due calculation for interval maintenance. Any positive number is valid. The default value is 1.
POSITION_PART_DLIMTR The delimiter that will be used to generate position parts in the system. A position part number is a concatenation of the given transfer prefix, delimiter, and catalog number. Any character is valid.
AUTO_TRANSFER_STR This determines if new structure positions that are introduced to an active template structure should be transferred automatically to manufacturing or not. If automatic transfer is not required, a manual retransfer of the entire template structure must be done before new structure positions are reflected both in the temporary transfer table and in manufacturing. Automatic part transfer is initiated at activation of the structure position. TRUE (default value)
FALSE
ADD_STR_POS_SETTING The default value of the Activate Structure Position option in the Add Structure Position dialog. This determines whether the new structure position is to be created in the Preliminary or Active status. TRUE (default value)
FALSE
RUN_IN_BATCH This determines whether the new alternates that are introduced to a template structure should be transferred to manufacturing through a background job or not. TRUE
FALSE (default value)
DEFAULT_FAULT_DATE This determines whether to use the last reported operational logging date or the current date as the default fault date when reporting a fault. LAST_OPER_LOG (default value)
TODAY

Prerequisites

N/A

System Effects

Several settings that affect, for example, background jobs, cleanups, application behavior are changed.