Examples: Profiles for time and attendance registrations [AX 2012]

Updated: October 19, 2012

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

The following sections provide examples of work time profiles for different workers and shifts. All examples are based on the standard setup of Calculation parameters, which is used to calculate time registrations and pay time, based on profile types. For more information, see About parameters for calculations.

Set up time registration profiles in the Profile form. Click Human resources > Setup > Time and attendance > Time profiles > Profiles.

Set up calculation parameters in the Calculation parameters form. Click Human resources > Setup > Time and attendance > Calculation parameters.

This is an example of a general profile that can be used for a day shift in a two-shift or three-shift rotation schedule, or for office workers who do not work in shifts.

Field

Value

Field

Value

New 24-hour period:

00:00:00

Overtime / flex limit:

00:00:00

24-hour period start:

This day

Max. flex limit:

00:00:00

Profile type

Start

End

Tolerance before start

Tolerance after start

Tolerance before end

Tolerance after end

Switch code

Secondary

Overtime

00:00

07:00

Clock in

07:00

07:00

15

2

Standard time

07:00

11:30

Break

11:30

12:00

Overtime

Standard time

12:00

15:00

Clock out

15:00

15:00

15

Overtime

15:00

00:00

Based on this example profile:

  • Clock-in between 06:45 and 07:00 will not result in overtime payment because of the tolerance (Tolerance before start).

  • Clock-in between 07:00 and 07:02 will not result in a reduction in pay because of the tolerance (Tolerance after end).

  • Clock-out between 15:00 and 15:15 will not result in overtime payment because of the tolerance (Tolerance after end).

  • If the break between 11:30 and 12:00 is cancelled, that time is considered to be overtime.

This profile can be used for workers who work flexible hours.

Field

Value

Field

Value

New 24-hour period:

00:00:00

Overtime / flex limit:

00:00:00

24-hour period start:

This day

Max. flex limit:

00:00:00

Profile type

Start

End

Tolerance before start

Tolerance after start

Tolerance before end

Tolerance after end

Switch code

Secondary

Overtime

00:00

07:00

Flex+

07:00

08:00

O1

Overtime

Clock in

08:00

08:00

Flex-

08:00

09:00

Paid break

09:00

09:15

Standard time

09:15

11:30

Break

11:30

12:00

Flex+

Standard time

12:00

13:45

Break

13:45

14:00

Standard time

14:00

15:00

Flex-

15:00

16:00

Clock out

16:00

16:00

Flex+

16:00

17:00

O2

Overtime

Overtime

17:00

00:00

Based on this example profile:

  • There is a two-hour flex zone in the morning and a two-hour flex zone in the afternoon.

  • Workers can clock in between 07:00 and 09:00 and clock out between 15:00 and 17:00 and still get paid for a full work day. Any difference between paid time and actual work time will cause an adjustment to the flex balance.

  • If the switch code O1 is registered, working between 06:00 and 07:00 is considered to be overtime.

  • If the switch code O2 is registered, working between 16:00 and 17:00 is considered to be overtime.

  • If the break between 11:30 and 12:00 is cancelled, that time is added to the flex balance.

This profile is an example of an evening shift.

Field

Value

Field

Value

New 24-hour period:

00:00:00

Overtime / flex limit:

00:00:00

24-hour period start:

This day

Max. flex limit:

00:00:00

Profile type

Start

End

Tolerance before start

Tolerance after start

Tolerance before end

Tolerance after end

Switch code

Secondary

Overtime

07:00

15:00

Clock in

15:00

15:00

15

2

Standard time

15:00

18:00

Break

18:00

18:30

Overtime

Standard time

18:30

23:00

Clock out

23:00

23:00

15

Overtime

23:00

07:00

Based on this example profile:

  • Clock-in between 14:45 and 15:00 will not result in overtime payment because of the tolerance (Tolerance before start).

  • Clock-in between 15:00 and 15:02 will not result in a reduction in pay because of the tolerance (Tolerance after end).

  • Clock out between 23:00 and 23:15 will not result in overtime payment because of the tolerance (Tolerance after end).

  • If the break between 18:00 and 18:30 is cancelled, that time is considered to be overtime.

This profile is an example of a shift that works across midnight.

Field

Value

Field

Value

New 24-hour period:

20:00:00

Overtime / flex limit:

00:00:00

24-hour period start:

Previous day

Max. flex limit:

00:00:00

Profile type

Start

End

Tolerance before start

Tolerance after start

Tolerance before end

Tolerance after end

Switch code

Secondary

Overtime

20:00

23:00

Clock in

23:00

23:00

15

2

Standard time

23:00

03:00

Break

03:00

03:30

Overtime

Standard time

03:30

07:00

Clock out

07:00

07:00

15

Overtime

07:00

20:00

Based on this example profile:

  • The Previous day selection in the 24-hour period start box indicates that the profile starts before midnight. If this is the profile for Monday, clock-in is expected at 22:00 on Sunday evening.

  • Clock-in after 20:00 (New 24-hour period field) means that the profile for the following day will be used.

  • Clock-in between 22:45 and 23:00 will not result in overtime payment because of the tolerance (Tolerance before start).

  • Clock-in between 23:00 and 23:02 will not result in a reduction in pay because of the tolerance (Tolerance after end).

  • Clock-out between 07:00 and 07:15 will not result in overtime payment because of the tolerance (Tolerance after end).

  • If the break between 03:00 and 03:30 is cancelled, that time is considered to be overtime.

NoteNote

The Push check box is relevant if a night shift profile crosses midnight and the profile date for the profile is the date of clock-in. In the night shift profile example above, the profile date is the date of clock-out because Previous day is selected in the 24-hour period start field.

Example using Push based on the night shift profile above:

  • In the New 24-hour period field, insert the time 02:00:00.

  • Select the Push check box.

  • In the 24-hour period start field, select This day.

If some workers have no fixed clock-in time, you can set up a profile like this one. In the example, workers are expected to work 7.5 hours a day. But they can decide themselves at which time during the day they will be at work.

They will generate flexible hours for a maximum of 2.0 hours per work day if they work more than 7.5 hours. Work time exceeding 9.5 hours a day will be converted into overtime.

Field

Value

Field

Value

New 24-hour period:

00:00:00

Overtime / flex limit:

07:30:00

24-hour period start:

This day

Max. flex limit:

02:00:00

Profile type

Start

End

Tolerance before start

Tolerance after start

Tolerance before end

Tolerance after end

Switch code

Secondary

Overtime

00:00

23:59

Overtime

23:59

22:00

Based on this example profile:

  • If a worker registers between 7.5 and 9.5 work hours on a day, 7.5 hours will be registered as standard time, and the rest of the work time will be added to the flex balance.

  • If a worker registers more than 9.5 hours on a day, 7.5 hours will be registered as standard time, 2.0 hours will be added to the flex balance, and the rest will be registered as overtime.

  • Breaks during the work day must be registered by the worker.

  • The reason for including a second line displaying Overtime from 23:59 to 22:00 (the following day) is to allow workers to work through the night on the same profile date.

  • If the worker works less than 7.5 hours a day, absence must be registered; this can be done automatically.

You can set up parameters to insert an absence code automatically in a flex profile with no fixed clock-in time:

  1. Click Human resources > Setup > Time and attendance > Time and attendance parameters.

  2. On the General tab, in the Auto insert flex- / absence field, select an absence code.

NoteNote

The selected absence code will be inserted automatically during calculation of the worker’s registrations.


Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).

Community Additions

ADD
Show: