Seitenhistorie

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

Version	Release date

22

24.

24

46

2022

2024-

06

12-

15

11

22

24.

22

42

2022

2024-

06

11-

01

13

22

24.

20

42

2022

2024-

05-1822.182022-05-0422.162022-04-2022.142022-04-0622.122022-03-2322.102022-03-1922.082022-02-2322.062022-02-0922.042022-01-2622.022022-01-1221.502021-12-15

11-06 NO regular Release
24.42	2024-10-30 NO regular Release
24.42	2024-10-16 NO regular Release
24.38	2024-09-30
24.38	2024-09-18 NO regular Release
24.36	2024-09-04 - IPA update will be now every 4 weeks
24.34	2024-08-21
24.32	2024-08-07 NO regular Release
24.30	2024-07-24 NO regular Release
24.29	2027-07-17
24.28	2024-07-10 NO regular Release
24.26	2024-06-26 NO regular Release
24.24	2024-06-12
24.22	2024-05-29
24.20	2024-05-15
24.18	NO regular Release on Wednesday 01.05.2024 due to public Holiday in Germany
24.16	2024-04-17
24.14	2024-04-03
24.12	2024-03-20
24.10	2024-03-06
24.08	2024-02-21
24.06	2024-02-07
24.04	2024-01-24
24.02	2024-01-10

Release dates PWS (onPrem) LIVE Environment

Version	Release date
3.19	2024-10
3.18	2024-05-22*
3.17	2024-03-06
3.16	2023-12-20

*: delayed

Release dates ESB (I/O) LIVE Environment

Version	Release date
2.6.3	2024-11-06
2.6.2	2024-09-25
2.6.1	2024-08-21
2.6.0	2024-07-15
2.5.3	2024-06-10
2.5.2	2024-05-15
2.5.1	2024-04-10
2.5.0	2024-02-26

Release dates PWS (onPrem) LIVE Environment

VersionRelease date3.62022-02-023.52021-11-29

Codeblock

language	xml
title	RoomID
collapse	true

<OTA_HotelResNotifRQ>
    <HotelReservations>
        <HotelReservation ResStatus="In-house">
            <RoomStays>
                <RoomStay MarketCode="AK22">
                    <RoomTypes>
                        <RoomType RoomID="15012" RoomTypeCode="JUNS"/>
                    </RoomTypes>
                    <RoomRates>
                        <RoomRate EffectiveDate="2022-08-04" ExpireDate="2022-08-06" RoomID="15012" RoomTypeCode="JUNS">

In-house reservations can not have the RoomID modified with this message.
Other data like MarketCode, DepartureDate, Services remains modifiable with this message.IPA-100922.04IPA 22.02 AnkerIPA 22.02IPA 22.02

IO_SystemDataRS
IO_ResModifyNotifRS
IO_InvoiceFiscalizeRS

outboundpAirIO_SystemDataRS | Success
IO_ResModifyNotifRS | Success
IO_InvoiceFiscalizeRS | Success

New xsd:

Codeblock

language	xml
title	Success
collapse	true

<xs:complexType name="IOMessageResultType">
    <xs:sequence>
        <xs:element minOccurs="0" name="Success">
            <xs:complexType>
                <xs:annotation>
                    <xs:documentation xml:lang="en">Existence of element in RS message signals successful processing.</xs:documentation>
                </xs:annotation>
            </xs:complexType>
        </xs:element>

Currently the <Success> element, if present, appears with Boolean value. (e.g. <Success>true</Success>)

With this change, the <Success> element, if present, will appear only as empty element. (e.g. <Success/>)

IPA-997

22.02OTA_HotelResNotifRQ outboundOnPrem

TBA IDS

TBA ESB
Bulk Export from SMP UI	outbound	OnPrem pAir	n/a	no schema change	Each 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-2928	TBA
Bulk Export from SMP UI	outbound	OnPrem pAir	n/a	no 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-8229	2.5.4

