Posting (Simple)
All interfaces can send also operations from their system to SIHOT. A general function is e.g. the posting of services.
Operationcode: PS
PS
Direction
IF Partner → SIHOT
Message
Example of a charge to a room number. This is an example for the use of the pool by the guest in room 102.
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4714</TN>
<OC>PS</OC>
<HN>4711</HN>
<RN>102</RN>
<PT>0</PT>
<TXT>Use of the pool, (31.05.2002 at 13:20)</TXT>
<BD>2002-05-31T13:20:00</BD>
<PPU>5.00</PPU>
</SIHOT-Document>
Attributes Message
| Attribute | Denotation | Type |
|---|---|---|
| OC | Action Type:PS = Posting Simple | String |
| TXT | Text | String |
| BD | Booking Date | Date Time |
| PT | Posting Type | Int |
| CT | Call Type | Int |
| PPU | Price per unit (including taxes, vat, …) in hotel currency | BCD |
| UN | Units. If unit is not given, we assume 1. | Long |
| OUTLET | Outlet where the posting is coming from | Long |
| CASHIER | Cashier who processed the posting | Long |
| TICKETNO | Ticket number from the external system | Long |
| PCIID | Pre Check-In ID | uns. Long |
| AN | Account Number | uns. Long |
| DU | Duration of a call in seconds | uns. Long |
| PIN | Pin number | uns. Long |
| HN | Hotel number to be posted on | Long |
Notes:
- If the
<CT>tag is missing, the phone call will be charged as private. - If the
<PIN>tag is present, the posting is processed through the PIN in addition to the PH provided. The processing is defined in SIHOT.
Cancellations
To cancel a booking, send UN with a negative amount. Examples: If no UN was given in the original posting, send UN -1 and if you had UN 10 given (e.g. 10 minutes internet), send UN -10. In any case, the PPU in the cancellation should be the same as in the original posting, NOT the inverted amount.
The TN does not need to match the TN of the original posting.
About Postings
See XML-Format/Important Hint.
General hints
After a posting command is processed, the sender should definitely check the return value. If the sender cannot deliver the message to SIHOT successfully, an error message should be displayed. See also FAQ When should postings be sent?.
Response
Everything was charged correctly:
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4714</TN>
<OC>ACK</OC>
<RC>0</RC>
</SIHOT-Document>
Attributes Response
Example
Example 1 - Charge including the PCIID
This is an example for the use of the pool by the guest identified by the unique id 538 in room 102:
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4715</TN>
<OC>PS</OC>
<HN>4711</HN>
<RN>102</RN>
<PCIID>538</PCIID>
<PT>0</PT>
<TXT>Use of the pool, (31.05.2002 at 13:20)</TXT>
<BD>2002-05-31T13:20:00</BD>
<PPU>5.00</PPU>
</SIHOT-Document>
Everything was charged correctly:
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4715</TN>
<OC>ACK</OC>
<RC>0</RC>
</SIHOT-Document>
Example 2 - Phone Charge to an Extension Number
This is an example of a phone charge to the extension 815 with 3 units and the dialled digits 0682196460. The charge is posted as a private call.
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4716</TN>
<OC>PS</OC>
<HN>4711</HN>
<PH>815</PH>
<PCIID>538</PCIID>
<PT>6</PT>
<CT>1</CT>
<TXT>0682196460</TXT>
<DU>39</DU>
<BD>2005-01-26T13:20:00</BD>
<PPU>0.50</PPU>
<UN>3</UN>
</SIHOT-Document>
Everything was charged correctly:
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4716</TN>
<OC>ACK</OC>
<RC>0</RC>
</SIHOT-Document>
Example 3 - Charge for an Outlet
This is an example for the use of a simple POS posting for a guest identified in room 102.
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4715</TN>
<OC>PS</OC>
<HN>4711</HN>
<RN>102</RN>
<PT>7</PT>
<TXT>Coca Cola</TXT>
<BD>2002-05-31T13:20:00</BD>
<PPU>2.50</PPU>
<OUTLET>1</OUTLET>
<TICKETNO>89123</TICKETNO>
<CASHIER>3</CASHIER>
<PPU>2.50</PPU>
</SIHOT-Document>
Everything was charged correctly.
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4715</TN>
<OC>ACK</OC>
<RC>0</RC>
</SIHOT-Document>
Example 4 - Phone Charge including a PIN
This is an example of a phone charge to the extension 815 with the PIN 1418, 3 units, and the dialed digits 0682196460. The charge is posted as a business call.
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4716</TN>
<OC>PS</OC>
<HN>4711</HN>
<PH>815</PH>
<PIN>1418</PIN>
<PCIID>538</PCIID>
<PT>6</PT>
<CT>2</CT>
<TXT>0682196460</TXT>
<DU>39</DU>
<BD>2005-01-26T13:20:00</BD>
<PPU>0.50</PPU>
<UN>3</UN>
</SIHOT-Document>
Everything was charged correctly:
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4716</TN>
<OC>ACK</OC>
<RC>0</RC>
</SIHOT-Document>
Example 5 - Charge to a card / guest ident
This is an example for the use of the pool by the guest with the card abc1234:
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4717</TN>
<OC>PS</OC>
<HN>4711</HN>
<CARD>
<TYPE>ABC</TYPE>
<NUMBER>abc1234</NUMBER>
</CARD>
<PT>0</PT>
<TXT>Use of the pool, (31.05.2002 at 13.15)</TXT>
<BD>2002-05-31T13:20:00</BD>
<PPU>5.00</PPU>
</SIHOT-Document>
Everything was charged correctly:
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4717</TN>
<OC>ACK</OC>
<RC>0</RC>
</SIHOT-Document>