refund_events
The steps each refund request went through. An event log for process mining. One row is one step of one request.
- One row is
- one step of one request
- Columns
- 5
- Rows in Sample
- 4,517
- Rows in Standard
- 46,532
- Rows in Full
- 461,808
Columns
| Column | Type | What it holds | Values or range |
|---|---|---|---|
| event_idkey | integer | Unique id for the row. | |
| refund_id | integer | Links to refunds. | |
| activity | text | The step. | Approved; Documentation check; Information received; Manager approval; More information requested; Payment issued; Rejected; Request received; Supervisor review |
| occurred_at | date and time | When the step happened. | 2018-01-01 08:26 to 2026-01-15 07:52 |
| handled_by_team | text | Team that did the step. | Finance; Guest Services; Guest Services Management; Refund Operations |
How it connects
This table points to
- refund_id matches refunds.refund_id
First five rows
Taken from the Sample size, exactly as they appear in the file. Empty cells are empty in the data.
| event_id | refund_id | activity | occurred_at | handled_by_team |
|---|---|---|---|---|
| 90000145 | 80000044 | Request received | 2018-01-03 14:26:38 | Guest Services |
| 90000146 | 80000044 | Approved | 2018-01-03 14:30:11 | Refund Operations |
| 90000147 | 80000044 | Payment issued | 2018-01-03 14:30:59 | Finance |
| 90001268 | 80000369 | Request received | 2018-01-15 12:59:59 | Guest Services |
| 90001269 | 80000369 | Documentation check | 2018-01-15 16:25:30 | Refund Operations |