This page (revision-21) was last changed on 26-Nov-2021 10:22 by JEscott

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
21 26-Nov-2021 10:22 11 KB JEscott to previous

Page References

Incoming links Outgoing links
ILGV
ILGV

Version management

Difference between version and

At line 2 removed one line
!!!RECORD GRIEVANCES
At line 6 added 2 lines
[{Image src='40600ILGV_00.JPG' width='400' align='right' link='attach/ILGV/40600ILGV_00.JPG' }]
At line 9 changed one line
Grievances may originate from [complaint|COMPLAINT]; however, not all grievances result from a complaint.
Grievances may originate from [complaint]; however, not all grievances result from a complaint.
At line 11 changed 2 lines
__Escalate a Complaint to a Grievance__
You may have also come to the ILGV screen by escalating a [complaint|COMPLAINT] to a grievance. In this scenario, you has created a grievance by selecting the Escalate to Grievance button on the [ILCM] form.
!Escalate a Complaint to a Grievance
You may have also come to the ILGV screen by escalating a [complaint] to a grievance. In this scenario, you has created a grievance by selecting the Escalate to Grievance button on the [ILCM] form.
At line 14 changed 4 lines
The data information for the Record Grievances screen can be found in the [P2K_LR_GRIEVANCES], [P2K_LR_GRIEVANCE_ACTIVITIES], and [P2K_LR_GRIEVANCE_PARTICIPANTS] tables.
;[Grievance|GRIEVANCE_TEXT]: This field displays detailed information about the grievance. %%strike This field is for display only%%.
;Participant: This field displays information about all the participants involved in the grievance. This field is for display only.
!!‘Record Grievances’ Field Descriptions
The data information for the Record Grievances screen can be found in the
[P2K_LR_GRIEVANCES], [P2K_LR_GRIEVANCES_ACTIVITIES], and
[P2K_LR_GRIEVANCE_PARTICIPANTS] tables.
;[Grievance]: This field displays detailed information about the grievance. This field is for display only.
;[Participant]: This field displays information about all the participants involved in the grievance. This field is for display only.
At line 19 changed one line
----
!!Details
;[Entity]: This field identifies the entity for which this grievance is being created. Entity from [IDEN] ([P2K_CM_ENTITIES]) is a mandatory field you may fill manually or through the LOV (F9) provided.
;[Unit]: This field identifies the unit for which this grievance is being created.
Unit from [IDUN] ([P2K_CM_UNITS]) is mandatory field you may fill manually or through the LOV (F9) provided.
;[Grievance]: This field is a user-defined code that uniquely identifies the grievance being defined. While you may define the grievance code, there is also the option of setting this field to automatically assign a sequential number to each new complaint entered. You may set up this option through the [IMCS] screen. Full details on this function are available through the User Interface manual. Grievance_Code is a mandatory 16-character alphanumeric field.
;[Description]: This field allows you to provide a short description of the grievance. Description is an optional 50-character alphanumeric field you may manually enter.
;[Dispute Type]: This field identifies the type of dispute under which this grievance falls. Dispute_Type from [ILGT] ([P2K_LR_DISPUTE_TYPE]) is a mandatory field you may fill manually or use the LOV (F9) provided.
;[Grievance Rule]: This field identifies the grievance rule or union contract under which this grievance falls. Grievance_Rules from [ILGR] ([P2K_LR_GRIEVANCE_RULES]) is a mandatory field you may fill manually or use the LOV (F9) provided.
;[Severity]: This field defines the severity of the grievance. Grievance_Serverity is an optional field you may fill with the fixed lexicon
[X_GRIEVANCE_SERVERITY].
;[Issue Date]: This field will define the issue date of the grievance. Grievance_Issue_Date is a mandatory field you may fill manually or by using the calendar icon (F9).
;[Incident Date]: This field records the date of the incident. Date_of_Incident is an optional field you may fill manually or by using the calendar icon (F9).
;[Approved]: If this toggle has been checked, the grievance has been approved.
Approved is an optional toggle you may select.
;[Stage]: This field defines the stage of the grievance. Greviance_Stage is an optional field you may fill using the user-defined lexicon [X_GRIEVANCE_STAGE]
;[Status]: This field identifies the current status of the grievance. Grievance_Status is an optional field you may fill from the fixed lexicon [X_GRIEVANCE_STATUS].
;[Location of Incident]: If information is added to this area, the data will be displayed in the text box at the top of the ILGV screen.\\
For instance:
At line 21 changed one line
!!Record Grievances (ILGV) - Grievance
If a location is identified, the text box at the top of the screen will indicate ‘The
grievance involves All Employees in Location ‘XXXXX’;
At line 23 changed 17 lines
!Details
;Entity: This field identifies the entity for which this grievance is being created. Entity from [IDEN] ([P2K_CM_ENTITIES]) is a mandatory field you may fill manually or through the LOV (F9) provided.
;Unit: This field identifies the unit for which this grievance is being created. Unit from [IDUN] ([P2K_CM_UNITS]) is mandatory field you may fill manually or through the LOV (F9) provided.
;[Grievance|GRIEVANCE_CODE]: This field is a user-defined code that uniquely identifies the grievance being defined. While you may define the grievance code, there is also the option of setting this field to automatically assign a sequential number to each new grievance entered. You may set up this option through the [IMCS] screen. Full details on this function are available through the User Interface manual. Grievance_Code is a mandatory 16-character alphanumeric field.
;[Description]: This field allows you to provide a short description of the grievance. Description is an optional 50-character alphanumeric field you may manually enter.
;Dispute Type: This field identifies the type of dispute under which this grievance falls. Dispute_Type from [ILDT] ([P2K_LR_DISPUTE_TYPES]) is a mandatory field you may fill manually or use the LOV (F9) provided.
;Grievance Rule: This field identifies the grievance rule or union contract under which this grievance falls. Grievance_Rules from [ILGR] ([P2K_LR_GRIEVANCE_RULES]) is a mandatory field you may fill manually or use the LOV (F9) provided.
;[Severity|GRIEVANCE_SEVERITY]: This field defines the severity of the grievance. Grievance_Serverity is an optional field you may fill with the fixed lexicon X_GRIEVANCE_SERVERITY.
;[Issue Date|GRIEVANCE_ISSUED_DATE]: This field will define the issue date of the grievance. Grievance_Issue_Date is a mandatory field you may fill manually or by using the calendar icon (F9).
;[Incident Date|DATE_OF_INCIDENT]: This field records the date of the incident. Date_of_Incident is an optional field you may fill manually or by using the calendar icon (F9).
;[Approved]: If this toggle has been checked, the grievance has been approved. Approved is an optional toggle you may select.
;[Stage|GRIEVANCE_STAGE]: This field defines the stage of the grievance. Greviance_Stage is an optional field you may fill using the user-defined lexicon X_GRIEVANCE_STAGE.
;[Status|GRIEVANCE_STATUS]: This field identifies the current status of the grievance. Grievance_Status is an optional field you may fill from the fixed lexicon X_GRIEVANCE_STATUS.
!Location of Incident
If information is added to this area, the data will be displayed in the text box at the top of the ILGV screen., For instance:
*If a location is identified, the text box at the top of the screen will indicate ‘The grievance involves All Employees in Location ‘XXXXX’;
* If a department is identified, the text box will indicate ‘The grievance involves All Employees in Unit ‘XXXXX’.
If a department is identified, the text box will indicate ‘The grievance involves All
Employees in Unit ‘XXXXX’.
At line 41 changed 3 lines
;Person Code: This field shows the name of the employee or company whom the grievance is against. For example, if this were a sexual harassment grievance against a supervisor, the supervisor’s name would be displayed here. Employee from [IEID] ([P2K_HR_IDENTITIES]) is an optional field you may fill manually or with the LOV (F9) provided.
;Location: If the grievance is on behalf of an entire location, that location may be entered in this field. Location from [IDLN] ([P2K_CM_LOCATIONS]) is an optional field you may fill manually or with the LOV (F9).
;Department: If the grievance is on behalf of an entire department, that department may be entered in this field. Department from [IDDP] ([P2K_CM_DEPARTMENTS]) is an optional field you may fill manually or with the LOV (F9).
;[Person Code]: This field shows the name of the employee or company whom the grievance is against. For example, if this were a sexual harassment grievance against a supervisor, the supervisor’s name would be displayed here. Employee from [IDEN] ([P2K_HR_IDENTITIES]) is an optional field you may fill manually or with the LOV (F9) provided.
;[Location]: If the grievance is on behalf of an entire location, that location may be entered in this field. Location from [IDLN] ([P2K_CM_LOCATIONS]) is an optional field you may fill manually or with the LOV (F9).
;[Department]: If the grievance is on behalf of an entire department, that department may be entered in this field. Department from [IDDP] ([P2K_CM_DEPARTMENT]) is an optional field you may fill manually or with the LOV (F9).
At line 47 changed 4 lines
;[Settlement|SETTLEMENT_AMOUNT]: If settlement amount has come from this grievance, that amount will be listed here Settlement_Amount is an optional 18-character numeric field you may enter manually.
;[Disciplinary Code|DISCIPLINARY_CODE]:If disciplinary action has been taken with this grievance, the disciplinary action code will be displayed here. Disciplinary_Code from [ILDI] ([P2K_LR_DISCIPLINARY_ISSUES]) is an optional field you may fill with the LOV (F9) provided.
;[Decision|GRIEVANCE_DECISION]: This field displays the decision made in for this grievance. Grievance_Decision is an optional field you may fill using the lexicon X_GRIEVANCE_DECISION.
;[Date|GRIEVANCE_CLOSED_DATE]: This field will display the date of the settlement. Grievance_Closed_Date is an optional field you may fill manually or with the calendar icon (F9) provided.
;[Settlement]: If settlement amount has come from this grievance, that amount will be listed here Settlement_Amount is an optional 18-character numeric field you may enter manually.
;[Disciplinary Code]:If disciplinary action has been taken with this grievance, the disciplinary action code will be displayed here. Discplinary_Code from [ILDI] ([P2K_DISCPLINARY_ISSUES]) is an optional field you may fill with the LOV (F9) provided.
;[Decision]: This field displays the decision made in for this grievance. Grievance_Decision is an optional field you may fill using the lexicon [X_COMPLAINT_DECISION].
;[Date]: This field will display the date of the settlement. Grievance_Closed_Date is an optional field you may fill manually or with the calendar icon (F9) provided.
At line 52 removed one line
----
At line 59 added one line
[{Image src='40600ILGV_01.JPG' width='400' align='right' link='attach/ILGV/40600ILGV_01.JPG' }]
At line 55 changed 3 lines
;[Witnesses|INCIDENT_WITNESSES]: This field allows you to provide additional and in depth information about the witnesses. Incident_Witnesses is an optional 4000-character alphanumeric field you may fill manually.
;[Contract Notes|CONTRACT_REFERENCE]: This field allows you to provide additional and in depth information about the contract. Contract_Notes is an optional 4000-character alphanumeric field you may fill manually.
;[Union Notes|UNION_REFERENCE]: This field allows you to provide additional and in depth information about the contract. Union_Notes is an optional 4000-character alphanumeric field you may fill manually.
;[Witnesses]: This field allows you to provide additional and in depth information about the witnesses. Incident_Witnesses is an optional 4000-character alphanumeric field you may fill manually.
;[Contract Notes]: This field allows you to provide additional and in depth information about the contract. Contract_Notes is an optional 4000-character alphanumeric field you may fill manually.
;[Union Notes]: This field allows you to provide additional and in depth information about the contract. Union_Notes is an optional 4000-character alphanumeric field you may fill manually.
At line 59 removed one line
----
At line 66 added one line
[{Image src='40600ILGV_02.JPG' width='400' align='right' link='attach/ILGV/40600ILGV_02.JPG' }]
At line 62 changed 3 lines
;Activity:This field defines the activities associated with this grievance. These activities are composed of the grievance steps defined in [ILGR]. Activity from ILGR ([P2K_LR_GRIEVANCE_RULES]) is an optional field you may fill from the LOV.
;[Status|GRIEVANCE_ACTIVITY_STATUS]: This field indicates the current status of the activity. Activity_Status is a mandatory field you may fill with a value from the fixed lexicon X_GRIEVANCE_ACTIVITY_STATUS.
;[Must Reply By|MUST_REPLY_BY]: This field defines the time limit for a response to this activity. Must_Reply_By is a mandatory field you may fill manually or through the calendar icon provided.
;[Activity]:This field defines the activities associated with this grievance. These activities are composed of the grievance steps defined in [ILGR]. Activity from ILGR ([P2K_LR_GRIEVANCES_RULES]) is an optional field you may fill from the LOV.
;[Status]: This field indicates the current status of the activity. Activity_Status is a mandatory field you may fill with a value from the fixed lexicon
[X_GRIEVANCE_ACTIVITY_STATUS].
;[Must Reply By]: This field defines the time limit for a response to this activity. Must_Reply_By is a mandatory field you may fill manually or through the calendar icon provided.
At line 66 changed one line
;Next Activity: This field defines the activity that must follow the activity being defined. This activity is derived from the grievance steps defined in ILGR. Next_Activity from [ILGR] ([P2K_LR_GRIEVANCE_RULES]) is an optional field you may fill from the LOV.
;[Next Activity]: This field defines the activity that must follow the activity being defined. This activity is derived from the grievance steps defined in ILGR.
Next_Activity from [ILGR] ([P2K_LR_GRIEVANCES_RULES]) is an optional field you may fill from
the LOV.
At line 68 changed 3 lines
;Participant Type:The Participant Type field will automatically fill once the Activity field has been defined.
;Activity Duration: The Activity Duration field will automatically fill once the Activity field has been defined.
;[Date|REPLY_TIMESTAMP]: This field identifies the date a reply is expected by. Reply_Timestamp is an optional field you may fill manually or with the calendar icon available.
;[Participant Type]:The Participant Type field will automatically fill once the Activity field has been defined.
;[Activity Duration]: The Activity Duration field will automatically fill once the Activity field has been defined.
;[Date]: This field identifies the date a reply is expected by. Reply_Timestamp is an optional field you may fill manually or with the calendar icon available.
At line 73 changed one line
;[Replied Via|GRIEVANCE_REPLY_BY]: This field indicates the way in which the reply was sent. Grievance_Reply_By is an optional 50-character alphanumeric field you may manually fill. e.g. email, letter, phone call
;[Replied Via]: This field indicates the way in which the reply was sent. Grievance_Reply_Type is an optional 50-character alphanumeric field you may manually fill. e.g. email, letter, phone call
At line 75 changed 4 lines
;[Reply Type|GRIEVANCE_REPLY_TYPE]: This field identifies the type of reply. Reply_Type is an optional field you fills with the fixed lexicon X_GRIEVANCE_REPLY_TYPE.
;Reply Interval: This time provides the time difference between when the step was started and a reply was issued.
;[Date|REPLY_TIMESTAMP]: This field identifies the date a reply was actually received. Reply_Timestamp is an optional field you may fill manually or with the calendar icon available.
;Reset Date: This button will change the date that the step was completed to the current date and time stamp.
;[Reply Type]: This field identifies the type of reply. Reply_Type is an optional field you fills with the fixed lexicon [X_GRIEVANCE_REPLY_TYPE].
;[Reply Interval]: This time provides the time difference between when the step was started and a reply was issued.
;[Date]: This field identifies the date a reply was actually received. Reply_Timestamp is an optional field you may fill manually or with the calendar icon available.
;[Reset Date]: This field changes the date that the step was completed to the current date and time stamp.
At line 81 changed one line
;[Text|GRIEVANCE_REPLY_TEXT]: This field allows you to provide either the full reply and/or more information regarding the reply. Grievance_Reply_Text is an optional 4000-character alphanumeric field you may manually fill.
;[Text]: This field allows you to provide either the full reply and/or more information regarding the reply. Grievance_Reply_Type is an optional 4000-character alphanumeric field you may manually fill.
At line 83 removed 2 lines
----
At line 93 added one line
[{Image src='40600ILGV_03.JPG' width='400' align='right' link='attach/ILGV/40600ILGV_03.JPG' }]
At line 88 changed one line
;[Participant Type|PARTICIPANT_TYPE]:This field identifies the type of participation for this individual. Participant_Type is a mandatory fixed lexicon you must fill with the fixed lexicon X_PARTICIPANT_TYPE provided.
;[Participant Type]:This field identifies the type of participation for this individual. Participant_Type is a mandatory fixed lexicon you must fill with the fixed lexicon [X_PARTICIPANT_TYPE] provided.
At line 90 changed one line
;[Settlement Amount|SETTLEMENT_AMOUNT]:If the participant has received a settlement amount through this grievance, this amount may be listed here. Settlement_Amount is an optional 18-character numeric field you may fill manually.
;[Settlement Amount]:If the participant has received a settlement amount through this grievance, this amount may be listed here. Settlement_Amount is an optional 18-character numeric field you may fill manually.
At line 93 changed 7 lines
;Employee Name OR Contact Name: These fields display the identity of the participant. This is a mandatory field you may fill manually or retrieve from the LOV provided.
;:* For internal contacts, use the Employee Name field. The link to [IEID] ([P2K_HR_IDENTITIES]) is made through the [foreign key] [EID_ID].
;:* For external contacts, use the Contact Name field. The link to [IECI] ([P2K_HR_CONTACTS]) is made through the [foreign key] [ECT_ID].
;Type: This field identifies if the participant is an employee (internal) or a contact (external). Type will default in once the ‘Name’ field has been filled.
;Address: This field identifies the street address of the participant being defined. Address will default in once the ‘Name’ field has been filled.
;Locality: This field identifies the city or town of the participant being defined. Locality will default in once the ‘Name’ field has been filled.
;Phone: This field identifies the phone number for the participant. Phone will default in once the ‘Name’ field has been filled.
;[Employee Name] OR [Contact Name]: These fields display the identity of the participant. You may only complete one of these fields. For internal participants, use the Employee Name field and for external participant, use the Contact Name field. Identity is derived from both the [IDEN] ([P2K_HR_IDENTITIES]) and [IECT] ([P2K_HR_CONTACTS]) tables. This is a mandatory field you may fill manually or retrieve from the LOV provided.
;[Type]: This field identifies if the participant is an employee (internal) or a contact (external). Type will default in once the ‘Name’ field has been filled.
;[Address]: This field identifies the street address of the participant being defined. Address will default in once the ‘Name’ field has been filled.
;[Locality]: This field identifies the city or town of the participant being defined. Locality will default in once the ‘Name’ field has been filled.
;[Phone]: This field identifies the phone number for the participant. Phone will default in once the ‘Name’ field has been filled.
At line 102 changed 6 lines
;[Text|PARTICIPANT_TEXT]:This field allows you to provide additional information about this participant. Participant_Info is an optional 4000-character alphanumeric field you may enter manually.
----
![Notes|Edit:Internal.ILGV]
[{InsertPage page='Internal.ILGV' default='Click to create a new notes page'}]
;[Text]:This field allows you to provide additional information about this participant. Participant_Info is an optional 4000-character alphanumeric field you may enter manually.
This page (revision-21) was last changed on 26-Nov-2021 10:22 by JEscottTop