The table below shows the data relationship between PMI data elements/fields (target) and corresponding source data elements/fields (source).
You will find the transformation/load rules meant to explain any programmatic manipulation and calculation applied in the adapter to get the desired data format and/or result in the PMI staging table where such have been applicable.
An example of the source file data, format and structure is also attached below the table.
This table will be updated whenever the source file or the adapter in question are changed throughout the interface life-cycle.
| Interface name incl. version | Comment |
|---|---|
| Delphi_OTB_V001 | File name pattern like: Delhi_OTB*.csv |
| DelphiEvent_OTB_V001 | File name pattern like: Delphi_event*.* |
| Column | Name |
|---|---|
| 1 | Date |
| 2 | Satus |
| 3 – 14 | Not used |
| 15 | SingleRooms |
| 16 – 31 | SingleRate |
| Column | Name |
|---|---|
| 1 – 3 | Not used |
| 4 | SegmentCode |
| 5 | Date |
| 6 | Cover1 |
| 7 | Cover2 |
| 8 | Beverage1 |
| 9 | Beverage2 |
| 10 | Food1 |
| 11 | Food2 |
| 12 – 15 | Not used |
| 16 | Rental |
| # | PMI data element (target) | Description | Mandatory / Optional | Data transformation/load rules | Planday data element (source) | Comment |
|---|---|---|---|---|---|---|
| 1 | Date | OTB Date | M | Directly mapped from the source file | Date | In the format yyyy-MM-dd hh:mm:ss |
| 2 | Department | Name or ID of the department within the property | O | Not used | ||
| 3 | Account | ID or name of the administrative category | O | Not used | ||
| 4 | Description | Description | O | Not used | Market code: DELPHI | |
| 5 | Revenue | Revenue | M | Directly mapped from the source file | SingleRate | Only where Status = 3 |
| 6 | Room Nights | Room nights | M | Directly mapped from the source file | SingleRooms | Only where Status = 3 |
| 7 | Room Nights Tentative | Tentative room nights | M | Directly mapped from the source file | SingleRooms | Only where Status = 2 |
| # | PMI data element (target) | Description | Mandatory / Optional | Data transformation/load rules | Planday data element (source) | Comment |
|---|---|---|---|---|---|---|
| 1 | Date | OTB Date | M | Directly mapped from the source file | Date | In the format yyyy-MM-dd hh:mm:ss |
| 2 | Department | Name or ID of the department within the property | O | Not used | ||
| 3 | Account | ID or name of the administrative category | O | Not used | ||
| 4 | Description | Description | O | Directly mapped from the source file | Market code: {Code}: {SegmentCode} | {Code}: B for Beverage (Covers and Revenue) F for food R for Rental |
| 5 | Revenue | Revenue | M | Directly mapped from the source file | Food1 or Food2 | For food food1 if it is larger than 0, otherwise food2 |
| 5 | Revenue | Revenue | M | Directly mapped from the source file | Beverage1 or Beverage2 | For Beverage Beverage1 if it is larger than 0, otherwise Beverage2 |
| 5 | Revenue | Revenue | M | Directly mapped from the source file | Rental | For Rental |
| 6 | Covers/Units | Covers/Units | M | Directly mapped from the source file | Cover1 or Cover2 | Cover1 if it is larger than 0, otherwise Cover2 |
Download an example of the source file format:
- For interface Delphi_OTB_V001: File:Delphi OTB V001.zip
- For interface Delphi_Event_OTB_V001: No file available