TBA PWS
OTA_ReadRQ/OTA_ResRetrieveRS	inbound	onPremise	extend the Reservation search by roomtypes

Codeblock

language	xml
collapse	true

<TPA

<OTA_

Extensions

ReadRQ xmlns

:px

="http://

protel.io/htng/extensions

www.opentravel.org/OTA/2003/05" CorrelationID="PWS-3822_LJ_01" TimeStamp="2021-08-26T10:10:00Z">

<px:ReservationExtensions>

<POS>

<px:FixedCharges>

<Source>

<px:FixedCharge

<RequestorID

Code

ID="

KosmetikExtNoR

3151"

Recurrence

Type="

floating

10"

From

ID_Context="

2021-01-05" To="2021-01-12" Quantity="1" RequestedIndicator="true"

protelIO"/>
			<BookingChannel Type="4" Primary="true"/>

<px:Price CurrencyCode="EUR" SingleAmountAfterTax="25.00"/> <px:UniqueID Type="FixedCharge" ID="103604" ID_Context="protelIO

</Source>
	</POS>
	<ReadRequests>
		<HotelReadRequest>
			<SelectionCriteria Start="2017-10-10" End="2017-10-10" ResStatus="Reserved"/>
			<TPA_Extensions>
				<px:

Item

ReadRequestExtensions

ItemID

xmlns:px="

75"/

http://protel.io/htng/extensions">
					<px:

InvoiceText>Kosmetik täglich ab 5.1.</px:InvoiceText> <px:ServiceDates> <px:ServiceDate From="2021-01-05" To="2021-01-07"

Room RoomTypeCode="Cl-Twin"/>

<px:ServiceDate From="2021-01-10" To="2021-01-12"/>

</px:

ServiceDates>

ReadRequestExtensions>
			</

px:FixedCharge>

TPA_Extensions>
		</

px:FixedCharges>

HotelReadRequest>
	</

px:ReservationExtensions>

ReadRequests>
</

TPA

OTA_

Extensions>

ReadRQ>

In the ReadRQ it is now possible to request the RoomType in addition to the time period and reservation status.

PWS-3822

TBA

TBA IPA

IO_SystemDataRS

outbound

pAir

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 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 / inbound

pAir

OTA_ProfileModifyRQ | ProfileModify | Customer | Document

Codeblock

language	xml
collapse	true

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

inbound

pAir

IO_SystemDataRQ | Request | Rates

Add the new Element "SerivceDates"

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

Possible Recurrence

OnArrival
OnDeparture
Daily
DaysOfWeek
Floating
Fixed

IPA-98522.02OTA_HotelInvBlockNotifRQInboundpAirOTA_HotelInvBlockNotifRQ | TPA_Extensions | InvBlockExtensions | CancellationInfo

Codeblock

language	xml
collapse	true

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

Codeblock

language	xml
collapse	true

									...
									<RateDescription Name="RateGroup">
										<Text TextFormat="PlainText">BAR</Text>
									</RateDescription>
									<MarketCode MarketCode="FAM" MarketCodeName="Famille"/>
								</RatePlan>
							</RatePlans>
						</RoomType>
					</RoomTypes>
					...

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

outbound

pAir

IO_SystemDataRS | SystemData | Rates | RatePlans | RatePlan

Implement the MarketCode for inbound allotments.IPA-98821.50PWS 3.6.X AnkerPWS 3.6.XPWS 3.6.X

OTA_HotelAvailNotifRQ

inboundOnPremOTA_HotelAvailNotifRQ | AvailStatusMessages | AvailStatusMessage | RestrictionStatus

Codeblock

language	xml
collapse	true

