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

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
39 26-Nov-2021 10:22 16 KB mmcfarland to previous
38 26-Nov-2021 10:22 15 KB mmcfarland to previous | to last
37 26-Nov-2021 10:22 15 KB mmcfarland to previous | to last
36 26-Nov-2021 10:22 14 KB mmcfarland to previous | to last
35 26-Nov-2021 10:22 14 KB mmcfarland to previous | to last
34 26-Nov-2021 10:22 13 KB rforbes to previous | to last
33 26-Nov-2021 10:22 13 KB jmyers to previous | to last
32 26-Nov-2021 10:22 13 KB jmyers to previous | to last
31 26-Nov-2021 10:22 13 KB jmyers to previous | to last EMAIL_ADDRESS ==> EMAIL_ADDRESS(Disambiguation)
30 26-Nov-2021 10:22 13 KB JMyers to previous | to last
29 26-Nov-2021 10:22 14 KB JMyers to previous | to last
28 26-Nov-2021 10:22 17 KB JMyers to previous | to last
27 26-Nov-2021 10:22 17 KB JMyers to previous | to last
26 26-Nov-2021 10:22 17 KB JMyers to previous | to last
25 26-Nov-2021 10:22 19 KB JMyers to previous | to last
24 26-Nov-2021 10:22 19 KB JMyers to previous | to last
23 26-Nov-2021 10:22 19 KB JMyers to previous | to last
22 26-Nov-2021 10:22 20 KB RForbes to previous | to last
21 26-Nov-2021 10:22 20 KB RForbes to previous | to last

Page References

Incoming links Outgoing links
IHIN
IHIN

Version management

Difference between version and

