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
22
24.
02
46
2022
2024-
01
12-
12
11
21
24.
50
42
2021
2024-
12
11-
15
13
21
24.
34
42
2021
2024-
08-2521.322021-08-11

Release dates PWS (onPrem) LIVE Environment

11-06  NO regular Release
24.422024-10-30 NO regular Release
24.422024-10-16 NO regular Release
24.382024-09-30
24.382024-09-18 NO regular Release
24.362024-09-04 - IPA update will be now every 4 weeks
24.342024-08-21
24.322024-08-07 NO regular Release
24.302024-07-24 NO regular Release
24.292027-07-17
24.282024-07-10 NO regular Release
24.262024-06-26 NO regular Release
24.242024-06-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


Codeblock
languagexml
collapsetrue
<OTA_ReadRQ
VersionRelease date3.62022-02-023.52021-11-293.42021-09-153.32021-08-04
Affected MessageDirection from protelPMSPathExampleSummaryInternal referenceVersionTBA IDSTBA PWSTBA IPAOTA_HotelInvBlockNotifRQInboundpAirOTA_HotelInvBlockNotifRQ | TPA_Extensions | InvBlockExtensions | CancellationInfo
Codeblock
languagexml
collapsetrue
<TPA_Extensions>
	<px:InvBlockExtensions>
		<px:InvBlockID ID="23" ID_Context="protelIO" Type="18"/>
		<px:CancellationInfo Code="Cancel" ID="13" ID_Context="protelIO" Timestamp="2019-07-30T10:44:26+02:00" Type="1" User="">erreur</px:CancellationInfo>
	</px:InvBlockExtensions>
	<px:ProfileInfoExtensions>
		<px:ContactDetails>
			<px:AdditionalInfo>
				<px:Entry DefaultInd="true" ID="1543" ID_Context="protelIO" RPH="6bee2ab8-f5a0-4ce0-9e50-6a52bff63aab" Type="1">memari</px:Entry>
				<px:Entry ID="1543" ID_Context="protelIO" RPH="be2ab219-99e0-4714-8e30-a6924aa820bf" Type="1"/>
			</px:AdditionalInfo>
		</px:ContactDetails>
	</px:ProfileInfoExtensions>
	<px:ReservationExtensions/>
</TPA_Extensions>
Implement the CancellationInfo for the inbound allotment.IPA-987IPA 22.02  AnkerIPA 22.02IPA 22.02HTNG_HotelFolioRSoutboundOnPremHTNG_HotelFolioNotifRQ | Folios | Folio | RevenueDetails | RevnueDetail | FolioIDs | FolioID Codeblock
languagexml
collapsetrue
<HTNG_HotelFolioRS> <Folios> <Folio> <RevenueDetails> <RevenueDetail> <FolioIDs xmlns="http://www.opentravel.org/OTA/2003/05"> <FolioID>SDate|2017-08-23</FolioID> <FolioID>InvID|122345</FolioID> </FolioIDs> <RevenueDetailItems> <RevenueDetailItem> <FolioIDs
 xmlns="http://www.opentravel.org/OTA/2003/05
"> <FolioID>SDate|2017-08-23</FolioID> </FolioIDs>
" 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-3822TBA
TBA 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


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

TBA
IO_SystemDataRQinboundpAir

IO_SystemDataRQ | Request | Rates 

Add a short in front of the FolioID Element, to describe what is displayed

Possible values

  • InvID
  • InvNo
  • GstID
  • Code
  • TAAGrp
  • PkgID
  • SDate
PWS-2961PWS 3.5.XHTNG_HotelFolioNotifRQoutboundOnPremHTNG_HotelFolioNotifRQ | Folios | Folio | RevenueDetails | RevnueDetail | FolioIDs | FolioID
Codeblock
languagexml
collapsetrue
<HTNG_HotelFolioNotifRQ>
	<Folios>
		<Folio>
			<RevenueDetails>
				<RevenueDetail>
					<FolioIDs xmlns="http://www.opentravel.org/OTA/2003/05">
						<FolioID>SDate|2017-08-23</FolioID>
                                                <FolioID>InvID|122345</FolioID>
					</FolioIDs>
					<RevenueDetailItems>
						<RevenueDetailItem>
							<FolioIDs xmlns="http://www.opentravel.org/OTA/2003/05">
								<FolioID>SDate|2017-08-23</FolioID>
							</FolioIDs>

