Ticket Request
In ScopeTechnical: TICKET_REQUEST | ID: OR-MFCS-TICKET_REQUEST
This table will be used to communicate to the batch program which prints tickets. This table is used to communicate the types of tickets which need to be printed and…
See how this object fits into Store Operations
Review the broader sequencing and dependencies for this domain
Migration Details
- Complexity
- Medium
- Sequencing
- Stage 2
- Typical Sources
- ERPLegacy
Target Structure
- Load Approach
- Table
- Target Objects
- TICKET_REQUEST
Field Definitions(17)
Rules & Considerations(50)
Sample Load Data(4)
| _scenario | IDRPK | QTYR | ITEMRPK | LOCATIONR | LOC_TYPER | LAST_UPDATE_IDR | TICKET_TYPE_IDRPK | CREATE_DATETIMER | PRINT_ONLINE_INDR | LAST_UPDATE_DATETIMER | ORDER_NO | MULTI_UNITS | UNIT_RETAIL | PRICE_CHANGE_ID | COUNTRY_OF_ORIGIN | MULTI_UNIT_RETAIL | PRICE_CHANGE_EFF_DATE |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| default | 1 | 11.0000 | Ticket Request-001 | 1 | Ticket Request-001 | MIG_USER | STD-TICKET_REQ-001 | 2026-01-01 | Ticket Request-001 | 2026-01-01 | 2 | 11.0000 | 11.0000 | 1000000001 | Ticket Request-001 | 11.0000 | 2026-01-01 |
default
- IDRPK
- 1
- QTYR
- 11.0000
- ITEMRPK
- Ticket Request-001
- LOCATIONR
- 1
- LOC_TYPER
- Ticket Request-001
- LAST_UPDATE_IDR
- MIG_USER
- TICKET_TYPE_IDRPK
- STD-TICKET_REQ-001
- CREATE_DATETIMER
- 2026-01-01
- PRINT_ONLINE_INDR
- Ticket Request-001
- LAST_UPDATE_DATETIMER
- 2026-01-01
- ORDER_NO
- 2
- MULTI_UNITS
- 11.0000
- UNIT_RETAIL
- 11.0000
- PRICE_CHANGE_ID
- 1000000001
- COUNTRY_OF_ORIGIN
- Ticket Request-001
- MULTI_UNIT_RETAIL
- 11.0000
- PRICE_CHANGE_EFF_DATE
- 2026-01-01