1. Tables and Views for Sales and Fusion Service
  2. CN_TP_EVENT_LOGS_ALL_INT

CN_TP_EVENT_LOGS_ALL_INT

The table stores the information of the events during the deployer process run. The row can contain the plan object event or a payment object event or a role compensation plan assignment row event. The table aslo stores events that affect multiple compensation plans as seperate rows. Earlier this data was constructed and stored in cn_temp_gt table. This table stores this information to make deployer process resilient.

Details

  • Schema: FUSION

  • Object owner: CN

  • Object type: TABLE

  • Tablespace: INTERFACE

Primary Key

Name Columns

CN_TP_EVENT_LOGS_ALL_INT_PK

EVENT_LOG_OBJECT_ID, WORKER_ID

Columns

Name Datatype Length Precision Not-null Comments
EVENT_LOG_OBJECT_ID NUMBER 18 Yes Used as Unique Identifier for the table.
EVENT_LOG_ID NUMBER 18 Event information copied from cn_tp_event_logs_all table.
PRIMARY_OBJECT_ID NUMBER 18 Object here can be a compensation plan or a payment object or a compensation role assignment object copied from cn_tp_event_logs_all table. For the denormalized compensation plans records, -1000 will be populated. It will be populated as -2000 for denormalized rows of event type NOTIFY
SECONDARY_OBJECT_ID NUMBER 18 Secondary object id will contain Compensation Plan Id for the plan related compenstion plan events create as part of denormalization of the plan object event affecting multiple plans Secondary object id will contain Role Id for Role compensation Plan event. For the all other events and direct event from logs table -1000 will be populated. It will be populated as -2000 for denormalized rows of event type NOTIFY
EVENT_TYPE VARCHAR2 30 Will represent whether a Plan object event or a Role compensation plan assignment event or a payment event . A different event type namely,plan event related compenstion plan is used to identify denormalized rows of the plan object event affecting multiple plans. An event type namely Notify is used to identify the denormalized participant information affected by the event.
EVENT_NAME VARCHAR2 30 Event name will be taken from the cn_tp_event_logs_all table. Will be null for denormalized event cp association.
REQUEST_ID NUMBER 18 Enterprise Service Scheduler: indicates the request ID of the job that created or last updated the row.
ORG_ID NUMBER 18 Yes Indicates the identifier of the business unit associated to the row.
DEPLOY_STATUS VARCHAR2 30 Column used to mark if a event is already processed by deployer in its run to populate the srp tables or payment tables. It will be populated as null for denormalized rows of event type NOTIFY
NOTIFY_LOG_STATUS VARCHAR2 30 Column used to mark if a event is already processed by notify_log process of the deployer. It will be populated as INCOMPLETE for denormalized rows of event type NOTIFY
CREATED_BY VARCHAR2 64 Yes Who column: indicates the user who created the row.
OBJECT_NUMBER VARCHAR2 30 The column will store the puid value of the object the event represents.
CREATION_DATE TIMESTAMP Yes Who column: indicates the date and time of the creation of the row.
LAST_UPDATED_BY VARCHAR2 64 Yes Who column: indicates the user who last updated the row.
LAST_UPDATE_DATE TIMESTAMP Yes Who column: indicates the date and time of the last update of the row.
LAST_UPDATE_LOGIN VARCHAR2 32 Who column: indicates the session login associated to the user who last updated the row.
OBJECT_VERSION_NUMBER NUMBER 9 Yes Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.
JOB_DEFINITION_NAME VARCHAR2 100 Enterprise Service Scheduler: indicates the name of the job that created or last updated the row.
JOB_DEFINITION_PACKAGE VARCHAR2 900 Enterprise Service Scheduler: indicates the package name of the job that created or last updated the row.
WORKER_ID NUMBER Yes Worker Number that will process this row. This worker number will belong between a range depending on the organization.
PARTICIPANT_ID NUMBER 18 Participant for whom notify logs needs to be populated. Will be only populated for event type as NOTIFY
PERIOD_ID NUMBER 18 Period for which the event is logged. Will be only populated for event type as NOTIFY
REVERT_STATE VARCHAR2 30 Revert State of the event. Will be only populated for event type as NOTIFY possible values are ROLLUP,CALCULATION and ELIGIBLE
SRP_COMP_PLAN_ID NUMBER 18 Points to cn_srp_comp_plans_all. Will be only populated for event type as NOTIFY and REVERT TYPE as ELIGIBLE.
PLAN_COMPONENT_ID NUMBER 18 Points to cn_plan_components_all .Will be only populated for event type as NOTIFY and REVERT TYPE as ELIGIBLE.
START_DATE DATE Period start date. Will be only populated for event type as NOTIFY
END_DATE DATE Period end date. Will be only populated for event type as NOTIFY.
BATCH_NUMBER NUMBER 18 Batch Identifier. Will be only populated for event type as NOTIFY.
ERROR_REASON VARCHAR2 240 The column will display the reason the event failed while processing.

Indexes

Index Uniqueness Tablespace Columns
CN_TP_EVENT_LOGS_ALL_INT_N1 Non Unique FUSION_TS_INTERFACE SECONDARY_OBJECT_ID, WORKER_ID
CN_TP_EVENT_LOGS_ALL_INT_N2 Non Unique FUSION_TS_INTERFACE EVENT_LOG_ID, WORKER_ID
CN_TP_EVENT_LOGS_ALL_INT_N3 Non Unique Default WORKER_ID, PARTICIPANT_ID, PERIOD_ID
CN_TP_EVENT_LOGS_ALL_INT_U1 Unique FUSION_TS_INTERFACE EVENT_LOG_OBJECT_ID, WORKER_ID