Add a short in front of the FolioID Element, to describe what is displayed

Possible values

  • InvID
  • InvNo
  • GstID
  • Code
  • TAAGrp
  • PkgID
  • SDate
PWS-2961PWS 3.5.XIPA 21.50  AnkerIPA 21.50IPA 21.50OTA_HotelInvBlockNotifRQInboundpAirOTA_HotelInvBlockNotifRQ | InvBlocks | InvBlock | RoomTypes | RoomType | RatePlans | RatePlan | MarketCode
Codeblock
languagexml
collapsetrue
									...
									<RateDescription Name="RateGroup">
										<Text TextFormat="PlainText">BAR</Text>
									</RateDescription>
									<MarketCode MarketCode="FAM" MarketCodeName="Famille"/>
								</RatePlan>
							</RatePlans>
						</RoomType>
					</RoomTypes>
					...

Implement the MarketCode for inbound allotments.IPA-98821.50PWS 3.6.X  AnkerPWS 3.6.XPWS 3.6.XHTNG_HotelChargePostingRQinboundOnPremHTNG_HotelChargePostingRQ | Posting | Transaction | RevenueDetails | RevenueDetail | @ReferenceID


Codeblock
languagexml
collapsetrue
<HTNG_ChargePostingRQ>
	<Posting ID="1">
		<Transaction TicketID="1">
			<RevenueDetails>
				<RevenueDetail Description="Upsell Article" PMSRevenueCode="1000" ReferenceID="1015" Amount="20.00" SubTypeID="Revenue">
					<ExtendedPrice AmountAfterTax="20.00" DecimalPlaces="2" Quantity="1"/>
					<Account ID="341977-2" Type="16" ID_Context="protelIO"/>
				</RevenueDetail>
With the Attribute @ReferenceID it will be possible to post as well articles. In the Attribute @ReferenceID the Article ID needs to be sent to Protel. In the Attribute @PMSRevenueCode the TAA from the article should be providedPWS-2996PWS 3.6.XIO_RatePackageNotifRQoutboundOnPremIO_RatePackageNotifRQ | Packages | Package | PackageItem | Calculation
    <p:Request xmlns:p="http://protel.io/soap">
        <p:UniqueID Type="10" ID="2575" ID_Context="protelIO"/>
        <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

TBA
IO_SystemDataRSoutboundpAir 

IO_SystemDataRS | SystemData | Rates | RatePlans | RatePlan


Codeblock
languagexml
collapsetrue
<IO_RatePackageNotifRQ>
	<Packages>
		<Package>
			<PackageItems>
				<PackageItem>
					<Calculation AmountBeforeTax="40" AmountAfterTax="40" Currency="AED" InclusiveInd="true" Recurrence="Daily" Relation="Complex">
						<DaysOfWeek Mon="true" Tue="true" Wed="true" Thu="true" Fri="true" Sat="true" Sun="true"/>

Fix the values for the Recurrence Attribute

Possible Recurrence

  • OnArrival
  • OnDeparture
  • Daily
  • DaysOfWeek
  • Floating
  • Fixed
PWS-3001


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.19.X 

Anker
PWS 3.19.X
PWS 3.19

PWS 3.6

.X

OTA_HotelResNotifRQ

outbound

inbound

OnPrem

OTA_HotelResNotifRQ | HotelReservations | HotelReservation | TPA_Extensions | px:ReservationExtensions | px:FixedCharges | px:FixedCharge | px:ServiceDates | px:ServiceDate

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="http://protel.io/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
Codeblock
languagexml
collapsetrue
<TPA_Extensions xmlns:px="http://protel.io/htng/extensions"> <px:ReservationExtensions> <px:FixedCharges> <px:FixedCharge Code="KosmetikExtNoR" Recurrence="floating" From="2021-01-05" To="2021-01-12" Quantity="1" RequestedIndicator="true"> <px:Price CurrencyCode="EUR" SingleAmountAfterTax="25.00"/> <px:UniqueID Type="FixedCharge" ID="103604
" ID_Context="protelIO"/>
		
<px
<p:
Item
Rates 
ItemID
IncludeInvisible="
75
true"/>
	
<px:InvoiceText>Kosmetik täglich ab 5.1.
</
px
p:
InvoiceText> <px:ServiceDates> <px:ServiceDate From="2021-01-05" To="2021-01-07"/> <px:ServiceDate From="2021-01-10" To="2021-01-12"/> </px:ServiceDates> </px:FixedCharge> </px:FixedCharges> </px:ReservationExtensions> </TPA_Extensions>