<?xml version='1.0' encoding='utf-8'?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
	<env:Body>
		<OTA_HotelAvailNotifRQ MessageContentCode="3" TimeStamp="2018-12-03T00:00:00.000Z" Version="2">
			<AvailStatusMessages HotelCode="3153">
				<AvailStatusMessage>
					<StatusApplicationControl Start="2021-08-09" End="2021-08-10" RatePlanCode="Ali2" InvTypeCode="CBR"/>
					<RestrictionStatus Restriction="Departure" Status="Close"/>
					<UniqueID Type="16" ID_Context="info.rateboard.rms" ID="2"/>
				</AvailStatusMessage>
				<AvailStatusMessage>
					<StatusApplicationControl Start="2021-08-09" End="2021-08-10" RatePlanCode="Ali2" InvTypeCode="CS"/>
					<RestrictionStatus Restriction="Departure" Status="Close"/>
					<UniqueID Type="16" ID_Context="info.rateboard.rms" ID="2"/>
				</AvailStatusMessage>
			</AvailStatusMessages>
		</OTA_HotelAvailNotifRQ>
	</env:Body>
</env:Envelope>

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

OTA_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

language	xml
collapse	true

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

outbound

OnPrem

Codeblock

language	xml
collapse	true

<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

Codeblock

language	xml
collapse	true

<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-3001PWS 3.6.X

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

3.17.0

HTNG_HotelRoomStatusUpdateNotifRQ

outbound / inbound

OnPrem

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

OTA_HotelResNotifRQ

outbound

OnPrem

OTA_

HotelResNotifRQ

ProfileCreateRQ |

HotelReservations

Profile |

HotelReservation

Customer |

TPA

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

Codeblock

language	xml
collapse	true

<TPA_Extensions xmlns:px="http://protel.io/htng/extensions

<RelatedTraveler BirthDate="2006-03-05">

<px:ReservationExtensions> <px:FixedCharges> <px:FixedCharge Code="KosmetikExtNoR" Recurrence="floating" From="2021-01-05" To="2021-01-12" Quantity="1" RequestedIndicator="true

<UniqueID ID="181493" ID_Context="protelIO" Type="1"/>
	<PersonName Language="de">

<px:Price CurrencyCode="EUR" SingleAmountAfterTax="25.00"

<NamePrefix/>
		<GivenName>Tick</GivenName>
		<MiddleName/>
		<Surname>Duck</Surname>

<px:UniqueID

<Document

Type

DocID="

FixedCharge

987654321"

ID

DocType="

103604" ID_Context="protelIO"

5"/>
	</PersonName>
	<TPA_Extensions>
		<px:

Item ItemID="75"/>

GuestStayExtensions>

<px:

InvoiceText>Kosmetik täglich ab 5.1.</px: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>

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

Codeblock

collapse	true

<TPA_Extensions xmlns:px="http://protel.io/htng/extensions">
    <px:ProfileInfoExtensions>

Add the new Element "SerivceDates"

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

Possible Recurrence

OnArrival
OnDeparture
Daily
DaysOfWeek
Floating
Fixed

language	xml
collapse	true

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

        <px:PersonInfos>
            <px:MarketingCodes>
                <px:Code DefaultInd="false" DisplaySequence="0" ID="3" ID_Context="protelIO" Type="MARKETINGCODE">Wintergast</px:Code>

<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

language	xml
collapse	true

<HTNG_HotelFolioNotifRQ> <Folios> <Folio> <RevenueDetails> <RevenueDetail> <FolioIDs xmlns="http://www.opentravel.org/OTA/2003/05"> <FolioID>SDate|2017-08-23</FolioID>

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>

<FolioID>InvID|122345</FolioID> </FolioIDs> <RevenueDetailItems> <RevenueDetailItem> <FolioIDs xmlns="http://www.opentravel.org/OTA/2003/05"> <FolioID>SDate|2017-08-23</FolioID> </FolioIDs>

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

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

language	xml
collapse	true

<p:IO_ResModifyNotifRQ xmlns:p="http://protel.io/soap" CorrelationID="UseCase11b"

<IO_StatsNotifRQ/

TimeStamp="2018-12-29T15:20:35.985Z" Version="1.00">
    <p:Reservations

