Versionen im Vergleich

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.

The purpose of this page is to inform you about upcoming changes within our OTA/HTNG implementation for both property management systems. Please note that the changes are divided into onPrem and pAir PMS changes. onPrem changes won't be rolled out globally at the date that is mentioned in the table below whilst pAir Updates will always be rolled out for all customers in one step. 

Please note that the XML of the examples are shortened for a clear arrangement. The full sample message can be found on the documentation page for the message.

Release dates pAIR LIVE Environment

VersionRelease date
23
24.
50
46
2023
2024-12-
13
11
23
24.
48
42
2023
2024-11-
29
13
23
24.
46
42
2023
2024-11-
1523.442023-11-01
06  NO regular Release
24.422024-10-30 NO regular Release
24
23
.42
2023
2024-10-
1823.402023-10-04
16 NO regular Release
24.382024-09-30
24
23
.38
2023
2024-09-
20
18 NO regular Release
24
23
.36
2023
2024-09-
06
04 - IPA update will be now every 4 weeks
24
23
.34
2023
2024-08-
23
21
23
24.32
2023
2024-08-
09
07 NO regular Release
24
23
.30
2023
2024-07-24 NO regular Release
24.292027-07-
26
17
23
24.28
2023
2024-07-
12
10 NO regular Release
24
23
.26
2023
2024-06-
28
26 NO regular Release
24
232023
2024-06-
14

Release dates PWS (onPrem) LIVE Environment

12
24.222024-05-29
24.202024-05-15
24.18NO regular Release on Wednesday 01.05.2024 due to public Holiday in Germany
24.162024-04-17
24.142024-04-03
24.122024-03-20
24.102024-03-06
24.082024-02-21
24.062024-02-07
24.042024-01-24
24.022024-01-10


Release dates PWS (onPrem) LIVE Environment

VersionRelease date
3.192024-10
3.182024-05-22*
3.172024-03-06
3.162023-12-20

*: delayed

Release dates ESB (I/O) LIVE Environment

VersionRelease date
2.6.32024-11-06
2.6.22024-09-25
2.6.12024-08-21
2.6.02024-07-15
2.5.32024-06-10
2.5.22024-05-15
2.5.12024-04-10
2.5.02024-02-26




TBA IDS

TBA ESB
Bulk Export from SMP UIoutbound

OnPrem

pAir

n/ano schema changeEach bulk job can be of maximum 2 years timespan. If it is necessary to have longer time span - more bulk jobs should be created.SMP-2928TBA
Bulk Export from SMP UIoutbound

OnPrem

pAir

n/ano schema change

#1

For one destination - only one bulk job can be running.

Any further bulk jobs for the same destination will be saved in the sequence - but it will not start unless all previous jobs are finalized (cancelled, completed).

#2 

If the queue for a destination in BULK mode exceeds 10K messages, no new bulk job should start. 

Any further bulk jobs for the same destination will be saved in the sequence - but it will not start unless the queue in BULK mode for the destination drops under 10K messages.

IO-82292.5.4








TBA PWS
OTA_ReadRQ/OTA_ResRetrieveRSinboundonPremiseextend the Reservation search by roomtypes
VersionRelease date3.152023-09-203.142023-07-053.132023-04-12
Affected MessageDirection from protelPMSPathExampleSummaryInternal referenceVersion
TBA IDS
TBA PWS
OTA_ResRetrieveRSoutboundonPremOTA_ResRetrieveRS | ReservationsList | HotelReservation | @RoomNumberLockedIndicator
Codeblock
languagexml
collapsetrue
<HotelReservation CreateDateTime="2022-12-07T11:40:52.250Z" CreatorID="protel 1" LastModifierID="protel 1" LastModifyDateTime="2023-05-23T14:08:29.770Z" ResStatus="Reserved" RoomNumberLockedIndicator="false">
This indicates if a room number has been permanently assigned. 

PWS-3650

OTA_ResRetrieveRSoutboundonPremOTA_ResRetrieveRS | ReservationsList | HotelReservation | RoomStays | RoomStay | RoomTypes | RoomType | TPA_Extensions | pxs:RoomStatusExtensions | pxs:HouseKeepingInfo | @RoomStatus
Codeblock
languagexml
collapsetrue
<TPA_Extensions>
	<pxs:RoomStatusExtensions xmlns:pxs="http://protel.io/htng/extensions">
		<pxs:HouseKeepingInfo RoomStatus="2"/>
	</pxs:RoomStatusExtensions>
</TPA_Extensions>
Displays the current status of the room for arrivals and in-house guests.PWS-3650OTA_HotelResNotifRQoutboundOTA_HotelResNotifRQ | HotelReservations | HotelReservation | @RoomNumberLockedIndicator
Codeblock
languagexml
collapsetrue
<HotelReservation CreateDateTime="2022-12-07T11:40:52.250Z" CreatorID="protel 1" LastModifierID="protel 1" LastModifyDateTime="2023-05-23T14:08:29.770Z" ResStatus="Reserved" RoomNumberLockedIndicator="false">
This indicates if a room number has been permanently assigned. PWS-3650OTA_HotelResNotifRQoutboundOTA_HotelResNotifRQ | HotelReservations | HotelReservation | RoomStays | RoomStay | RoomTypes | RoomType | TPA_Extensions | pxs:RoomStatusExtensions | pxs:HouseKeepingInfo | @RoomStatus
Codeblock
languagexml
collapsetrue
<TPA_Extensions>
	<pxs:RoomStatusExtensions xmlns:pxs="http://protel.io/htng/extensions">
		<pxs:HouseKeepingInfo RoomStatus="0"/>
	</pxs:RoomStatusExtensions>
</TPA_Extensions>
Displays the current status of the room for arrivals and in-house guests.PWS-3650OTA_HotelResNotifRQoutboundOTA_HotelResNotifRQ | HotelReservations | HotelReservation | TPA_Extensions | px:TracesNo change in the XML, but traces from the past (before the current PMS date) are no longer sent. PWS-3676TBA IPAOTA_HotelResNotifoutbound + inboundpair

HotelReservation | ResGuests | ResGuest | TPA_Extensions | px:GuestStayExtensions | px:StayInfo

@RelationToPrimary


Codeblock
languagexml
collapsetrue
<GuestStayExtensions
<OTA_ReadRQ xmlns
:htng
="http://
htng
www.opentravel.org/
2014B
OTA/2003/05" 
xmlns:p="http://protel.io/soap" xmlns:px="http://protel.io/htng/extensions"> <StayInfo Role="BookerAndArrivingGuest" RelationToPrimary="Abuelo" PrimaryInd="false" /> </GuestStayExtensions>
CorrelationID="PWS-3822_LJ_01" TimeStamp="2021-08-26T10:10:00Z">
	<POS>
		<Source>
			<RequestorID ID="3151" Type="10" ID_Context="protelIO"/>
			<BookingChannel Type="4" Primary="true"/>
		</Source>
	</POS>
	<ReadRequests>
		<HotelReadRequest>
			<SelectionCriteria Start="2017-10-10" End="2017-10-10" ResStatus="Reserved"/>
			<TPA_Extensions>
				<px:ReadRequestExtensions xmlns:px="http://protel.io/htng/extensions">
					<px:Room RoomTypeCode="Cl-Twin"/>
				</px:ReadRequestExtensions>
			</TPA_Extensions>
		</HotelReadRequest>
	</ReadRequests>
</OTA_ReadRQ>


In the ReadRQ it is now possible to request the RoomType in addition to the time period and reservation status.PWS-3822TBATBA IPA

IO_SystemDataRS

