HCR_EM_EVNT_LOG (SQL Table)	Index Back
Event Manager - Event Log HCR Event Manager - This table contains a row for every Event that has been raised, for those Event Types that have the "Log" flag enabled in the Registry.

HCR_EM_EVNT_LOG

(SQL Table)

Event Manager - Event Log

HCR Event Manager - This table contains a row for every Event that has been raised, for those Event Types that have the "Log" flag enabled in the Registry.

Parent Record Of HCR_EM_HNDL_LOG

# PeopleSoft Field Name PeopleSoft Field Type Database Column Type Description

1 MSGNODENAME Character(30) VARCHAR2(30) NOT NULL Application Message Node Name. Name of the Application Message Node Definition. (see PSMSGNODEDEFN).

2 HCR_EM_EVENT_ID Number(10,0) DECIMAL(10) NOT NULL HCR Event Manager - Raw Binary serial number identifying a particular Event that has been raised in the framework.

3 HCR_EM_EVENT_NAME Character(30) VARCHAR2(30) NOT NULL HCM Event Manager - Event Name (corresponds to Event Handler app class names in HCR_EVENT_MANAGER:Events).

4 CHNLNAME Character(30) VARCHAR2(30) NOT NULL Channel Name (see PSCHNLDEFN).

5 HCR_EM_DTTM DateTime(26) TIMESTAMP HCR Event Manager - Date Time Stamp.

6 HCR_EM_PROC_DTTM DateTime(26) TIMESTAMP HCM Event Manager - indicates the date and time that the event was processed. That is - the local date and time at which the Event Manager framework began executing local handlers. Generally, this is the same Date/Time at which the Event is raised - so this field doesn't have much significance in database in which the Event is raised. For remote Events, this represents the local date and time that the Event Message was received, and the IB subscription handler began processing the message. The difference between this Data/Time and the Date/Time that the Event was raised represents the Remote/Local IB time lag. Be aware that these two Date/Time stamps could be in different timezones.
Default Value: %DateTime

7 OPRID Character(30) VARCHAR2(30) NOT NULL A user's ID (see PSOPRDEFN).

8 HCR_EM_PROC_STAT Character(1) VARCHAR2(1) NOT NULL HCM Event Manager - Process status of an event. (P)ending, (S)tarted or (C)ompleted. Pending status normally relates to Asyncrhonous events for which the message subscription has not yet executed.
C=Complete
P=Pending
S=Started
Default Value: P

9 HCR_EM_KEY_DATA Long Character CLOB HCR Event Manager - Contains the Event Keys, coded as XML.

#	PeopleSoft Field Name	PeopleSoft Field Type	Database Column Type	Description
1	MSGNODENAME	Character(30)	VARCHAR2(30) NOT NULL	Application Message Node Name. Name of the Application Message Node Definition. (see PSMSGNODEDEFN).
2	HCR_EM_EVENT_ID	Number(10,0)	DECIMAL(10) NOT NULL	HCR Event Manager - Raw Binary serial number identifying a particular Event that has been raised in the framework.
3	HCR_EM_EVENT_NAME	Character(30)	VARCHAR2(30) NOT NULL	HCM Event Manager - Event Name (corresponds to Event Handler app class names in HCR_EVENT_MANAGER:Events).
4	CHNLNAME	Character(30)	VARCHAR2(30) NOT NULL	Channel Name (see PSCHNLDEFN).
5	HCR_EM_DTTM	DateTime(26)	TIMESTAMP	HCR Event Manager - Date Time Stamp.
6	HCR_EM_PROC_DTTM	DateTime(26)	TIMESTAMP	HCM Event Manager - indicates the date and time that the event was processed. That is - the local date and time at which the Event Manager framework began executing local handlers. Generally, this is the same Date/Time at which the Event is raised - so this field doesn't have much significance in database in which the Event is raised. For remote Events, this represents the local date and time that the Event Message was received, and the IB subscription handler began processing the message. The difference between this Data/Time and the Date/Time that the Event was raised represents the Remote/Local IB time lag. Be aware that these two Date/Time stamps could be in different timezones. Default Value: %DateTime
7	OPRID	Character(30)	VARCHAR2(30) NOT NULL	A user's ID (see PSOPRDEFN).
8	HCR_EM_PROC_STAT	Character(1)	VARCHAR2(1) NOT NULL	HCM Event Manager - Process status of an event. (P)ending, (S)tarted or (C)ompleted. Pending status normally relates to Asyncrhonous events for which the message subscription has not yet executed. C=Complete P=Pending S=Started Default Value: P
9	HCR_EM_KEY_DATA	Long Character	CLOB	HCR Event Manager - Contains the Event Keys, coded as XML.