Add the new Element "SerivceDates"

This Element will be displayed for the Recurrence= "floating"

Possible Recurrence

  • OnArrival
  • OnDeparture
  • Daily
  • DaysOfWeek
  • Floating
  • Fixed
PWS-2547PWS 3.6.XHTNG_HotelFolioRSoutboundOnPrem
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" Visible="true">
					<ns2:Name Language="en">Brother</ns2:Name>
				</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@TaxInclusive
HTNG_HotelFolioNotifRQ | Folios | Folio | RevenueDetails | RevnueDetail | FolioIDs | FolioID


Codeblock
languagexml
collapsetrue
<HTNG_HotelFolioRS>
	<Folios>
		<Folio>
			<RevenueDetails>
				<RevenueDetail>
					<FolioIDs xmlns="http://www.opentravel.org/OTA/2003/05">
						<FolioID>SDate|2017-08-23</FolioID>
                                                <FolioID>InvID|122345</FolioID>
					</FolioIDs>
					<RevenueDetailItems>
						<RevenueDetailItem>
							<FolioIDs xmlns="http://www.opentravel.org/OTA/2003/05">
								<FolioID>SDate|2017-08-23</FolioID>
							</FolioIDs>

Add a short in front of the FolioID Element, to describe what is displayed

Possible values

  • InvID
  • InvNo
  • GstID
  • Code
  • TAAGrp
  • PkgID
  • SDate
PWS-2961PWS 3.5.XHTNG_HotelFolioNotifRQoutboundOnPremHTNG_HotelFolioNotifRQ | Folios | Folio | RevenueDetails | RevnueDetail | FolioIDs | FolioID
Codeblock
languagexml
collapsetrue
<HTNG_HotelFolioNotifRQ>
	<Folios>
		<Folio>
			<RevenueDetails>
				<RevenueDetail>
					<FolioIDs xmlns="http://www.opentravel.org/OTA/2003/05">
						<FolioID>SDate|2017-08-23</FolioID>
                                                <FolioID>InvID|122345</FolioID>
					</FolioIDs>
					<RevenueDetailItems>
						<RevenueDetailItem>
							<FolioIDs xmlns="http://www.opentravel.org/OTA/2003/05">
								<FolioID>SDate|2017-08-23</FolioID>
							</FolioIDs>

Add a short in front of the FolioID Element, to describe what is displayed

Possible values

  • InvID
  • InvNo
  • GstID
  • Code
  • TAAGrp
  • PkgID
  • SDate
PWS-2961PWS 3.5.XIO_StatsNotifRQoutboundOnPremIO_StatsNotifRQ | Statistics | Statistic | StatisticApplicationSet | RevenueCategorySummaries Codeblock
languagexml
collapsetrue
<IO_StatsNotifRQ/> <Statistics> <Statistic> <StatisticApplicationSets> <StatisticApplicationSet Start="2021-10-28" End="2021-10-28"> <StatisticCodes> <StatisticCode StatCode="Group" StatCategoryCode="3" />
<RatePlan 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-3246
3.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-1365TBA
IO_SystemDataRSoutboundpAir

IO_SystemDataRS | SystemData | Accounting | InvoiceFormat


Codeblock
languagexml
collapsetrue
              
<StatisticCode
 
StatCode="1"
 
StatCategoryCode="Pseudo"
 
/>
   <ns2:InvoiceFormats>
           
</StatisticCodes>
             
<RevenueCategorySummaries>
<ns2:InvoiceFormat Code="ItemsSortDate">
                
<RevenueCategorySummary
 
RevenueCategoryCode="3"
 
CurrencyCode="EUR"
 
Amount="0.00"
 
/>
        
<RevenueCategorySummary RevenueCategoryCode="6" CurrencyCode="EUR" Amount="0.00" />
<ns2:Description Language="en_US">Single items, sort by date</ns2:Description>
                    
<RevenueCategorySummary
 
RevenueCategoryCode="9"
 
CurrencyCode="EUR"
 
Amount="0.00"
 </
>
ns2:InvoiceFormat>
                      
<RevenueCategorySummary
 
RevenueCategoryCode="17" CurrencyCode="EUR" Amount="0.00" />
 <ns2:InvoiceFormat Code="ItemsSortGuest">
                            