outboundpAir

no schema change

but we will expand for pAir the attributes

  • @AgeFrom
  • @AgeTo
  • @AgeQualifyingCode

no schema change

In the pAir SystemData in Rate Configuration you can define  Discount Groups. With the extension for pAir  we send the attributes

  • @AgeFrom
  • @AgeTo
  • @AgeQualifyingCode

IPA-1467

TBA

OTA_ProfileCreateRQ

OTA_ProfileModifyRQ

outbound / inbound pAir

no schema change

no schema change

no change in the Schema.

Export @LoyalLevel value with the string label the way it is defined by the user instead of the PMS SystemData ID 


IPA-1277

TBA

OTA_HotelResNotifRQ

OTA_ProfileCreateRQ 

OTA_ProfileModifyRQ 

OTA_HotelStayInfoNotifRQ 

outbound / inboundpAir

OTA_ProfileModifyRQ | ProfileModify | Customer | Document

IPA-1302OTA_ResRetrieveRS outboundpAir

OTA_ResRetrieveRS | ReservationsList | HotelReservation |
TPA_Extensions | px:ReservationGroupExtensions| px:GroupInfo| 

@GroupName
@GroupID
@PrimaryInd

ResGuests | ResGuest | Profile | TPA_Extensions | px:ReservationGroupExtensions | px:GroupInfo| 

@GroupName
@GroupID
@PrimaryInd

Codeblock
collapsetrue
<TPA_Extensions>
  <px:ReservationGroupExtensions >
    <px:GroupInfo GroupName="Viaggi in Stile SpA -2022-01-17" GroupID="113" PrimaryInd="true" />
  </px:ReservationGroupExtensions >
</TPA_Extensions>

Due to Italian legal requirements (Police reports and Tourism Statistics), we're extending the schema to be able to export information about groups: group name, group ID and group leader.
On reservation level, PrimaryInd="true" will be shown for the reservation containing the group leader profile, all other reservations of this group will be shown with PrimaryInd="false".

On profile level,  PrimaryInd="true" will be shown for the group leader profile, all other profiles of this group will be shown with PrimaryInd="false".

IPA-1040

IO_InvoiceFiscalizeRQ

IO_InvoiceFiscalizeNotifRQ

outboundpAir

IO_InvoiceFiscalizeRQ | Invoice | @TaxProcedureCode

IO_InvoiceFiscalizeNotifRQ | Invoice | @TaxProcedureCode


Codeblock
languagexml
collapsetrue
<OTA_ProfileCreateRQ>
	<Profile>
		<Customer>
			<Document DocIssueLocation="Dortmund_22" DocID="123456" DocType="4" EffectiveDate="2018-12-12" ExpireDate="2050-12-31" DocIssueAuthority="1234"/>
		</Customer>
	</Profile>
</OTA_ProfileCreateRQ>


To be legal in Austria, a new Attribute is added to the Document Element with the label "Issuing Authorities"

IPA-1369

TBAIO_SystemDataRQinboundpAir

IO_SystemDataRQ | Request | Rates 

<p:Invoice BusinessDate="2023-08-10" DeliveryDate="2023-08-10" ExternallyFiscalized="false" FiscalCode="123456" FiscalCodeID="2" FiscalCodeName="Nota de plata" FiscalDate="2023-08-10T08:19:02+03:00" Fiscalized="true" InvoiceCode="RE_8623" InvoiceDate="2023-08-10T08:19:02+03:00" InvoiceID="4321" Open="false" PastEndOfDay="false" Type="Reservation" User="Beniamin Icobescu" UserTaxNo="" Void="false" TaxProcedureCode="FP">

Due to Polish legal fiscal requirements, we're extending the schema by adding a new attribute.

For some TAA’s it’s necessary to assign TaxProcedureCode. When this code is assigned then it has to be reported to the Government server.

e.g.:

"FP" = Invoice that has been generated to fiscal receipt

Full list of allowed values: PMS_TaxProcedureCode

IPA-1190

IO_InvoiceFiscalizeRQ

IO_InvoiceFiscalizeNotifRQ

outboundpAir

IO_InvoiceFiscalizeRQ | Invoice |  Charges | Item | @GroupCode

IO_InvoiceFiscalizeNotifRQ | Invoice |  Charges | Item | @GroupCode


Codeblock
languagexml
collapsetrue
<p:Charges>
    <p:Request xmlns:p="http://protel.io/soap">
        <p:
Item
UniqueID 
ID
Type="
230326
10" 
PostingAccount
ID="
4
2575" 
Quantity
ID_Context="
1
protelIO"
ServiceDate="2023-08-09" SystemDate="2023-08-09T20:19:35+03:00" TaxCode="19%" TaxRate="19.000000000" Type="Article" GroupCode="GTU01">

Due to Polish legal fiscal requirements, we're extending the schema by adding a new attribute.

In some situations it is necessary to have GTUCode assigned to the invoice header.

This should be related to fiscal code (assignable to fiscal code in PMS SD).

e.g.:

"GTU01" = Alcohol products

"GTU02" = Fuel products

Full list of allowed values: PMS_GroupCode

IPA-1190ESB 323 AnkerESB 323ESB 323
/>
        <p:Rates IncludeInvisible="true or false"/>
    </p:Request>


The vendor should be able to tell us in the RQ with the attribute IncludeInvisible="true or false" which rates he wants to see.

  • If we do not receive a restriction in the RQ, we send out all data by default
  • If we receive the restriction IncludeInvisible="true", we send all rates (like default)
  • If we receive the restriction IncludeInvisible="false", we send all rates that are currently valid 

IPA-1404

TBAIO_SystemDataRSoutboundpAir 

IO_SystemDataRS | SystemData | Rates | RatePlans | RatePlan

HTNG_ChargePostingRSoutbound

onPrem

pAir

 HTNG_ChargePostingRS | Errors | Error


Codeblock
languagexml
collapsetrue
<Errors>
                <Error Code="188" Type="1" ShortText="Transaction error - please report. Incomplete Posting flow. Please check the guest folio before a retry."/>
            </Errors>
If no RS is generated by the PMS service within ~55 seconds, then:
  • the ESB will not do retries itself
  • the ESB will generate a generic RS to inform the sender of the RQ about the failure.

! The RQ should not be automatically retried - the posting itself could have happened, yet for some reason - no RS could have been generated by the PMS service (e.g. fiscalization error).

IO-7390ESB 323


The vendor should be able to tell us in the RQ with the attribute IncludeInvisible="true or false" which rates he wants to see.

  • If we do not receive a restriction in the RQ, we send out all data by default
  • If we receive the restriction IncludeInvisible="true", we send all rates (like default)
  • If we receive the restriction IncludeInvisible="false", we send all rates that are currently valid 

IPA-1403

TBA

PWS 3.19PWS 3.14.X 

Anker
PWS 3.
14
19.X
PWS 3.
14
19.X

OTA_

ProfileModifyRQIn/OutboundonPremProfileModify | Customer | TPA_Extensions | ProfileInfoExtensions | PersonInfos | Registration

HotelResNotifRQ

inbound

OnPrem

no schema changes


We will no longer import fixed charges with inbound OTA_HotelResNotifRQ. This can only be done with IO_ResModifyNotifRQ.

PWS-3810

3.19.0

OTA_HotelResNotifRQ

inbound

OnPrem

no schema changes


Implemented the import of the attributes CommunicationChannel and TravelReason.

PWS-3820

3.19.0

OTA_HotelRatePlanNotifRQ

inbound

OnPrem

