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

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
33 26-Nov-2021 10:22 6 KB jmyers to previous
32 26-Nov-2021 10:22 8 KB JEscott to previous | to last
31 26-Nov-2021 10:22 8 KB RForbes to previous | to last
30 26-Nov-2021 10:22 8 KB RForbes to previous | to last
29 26-Nov-2021 10:22 8 KB RForbes to previous | to last
28 26-Nov-2021 10:22 8 KB RForbes to previous | to last
27 26-Nov-2021 10:22 8 KB Administrator to previous | to last
26 26-Nov-2021 10:22 8 KB Administrator to previous | to last
25 26-Nov-2021 10:22 8 KB Administrator to previous | to last
24 26-Nov-2021 10:22 8 KB Administrator to previous | to last
23 26-Nov-2021 10:22 8 KB Administrator to previous | to last
22 26-Nov-2021 10:22 8 KB Administrator to previous | to last
21 26-Nov-2021 10:22 8 KB Administrator to previous | to last

Page References

Incoming links Outgoing links
ILCM
ILCM

Version management

Difference between version and

At line 1 changed one line
You may add or maintain employee complaints in the eP through the Record Complaints (ILCM) screen. This form will hold important detailed information about the complaint itself, as well as information about the participants and witnesses to the complaint\\
[{TableOfContents }]
!!!RECORD EMPLOYEE COMPLAINTS
At line 3 changed one line
[{Image src='40600ILCM_00.JPG' width='400' align='right' link='ILCM\40600ILCM_00.JPG'}]
You may add or maintain employee complaints in the application through the Record Complaints (ILCM) screen. This form will hold important detailed information about the complaint itself, as well as information about the participants and witnesses to the complaint
At line 7 changed 2 lines
;[Complaint]: This field displays detailed information about the complaint. This field is for display only.
;[Participant]: This field displays information about all the participants involved in the complaint. This field is for display only.
;[Complaint|COMPLAINT_TEXT]: This field displays detailed information about the complaint. %%strike This field is for display only.%%
;Participant: This field displays information about all the participants involved in the complaint. This field is for display only.
At line 11 added 4 lines
----
!!Record Complaints (ILCM) - Complaint
At line 11 changed 9 lines
;[Entity]:The field identifies the entity associated with this complaint. Entity from [IDEN] ([P2K_CM_ENTITIES]) is a mandatory field you must enter manually or through LOV (F9) provided.
;[Complaint]:This field is a user-defined code that uniquely identifies the complaint being defined. While you may define the complaint 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. Complaint_Code is a mandatory 16-character alphanumeric field you must manually enter.
;[Date Issued]: This field records the date the complaint was issued. Date_Issued is mandatory field you must fill manually or through the calendar provided (F9).
;[Dispute Type]: This field identifies the type of dispute under which this complaint falls. Dispute_Type from [ILDT] ([P2K_LR_DISPUTE_TYPES]) is a mandatory field you must fill manually or through the LOV (F9) provided.
;[Status|COMPLAINT_STATUS]:This field indicates the status of the complaint. Complaint_Status is a mandatory field you may select from the fixed lexicon [X_COMPLAINT_STATUS].
;[Stage]:This field is displays the stage of the complaint. eg Logged, Settled. Complaint_Stage is an optional field you may fill with the user-defined lexicon [X_COMPLAINT_STAGE].
;[Severity|DISPUTE_SEVERITY]:This field indicates the severity of the complaint. Dispute_Severity is an optional field you may fill with the fixed lexicon [X_DISPUTE_SEVERITY].
;[Incident Date]: This field displays the date the complaint incident took place. Date_of_Incident is a mandatory field you must fill manually or with the calendar icon (F9).
;[Description]:This field allows you to provide a short description of the complaint. Description is an optional 50-character alphanumeric field you may fill manually.
;[Entity|ENTITY_CODE]:The field identifies the entity associated with this complaint. Entity from [IDEN] ([P2K_CM_ENTITIES]) is a mandatory field you must enter manually or through LOV (F9) provided.
At line 18 added 9 lines
;[Complaint|COMPLAINT_CODE]:This field is a user-defined code that uniquely identifies the complaint being defined. While you may define the complaint 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.
;[Date Issued|COMPLAINT_ISSUED_DATE]: This field records the date the complaint was issued.
;Dispute Type: This field identifies the type of dispute under which this complaint falls. Dispute_Type from [ILDT] ([P2K_LR_DISPUTE_TYPES]) is a mandatory field you must fill manually or through the LOV (F9) provided.
;[Status|COMPLAINT_STATUS]:This field indicates the status of the complaint.
;[Stage|COMPLAINT_STAGE]:This field is displays the stage of the complaint. eg Logged, Settled.
;[Severity|COMPLAINT_SEVERITY]:This field indicates the severity of the complaint.
;[Incident Date|DATE_OF_INCIDENT]: This field displays the date the complaint incident took place.
;[Description|DESCRIPTION]:This field allows you to provide a short description of the complaint.
At line 22 changed 4 lines
;[Settlement]:This field displays any settlement amount that may have come from this complaint. Settlement_Agreement is an optional 18-character numeric field you may fill manually.
;[Date Closed]:This field shows the date of the complaint issue was closed. Date_of_Incident is an optional field you may fill manually or with the calendar provided (F9).
;[Disciplinary Issue]:This field displays the disciplinary issue under which this complaint falls. Disciplinary_Issue from [ILDI] ([P2K_LR_DISCIPLINARY_ISSUES]) is an optional field you may fill from the LOV provided (F9).
;[Decision]:This field shows the final decision made on this case. Complaint_Decision is an optional field you may fill from the fixed lexicon [X_COMPLAINT_DECISION].
;[Settlement|SETTLEMENT_AMOUNT]:This field displays any settlement amount that may have come from this complaint.
;[Date Closed|COMPLAINT_CLOSED_DATE]:This field shows the date of the complaint issue was closed.
;[Disciplinary Issue|DISCIPLINARY_CODE]:This field displays the disciplinary issue under which this complaint falls. Disciplinary_Issue from [ILDI] ([P2K_LR_DISCIPLINARY_ISSUES]) is an optional field you may fill from the LOV provided (F9).
;[Decision|COMPLAINT_DECISION]:This field shows the final decision made on this case.
At line 30 changed 5 lines
;[Employee #|PERSON_CODE]:This field shows the name of the employee whom the complaint is against. For example, if this were a sexual harassment complaint 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.
;[Name]: This field identifies the employee by name. This field will be automatically completed when the Employee # field is filled.
;[Location]:If the complaint 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).
;[Unit]: If the complaint is on behalf of an entire [unit], that unit may be entered in this field. Unit from [IDUN] ([P2K_CM_UNITS]) is an optional field you may fill manually or with the LOV (F9).
;[Department]: If the complaint 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).
;[Employee #|PERSON_CODE]:This field shows the name of the employee whom the complaint is against. For example, if this were a sexual harassment complaint against a supervisor, the supervisor’s name would be displayed here.
;Name: This field identifies the employee by name. This field will be automatically completed when the Employee # field is filled.
;[Location|LOCATION_CODE]:If the complaint is on behalf of an entire location, that location may be entered in this field.
;[Unit|UNIT_CODE]: If the complaint is on behalf of an entire unit, that unit may be entered in this field.
;[Department|DEPARTMENT_CODE]: If the complaint is on behalf of an entire department, that department may be entered in this field.
At line 36 changed one line
;[Escalate Grievance|MMLCM]:This button can be used to escalate a complaint into a [grievance].
;[Escalate Grievance|MLLCM]:This button can be used to escalate a complaint into a [grievance|GRIEVANCE].
At line 39 changed 2 lines
[{Image src='40600ILCM_01.JPG' width='400' align='right'}]
!Record Complaints (ILCM) - Notes
----
!!Record Complaints (ILCM) - Notes
At line 42 changed 3 lines
;[Witness Information]:This field allows you to provide additional information about the witnesses involved. Incident_Witnesses_Info is an optional 4000-character alphanumeric field you may enter manually.
;[Union Notes]:This field allows you to provide additional information associated with the union involved. Union_Reference is an optional 4000-character alphanumeric field you may enter manually
;[Contact Information]:This field allows you to provide additional information from and associated with the union contract. Contact_Reference is an optional 4000-character alphanumeric field you may enter manually.
;[Witness Information|INCIDENT_WITNESSES]:This field allows you to provide additional information about the witnesses involved. Incident_Witnesses_Info is an optional 4000-character alphanumeric field you may enter manually.
;[Union Notes|UNION_REFERENCE]:This field allows you to provide additional information associated with the union involved.
;[Contract Information|CONTRACT_REFERENCE]:This field allows you to provide additional information from and associated with the union contract.
At line 46 changed 2 lines
[{Image src='40600ILCM_02.JPG' width='400' align='right'}]
!Record Complaints (ILCM) - Participants
----
At line 54 added 2 lines
!!Record Complaints (ILCM) - Participants
At line 50 changed 9 lines
;[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.
;[Description]: This field allows you to provide a short description of the participant. Description is an optional 50-character alphanumeric 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.
;[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.
;[Participant 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.
;[Participant Text|PARTICIPANT_INFO]:This field allows you to provide additional information about this participant. Participant_Info is an optional 4000-character alphanumeric field you may enter manually.
;[Participant Type|PARTICIPANT_TYPE]:This field identifies the type of participation for this individual.
;[Description|DESCRIPTION]: This field allows you to provide a short description of the participant.
;[Settlement Amount|SETTLEMENT_AMOUNT]:If the participant has received a settlement amount through this grievance, this amount may be listed here.
;Employee Name OR Contact Name:These fields display the identity of the participant. __You may only complete one of these fields.__
;:* For internal contacts, use the Employee Name field. The link to [IEID] ([P2K_HR_IDENTITIES]) is made through the [foreign key|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|FOREIGN KEY] [ECT_ID].
;Participant 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.
;[Participant Text|PARTICIPANT_TEXT]:This field allows you to provide additional information about this participant.
----
![Notes|Edit:Internal.ILCM]
[{InsertPage page='Internal.ILCM' default='Click to create a new notes page'}]
This page (revision-33) was last changed on 26-Nov-2021 10:22 by jmyersTop