Set parameters for the features of the Work module to work properly.
Work parameters are related to work orders, budgets, and project management features that must be set for the features of the application to work properly.
Set values for work parameters according to the following table.
Code |
Description |
Fixed |
---|---|---|
@WOPTDET |
Whether to export work order part with more details in outbound Maintenance Order BOD. If set to Y, the BOD will detail items allocated for a work order by store and if the parts are planned, reserved, or direct purchase. If set to N, the BOD will summarize the parts for the work order. |
No |
7ISCDKEY |
HxGN EAM Caller Login for Service Requests CD key. |
No |
AUTODMEC |
This code determines whether the Remove Equipment hyperlink on the Equipment page of the Work Orders form breaks the association between the parent work order and a multiple equipment child work order or whether the system also deletes the multiple equipment child work order. |
|
Valid values are Y or N. By default the parameter is set to Y, which means that the system deletes the related multiple equipment child records. |
||
AUTOPMCL |
This code indicates whether to automatically close all released minor PMs at release of the major PMs (YES/NO). |
No |
BOOKDATE |
Indicates whether to enforce date constraints when booking hours. If set to OFF, the system ignores the constraints. If set to ON, the system enforces the constraints. |
No |
Setting this parameter OFF may result in inconsistencies within your booked hours data. |
||
Setting BOOKDATE to OFF enables you to book labor hours for a date that is earlier than Date reported. By enabling you to book the hours without any date restrictions based on the Date reported field, you can leave the value for Date reported as is and still book hours for work that has already been completed. |
||
BOOPLAN |
Booking hours. Valid values are ON and OFF. When booking hours, if the value is ON, the system gets the trade rate from the activity on which hours are booked. If the value is OFF, the system gets the rate from the employee table. Changing this value will not affect existing data. If you change this parameter and open work orders exist on which hours have already been booked, inconsistencies will arise. Close work orders before changing BOOPLAN. |
No |
CALSTD |
Determines if calibration standards that have overdue PM work orders can be used to perform a calibration. |
No |
If CALSTD is set to YES, equipment with overdue PM work orders are available for selection as a calibration standard. |
||
If CALSTD is set to NO, equipment with overdue PM work orders are not available for selection as a calibration standard. |
||
CASCLOC |
Cascade equipment Location changes to PM equipment records. If set to YES cascade changes. If set to NO, do not cascade changes. |
No |
CLPBWOST |
This parameter identifies the work order status after checklist Performed By is signed. |
No |
Example: WCMP |
||
CLRBWOST |
This parameter identifies the work order status after checklist Reviewed By is signed. |
No |
Example: COMP |
||
CLRRWOST |
This parameter identifies the work order status after checklist Performed By is rejected. |
No |
Example: INPR |
||
COMDAYS |
Number of days during which you can book hours on closed work orders. Infor recommends a minimum value of 1. Changing the value will not affect existing data. |
No |
Example: 14 |
||
COPTMKEY |
Constraint Optimizer server API key |
No |
COPTMURL |
Constraint Optimizer server URL |
No |
COVDUPAC |
This code indicates whether the system allows multiple active warranties. If set to Yes (+), more than one active warranty on a certain equipment can be specified. If set to No(-), only one active warranty on a certain equipment can be specified. |
No |
Example: * |
||
COVDURUP |
This code indicates whether the duration fields are display-only. If set to Yes (+), the duration fields can be entered manually. If set to No (-), the duration fields are display-only. |
No |
Example: + |
||
DSCHAVAI |
Number of days from current date used to calculate labor availability in daily scheduling. |
No |
Example: 7 |
||
DUPCHECK |
If code is set to ON, the system checks for duplicate and repeated service requests. |
No |
EVTCASCD |
Event cascade. This code indicates whether changing a parent work order’s status to Closed or Canceled causes the status of child work orders to also change. |
No |
Example: N |
||
INRVCTRL |
This code indicates whether Revision control is activated for inspections. |
No |
Example: NO |
||
INSWOST |
This code identifies the status used to create work orders from inspection forms. You can choose user codes equivalent to type R (Released). |
No |
Example: L |
||
ISSDAYS |
Issue days. This code indicates the number of days for which issues can be made after you close a work order. Valid values are any non-negative numbers. Changing the value will not affect existing data. |
No |
Example: 0 |
||
JTAUTH |
This code indicates whether work order type authorization is activated. Work order type authorization limits which users can update, insert, or delete work orders based on the type of work order. |
No |
Example: NO |
||
NPRDAYS |
Nonproductive days. This code indicates the number of days for which you can book past nonproductive hours, which is labor performed without a work order. |
No |
This parameter may interfere with closed periods data. Changing the value will not affect existing data. |
||
Example: 14 |
||
PLANLEV |
This code determines the level at which planning will be performed. If JOB is selected then planning can only be done at the job level. If TASK is selected then planning can only be done at the task level. If EITHER then planning can be done on either tasks or jobs. |
No |
PMNEST |
Indicates whether to enable the following PM nesting enhancements. Valid values are YES or NO. |
No |
|
||
|
||
|
||
|
||
PMCRPAST |
This code indicates whether the system can generate new fixed PM or duplicate PM work orders with a due date in the past. Valid values are YES and NO. The default setting is NO. |
No |
If the value is set to YES, the system creates the next PM work order with a due date that reflects the calculated work order due date and the PM frequency, even if the next due date is in the past. If the value is NO, the system always creates the PM work order with a future due date. |
||
PMRVCAPP |
PM Revision Control. This code indicates whether you can create a new revision only from an approved revision. |
No |
Example: NO |
||
PMRVCDEP |
PM Revision Control. This code indicates whether components of a PM depend on the PM itself. Example: NO |
No |
PMRVCRES |
PM Revision Control. This code indicates whether users can approve lines only from their own departments. |
No |
Example: YES |
||
PMRVCTRL |
PM Revision Control. This code indicates whether PM Revision Control is activated. |
No |
Example: NO |
||
PMWODATE |
This code indicates the starting date used when calculating the next due date of a variable PM work order. Set to C for completion date, PB for calibration Performed By date, or RB for calibration Reviewed By date. |
No |
Example: C |
||
PPMSTAT |
PM Status. This code indicates the status of a PM work order when generated from a PM schedule. Valid values are A for Awaiting Release and R for Released. Changing the value will not affect existing data. |
No |
PROJWOST |
This code identifies the status used to create work orders on the Project form. |
No |
Example: L |
||
REOPENPM |
Reopen PMs. This code indicates whether a PM work order can be reopened. |
No |
Example: NO |
||
REQDAYS |
Number of days after completing a work order that a requisition can be created against it. |
No |
Example: -999 |
||
RSPCOMP |
Indicates whether to display the Qty. Completed on work orders for internally repaired repairable spare parts. If set to NO, the system does not display Qty. Completed. If set to YES, the system displays Qty. Completed and restricts internal repair receipts to completed repairs. |
No |
RTNDAYS |
Return days. This code indicates the number of days that parts can be returned to the store after the work order has been closed. Valid values are any non-negative numbers. Note that this parameter may interfere with closed periods data. Changing the value will not affect existing data. |
No |
Example: 14 |
||
SCHPAST |
Set SCHPAST to YES to allow scheduling in the past. Set SCH PAST to NO to prevent scheduling in the past. Example: NO |
No |
SCHSTAT |
The user status of a work order after you have scheduled an activity. You can select any status. |
No |
SHOWJOB |
This code determines whether job plan information is visible in the product. If YES then the Job Plan screen, tabs, and fields will be visible in the product. If NO then this information will not be visible. The default value is NO. |
No |
SRCLOSE |
This code indicates whether to automatically close an associated service request when a work order is closed. Valid values are YES and NO. |
No |
TOOLDAYS |
This code identifies the number of days to update tool usage costs after completion of a work order. |
No |
Example: 3 |
||
UPWOMATL |
Determines if the work order planned parts list is updated to include direct requisition and PO line parts if they are not already planned. If N, the work order planned parts list is not updated. If Y, the work order planned parts list is updated. If P, choose whether the work order planned parts list gets updated as lines are added to requisitions and POs. If A, the planned parts list is updated only after the line is approved. |
No |
VTTAUTH |
Determines whether the system uses vehicle ticket type authorization. Valid values are ON and OFF. |
No |
WFFTAUTH |
Comments code. The system uses this code to determine who has authority to change comments in the Comments grid for work orders on the (WXDONE) form. If the installation parameter is set to NO, all users can change comments; if the installation parameter is set to YES, only users who can reopen work orders have permission to change comments. |
No |
WOCLPOUT |
This code indicates whether a work order can be closed if purchase requisitions and purchase orders are still outstanding. If set to YES, work orders with outstanding requisitions and purchase orders may be closed. |
No |
This parameter may affect purchase order generation if you allow work orders to be closed for which there are existing open requisitions. |
||
WOOSKEY |
The API key for the Constraint Optimizer that is used to dispatch and sequence EAM work order activities. This key is used with the URL specified in the installation parameter WOOSURL to connect to the Constraint Optimizer. |
|
WOOSURL |
The URL for the Constraint Optimizer used to dispatch and sequence EAM work order activities. |
No |
WOQUAL |
Qualification enforcement for work. Valid values are ON and OFF. When scheduling work, if the value is ON, the system determines whether an employee is eligible to perform work by comparing the qualifications associated with a work order activity with the qualifications associated with employees on the Employees form. The system enables you to assign any employee with the necessary qualifications/training to perform the work. |
No |
When scheduling work, if the value is OFF, the system does not check qualifications for work scheduling, and any authorized users can perform work regardless of any qualifications associated with work order activities. |
||
WORKDAY |
Work day hours. This code indicates the default number of hours in a working day. The system uses this value on the Activities tab of the Work Orders form to calculate the required number of people when an estimated number of hours and the duration is specified. Changing the value will not affect existing data. |
No |
Example: 8 |
||
WORKWOST |
This code identifies the user status for work orders when updated by the Generate/Release WOs form. The work order must have the system status R. |
No |
Example: L |