no schema changes


  • Overlay = All data is overwritten 
  • Delta = Only the specified data record in the RQ is adjusted. All other data remains unchanged. 

PWS-3821

3.19.0

IO_SystemDataRQ

inbound

OnPrem

IO_SystemDataRQ | Request | Rates @IncludeInvisible


Codeblock
languagexml
collapsetrue
<p:IO_SystemDataRQ xmlns:p
Codeblock
languagexml
collapsetrue
<px:Registration BirthCountry="IT" BirthPlace="CALVIGNASCO" LicensePlate="35347444" /> 
Implmented guest BirthCountry & BirthPlace in profile messages, both inbound and outbound.PWS-35713.14.XOTA_ProfileModifyRQIn/OutboundonPremProfileModify | Customer | TPA_Extensions | ProfileInfoExtensions | AccountingInfos Codeblock
languagexml
collapsetrue
<px:TPA_Extensions xmlns:px
="http://protel.io/
htng/extensions"> <px:ProfileInfoExtensions> <px:AccountingInfos ARNumber="223344" Tax1="222222" Tax2="333333" /> </px:ProfileInfoExtensions> </px:TPA_Extensions>Implemented Tax1 and Tax2 attributes in the profile messages.PWS-35903.14.XIO_SystemDataRSOutboundonPremIO_SystemDataRS | Reservations | DefaultValues Codeblock
languagexml
collapsetrue
<?xml version="1.0" encoding="utf-8"?> <env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:htnga="http://htng.org/PWSWG/2007/02/AsyncHeaders" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <env:Header> <htnga:CorrelationID>CorrelationID123</htnga:CorrelationID> <Source xmlns="http://protel.io/soap" Module="protel.WebServices" ModuleVersion="0.0.0.3" Product="protel On Premise SPE" ProductVersion="23.01000" Service="io.protel.onpremise"/> </env:Header> <env:Body> <ns2:IO_SystemDataRS xmlns:ns2="http://protel.io/soap" CorrelationID="CorrelationID123" TimeStamp="2023-05-11T07:25:25.4624218Z" Version="3.000"> <ns2:UniqueID ID="3152
soap" TimeStamp="2020-08-20T07:15:51.4023488Z" Version="1.000" CorrelationID="IncludeInvisible">
	<p:Request xmlns:p="http://protel.io/soap">
		<p:UniqueID Type="10" ID="3152" ID_Context="protelIO"/>
		<p:Rates IncludeInvisible="true"/>
	</p:Request>
</p:IO_SystemDataRQ>


To shorten the RS message we implemented a new attribute to exclude information about expired rates. If this new attribute is not provided, the RS message will contain information about all rates as before  (default=true). If the new attribute is sent with "false", the RS message will no longer contain information about expired rates.

PWS-3805
PWS-3806

3.19.0

IO_SystemDataRS

outbound

OnPrem

IO_SystemDataRS | SystemData | Reservations | GuestRelationTypes | GuestRelationType 


Codeblock
<ns2:IO_SystemDataRS>
	<ns2:SystemData>
		<ns2:Reservations>
			<ns2:GuestRelationTypes>
				<ns2:GuestRelationType Code="BRO" ID="1" ID_Context="protelIO" 
Type
Visible="
10
true"
/
>
					<ns2:
Success/> <ns2:SystemData ChainCode
Name Language="
HC1" HotelCode="3152" HotelID="1" HotelName="Hotel Lamm"> <ns2:UniqueID ID="3152" ID_Context="protelIO" Type="10"/> <ns2:Reservations>
en">Brother</ns2:Name>
				
<ns2:DefaultValues ArrivalTime="14:00" DepartureTime="10:00"/> </ns2:Reservations> </ns2:SystemData> </ns2:IO_SystemDataRS> </env:Body> </env:Envelope>
</ns2:GuestRelationType>


Added the GuestRelationType to the SystemDataRS.

PWS-3835

3.19.0

PWS 3.17.X 

Anker
PWS 3.17.X
PWS 3.17.X

OTA_HotelInvBlockNotifRQ

outboundOnPremOTA_HotelInvBlockNotifRQ | InvBlocks | InvBlock | RoomTypes | RoomType | RatePlans | RatePlan@TaxInclusiveThe default arrival / departure time which is set by hotel can be displayed in the reservation section of IO_SystemDataRSPWS-35733.14.XHTNG_HotelCheckOutNotifRQInboundonPremHTNG_HotelCheckOutNotifRQ | RetransmissionIndicator


Codeblock
languagexml
collapsetrue
<?xml
<RatePlan 
version='1.0' encoding='utf-8'?> <env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"> <soapenv:Header xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"> </soapenv:Header> <soapenv:Body xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"> <HTNG_HotelCheckOutNotifRQ xmlns="http://htng.org/2014B" EchoToken="PWS_3542_13" CorrelationID="PWS_3542_13" RetransmissionIndicator="true"> <POS> <Source xmlns="http://www.opentravel.org/OTA/2003/05"> <RequestorID ID="3153" Type="10" ID_Context="protelIO"/> <BookingChannel Type="4" Primary="true"/> </Source> </POS> <PropertyInfo ChainCode="n/a" HotelCode="3153" HotelCodeContext="protelIO" HotelName="protel"/> <AffectedGuests> <UniqueID ID="342692" ID_Context="protelIO" Type="14"/> </AffectedGuests> <HotelReservations> <HotelReservation xmlns="http://www.opentravel.org/OTA/2003/05" CreateDateTime="2020-08-14T15:59:15Z" CreatorID="ame1" ResStatus="Checked Out"> <UniqueID ID="342692" Type="14" ID_Context="protelIO"/> </HotelReservation> </HotelReservations> </HTNG_HotelCheckOutNotifRQ> </soapenv:Body> </env
CurrencyCode="EUR" End="2100-01-01" MaxGuestApplicable="9999" RatePlanCode="StdRateExclTax" Start="1980-01-01" TaxInclusive="false">


Flag is linked to the system setup for rate values. If the PWS is set to send "net values only", the attribute will be send with "false". If the system is set up to send "gross values only" OR "net and gross values", the attribute will be send with "true".PWS-37293.17.0

HTNG_HotelRoomStatusUpdateNotifRQ

outbound / inboundOnPrem


Message implemented for outbound and inbound processing.PWS-3202
PWS-32463.17.0

PWS 3.16.X 

Anker
PWS 3.16.X
PWS 3.16.X

OTA_ProfileCreateRQ

OTA_ProfileModifyRQ

outbound

OnPrem

OTA_ProfileCreateRQ | Profile | Customer | Document

OTA_ProfileModifyRQ | ProfileModify | Customer | Document

no schema change

With OnPrem 23.060 it will be possible to store more than one travel document per profile so that the outbound profile messages may contain more than one document element.

PWS-3723

3.16.0

OTA_HotelResNotifRQ

outbound

OnPrem

HotelReservation | ResGuests | ResGuest | Profiles | ProfileInfo | Profile | Customer | RelatedTraveler | TPA_Extensions | px:GuestStayExtensions | px:StayInfo


Codeblock
languagexml
collapsetrue
<RelatedTraveler BirthDate="2006-03-05">
	<UniqueID ID="181493" ID_Context="protelIO" Type="1"/>
	<PersonName Language="de">
		<NamePrefix/>
		<GivenName>Tick</GivenName>
		<MiddleName/>
		<Surname>Duck</Surname>
		<Document DocID="987654321" DocType="5"/>
	</PersonName>
	<TPA_Extensions>
		<px:GuestStayExtensions>
			<px:StayInfo PrimaryInd="false" RelationToPrimary="Neffe / Nichte"/>
		</px:GuestStayExtensions>
	</TPA_Extensions>
