Historical lost sales
In ScopeTechnical: historical_lost_sales | ID: RELEX-RA-HISTORICAL_LOST_SALES
In addition to be nice to have for mentioned modules, lost sales are useful for KPIs & reporting. To calculate other metrics e.g. lost sales rows from history.
See how this object fits into Sales Demand
Review the broader sequencing and dependencies for this domain
Migration Details
- Complexity
- Medium
- Sequencing
- Stage 2 - Demand Signals
- Typical Sources
- ERPLegacy
Target Structure
- Load Approach
- Table
- Target Objects
- transactions
Field Definitions(5)
Rules & Considerations(12)
Row Count
Field Mapping
Data Accuracy
Sample Load Data(4)
| _scenario | dateR | typeR | productR | locationR | quantityR | time | value | transaction_uid |
|---|---|---|---|---|---|---|---|---|
| default | 2021-05-31 | LOST_SALE | 58974 | 100 | 10 | 12:00:00 | 5 | TID12345 |
| default | 2021-06-01 | LOST_SALE-ALT | 58974-ALT | 100-ALT | 11 | 12:00:00-ALT | 6 | TID12345-ALT |
| default | 2021-06-02 | LOST_SALE-EDGE | 58974-EDGE | 100-EDGE | 12 | 12:00:00-EDGE | 7 | TID12345-EDGE |
default
- dateR
- 2021-05-31
- typeR
- LOST_SALE
- productR
- 58974
- locationR
- 100
- quantityR
- 10
- time
- 12:00:00
- value
- 5
- transaction_uid
- TID12345
default
- dateR
- 2021-06-01
- typeR
- LOST_SALE-ALT
- productR
- 58974-ALT
- locationR
- 100-ALT
- quantityR
- 11
- time
- 12:00:00-ALT
- value
- 6
- transaction_uid
- TID12345-ALT
default
- dateR
- 2021-06-02
- typeR
- LOST_SALE-EDGE
- productR
- 58974-EDGE
- locationR
- 100-EDGE
- quantityR
- 12
- time
- 12:00:00-EDGE
- value
- 7
- transaction_uid
- TID12345-EDGE