<RevenueCategorySummary
<ns2:Description 
RevenueCategoryCode
Language="
123
en_US"
CurrencyCode="EUR" Amount="0.00" />
>Single items, sort by guest</ns2:Description>
                    
<RevenueCategorySummary
 
RevenueCategoryCode="126"
 
CurrencyCode="EUR"
 
Amount="0.00"
 </
>
ns2:InvoiceFormat>
                     
<RevenueCategorySummary
  
RevenueCategoryCode="129" CurrencyCode="EUR" Amount="0.00" />
 <ns2:InvoiceFormat Code="ItemsSortRoom">
                       
<RevenueCategorySummary RevenueCategoryCode="1217" CurrencyCode="EUR" Amount="0.00" />
     <ns2:Description Language="en_US">Single items, sort by room</ns2:Description>
            
</RevenueCategorySummaries>
            </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 

If the all value for the RevenueCategorySummaries is zero, we will not display the ElementPWS-2998PWS 3.5.XPWS 3.5.X  AnkerPWS 3.5.XPWS 3.5.XOTA_HotelStayInfoNotifRQoutboundOnPremOTA_HotelStayInfoNotifRQ | StayInfos | StayInfo | RevenueCategory | @RevenueCategoryCode="2000"
Codeblock
languagexml
collapsetrue
<RevenueCategory RevenueCategoryCode="2000">
	<SummaryAmount CurrencyCode="AED" Amount="-122.50"/>
	<RevenueDetails>
		<RevenueDetail ReferenceID="575679481" TransactionDate="2019-08-30" RatePlanCode="0" Description="MASTER CARD" PMSRevenueCode="12" CurrencyCode="AED" Amount="-32.40">
			<FolioIDs>
				<FolioID>InvID|408918</FolioID>
				<FolioID>ResID|2390678</FolioID>
				<FolioID>GstID|5391177</FolioID>
				<FolioID>TAAGrp|PAYMENTS</FolioID>
			</FolioIDs>
		</RevenueDetail>
		<RevenueDetail ReferenceID="575679479" TransactionDate="2019-08-30" RatePlanCode="0" Description="CASH (AED)" PMSRevenueCode="1" CurrencyCode="AED" Amount="-20.0">
			<FolioIDs>
				<FolioID>InvID|408918</FolioID>
				<FolioID>ResID|2390678</FolioID>
				<FolioID>GstID|5391177</FolioID>
				<FolioID>TAAGrp|PAYMENTS</FolioID>
			</FolioIDs>
		</RevenueDetail>
		<RevenueDetail ReferenceID="575679478" TransactionDate="2019-08-30" RatePlanCode="0" Description="DISCOVERY Dollars" PMSRevenueCode="146" CurrencyCode="AED" Amount="-55.10">
			<FolioIDs>
				<FolioID>InvID|408918</FolioID>
				<FolioID>ResID|2390678</FolioID>
				<FolioID>GstID|5391177</FolioID>
				<FolioID>TAAGrp|PAYMENTS</FolioID>
			</FolioIDs>
		</RevenueDetail>
		<RevenueDetail ReferenceID="575679480" TransactionDate="2019-08-30" RatePlanCode="0" Description="JCB CARD" PMSRevenueCode="14" CurrencyCode="AED" Amount="-15.00">
			<FolioIDs>
				<FolioID>InvID|408918</FolioID>
				<FolioID>ResID|2390678</FolioID>
				<FolioID>GstID|5391177</FolioID>
				<FolioID>TAAGrp|PAYMENTS</FolioID>
			</FolioIDs>
		</RevenueDetail>
	</RevenueDetails>

Add a new @RevenueCategoryCode = 2000 for Payments 

needs to be disabled via Xsetup

PWS-3014PWS 3.5.1OTA_ProfileModifyRQ
OTA_ProfileCreateRQOutboundOnPremOTA_ProfileModifyRQ | ProfileModify | StatusCode
Codeblock
languagexml
collapsetrue
<ProfileModify RPH="155474" LastModifyDateTime="2021-08-11T15:08:20.1833472+02:00" StatusCode="3" />

Extend the StatusCode for Profiles

1= Marked for deletion

2= anonymized profile 

3=deleted profile

4 = active