</RelatedTraveler>


The legal requirements in Spain stipulate that additional guests can be related to the main guest.

The relationship to the main guest can soon be transferred by the additional attribute with.

This is for example important  for police reports.

PWS-3697

3.16.0

OTA_HotelResNotifRQ

outbound

OnPrem

OTA_HotelResNotifRQ | HotelReservations | HotelReservation | TPA_Extensions | px:Traces


No change in XML, but traces from the past (before the current PMS business date) are no longer sent.

PWS-3676

3.16.0

OTA_ProfileModifyRQ

outbound

OnPrem

OTA_ProfileModifyRQ | ProfileModify | Customer | TPA_Extensions | px:ProfileExtensions | px:PersonInfos | px:Registration | px:Occupation


Codeblock
collapsetrue
<TPA_Extensions xmlns:px="http://protel.io/htng/extensions">
    <px:ProfileInfoExtensions>
        <px:PersonInfos>
            <px:MarketingCodes>
                <px:Code DefaultInd="false" DisplaySequence="0" ID="3" ID_Context="protelIO" Type="MARKETINGCODE">Wintergast</px:Code>
            </px:MarketingCodes>
            <px:Registration BirthCountry="DE" BirthPlace="Oberhausen">
                <px:Occupation>Polizist</px:Occupation>
            </px:Registration>
            <px:Language DefaultInd="true">en</px:Language>
        </px:PersonInfos>
        <px:Salutation ID="1" ID_Context="protelIO" Type="Salutation">Sehr geehrte Frau Werner</px:Salutation>
    </px:ProfileInfoExtensions>
</TPA_Extensions>


The attribute occupation was added. 

PWS-3714

3.16.0

IO_ResModifyNotifRQ

inbound

OnPrem

IO_ResModifyNotifRQ | Reservations | Reservation | ProfileReferences | ProfileReference

@RelationToPrimary


Codeblock
languagexml
collapsetrue
<p:IO_ResModifyNotifRQ xmlns:p="http://protel.io/soap" CorrelationID="UseCase11b" TimeStamp="2018-12-29T15:20:35.985Z" Version="1.00">
    <p:Reservations HotelCode="3152">
        <p:Reservation ArrivalDate="2018-11-11">
            <p:UniqueID ID="345474" Type="Reservation" ID_Context="Protel_IO"/>
            <p:ProfileReferences>
                <p:ProfileReference ID_Context="protelIO" Type="Customer" ID="181491" RelationToPrimary="Son" Action="CREATE"/>
            </p:ProfileReferences>
        </p:Reservation>
    </p:Reservations>
</p:IO_ResModifyNotifRQ>


The legal requirements in Spain stipulate that additional guests can be related to the main guest.

The relationship to the main guest can be transferred by the additional attribute for UseCase 11b only.

The relation is for example important for police reports. 

PWS-3700

3.16.0

OTA_HotelResNotifRQ

OTA_HotelStayInfoNotifRQ

OTA_ProfileCreateRQ 

OTA_ProfileCreateRQ

outbound

OnPrem

OTA_HotelResNotifRQ | HotelReservations | HotelReservation | ResGuests | ResGuest | Profiles | ProfileInfo | Profile | Profile | Customer | TPA_Extensions | px:ProfileInfoExtensions | px:ProfileInfoExtensions | px:PersonInfos | px:Registration |  | px:DocumentInfos | px:DocumentInfo

OTA_HotelStayInfoNotifRQ | StayInfos | StayInfo | HotelReservation | ResGuests | ResGuest | Profiles | ProfileInfo | Profile | Profile | Customer | TPA_Extensions | px:ProfileInfoExtensions | px:ProfileInfoExtensions | px:PersonInfos | px:Registration |  | px:DocumentInfos | px:DocumentInfo

OTA_ProfileCreateRQ | Profile | Customer | TPA_Extensions | px:ProfileInfoExtensions | px:ProfileInfoExtensions | px:PersonInfos | px:Registration |  | px:DocumentInfos | px:DocumentInfo

OTA_ProfileModifyRQ | ProfileModify | Customer | TPA_Extensions | px:ProfileInfoExtensions | px:ProfileInfoExtensions | px:PersonInfos | px:Registration  |  px:DocumentInfos | px:DocumentInfo


Codeblock
languagexml
collapsetrue
<Customer>
    <TPA_Extensions>
    ....
        <ProfileInfoExtensions>
        ....
            <PersonInfos>
            ....           
                <Registration BirthDate="1980-01-06" BirthCountry="MA">
                    <Occupation>Mechanic</Occupation>
                    <DocumentInfos>                 
                      <DocumentInfo RPH="665554444" ID_Context="SNDS" ID="120-24440-GV0" Type="DocumentIdentifier"/>
                    </DocumentInfos>
                </Registration> 
            </PersonInfos>
        </ProfileInfoExtensions> 
    </TPA_Extensions>
</Customer>


Due to Spanish legal requirements (Police reports), we extend the TPA extensions in the Customer  element with DocumentInfo for the support number  of Spanish documents.

PWS-3712

3.16.0

OTA_HotelResNotifRQ

OTA_ProfileCreateRQ 

OTA_ProfileCreateRQ 

inbound

OnPrem 

OTA_HotelResNotifRQ | HotelReservations | HotelReservation | ResGuests | ResGuest | Profiles | ProfileInfo | Profile | Profile | Customer | TPA_Extensions | px:ProfileInfoExtensions | px:ProfileInfoExtensions | px:PersonInfos | px:Registration |  | px:DocumentInfos | px:DocumentInfo

OTA_ProfileCreateRQ | Profile | Customer | TPA_Extensions | px:ProfileInfoExtensions | px:ProfileInfoExtensions | px:PersonInfos | px:Registration |  | px:DocumentInfos | px:DocumentInfo

OTA_ProfileModifyRQ | ProfileModify | Customer | TPA_Extensions | px:ProfileInfoExtensions | px:ProfileInfoExtensions | px:PersonInfos | px:Registration  |  px:DocumentInfos | px:DocumentInfo


Codeblock
languagexml
collapsetrue
<Customer>
    <TPA_Extensions>
    ....
        <ProfileInfoExtensions>
        ....
            <PersonInfos>
            ....           
                <Registration BirthDate="1980-01-06" BirthCountry="MA">
                    <Occupation>Mechanic</Occupation>
                    <DocumentInfos>                 
                      <DocumentInfo RPH="665554444" ID_Context="SNDS" ID="120-24440-GV0" Type="DocumentIdentifier"/>
                    </DocumentInfos>
                </Registration> 
            </PersonInfos>
        </ProfileInfoExtensions> 
    </TPA_Extensions>
</Customer>


Due to Spanish legal requirements (Police reports), we extend the TPA extensions in the Customer  element with DocumentInfo for the support number  of a Spanish documents.

PWS-3713

3.16.0

OTA_ProfileCreateRQ

OTA_ProfileCreateRQ 


inbound

OnPrem

no change in xml


Codeblock
languagexml
collapsetrue
<Customer Gender="Male" BirthDate="2020-01-01" VIP_Indicator="true" Language="de" CustomerValue="ECA - 10%|0;VIP|2">
	<PersonName>
		<NamePrefix>Herr</NamePrefix>
		<GivenName>Donald</GivenName>
		<Surname>Duck</Surname>
	</PersonName>
	<CitizenCountryName DefaultInd="true" Code="DE"/>
	<Document DocID="123456798" DocIssueLocation="" DocType="2" EffectiveDate="2020-01-01" ExpireDate="2030-01-01"/>
	<Document DocID="963852" DocType="1" EffectiveDate="2021-10-10"/>