HotelCode="3152">

<p:Reservation ArrivalDate="2018-11-11">

  <p:UniqueID

<StatisticApplicationSet Start="2021-10-28" End="2021-10-28"

ID="345474" Type="Reservation" ID_Context="Protel_IO"/>

<p:ProfileReferences>

<StatisticCode StatCode

<p:ProfileReference ID_Context="

Group

protelIO"

StatCategoryCode

Type="

3

Customer"

/> <StatisticCode StatCode="1" StatCategoryCode="Pseudo" />

ID="181491" RelationToPrimary="Son" Action="CREATE"/>
            </

StatisticCodes>

p:ProfileReferences>

</p:Reservation>

<RevenueCategorySummaries> <RevenueCategorySummary RevenueCategoryCode="3" CurrencyCode="EUR" Amount="0.00" /> <RevenueCategorySummary RevenueCategoryCode="6" CurrencyCode="EUR" Amount="0.00" /> <RevenueCategorySummary RevenueCategoryCode="9" CurrencyCode="EUR" Amount="0.00" /> <RevenueCategorySummary RevenueCategoryCode="17" CurrencyCode="EUR" Amount="0.00" /> <RevenueCategorySummary RevenueCategoryCode="123" CurrencyCode="EUR" Amount="0.00" /> <RevenueCategorySummary RevenueCategoryCode="126" CurrencyCode="EUR" Amount="0.00" /> <RevenueCategorySummary RevenueCategoryCode="129" CurrencyCode="EUR" Amount="0.00" /> <RevenueCategorySummary RevenueCategoryCode="1217" CurrencyCode="EUR" Amount="0.00" /> </RevenueCategorySummaries>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.XHTNG_HotelFolioRSoutboundOnPrem

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

Codeblock

language	xml
collapse	true

<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

Codeblock

language	xml
collapse	true

<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

inbound

OnPrem

no change in xml

Codeblock

language	xml
collapse	true

<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

outbound / inbound

OnPrem

Codeblock

language	xml
collapse	true

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

outbound

onPrem

pAir

HTNG_ChargePostingRS | Errors | Error

Codeblock

language	xml
collapse	true

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

ESB 323

IPA 24.38

Anker

	IPA 24.38
	IPA 24.38

OTA_HotelResNotifRQ

inbound

pAir

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 / inbound

pAir

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

24.29

IPA 24.24

Anker

	IPA 24.24
	IPA 24.24

IO_InvoiceFiscalizeRQ

IO_InvoiceFiscalizeNotifRQ

outbound

pAir

IO_InvoiceFiscalizeRQ | Invoice | AdditionalText

Codeblock

language	xml
collapse	true

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

TBA

IO_InvoiceFiscalizeRQ

IO_InvoiceFiscalizeNotifRQ

outbound

pAir

IO_InvoiceFiscalizeRQ | Invoice | InvoiceFormat

Codeblock

language	xml
collapse	true

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

TBA

IO_SystemDataRS

outbound

pAir

IO_SystemDataRS | SystemData | Accounting | InvoiceFormat

Codeblock

language	xml
collapse	true

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

TBA

IO_InvoiceFiscalizeRQ

IO_InvoiceFiscalizeNotifRQ

outbound

pAir

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

outbound

pAir

@CheckedIn

@CheckedOut

Codeblock

language	xml
collapse	true

<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 / inbound

pAir

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

@FullOverlay

@Role

Codeblock

language	xml
title	Overlay profiles
collapse	true

<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

outbound

pAir

IO_InvoiceFiscalizeRQ | Invoice

Codeblock

language	xml
collapse	true

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

24.14

IO_InvoiceFiscalizeRQ

IO_InvoiceFiscalizeNotifRQ

outbound

pAir

IO_InvoiceFiscalizeRQ | Invoice | InvoiceRecipient | AccountingInfos

Codeblock

language	xml
collapse	true

<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

