The Input Data Model
The input data is expected to be provided in a well-defined schema. The event log must contain only the fields specified by the schema. For any additional data about the events and cases, please use the event or case dimensions.
The data may be provided as (external) tables or views.
The Event Log
Columns which are not marked as mandatory can be omitted or contain NULL values.
| Field Name | TYPE | Mandatory | Description |
|---|---|---|---|
| EL_LINK | VARCHAR | (✓)¹ | Unique Identification used to cluster related OCPM-Cases |
| EL_CASE_ID | VARCHAR | ✓ | Unique Case identification (z.B. Purchase Order, Sales Order). |
| EL_EVENT_ID | VARCHAR | Unique Event identification within a case | |
| EL_ACTIVITY_TYPE | VARCHAR | ✓ | Name of the activity/event |
| EL_ACTIVITY_TYPE_ID | NUMBER | Technical ID of the activity/event | |
| EL_OBJECT_TYPE | VARCHAR | (✓)¹ | Used to decide which CaseID belongs to which type of object. |
| EL_PRINCIPAL_OBJECT_TYPE | VARCHAR | (✓)¹ | Used to keep the information from which object an activity was originally caused |
| EL_ACTIVITY_START_TIMESTAMP | TIMESTAMP_NTZ | (✓)² | Start timestamp of activity If it is not differentiated between begin and end timestamp of an activity use EL_ACTIVITY_TIMESTAMP instead. |
| EL_ACTIVITY_END_TIMESTAMP | TIMESTAMP_NTZ | (✓)² | End timestamp of activity If it is not differentiated between begin and end timestamp of an activity use EL_ACTIVITY_TIMESTAMP instead. |
| EL_ACTIVITY_TIMESTAMP | TIMESTAMP_NTZ | (✓)² | Timestamp of an activity if no distinction is made between start and end. |
| EL_ACTIVITY_ORIGIN_ID | VARCHAR | (✓)¹ | ID for the origin of the event. Example: IDs that reference the event in the SAP tables specified in EL_ACTIVITY_ORIGIN. |
| EL_ACTIVITY_ORIGIN | VARCHAR | Reference to the origin of the events Example: Tables in SAP concatenated from which the event originates. | |
| EL_USERNAME | VARCHAR | This fields holds the user who is responsible for completing an activity. It can also be a technical user, if the activity is automated. | |
| EL_GEOFIELD | VARCHAR | Contains geographic information, like country, region, city, co-ordinates, addresses, or other spatial data. | |
| EL_RESOURCE | VARCHAR | Name of a Resource used to mine a resource log | |
| EL_REAL_USER | NUMBER(1,0) BOOLEAN | Flag which marks an event as executed by a real user. Can also be derived from the EL_USERNAME field by configuring a pattern in the mpmX Snowflake App like *Robot*,System | |
| EL_REWORK_EVENT | NUMBER(1,0) BOOLEAN | Flag which marks an event as rework event. Can also be derived from the EL_ACTIVITY_TYPE field by configuring a pattern in the mpmX Snowflake App like *Delete*,*Change*,*Cancel* |
¹ Mandatory in OCPM event logs
² Mandatory, define either EL_ACTIVITY_TIMESTAMP or both EL_ACTIVITY_START_TIMESTAMP and EL_ACTIVITY_END_TIMESTAMP
See also:
The Case Dimensions
| Field Name | TYPE | Description |
|---|---|---|
| KEY_CASE_ID | VARCHAR | Unique Case identification, relates to EL_CASE_ID in event log |
CD_<any CaseDimension> | ANY | Any columns starting with CD_ (examples: CD_CaseDimension1-5 and CD_CaseValue1-2)Requires a mapping in the configuration so that we can continue to analyze CaseDimension1-5 and CaseValue1-2 in Qlik Sense. |
The Event Dimensions
| Field Name | TYPE | Description |
|---|---|---|
| KEY_EVENT_ID | VARCHAR | Unique Event identification within a case, relates to EL_EVENT_ID in event log |
ED_<any EventDimension> | ANY | Any columns starting with ED_ (examples: ED_EventDimension1-3 and ED_EventValue1-2)Requires a mapping in the configuration so that we can continue to analyze EventDimension1-3 and EventValue1-2 in Qlik Sense. |