</Customer>


With OnPrem version 23.060 and higher it is possible to send more than one document per profile.

PWS-3651

3.16.0

OTA_HotelResNotifRQ

OTA_ProfileCreateRQ

OTA_ProfileCreateRQ 

outbound / inbound

OnPrem

OTA_HotelResNotifRQ | HotelReservations | HotelReservation | ResGuests | ResGuest | Profiles | ProfileInfo | Profile | Profile | Customer | TPA_Extensions | px:ProfileInfoExtensions | px:ProfileInfoExtensions | px:PersonInfos | px:Registration | LicensePlate


OTA_ProfileCreateRQ | Profile | Customer | TPA_Extensions | px:ProfileInfoExtensions | px:ProfileInfoExtensions | px:PersonInfos | px:Registration | LicensePlate

OTA_ProfileModifyRQ | ProfileModify | Customer | TPA_Extensions | px:ProfileInfoExtensions | px:ProfileInfoExtensions | px:PersonInfos | px:Registration | LicensePlate


Codeblock
languagexml
collapsetrue
<px:ProfileInfoExtensions>
    <px:PersonInfos>
        <px:Registration BirthCountry="DE" BirthPlace="Entenhausen">
            <LicensePlate>ENT-DD 1</LicensePlate>
        </px:Registration>
    </px:PersonInfos>
</px:ProfileInfoExtensions>


Corrected the xml to follow the schema.

PWS-3711

3.16.0

ESB 323

Anker
ESB 323
ESB 323








HTNG_ChargePostingRSoutbound

onPrem

pAir

 HTNG_ChargePostingRS | Errors | Error


Codeblock
languagexml
collapsetrue
<Errors>
                <Error Code="188" Type="1" ShortText="Transaction error - please report. Incomplete Posting flow. Please check the guest folio before a retry."/>
            </Errors>


If no RS is generated by the PMS service within ~55 seconds, then:
  • the ESB will not do retries itself
  • the ESB will generate a generic RS to inform the sender of the RQ about the failure.

! The RQ should not be automatically retried - the posting itself could have happened, yet for some reason - no RS could have been generated by the PMS service (e.g. fiscalization error).

IO-7390ESB 323

IPA 24.38

Anker
IPA 24.38
IPA 24.38









OTA_HotelResNotifRQ

inboundpAir

no schema change

no schema change

Handling for CC-Cards

  • inbound @CardCode Attribute needs to be configured in the pAir SystemData that it can be used for Payment Posting or Deposit Posting
  • Case-insensitive is working for the @CardCode Attribute
    • CardCode in the SystemData: "Mastercard" → inbound CardCode "MasterCard"
    • CardCode in the SystemData: "Mastercard" → inbound CardCode "mastercards"
  • Detokenize Card Number is always possible

→ Important for Hotels → all possible inbound CardCodes needs to be configured in the System Data (if a vendor is sending "Mastercard (virtual credit card)" it needs to be configured in the SystemData)
→ Important for Vendor → discuss with the Hotels with CardCode are configured in their System Data.

IPA-1568

24.38

IPA 24.29

Anker
IPA 24.29
IPA 24.29









IO_SystemDataRS 


IO_ResModifyNotifRQ


OTA_HotelResNotifRQ



outbound


outbound


outbound / inbound

pAir

no schema change

no schema change

If the new Xsetup (Guest Relation with Primary) is set for the relations of the guests to the main guest, the various GuestRelationTypes can be queried from the system data via IO_SystemDataRS and sent via IO_ResModifyNotifRQ and OTA_HotelResNotifRQ with the attribute @RelationToPrimary.NGPR-8321 / IOTEC-599924.29

IPA 24.24

Anker
IPA 24.24
IPA 24.24









IO_InvoiceFiscalizeRQ 

IO_InvoiceFiscalizeNotifRQ

outboundpAir

IO_InvoiceFiscalizeRQ | Invoice | AdditionalText


Codeblock
languagexml
collapsetrue
<p:AdditionalText>test 123 </p:AdditionalText>




Due to the legal requirements in Romania, we are extend the invoice element with a new element for the additional text  for invoices.

IPA-1367TBA

IO_InvoiceFiscalizeRQ 

IO_InvoiceFiscalizeNotifRQ

outboundpAir

IO_InvoiceFiscalizeRQ | Invoice | InvoiceFormat


Codeblock
languagexml
collapsetrue
<p:InvoiceFormat>ItemsSortDate</p:InvoiceFormat>


Due to the legal requirements in Romania, we are expanding the invoice element with a new element for the invoice format for invoices.

IPA-1365TBAIO_SystemDataRSoutboundpAir

IO_SystemDataRS | SystemData | Accounting | InvoiceFormat


Codeblock
languagexml
collapsetrue
                    <ns2:InvoiceFormats>
                        <ns2:InvoiceFormat Code="ItemsSortDate">
                            <ns2:Description Language="en_US">Single items, sort by date</ns2:Description>
                        </ns2:InvoiceFormat>
                        <ns2:InvoiceFormat Code="ItemsSortGuest">
                            <ns2:Description Language="en_US">Single items, sort by guest</ns2:Description>
                        </ns2:InvoiceFormat>
                        <ns2:InvoiceFormat Code="ItemsSortRoom">
                            <ns2:Description Language="en_US">Single items, sort by room</ns2:Description>
                        </ns2:InvoiceFormat>
                        <ns2:InvoiceFormat Code="ItemsSortCrs">
                            <ns2:Description Language="en_US">Single items, sort by CRS number</ns2:Description>
                        </ns2:InvoiceFormat>
                        <ns2:InvoiceFormat Code="ItemsGroupCode">
                            <ns2:Description Language="en_US">Combine identical items</ns2:Description>
                        </ns2:InvoiceFormat>
                        <ns2:InvoiceFormat Code="ItemsGroupDate">
                            <ns2:Description Language="en_US">Combine identical items and dates</ns2:Description>
                        </ns2:InvoiceFormat>
                        <ns2:InvoiceFormat Code="ItemsGroupGuest">
                            <ns2:Description Language="en_US">Combine identical items and guest</ns2:Description>
                        </ns2:InvoiceFormat>
                        <ns2:InvoiceFormat Code="ItemsGroupRoom">
                            <ns2:Description Language="en_US">Combine identical items and rooms</ns2:Description>
                        </ns2:InvoiceFormat>
                        <ns2:InvoiceFormat Code="ItemsGroupCrs">
                            <ns2:Description Language="en_US">Combine identical items and CRS number</ns2:Description>
                        </ns2:InvoiceFormat>
                    </ns2:InvoiceFormats>


Due to the legal requirements in Romania, we are expanding the Accounting element with a new element for the invoice format for invoices.

IPA-1365TBA

IO_InvoiceFiscalizeRQ

IO_InvoiceFiscalizeNotifRQ

outboundpAir

no schema change

no schema change

no change in the Schema.

To be legal in Portugal, an IO_InvoiceFiscalizeRQ needs to be triggered as soon as an Proforma or Info Invoice is created.

IPA-1345

24.24

IPA 24.20

Anker
IPA 24.20
IPA 24.20









OTA_HotelResNotifRQOTA_HotelStayInfoNotifRQOTA_ResRetrieveRSHTNG_HotelCheckInNotifRQHTNG_HotelCheckOutNotifRQ 

outboundpAir

HotelReservation | ResGuests |  ResGuest | TPA_Extensions | px:GuestStayExtensions | px:StayInfo