outbound

pAir

IO_InvoiceFiscalizeRQ | Invoice | InvoiceRecipient | AccountingInfos

Codeblock

language	xml
collapse	true

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

24.14

OTA_ProfileCreateRQ

OTA_ProfileModifyRQ

outbound

inbound

pAir

Customer | TPA_Extensions | px:ProfileInfoExtensions | px:AccountingInfos

Codeblock

language	xml
collapse	true

<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

Codeblock

language	xml
collapse	true

<HTNG_HotelFolioRS>

<px:ProfileInfoExtensions>

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

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

outbound

pAir

Codeblock

language	xml
collapse	true

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

outbound / inbound

pAir

Codeblock

language	xml
collapse	true

<TPA_Extensions>
    <px:GuestStayExtensions>

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

Possible values

InvID
InvNo
GstID
Code
TAAGrp
PkgID
SDate

language	xml
collapse	true

<HTNG_HotelFolioNotifRQ> <Folios> <Folio> <RevenueDetails> <RevenueDetail> <FolioIDs xmlns="http://www.opentravel.org/OTA/2003/05"> <FolioID>SDate|2017-08-23</FolioID>

        <px:StayInfo Arrival="2024-02-07T12:00:00+01:00" Departure="2024-02-08T12:00:00+01:00"

<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.XOTA_HotelStayInfoNotifRQoutboundOnPrem

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

outbound

pAir

IO_SystemDataRS | SystemData | Reservations | GuestRelationTypes | GuestRelationType

OTA_HotelStayInfoNotifRQ | StayInfos | StayInfo | RevenueCategory | @RevenueCategoryCode="2000"

Codeblock

language	xml
collapse	true

<RevenueCategory RevenueCategoryCode

<ns2:GuestRelationTypes>
	<ns2:GuestRelationType Code="

2000

Abuelo"

> <SummaryAmount

CurrencyCode

ID="

AED

1"

Amount

ID_Context="

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

protelIO" PrimaryInd="false" Visible="true">
		<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-1353

24.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

language	xml
collapse	true

<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

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

language	xml
collapse	true

<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

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

Codeblock

language	xml
collapse	true

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

Codeblock

language	xml
collapse	true

<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

language	xml
collapse	true

<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_ProfileCreateRQInboundOnPremOTA_ProfileModifyRQ | ProfileModify | Comments | Comment
OTA_ProfileCreateRQ | ProfileModify | Comments | Comment

Codeblock

language	xml
collapse	true

<ProfileModify ShareAllOptOutInd="Yes" ProfileType="1" CreateDateTime="2021-01-20T14:42:00" CreatorID="protelIO" RPH="155522" LastModifyDateTime="2021-09-29T12:34:49" LastModifierID="protel 37" StatusCode="4"> <Customer Gender="Unknown" Language="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>
    ....
        <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_HotelStayInfoNotifRQ

outbound

pAir

Codeblock

language	xml
collapse	true

<Customer>
	<TPA_Extensions>
    ....
        <ProfileInfoExtensions>
            ....

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

         <px:AccountingInfos PublicAdministrationInd="true" SplitPaymentInd="true"/>
		</

Comment>

ProfileInfoExtensions>
	</

Comments> </ProfileModify>

TPA_Extensions>
</Customer>

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

@PublicAdministrationInd

@SplitPaymentInd

IPA-1339

24.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-1334

24.02

OTA_ResRetrieveRS

outbound

pAir

@GroupName
@GroupID
@PrimaryInd

@GroupName
@GroupID
@PrimaryInd

Codeblock

collapse	true

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

24.02

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.XOTA_ProfileModifyRQ
OTA_ProfileCreateRQinboundOnPrem

OTA_ProfileModifyRQ | ProfileModify | Customer | Address

Codeblock

language	xml
collapse	true

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

Seitenhierarchie

Versionen im Vergleich

Alte Version 334

Neue Version Aktuell

Schlüssel