EHORS API
Page tree

Versions Compared

Old Version 15

changes.mady.by.user Charlie Seah

Saved on

compared with

New Version 16

changes.mady.by.user Charlie Seah

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagexml
titleSuccess XML Sample
linenumberstrue
<?xml version="1.0" encoding="utf-8"?>
<SCRIPT_RESULT>
  <RESULT>
    <ATTRACTION_ITEMS_DETAILS BDIID="CB55" packageID="" guestFolioID="HAB461171" revenuePropertyID="2" reservationBDISessionID="HAB668752" posGuestID=""/>
    <ATTRACTION_ITEMS_DETAILS BDIID="BB600" packageID="" guestFolioID="HAB461171" revenuePropertyID="2" reservationBDISessionID="HAB668753" posGuestID=""/>
    <ATTRACTION_ITEMS_DETAILS BDIID="BB600" packageID="" guestFolioID="HAB461171" revenuePropertyID="2" reservationBDISessionID="HAB668754" posGuestID=""/>
    <ATTRACTION_ITEMS_DETAILS BDIID="CB71" packageID="" guestFolioID="HAB461171" revenuePropertyID="2" reservationBDISessionID="HAB668755" posGuestID=""/>
    <ATTRACTION_ITEMS_DETAILS BDIID="CB13" packageID="BB5547" guestFolioID="HAB461171" revenuePropertyID="2" reservationBDISessionID="HAB668756" posGuestID=""/>
    <ATTRACTION_ITEMS_DETAILS BDIID="CB11" packageID="BB5547" guestFolioID="HAB461171" revenuePropertyID="2" reservationBDISessionID="HAB668757" posGuestID=""/>
    <ATTRACTION_ITEMS_DETAILS BDIID="BB15" packageID="BB5547" guestFolioID="HAB461171" revenuePropertyID="2" reservationBDISessionID="HAB668758" posGuestID=""/>
    <ATTRACTION_ITEMS_DETAILS BDIID="BB10" packageID="BB5547" guestFolioID="HAB461171" revenuePropertyID="2" reservationBDISessionID="HAB668759" posGuestID=""/>
    <ATTRACTION_ITEMS_DETAILS BDIID="BB17" packageID="BB5547" guestFolioID="HAB461171" revenuePropertyID="2" reservationBDISessionID="HAB668760" posGuestID=""/>
    <ATTRACTION_ITEMS_DETAILS BDIID="BB12" packageID="BB5547" guestFolioID="HAB461171" revenuePropertyID="2" reservationBDISessionID="HAB668761" posGuestID=""/>
    <ATTRACTION_ITEMS reservationID="HAB181155" guestFolioID="HAB461171" reservationDetailID="HAB246206" tempWristbandNo="605434177_52425a43" posGuestID="" revenuePropertyID="2" seqNo=""/>
  </RESULT>
  <SCRIPT_STATUS>SUCCESS</SCRIPT_STATUS>
</SCRIPT_RESULT>

XML Node Explain

NodeImportanceExplain
#ATTRACTION_ITEMS_DETAILSLowEach 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@BDIIDLowUnique 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@packageIDLowCan be blank if its individual attraction, if isn't blank this node is for selected package
#ATTRACTION_ITEMS_DETAILS@guestFolioIDLow

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@revenuePropertyIDLowEHORS 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@reservationBDISessionIDLow
#ATTRACTION_ITEMS_DETAILS@posGuestIDLow#ATTRACTION_ITEMSHigh#ATTRACTION_ITEMS@reservationIDHigh#ATTRACTION_ITEMS@guestFolioIDHigh#ATTRACTION_ITEMS@reservationDetailIDHigh#ATTRACTION_ITEMS@tempWristbandNoLow#ATTRACTION_ITEMS@posGuestIDLow#ATTRACTION_ITEMS@revenuePropertyIDLow#ATTRACTION_ITEMS@seqNoLow
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@posGuestIDLowEHORS 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_ITEMSHighThis node will give a booking details of the ticket sales like booking number, if successfully reserve in EHORS
#ATTRACTION_ITEMS@reservationIDHighUnique 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@guestFolioIDHighUnique 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@reservationDetailIDHighThis 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@tempWristbandNoLowTemporary wristband number / ticket ID created by EHORS and only needed by EHORS ticket sales back end program, can be ignore.
#ATTRACTION_ITEMS@posGuestIDLowWill be always empty, can be ignored
#ATTRACTION_ITEMS@revenuePropertyIDLowEHORS 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@seqNoLowWill be always empty, can be ignored