@CheckedIn

@CheckedOut 


Codeblock
languagexml
collapsetrue
<TPA_Extensions>
    <px:GuestStayExtensions>
        <px:StayInfo Arrival="2024-02-27T09:13:06+01:00" CheckedIn="2024-04-26T09:13:06+02:00" CheckedOut="2024-05-02T15:12:21+02:00" Departure="2024-02-28T15:12:21+01:00" PrimaryInd="true" Role="BookerAndArrivingGuest" Status="Checked out"/>
        <px:TelephoneSetting ClassOfService="3"/>
    </px:GuestStayExtensions>
</TPA_Extensions> 


To be legal compliant for police reports we added  new attributes in the StayInfo Element 

@CheckedIn = date and time for the logged checkin for the reservation 

@CheckedOut = date and time for the logged checkout for the reservation 

IPA-1392

24.20

OTA_HotelResNotifRQ

outbound / inboundpAir

px:ReservationExtensions | px:ProcessingInstructions | px:ResGuests |

@FullOverlay

@Role



Codeblock
languagexml
titleOverlay profiles
collapsetrue
<px:ReservationExtensions>
    <px:ProcessingInstructions>
        <px:ResGuests FullOverlay="true" Role="LinkedProfile"/>
    </px:ProcessingInstructions>


Extending the handling of list of profiles linked to a reservation:

  • If px:ProcessingInstructions | px:ResGuests | @FullOverlay="true", then the list of profiles provided in the inbound RQ msg will completely replace those existing in the PMS for the designated @Role. This allows to use intentional removal of existing profiles linked to a reservation. 
  • Else - if the new element is missing or the @FullOverlay="false" - the current existing logic remains - profiles are appended to the reservation.

! Caution - If the vendor does not have the intention to remove a profile from a reservation - then this element should not be sent inbound !

IPA-1387

24.20







IPA 24.14

Anker
IPA 24.14
IPA 24.14








IO_InvoiceFiscalizeRQ

IO_InvoiceFiscalizeNotifRQ

outboundpAir

IO_InvoiceFiscalizeRQ | Invoice


Codeblock
languagexml
collapsetrue
<p:Invoice BusinessDate="2022-08-09" ExternallyFiscalized="false" FiscalCode="gg12cc" FiscalCodeID="2" FiscalCodeName="Test_AB" FiscalDate="2024-03-27T08:31:34+01:00" Fiscalized="true" InvoiceCode="RE_23" InvoiceDate="2024-03-27T08:31:34+01:00" InvoiceID="34" Open="false" PastEndOfDay="false" SystemFiscalCode1="AA" SystemFiscalCode2="bb" SystemFiscalCode3="cc" Type="Reservation" User="Julia W" UserTaxNo="" Void="false">



Due to legal requirements in Portugal, we are expanding 
the invoice element with the attributes from the fiscal code in the systemdata:


@SystemFiscalCode1 for ATCUD

@SystemFiscalCode2 for NIF

@SystemFiscalCode3 for SAFT


IPA-135024.14

IO_InvoiceFiscalizeRQ

IO_InvoiceFiscalizeNotifRQ

outboundpAir

IO_InvoiceFiscalizeRQ | Invoice | InvoiceRecipient | AccountingInfos


Codeblock
languagexml
collapsetrue
<p:InvoiceRecipient ProfileID="919" ProfileType="Corporation">
	<p:FirstName/>
	<p:LastName>Agenzia delle Entrate</p:LastName>
	<p:Language>it_IT</p:Language>
	<p:Notes/>
	<p:Gender/>
	<p:TaxNumber>06363391001</p:TaxNumber>
	<p:AccountingInfos CompanyRegNumber="987654321" FiscalUID="1234567890" PublicAdministrationInd="false" SplitPaymentInd="false" Tax1="06363391001" Tax2="06363391001"/>
</p:InvoiceRecipient>



We extend the AccountingInfos with the attributes 

@FiscalUID

@CompanyRegNumber

IPA-1380

24.14

IO_InvoiceFiscalizeNotifRQ 

IO_InvoiceFiscalizeRQ

outboundpAir

IO_InvoiceFiscalizeRQ | Invoice | InvoiceRecipient | AccountingInfos

 

Codeblock
languagexml
collapsetrue
<p:InvoiceRecipient ProfileID="1234" ProfileType="Customer">
	<p:FirstName>Jessica</p:FirstName>
	<p:LastName>Alba</p:LastName>
	<p:BirthDate>1980-10-10</p:BirthDate>
	<p:Gender>F</p:Gender>
	<p:Addresses/>
	<p:AccountingInfos PublicAdministrationInd="true" SplitPaymentInd="true"/>
</p:InvoiceRecipient>


Due to legal requirements in Italy, we extend 
the AccountingInfos with the attributes 

@PublicAdministrationInd

@SplitPaymentInd

IPA-136324.14

OTA_ProfileCreateRQ

OTA_ProfileModifyRQ

outbound

inbound

pAir

Customer | TPA_Extensions | px:ProfileInfoExtensions  | px:AccountingInfos

 

Codeblock
languagexml
collapsetrue
<px:ProfileInfoExtensions>
	<px:AddressTypes/>
</px:ContactDetails>
</px:PersonInfos>
<px:AccountingInfos CompanyRegNumber="98711654321" FiscalUID="1525234567890"/>
</px:ProfileInfoExtensions>


We extend the AccountingInfos with the attributes 

@FiscalUID

@CompanyRegNumber

IPA-1377

IPA-1378

24.14

OTA_HotelResNotif

outbound

inbound


pAir

OTA_HotelResNotifRQ | HotelReservations | HotelReservation | ResGuests | ResGuest | Profiles | ProfileInfo | Profile | Customer | TPA_Extensions | px:ProfileInfoExtensions | px:AccountingInfos

 

:Envelope>Implemented the RetransmissionIndicator. When true, indicates the message is being re-sent. The RS message will hold all invoices attached to the reservation for the CO guest. PWS-35423.14.XOTA_HotelResNotifRQInboundonPremOTA_HotelResNotifRQ | HotelReservations | HotelReservation | Services | Service

Codeblock
languagexml
collapsetrue
<Services>
    <Service ID="RemoveAll" ID_Context="protelIO" Type="16"/>
</Services>
For Transaction Action "Modify":
If Service/@ID="RemoveAll" is provided, then any bookable package/s that are attached to the reservation will be removed from it.PWS-35563.14.XPWS 3.13.X AnkerPWS 3.13.XPWS 3.13.XIO_ResModifyNotifRQinbound onPremIO_ResModifyNotifRQ | Reservations | Reservation | ProfileReferences | ProfileReferenceUse Case 11 (Change attached guest profile): only the main reservation profile can be exchanged, no profiles on the list of attached guest profiles
Use Case 11b (Add attached guest profile): an unlimited number of profiles can be attached to the list of attached guest profiles.
<px:ProfileInfoExtensions>
	<px:AddressTypes/>
</px:ContactDetails>
</px:PersonInfos>
<px:AccountingInfos CompanyRegNumber="98711654321" FiscalUID="1525234567890"/>
</px:ProfileInfoExtensions>


We extend the AccountingInfos with the attributes 

@FiscalUID

@CompanyRegNumber

IPA-1377

IPA-1378

24.14OTA_HotelStayInfoNotifRQoutboundpAir

OTA_HotelStayInfoNotifRQ | StayInfos | StayInfo | HotelReservation | ResGuests | ResGuest | Profiles | ProfileInfo | Profile| Customer | TPA_Extensions | px:ProfileInfoExtensions | px:AccountingInfos