PWS-2955PWS 3.5.XOTA_HotelResNotifRQOutboundOnPrem
  1. OTA_HotelResNotifRQ | HotelReservations | HotelReservation | TPA_Extensions | px:UserDefinedFieldExtensions
  2. OTA_HotelResNotifRQ | HotelReservations | HotelReservation | ResGuests | ResGuest | Profiles | ProfileInfo | Profile | Customer | px:TPA_Extensions | px:UserDefinedFieldExtensions
  3. OTA_HotelResNotifRQ | HotelReservations | HotelReservation | ResGuests | ResGuest | Profiles | ProfileInfo | Profile | TPA_Extensions | px:UserDefinedFieldExtensions
Codeblock
languagexml
collapsetrue
<TPA_Extensions xmlns:px="http://protel.io/htng/extensions">
	<px:UserDefinedFieldExtensions>
		<px:UserDefinedField Name="BWI Group" Type="Integer">local</px:UserDefinedField>
		<px:UserDefinedField Name="BWI Cancellation Date" Type="Date"/>
		<px:UserDefinedField Name="BWI Cancellation Time" Type="DateTime"/>
		<px:UserDefinedField Name="BWI Groupratecode" Type="String">GRP Test</px:UserDefinedField>
	</px:UserDefinedFieldExtensions>
</TPA_Extensions>
Added UDF information on reservation level (1.), on private profile level (2.) and on company/source/travel agent profile level (3.).PWS-2907PWS 3.5.XOTA_ProfileModifyoutboundonPremOTA_ProfileModifyRQ | ProfileModify | TPA_Extensions | px:ProfileInfoExtensions | PersonInfos | Registration | @LicensePlate


Codeblock
languagexml
collapsetrue
<px:TPA_Extensions xmlns:px="http://protel.io/htng/extensions">
	<px:ProfileInfoExtensions>
		<px:PersonInfos>
			<px:Registration LicensePlate="AB-12345" />
		</px:PersonInfos>
		<px:Salutation ID="1" ID_Context="protelIO" Type="Salutation">Dear Mrs. memari21</px:Salutation>
	</px:ProfileInfoExtensions>
	<px:UserDefinedFieldExtensions>
		<px:UserDefinedField Name="Pet Name" Type="String">pepelolo</px:UserDefinedField>
	</px:UserDefinedFieldExtensions>
</px:TPA_Extensions>
Add the license plate to the outbound profile MessagePWS-2916PWS 3.5.XOTA_ProfileModifyRQ
OTA_ProfileCreateRQinboundOnPrem
OTA_ProfileCreateRQ | Profile | CompanyInfo | CompanyName 
Codeblock
languagexml
collapsetrue
<OTA_ProfileCreateRQ>
	<UniqueID Type="4" ID="615" ID_Context="External"/>
	<Profile>
		<CompanyInfo>
			<CompanyName CompanyShortName="CKO" Department="DEP">Protel Hotelsoftware GmbH</CompanyName>
with an inboud Profile you can create / change the Department Attribute Information, the Information in the Database where the Department name is stored is "Kunden.abteil" CompanyName | @DepartmentPWS-2855PWS 3.5.XOTA_ProfileModifyRQ
OTA_ProfileCreateRQInboundOnPrem
<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

OTA_ProfileModifyRQ | ProfileModify | Comments | Comment
OTA_ProfileCreateRQ | ProfileModify | Comments | Comment


Codeblock
languagexml
collapsetrue
<ProfileModify ShareAllOptOutInd="Yes" ProfileType="1" CreateDateTime="2021-01-20T14:42
<p:Invoice BusinessDate="2022-08-09" ExternallyFiscalized="false" FiscalCode="gg12cc" FiscalCodeID="2" FiscalCodeName="Test_AB" FiscalDate="2024-03-27T08:31:34+01:00" 
CreatorID
Fiscalized="
protelIO
true" 
RPH
InvoiceCode="
155522
RE_23" 
LastModifyDateTime
InvoiceDate="
2021
2024-
09
03-
29T12
27T08:31:34
:49
+01:00" InvoiceID="34" 
LastModifierID
Open="false"
protel
 
37
PastEndOfDay="false" 
StatusCode
SystemFiscalCode1="
4
AA"
> <Customer
 
