Convert Leave Trigger Transaction (CLTRG)

The Convert Leave Trigger (CLTRG) transaction allows you to create, modify and view convert leave triggers and enter manual triggers for situations where automatic triggers do not occur, when a change in schedule hour occurs.

Field InformationField Information

The Convert Leave Trigger Transaction contains the following fields:

Field Name

Description

Employee ID

The identification code associated with the employee. The Employee ID is used to identify the employee in the system. This code can be any combination of letters and numbers and can be from 1 to 10 characters in length. If the Yes/No Flag for the AUTO GEN EMPLOYEE ID parameter on the Site Specific Parameters (SPAR) page is selected, the Employee ID field will be automatically generated and cannot be entered or modified by the user. If the Yes/No Flag is cleared, the Employee ID field on the Employee Status Maintenance (ESMT) transaction must be manually entered by a user.

In order to change an existing Employee ID, the Employee Identification Change Form (EICF) can be used. The Generate New ID check box on the EICF form must be selected, and the New Employee ID field must be left blank.

Appointment ID

If this field is blank, the employee data pertains to the employee's primary (blank) appointment. If the employee holds more than one appointment, this field represents the appropriate appointment identification number for the employee. If this field contains an asterisk (*), the employee data pertains to all appointments.

Type ID

  • Type ID defines the type of trigger.

  • Valid values are: Current (C), and Retroactive (R).

  • A trigger is considered current when the trigger date is on or after the employee’s assignment effective date and falls within the current or open processing period.

  • Current triggers are processed immediately during the job execution.

  • A trigger is considered retro when the trigger date falls prior to the current processing period but after the employee’s assignment effective date.

Trigger Date

Trigger date information becomes effective to know when the trigger was created. This field should be entered in mm/dd/ccyy format.

Trigger date earlier than assignment date → Processing is blocked.

Trigger date outside allowed processing windows → Trigger is not executed.

Trigger dates beyond the allowed future-effective window are not permitted.

Future-dated triggers cannot be processed until the trigger date becomes effective.

If a future date is entered that exceeds system-configured limits, the trigger is rejected during validation.

Old Leave Policy

This field is a pick list and the user can select the leave policy used before modification.

New Leave Policy

This field is a pick list and the user can select the leave policy used after modification.

Comments

This field is a text box - the user can write if there are any comments to be added.

The Convert Leave Trigger transaction can be created in the following way:

  • Select the Create action on the Transaction Catalog.

  • Select the Leave Conversion Trigger row-level action on the Leave Conversion Trigger tab of the Trigger Management (TRGM) activity folder.

  • Select Modify row-level action to open the transaction in edit mode. The Modify button is enabled only for transactions that are eligible for update.