Codeblock
languagexml
collapsetrue
<px:ProfileInfoExtensions>
	<px:AddressTypes/>
</px:ContactDetails>
</px:PersonInfos>
<px:AccountingInfos CompanyRegNumber="98711654321" FiscalUID="1525234567890"/>
</px:ProfileInfoExtensions>



We extend the AccountingInfos with the attributes 

@FiscalUID

@CompanyRegNumber

IPA-1377

24.14

IPA 24.12

Anker
IPA 24.12
IPA 24.12








OTA_HotelResNotifRQoutbound / inboundpAir

OTA_HotelResNotifRQ | HotelReservations | HotelReservation | ResGuests | ResGuest | TPA_Extensions | px:GuestStayExtensions | px:StayInfo

 

Codeblock
languagexml
collapsetrue
<TPA_Extensions>
    <px:GuestStayExtensions>
PWS-34893.13.3OTA_HotelAvailRSoutboundonPremOTA_HotelAvailRS | RoomStays | RoomStay | RoomRates | RoomRate | Rates | Rates | TPA_Extensions | 
px:FixedChargesAmountsExtensions Codeblock
languagexml
collapsetrue
<Rate RateTimeUnit="Day" EffectiveDate="2019-02-01" ExpireDate="2019-02-03" UnitMultiplier="2"> <Base AmountAfterTax="117.00" CurrencyCode="EUR"/> <Total AmountAfterTax="234.00" CurrencyCode="EUR"/> <TPA_Extensions> <px:FixedChargesAmountsExtensions

        <px:StayInfo 
xmlns:px="http://protel.io/htng/extensions" End="2019-02-03" Start="2019-02-01"
Arrival="2024-02-07T12:00:00+01:00" Departure="2024-02-08T12:00:00+01:00" PrimaryInd="true" Role="LinkedProfile" Status="Reserved"/>
        
<px:
RateAmount
TelephoneSetting 
AmountAfterTax
ClassOfService="
10.00" RevenueCategoryCode="17" CurrencyCode="EUR"
3"/>
    
</px:
FixedChargesAmountsExtensions>
GuestStayExtensions>
</TPA_Extensions>
</Rate>

New element TPA_Extensions will be added IF the respective rate has an exclusive fixed charge package.

The value of the FixedChargesAmountsExtensions | RateAmount | AmountAfterTax is NOT included in the Base/Total amounts and should NOT be used for OTA_HotelResNotifRQ to the PMS. This value has informative purpose to the walk-in guest - since the charge will be added automatically by the PMS logic during EOD.

PWS-35053.13.0


There is now a new function in the PMS so that the PrimaryInd= true attribute can be used to specify the profile of the leading company OR the travel agency within the same reservation.



IPA-1357

IPA-1358

24.12

IPA 24.08

Anker
IPA 24.08
IPA 24.08









IO_SystemDataRS

outboundpAirIO_SystemDataRS | SystemData | Reservations | GuestRelationTypes | GuestRelationType 


Codeblock
languagexml
collapsetrue
<ns2:GuestRelationTypes>
	<ns2:GuestRelationType Code="Abuelo" ID="1" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Abuelo</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Abuela" ID="2"
IO_ResModifyNotifRQinboundonPremIO_ResModifyNotifRQ | Reservations | Reservation | ProfileReferences | ProfileReference
UseCase 11: Change arriving guest
Codeblock
languagexml
collapsetrue
<p:ProfileReferences>
	<p:ProfileReference ID_Context="protelIO" TypePrimaryInd="Customerfalse" IDVisible="36975" Action="DELETE"/>
	<p:ProfileReferencetrue">
		<ns2:Name Language="es_ES">Abuela</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Padre" ID="3" ID_Context="protelIO" TypePrimaryInd="Customerfalse" IDVisible="36888" Action="CREATE"/>
</p:ProfileReferences>
UseCase 11: Change arriving guest
With this PWS version, only the arriving guest will be exchanged, all folio recipients remain as they are.PWS-34633.13.0IO_ResModifyNotifRQinboundonPremIO_ResModifyNotifRQ | Reservations | Reservation | InvoiceReferences | InvoiceReference | ProfileReferences | ProfileReference
UseCase 12: Change invoice recipient
Codeblock
languagexml
collapsetrue
<p:InvoiceReferences>
	<p:InvoiceReference Type="Invoice" ID="34161-0true">
		<ns2:Name Language="es_ES">Padre</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Madre" ID="4" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<p:ProfileReferences>
			<p:ProfileReference ID_Context="protelIO" Type="Customer" ID="36975" Action="DELETE" Role="InvoiceRecipient"/>
			<p:ProfileReference ID_Context="protelIO" Type="Customer" ID="36842" Action="CREATE" Role="InvoiceRecipient"/>
		</p:ProfileReferences>
	</p:InvoiceReference>
</p:InvoiceReferences>
UseCase 12: Change invoice recipient
With this PWS version, the invoice recipient for folios A to F can be exchanged. The arriving guest will not be touched.PWS-34633.13.0IO_RatePackageNotifRQOutboundonPremIO_RatePackageNotifRQ | Packages | Package | PackageItems | PackageItem | Calculation | @FixedChargeInd
Codeblock
languagexml
collapsetrue
<Calculation AmountAfterTax="10.00" AmountBeforeTax="8.06" Currency="EUR" InclusiveInd="false" FixedChargeInd="false" Recurrence="Daily" Relation="PerAdult">
    <DaysOfWeek Fri="true" Mon="true" Sat="true" Sun="true" Thu="true" Tue="true" Wed="true"/>
</Calculation>
New attribute added to schema: @FixedChargeInd. The attribute is boolean and optional. 

If @FixedChargeInd="false" (or the attribute is missing) then the package is "not a fixed charge". 

Else if the @FixedChargeInd="true" then the package "is a fixed charge". This is extra cost to the accommodation amount - but unlike the "add to rate" packages, it should not be included in the inbound reservation total amount to the PMS.

PWS-34923.13.0HTNG_ChargePostingRQInboundonPremHTNG_ChargePostingRQ | Posting | Transaction | RevenueDetails | RevenueDetail
Codeblock
languagexml
collapsetrue
<RevenueDetails><RevenueDetail Description="Cash" PMSRevenueCode="1" CurrencyCode="AED" Amount="-10.00" SubTypeID="Deposit"><Account ID="342451" Type="14" ID_Context="protelIO"/></RevenueDetail></RevenueDetails>
The new value 'Deposit' can be applied to the SubTypeID attribute. In this case partial payments for the guests who depart on the current business date will be possible.PWS-35093.13.0

IPA 23.38

AnkerIPA 23.38IPA 23.38OTA_HotelResNotifRQoutboundpAirno changes in XMLOnly the current traces for a reservation are sent (from current protel date onwards) and not the ones from the past.IPA-129523.38

IPA 23.36

AnkerIPA 23.36IPA 23.36

OTA_ProfileCreateRQ
OTA_ProfileModifyRQ