Gender
SystemFiscalCode2="
Unknown
bb" 
Language
SystemFiscalCode3="cc"
ENG"> <PersonName> <GivenName>ali</GivenName> <Surname>memari13</Surname> </PersonName> <Telephone ShareMarketInd="No" PhoneNumber="123456" PhoneLocationType="6" PhoneTechType="1" FormattedInd="false" DefaultInd="true" /> <Address FormattedInd="false" ShareMarketInd="No" Type="1" DefaultInd="true" UseType="6"> <AddressLine>str01</AddressLine> <StateProv/> <CountryName Code="DE">Germany</CountryName> </Address> <CitizenCountryName DefaultInd="true" Code="DE" /> <Document /> <EmployerInfo CompanyShortName="" Department=""/> </Customer> <TPA_Extensions xmlns:px="http://protel.io/htng/extensions" /> <Comments> <Comment Name="Customer_Comment"> <Text TextFormat="PlainText">Remark visible to all Hotels</Text> </Comment> <Comment Name="Restaurant_Comment"> <Text TextFormat="PlainText">Notes to restaurant</Text> </Comment> </Comments> </ProfileModify>Importing Restuarant and Customer notes is possible for OnPrem. There is an extra Xsetup to active/deactive override notes in OnPrem.
pws | override_profile_notesPWS-2890PWS 3.5.X
 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

 

OTA_ProfileModifyRQ
OTA_ProfileCreateRQinboundOnPremOTA_ProfileModifyRQ | ProfileModify | Customer | Address

Codeblock
languagexml
collapsetrue
<OTA_ProfileModifyRQ>
	<UniqueID Type="4" ID="615" ID_Context="External"/>
		<ProfileModify ShareAllOptOutInd="Yes" ProfileType="1" CreateDateTime="2021-08-11T12:42:00" 	CreatorID="protel 1" RPH="12" LastModifyDateTime="2021-08-31T09:05:24" LastModifierID="protel 1" StatusCode="4">
			<Customer Gender="Male" BirthDate="1980-10-20" VIP_Indicator="true" Language="de" CustomerValue="V6 – Previous Feedback Guest|0;V7 – Long Stay Guest |2;V8 – Black Listed Guest|2">
				<Address FormattedInd="false" ShareMarketInd="No" Type="1" DefaultInd="true" UseType="6">
					<AddressLine>Main Address 110</AddressLine>
					<CityName>Osterode</CityName>
					<PostalCode>37520</PostalCode>
					<StateProv>Niedersachsen</StateProv>
					<CountryName Code="DE">Germany</CountryName>
				</Address>
It is possible to send inbound Customer profile modify request with AddressLine , CityName and PostCodePWS-2864PWS 3.5.XPWS 3.4.X 
<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

 

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_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

 

AnkerPWS 3.4.XPWS 3.4.XOTA_ProfileModifyRQ
OTA_ProfileCreateRQOutboundOnPremProfile | Outbound | Document element | remove @BirthDate Attribute

Codeblock
languagexml
collapsetrue
<OTA
<TPA_
ProfileModifyRQ> <ProfileModify> <Customer BirthDate="1980-09-21T00:00:00"> <Document DocID="M1544474" DocType="2" ExpireDate="2025-10-10"/> <Document DocID="M1544474" ExpireDate="2025-10-10"/> <Document DocID="M1544474" ExpireDate="2025-10-10"/> <Document DocID="M1544474" ExpireDate="2025-10-10"/>@BirthDate attribute will be removed from this element.PWS-2823PWS 3.4.XOTA_HotelInvCountNotifRQoutboundOnPremno changes in XMLSend Delta inventory changesPWS-112PWS 3.4.X
Extensions>
    <px:GuestStayExtensions>
        <px:StayInfo Arrival="2024-02-07T12:00:00+01:00" Departure="2024-02-08T12:00:00+01:00" PrimaryInd="true" Role="LinkedProfile" Status="Reserved"/>
        <px:TelephoneSetting ClassOfService="3"/>
    </px:GuestStayExtensions>
</TPA_Extensions>


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 
HTNG_HotelFolioRS/HTNG_HotelFolioNotifRQoutboundOnPrem

HTNG_HotelFolioNotifRQ | Folios | Folio | @FolioID

HTNG_HotelFolioNotifRQ | Folios | Folio | @InvoiceID


Codeblock
languagexml
collapsetrue
<HTNG_HotelFolioNotifRQ> <UniqueID Type="14
<ns2:GuestRelationTypes>
	<ns2:GuestRelationType Code="Abuelo" ID="
