PAYRULE_BASED_SCHED_COST_CALC_TIMECODE_CONVERSION

In some scenarios, the schedule cost is zero when the SO_PAY_RULE_BASED_SCHED_COST_CALC registry parameter is set to true (schedule costing based on pay rules) and the WRK activity is associated with the UAT time code. This can also occur in some situations when BRK is associated with BRKP.

For many users in the Time and Attendance module, before the employee actually clocks, WFM does not show costs because the costs are not occurring yet. Eventually, after the employee clocks, time code WRK will be associated with work activity. However, prior to the time code WRK, the UAT time code is associated with work activity in order to not show costs.

Usually the time code BRK is associated with break activity after the employee clocks, meaning the break is unpaid. However, there are situations where the break is paid and BRKP is associated with break activity after the employee clocks. In this case, in order not to show costs, the time code BRK is associated with break activity prior to that.

For the LFSO schedule view, WFM will display estimated costs. To do this, UAT is treated as WRK and in certain situations BRK as BRKP. For example, if UAT and BRK should be factored in the cost calculations, then you can set this parameter to UAT,WRK. If you also want to associate BRK with BRKP, you can specify UAT,WRK,BRK,BRKP.

When using this parameter you must specify an even number of comma-delimited string time codes such as UAT,WRK,BRK,BRKP. If you specify an odd number of time codes, the last time code is silently ignored. An unrecognizable time code name in the string raises an exception. Spaces are allowed between time code names and delimiters.

For more information on configuring calculation groups and pay rules, see Time and Attendance Implementation and Administration Guide. You can also refer to SO_PAY_RULE_BASED_SCHED_COST_CALC.

An even number of comma-delimited string time codes.

Blank

system/modules/scheduling

6.2.4.9