outboundpAirCustomer | TPA_Extensions | px:ProfileInfoExtensions | px:DocumentTypes | px:DocumentType 
Codeblock
languagexml
collapsetrue
<TPA_Extensions>
	<px:ProfileInfoExtensions>
		<px:AddressTypes/>
		<px:ContactDetails>
			<px:AdditionalInfo/>
		</px:ContactDetails>
		<px:PersonInfos>
			<px:LastNameAtBirth/>
			<px:FirstNameAtBirth/>
			<px:LastNameMother/>
			<px:FirstNameMother/>
			<px:Language DefaultInd="true">en-us</px:Language>
			<px:VipCodes/>
			<px:MarketingCodes/>
			<px:Keywords/>
		</px:PersonInfos>
		<px:ProfileStatus/>
		<px:DocumentTypes>
			<px:DocumentType DefaultInd="false" DisplaySequence="-1" ID="199" ID_Context="protelIO" RPH="cd434bf7-2fc0-4245-8a1d-f1cd0fd41695" Type="Checking for validation">Checking for validation</px:DocumentType>
			<px:DocumentType DefaultInd="true" DisplaySequence="1" ID="350" ID_Context="protelIO" RPH="9b313b86-b33a-49da-87aa-8c81dd4ea22c" Type="Identity card">Identity card</px:DocumentType>
		</px:DocumentTypes>
		<px:StatisticalInfos/>
		<px:Traces/>
		<px:LogEntries/>
		<px:Memberships/>
	</px:ProfileInfoExtensions>
	<px:UserDefinedFieldExtensions>
		<px:UserDefinedField Name="BM" Type="List">August</px:UserDefinedField>
		<px:UserDefinedField Name="AM" Type="List">September</px:UserDefinedField>
		<px:UserDefinedField Name="DR" Type="List">Allergy</px:UserDefinedField>
	</px:UserDefinedFieldExtensions>
</TPA_Extensions>
<ns2:Name Language="es_ES">Madre</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Tio" ID="5" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Tio</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Tia" ID="6" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Tia</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Tutor Legal" ID="7" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Tutor Legal</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Hijo" ID="8" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Hijo</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Hija" ID="9" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Hija</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Nieto" ID="10" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Nieto</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Nieta" ID="11" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Nieta</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Sobrino" ID="12" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Sobrino</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Sobrina" ID="13" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Sobrina</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Primo" ID="14" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Primo</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Prima" ID="15" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Prima</ns2:Name>
	</ns2:GuestRelationType>
</ns2:GuestRelationTypes>


Due to legal requirements in Spain, we are expanding the GuestRelationTypeselement with the attributes for the relationship types.IPA-135324.08

IPA 24.02

Anker
IPA 24.02
IPA 24.02









OTA_ProfileCreateRQ

OTA_ProfileModifyRQ

outbound

inbound

pAir

Customer | TPA_Extensions | px:ProfileInfoExtensions  | px:AccountingInfos


Codeblock
languagexml
collapsetrue
<Customer>
	<TPA_Extensions>
    ....
        <ProfileInfoExtensions>
            ....         
                <px:AccountingInfos PublicAdministrationInd="true" SplitPaymentInd="true"/>
		</ProfileInfoExtensions>
	</TPA_Extensions>
</Customer>


Due to legal requirements in Italy, we extend 
the AccountingInfos with the attributes 

@PublicAdministrationInd

@SplitPaymentInd


IPA-1346

IPA-1339

24.02

OTA_HotelResNotif

outbound

inbound


pAir

OTA_HotelResNotifRQ | HotelReservations | HotelReservation | ResGuests | ResGuest | Profiles | ProfileInfo | Profile | Customer | TPA_Extensions | px:ProfileInfoExtensions | px:AccountingInfos


Codeblock
languagexml
collapsetrue
<Customer>
	<TPA_Extensions>
    ....
        <ProfileInfoExtensions>
            ....         
                <px:AccountingInfos PublicAdministrationInd="true" SplitPaymentInd="true"/>
		</ProfileInfoExtensions>
	</TPA_Extensions>
</Customer>


Due to legal requirements in Italy, we extend 
the AccountingInfos with the attributes 

@PublicAdministrationInd

@SplitPaymentInd


IPA-1346

IPA-1339

24.02OTA_HotelStayInfoNotifRQoutboundpAir

OTA_HotelStayInfoNotifRQ | StayInfos | StayInfo | HotelReservation | ResGuests | ResGuest | Profiles | ProfileInfo | Profile| Customer | TPA_Extensions | px:ProfileInfoExtensions | px:AccountingInfos

Extension of the TPA extension in the Customer element with DocumentType. IPA-127523.36

IPA 23.32

AnkerIPA 23.32IPA 23.32OTA_HotelResNotifRQ, OTA_ResRetrieveRS outboundpAirRoomStay | RoomTypes | RoomType | TPA_Extension | RoomStatusExtensions


Codeblock
languagexml
collapsetrue
<RoomStays> <RoomStay MarketCode="CORP_GRP" SourceOfBusiness="3PAR"> <RoomTypes> <RoomType IsRoom="true" NumberOfUnits="1" RoomID="53" RoomType="51" RoomTypeCode="CLASTW"> <TPA_Extensions> <px:RoomStatusExtensions> <px:HouseKeepingInfo RoomStatus="1"/> </px:RoomStatusExtensions>
<Customer>
	<TPA_Extensions>
    ....
        <ProfileInfoExtensions>
            ....         
                <px:AccountingInfos PublicAdministrationInd="true" SplitPaymentInd="true"/>
		</ProfileInfoExtensions>
	</TPA_Extensions>
</
RoomType>
Customer>


Due to legal requirements in Italy, we extend 
the AccountingInfos with the attributes 

@PublicAdministrationInd

@SplitPaymentInd


IPA-133924.02OTA_HotelAvailNotifRQ

outbound

inbound

pAir

OTA_HotelAvailNotifRQ |

@MessageContentCode

no changes in xml - new values for MessageContentCode

We use the value 4 for the restrictions on rate group level.

IPA-133424.02OTA_ResRetrieveRS  </RoomTypes>

For reservations that will arrive on the business day, the status of the room (clean, dirty, etc.) will be sent with. 

Possible values: IO Types#RoomStatusType

IPA-125923.32

IPA 23.30

AnkerIPA 23.30IPA 23.30OTA_HotelResNotifRQoutboundpAir

OTA_

HotelResNotifRQ

ResRetrieveRS |

HotelReservations

ReservationsList | HotelReservation |

@RoomNumberLockedIndicator
Codeblock
languagexml
collapsetrue
<HotelReservation CreateDateTime="2023-07-20T12:55:31+02:00" CreatorID="isabell.kniza@protel.net" LastModifierID="isabell.kniza@protel.net" LastModifyDateTime="2023-07-20T12:56:06+02:00" ResStatus="Reserved" RoomNumberLockedIndicator="true"> 


TPA_Extensions | px:ReservationGroupExtensions| px:GroupInfo| 

@GroupName
@GroupID
@PrimaryInd

ResGuests | ResGuest |  TPA_Extensions | px:ReservationGroupExtensions | px:GroupInfo| 

@GroupName
@GroupID
@PrimaryInd



Codeblock
collapsetrue
<TPA_Extensions>
  <px:ReservationGroupExtensions >
    <px:GroupInfo GroupName="Viaggi in Stile SpA -2022-01-17" GroupID="113" PrimaryInd="true" />
  </px:ReservationGroupExtensions >
</TPA_Extensions>


Due to Italian legal requirements (Police reports and Tourism Statistics), we're extending the schema to be able to export information about groups: group name, group ID and group leader.
On reservation level, PrimaryInd="true" will be shown for the reservation containing the group leader profile, all other reservations of this group will be shown with PrimaryInd="false".

On profile/resguest level,  PrimaryInd="true" will be shown for the group leader profile, all other profiles of this group will be shown with PrimaryInd="false".

IPA-104024.02If true, then the room for this reservation cannot be changed by the vendor. If false, then the vendor can be searched for a new available room with the message OTA_ReadRQ. IPA-126023.30