341806
1" ID_Context="protelIO" PrimaryInd="false" 
/
Visible="true">
<Folios> <Folio FolioID="341806-0" FolioGroupingID="Closed" FolioType="Room" InvoiceID="340" GuestPayable="true"/> <Folio FolioID="341806-1" FolioGroupingID="Open" FolioType="Room" InvoiceID="0" GuestPayable="true">

@FolioID will always display the ReservationID+Folio

@InvoiceID will always display the InvoiceID as soon as it is created

PWS-2774PWS 3.4.XOTA_ProfileModifyRQoutboundOnPremOTA_ProfileModifyRQ | ProfileModify | StatusCode
Codeblock
languagexml
collapsetrue
<ProfileModify RPH="155474" LastModifyDateTime="2021-08-11T15:08:20.1833472+02:00" StatusCode="2" />

Extend the StatusCode for Profiles

1= Marked for deletion

2= Lapsed

PWS-1168PWS 3.4.XIO_StatsNotifRQoutboundOnPremIO_StatsNotifRQ | Statistics | Statistic | StatisticApplicationSets | StatisticApplicationSet | CountCategorySummaries | CountCategorySummary
Codeblock
languagexml
collapsetrue
<StatisticApplicationSet Start="2018-09-12" End="2018-09-12">
	<StatisticCodes/>
	<RevenueCategorySummaries>
		<RevenueCategorySummary RevenueCategoryCode="3" CurrencyCode="EUR" Amount="0.00"/>
		<RevenueCategorySummary RevenueCategoryCode="6" CurrencyCode="EUR" Amount="160.00"/>
		<RevenueCategorySummary RevenueCategoryCode="9" CurrencyCode="EUR" Amount="1000.00"/>
		<RevenueCategorySummary RevenueCategoryCode="17" CurrencyCode="EUR" Amount="1160.00"/>
		<RevenueCategorySummary RevenueCategoryCode="123" CurrencyCode="EUR" Amount="0.00"/>
		<RevenueCategorySummary RevenueCategoryCode="126" CurrencyCode="EUR" Amount="160.00"/>
		<RevenueCategorySummary RevenueCategoryCode="129" CurrencyCode="EUR" Amount="1000.00"/>
		<RevenueCategorySummary RevenueCategoryCode="1217" CurrencyCode="EUR" Amount="1160.00"/>
	</RevenueCategorySummaries>
	<CountCategorySummaries>
		<CountCategorySummary SummaryCount="86" CountCategoryCode="8"/>
		<CountCategorySummary SummaryCount="0" CountCategoryCode="9"/>
		<CountCategorySummary SummaryCount="0" CountCategoryCode="10"/>
		<CountCategorySummary SummaryCount="4" CountCategoryCode="11"/>
		<CountCategorySummary SummaryCount="4" CountCategoryCode="12"/>
		<CountCategorySummary SummaryCount="0" CountCategoryCode="13"/>
		<CountCategorySummary SummaryCount="0" CountCategoryCode="14"/>
		<CountCategorySummary SummaryCount="0" CountCategoryCode="15"/>
		<CountCategorySummary SummaryCount="0" CountCategoryCode="19"/>
		<CountCategorySummary SummaryCount="0" CountCategoryCode="22"/>
	</CountCategorySummaries>
</StatisticApplicationSet>
Add the CountCategorySummary to the property levelPWS-2746PWS 3.4.XIPA 21.34  AnkerIPA 21.34IPA 21.34HTNG_ChargePostingRQinboundpAirno changes in XMLOnly negative amounts are allowed, positive amounts will not be processed.IPA-943IPA 21.34IPA 21.32  AnkerIPA 21.32IPA 21.32OTA_HotelResNotifRQ InboundpAirOTA_HotelResNotifRQ | HotelReservations | HotelReservation | RoomStays | RoomStay | RoomRates | RoomRate
Codeblock
languagexml
collapsetrue
<RoomRate BookingCode="JST" EffectiveDate="2020-08-31" ExpireDate="2020-09-01" InvBlockCode="" NumberOfUnits="1" RatePlanCategory="BAR" RatePlanCode="Alireza" RatePlanID="28" RoomID="10-2L" RoomTypeCode="JST">
Receiving an inbound reservation with @InvBlockCode = "" will delete and remove the assigned allotment.IPA-823IPA 21.32PWS 3.3.X  AnkerPWS 3.3.XPWS 3.3.XHTNG_HotelCheckInNotifRQOutboundOnPremwhole messageHTNG_HotelCheckInNotifRQ implemented for OnPrem and it generates as soon as the room gets check in.PWS-2737PWS 3.3.X
		<ns2:Name Language="es_ES">Abuelo</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Abuela" ID="2" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Abuela</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Padre" ID="3" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<ns2:Name Language="es_ES">Padre</ns2:Name>
	</ns2:GuestRelationType>
	<ns2:GuestRelationType Code="Madre" ID="4" ID_Context="protelIO" PrimaryInd="false" Visible="true">
		<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