At line 8 changed 2 lines
;[Entity|ENTITY_CODE]: This field identifies the entity associated with this incident. Entity from [IDEN] ([P2K_CM_ENTITIES]) is a mandatory field you must fill through the LOV.
;[Incident Code|INCIDENT_CODE]: This field displays a user-defined code that uniquely identifies the incident. Incident_Code is a mandatory 16-character alphanumeric field you may fill manually.
;[Entity|ENTITY_CODE]: This field identifies the entity associated with this incident.
;[Incident Code|INCIDENT_CODE]: This field displays a user-defined code that uniquely identifies the incident.
At line 16 changed 6 lines
;[Incident Date|INCIDENT_DATE]: This field indicates the date the incident occurred. Date_of_Incident is an optional date field you must fill either manually or using the calendar icon (F9).
;[Incident Time|TIME_OF_INCIDENT]: This field will display the time the incident occurred. Time_Of_Incident is an optional field you may fill manually. Please note that unless indicated otherwise, the time will default to ‘AM’. EG 4:30 PM must be inputted as either ‘430 PM’ or ‘1630’.
;[Incident Status|INCIDENT_STATUS]: This field displays the current status of the incident. Incident_Status is an optional field you may fill from the fixed lexicon [X_INCIDENT_STATUS].
;[Incident Type|INCIDENT_TYPE]: This field displays the nature of the incident. Incident_Type is an optional field you may fill from the fixed lexicon [X_INCIDENT_TYPE].
;[Incident Category|INCIDENT_CATEGORY]: This field allows you to further categorize the incident. Incident_Category is an optional field you may fill from the user-defined lexicon [X_INCIDENT_CATEGORY].
;[Incident Reason|INCIDENT_REASON]: This field allows you to identify a reason for the incident, if applicable. Incident_Reason is an optional field you may fill from the fixed lexicon [X_INCIDENT_REASON].
;[Incident Date|INCIDENT_DATE]: This field indicates the date the incident occurred.
;[Incident Time|TIME_OF_INCIDENT]: This field will display the time the incident occurred.
;:%%information Please note that unless indicated otherwise, the time will default to ‘AM’. EG 4:30 PM must be inputted as either ‘430 PM’ or ‘1630’.%%
;[Incident Status|INCIDENT_STATUS]: This field displays the current status of the incident.
;[Incident Type|INCIDENT_TYPE]: This field displays the nature of the incident.
;[Incident Category|INCIDENT_CATEGORY]: This field allows you to further categorize the incident.
;[Incident Reason|INCIDENT_REASON]: This field allows you to identify a reason for the incident, if applicable.
At line 24 changed one line
;Report by Employee Or by Contact: These fields will identify the individual who reported the incident. This is an optional field you may fill manually or retrieve from the LOV provided.
;Report by Employee Or by Contact: These fields will identify the individual who reported the incident.
At line 28 changed 4 lines
;[Date Reported |DATE_REPORTED]: This field displays the date the incident was reported. Date_Reported is an optional field you may fill either manually or using the calendar icon (F9).
;[Time Reported|TIME_REPORTED]: This field displays the time the incident was reported. Time_Reported is an optional field you may fill manually. Please note that unless indicated otherwise, the time will default to ‘AM’. EG 4:30 PM must be inputted as either ‘430 PM’ or ‘1630’.
;[How Reported|HOW_REPORTED]: This field displays the communication method used to report the incident. How_Reported is an optional field you may fill from the fixed lexicon [X_HOW_REPORTED].
;[Anonymous|ANONYMOUS]: If this toggle is ON, the incident was reported anonymously. Anonymous is an optional toggle field.
;[Date Reported |DATE_REPORTED]: This field displays the date the incident was reported.
;[Time Reported|TIME_REPORTED]: This field displays the time the incident was reported.
;:%%information Please note that unless indicated otherwise, the time will default to ‘AM’. EG 4:30 PM must be inputted as either ‘430 PM’ or ‘1630’.%%
;[How Reported|HOW_REPORTED]: This field displays the communication method used to report the incident.
;[Anonymous|ANONYMOUS]: If this toggle is ON, the incident was reported anonymously.
At line 34 changed 7 lines
;[Location|LOCATION_CODE]: This field will identify the location of the incident. For instance, if an entity has two or three plants, this field will identify which plant is incident spot. Location from [IDLN] ([P2K_CM_LOCATIONS]) is a mandatory field you must fill through the LOV
;[Place of Incident|PLACE_OF_INCIDENT]: This field allows you to further define the exact location of the incident, by room, station, etc. Place_of_Incident is an optional 50-character alphanumeric field you may fill manually. Once the ‘Location’ field has been selected, any information defined on the [IDLN] table (e.g. address, phone number, email address), will default into the fields below. These fields can, however, be edited.
;[Address Line 1|ADDRESS_LINE_1]: This field displays the exact address of the incident. Address_Line_1 is an optional 50-character alphanumeric field you may fill manually.
;[Address Line 2|ADDRESS_LINE_2]: This field displays further information for the exact address of the incident. Address_Line_2 is an optional 50-character alphanumeric field you may fill manually.
;[Locality|LOCALITY]: This field will display the town or city of the incident. Locality is an optional 50-character alphanumeric field you may fill manually.
;[State/Province|STATE_PROVINCE_CODE]: This field allows you to define the state or province of the incident. State_Province from [IDSP] ([P2K_CM_STATE_PROVINCES]) is a mandatory field you must fill through the LOV.
;[Zip Postal|ZIP_POSTAL]: This field will display the zip or postal code for the address of the incident location. Zip_Postal is an optional 16-character alphanumeric field you may fill manually.
;[Location|LOCATION_CODE]: This field will identify the location of the incident. For instance, if an entity has two or three plants, this field will identify which plant is incident spot.
;[Place of Incident|PLACE_OF_INCIDENT]: This field allows you to further define the exact location of the incident, by room, station, etc.
;:Once the ‘Location’ field has been selected, any information defined on the [IDLN] table (e.g. address, phone number, email address), will default into the fields below. These fields can, however, be edited.
;[Address Line 1|ADDRESS_LINE_1]: This field displays the exact address of the incident.
;[Address Line 2|ADDRESS_LINE_2]: This field displays further information for the exact address of the incident.
;[Locality|LOCALITY]: This field will display the town or city of the incident.
;[State/Province|STATE_PROVINCE_CODE]: This field allows you to define the state or province of the incident.
;[Zip Postal|ZIP_POSTAL]: This field will display the zip or postal code for the address of the incident location.
At line 43 changed 5 lines
;[Phone #|PHONE_NUMBER]: This field will display the phone number of the incident location. Phone_Number is an optional 20-character alphanumeric field you may fill manually.
;[Phone Extension|PHONE_EXTENSION]: If there is a phone extension for the incident location, that number will be displayed here. Phone_Extension is an optional 16-character alphanumeric field you may fill manually.
;[Fax #|FAX_NUMBER]: If there is a fax number for the incident location, that number will be displayed here. Fax_Number is an optional 20-character alphanumeric field you may fill manually.
;[Email Address|EMAIL_ADDRESS]: If there is an email address for the incident location, you may input that address in this field. Email_Address is an optional 50-character alphanumeric field you may fill manually.
;[Notification List|NOTIFICATION_LIST]: This field displays all those who were notified of the incident. Notification_List is an optional 4000-character alphanumeric field you may fill manually.
;[Phone #|PHONE_NUMBER]: This field will display the phone number of the incident location.
;[Phone Extension|PHONE_EXTENSION]: If there is a phone extension for the incident location, that number will be displayed here.
;[Fax #|FAX_NUMBER]: If there is a fax number for the incident location, that number will be displayed here.
;[Email Address|EMAIL_ADDRESS]: If there is an email address for the incident location, you may input that address in this field.
;[Notification List|NOTIFICATION_LIST]: This field displays all those who were notified of the incident.
This page (revision-39) was last changed on 26-Nov-2021 10:22 by mmcfarlandTop