| Node | Importance | Explain |
|---|
#ATTRACTION_ITEMS_DETAILS | Low | Each node explain the session reserved in EHORS system number of node should equal to total number of sessions selected for both package and/or individual. |
#ATTRACTION_ITEMS_DETAILS@BDIID | Low | Unique BDI ID mapped back to attraction selected, if 2 sessions selected for 1 attraction. I'l have 2 nodes with same BDIID |
#ATTRACTION_ITEMS_DETAILS@packageID | Low | Can be blank if its individual attraction, if isn't blank this node is for selected package |
#ATTRACTION_ITEMS_DETAILS@guestFolioIDHigh | This will only be a single node with child attribute of the sales reservation details like invoice number, receipt number from Ehors to indicated this booking are confirmed and revenue booked correctly when you have this node. |
#ATTRACTION_ITEMS@foInvoiceID | High | The invoice number from Ehors which later for the guest as one of the reference number to check his/her sales booking from Ehors when he is physically check-in |
#ATTRACTION_ITEMS@foInvoicePaymentID | Low | Payments details ID from Ehors to check if the payment sub-ledger are in Ehors or not |
#ATTRACTION_ITEMS@revenuePropertyID | Low | EHORS is an ERP system whereas each and every module follows the same hierarchy and system flow, | therefore therefore certain fields do not require a further explanation and are just needed to support to flow of EHORS. Can be | ignoreignored. |
#ATTRACTION_ | ITEMS_DETAILS@revenuePropertyIDITEMS@posGuestDummyID | High | This serves as official receipt number from Ehors which guest can request a reprint of the official receipt number from Ehors |
#ATTRACTION_ITEMS@outletID | Low | EHORS is an ERP system whereas each and every module follows the same hierarchy and system flow, | therefore therefore certain fields do not require a further explanation and are just needed to support to flow of EHORS. | Can Can be | ignoreignored. |
#ATTRACTION_ | ITEMS_DETAILS@reservationBDISessionIDITEMS@reservationID | LowHigh | Unique ID from EHORS | is an ERP system whereas each and every module follows the same hierarchy and system flow, therefore certain fields do not require a further explanation and are just needed to support to flow of EHORS. Can be ignore.
#ATTRACTION_ITEMS_DETAILS@posGuestID | Low | EHORS is an ERP system whereas each and every module follows the same hierarchy and system flow, therefore certain fields do not require a further explanation and are just needed to support to flow of EHORS. Can be ignore. |
#ATTRACTION_ITEMS | High | This node will give a booking details of the ticket sales like booking number, if successfully reserve in EHORS |
#ATTRACTION_ITEMS@reservationID | High | Unique ID from EHORS system when the booking are book in system but yet to confirm until payment information receive, thus this variable is crucial to be send and use on next command |
#ATTRACTION_ITEMS@guestFolioID | High | Unique ID from EHORS similar to reservation ID, but one reservation ID can contain many guest folio ID, unlike #ATTRACTION_ITEMS_DETAILS, this node are need for later command to confirm the booking |
#ATTRACTION_ITEMS@reservationDetailID | High | This is a mapping ID generated by EHORS similar usage like guest folio ID, this ID use to map related information of the booked and selected details. |
#ATTRACTION_ITEMS@tempWristbandNo | Low | Temporary wristband number / ticket ID created by EHORS and only needed by EHORS ticket sales back end program, can be ignore. |
#ATTRACTION_ITEMS@posGuestID | Low | Will be always empty, can be ignored |
#ATTRACTION_ITEMS@revenuePropertyID | Low | EHORS is an ERP system whereas each and every module follows the same hierarchy and system flow, therefore certain fields do not require a further explanation and are just needed to support to flow of EHORS. Can be ignore. |
#ATTRACTION_ITEMS@seqNo | Low | Will be always empty, can be ignoredsystem when the booking is in system. This to confirm from your given parameter are matched |
#TICKET_NODE | High | Number of nodes indicated how many guest folio or combinations of sales, example if 1 folio is booked with package for 2 pax and another folio booked with an individual for 3 pax, this node will appear 2x with 2 different guest folio ID |
#TICKET_NODE@guestFolioID | Low | Unique ID generated from Ehors from previous command [ P_TKT_NewSales ] Add New Ticket Sales, if the guest folio are confirmed correctly in the system this should matched the parameters guestFolioID_{x0} send to API |
#TICKET_NODE@mainTicketNo | High | Main ticket number from Ehors, last 5 digits (xxxxx) from the number will be the total number of guest for this guest folio combination. First 8 characters are uniquely generated from Ehors for each guest folio |
#TICKET_NODE@totalNoPax | High | A number of pax for this folio is a multiplier for each combinations sales of package and or attraction on the following node. Example if 1 package with additional individual attraction for 2 pax. It'll have 2x following sub child node |
#TICKET_NODE#TICKET_INFO_NODE | High | Sub child node from #TICKET_NODE is for each single tickets of the sales. if 4 pax from the combination package and or attraction on the single guest folio this will be 4 tickets generated |
#TICKET_NODE#TICKET_INFO_NODE@ticketQRNumber | High | Unique ticket number for guest to be used in physical property check-in and utilize the attraction and or package. This should be generated in standard QR format with the given serial for each ticket so your guest can use in the property. |
#TICKET_NODE#TICKET_INFO_NODE@generatedDate | Low | Date of the QR ticket number generated |
#TICKET_NODE#TICKET_INFO_NODE#TICKET_DETAIL_NODE | High | This node details for the ticket, so it'll indicate the breakdown and what are inclusive in this ticket, can have 1 or 2 only for this child node. Either a single package or "extra" or package + extra, a total maximum of this child node is only 2 and minimum 1 |
#TICKET_NODE#TICKET_INFO_NODE#TICKET_DETAIL_NODE@detailMode | High | Type of the breakdown details, ether a "PACKAGE:(PACKAGE_NAME)" = package in combinations of attractions / BDI or "EXTRA" = Individual attraction |
#TICKET_NODE#TICKET_INFO_NODE#TICKET_DETAIL_NODE#BDI_SESSION_NODE | High | Sessions node are the actual attraction, either in a combination of packages and or selected individual attraction, minimum one node from parent node #TICKET_DETAIL_NODE. Attributes of this node are the details for the attraction' session. |
#TICKET_NODE#TICKET_INFO_NODE#TICKET_DETAIL_NODE#BDI_SESSION_NODE@sessionFrom | High | The session's valid from time. Refer to node #PLANBOARD_ITEMS@startTime from [ G_ATT_Planboard ] Get Plan Board Availability |
#TICKET_NODE#TICKET_INFO_NODE#TICKET_DETAIL_NODE#BDI_SESSION_NODE@sessionUntil | High | The session's valid until time. Refer to node #PLANBOARD_ITEMS@endTime from [ G_ATT_Planboard ] Get Plan Board Availability |
#TICKET_NODE#TICKET_INFO_NODE#TICKET_DETAIL_NODE#BDI_SESSION_NODE@attractionName | High | Session name created from Ehors for the attraction |