HTNG_HotelCheckOutNotifRQOutboundOnPremwhole messageHTNG_HotelCheckOutNotifRQ implemented for OnPrem and it generates as soon as the room gets check out.PWS-2735PWS 3.3.X

HTNG_HotelFolioNotifRQ

HNTG_HotelFolioRS

outboundonPrem

no changes in XML

GuestPayable = false should be used for all types of payments that have the type DEBITOR assigned.

GuestPayable = true should be used for all types of payments that have the type CC assigned.

PWS-2677PWS 3.3.XHTNG_HotelCheckOutNotifRQ outboundOnPrem

no changes in XML

HTNG_HotelCheckOutNotifRQ/RSImplement the HTNG_HotelCheckOutNotifRQ outboundPWS-2735PWS 3.3.XHTNG_HotelCheckInNotifRQ outboundOnPremno changes in XMLHTNG_HotelCheckInNotifRQ/RSImplement the HTNG_HotelCheckInNotifRQ outboundPWS-2737PWS 3.3.X

OTA_ProfileCreateRQ

OTA_ProfileModifyRQ

outboundOnPremOTA_ProfileModifyRQ | ProfileModify | Customer | TPA_Extensions | px:UserDefinedFieldExtensions


Codeblock
languagexml
collapsetrue
<OTA_ProfileCreateRQ>
<Customer>
	
<Profile> <Customer> <TPA_Extensions> <px:UserDefinedFieldExtensions> <px:UserDefinedField Name="Test" Type="Integer">1</px:UserDefinedField> <px:UserDefinedField Name="Test_2" Type="String">222</px:UserDefinedField> </px:UserDefinedFieldExtensions> </TPA_Extensions>Add the Element px:UserDefinedFieldExtensions to the outbound Profile messagePWS-2704PWS 3.3.XOTA_HotelResNotifRQoutboundOnPremOTA_HotelResNotifRQ | HotelReservations | HotelReservation | ResGuests | ResGuest | TPA_Extension | StayInfo | @RegistrationCode
<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_HotelStayInfoNotifRQoutboundpAir

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


Codeblock
languagexml
collapsetrue
<OTA_HotelResNotifRQ> <HotelReservations> <HotelReservation> <ResGuests> <ResGuest>
<Customer>
	<TPA_Extensions>
<px:GuestStayExtensions> <px:StayInfo Arrival="2021-07-15T14:19:00" Departure="2021-07-18T08:24:00" RegistrationCode="10006"/> </px:GuestStayExtensions>Add the new Attribute @RegistrationCode to display the Registration NumberPWS-2733PWS 3.3.XOTA_HotelResNotifRQoutboundOnPremOTA_HotelResNotifRQ | HotelReservations | HotelReservation | Services
Codeblock
languagexml
collapsetrue
<Service ID="1" ID_Context="protelIO" Type="18" ServicePricingType="Per stay" ServiceInventoryCode="Notebook" InventoryBlockCode="Technik" Quantity="1" RequestedIndicator="true">
	<ServiceDetails>
		<TimeSpan Start="pobjres.d1" End="pobjres.d2"/>
		<Comments>
			<Comment Name="RentableObject" >
				<Text TextFormat="PlainText">Notebook</Text>
			</Comment>
		</Comments>
	</ServiceDetails>
</Service>
OTA_HotelResNotifRQ | HotelReservations | HotelReservation | Services | ServiceServiceDetails | Comments | Comment | @Name="RentableObject"PWS-11463.3.XHTNG_HotelCheckInNotifRQinboundOnPremno changes in XMLIn case of receiving a Check-in for a reservation without assigned room. The PWS takes the first available clean/checked room when choosing a RoomID in order to assign it to the reservation. 
In OnPrem it is possible to assign preferred rooms in a ProfilePWS-2656

    ....
        <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-133924.02
OTA_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.02
OTA_ResRetrieveRS outboundpAir

OTA_ResRetrieveRS | ReservationsList | HotelReservation |
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.02
3.3.X