This task allows the client to change the room type for the one originally requested.
Transaction Name:
PNRBFManagement_49
Can any other transaction(s) perform this same task?
Other transactions that can contain a hotel sell are:
Can this task be performed in a sessionless environment?
Yes.
Are the request and response identical on both the Apollo and Galileo systems?
They are identical.
List any industry-specific knowledge required to understand this task in terms of the specific business process.
No industry specific knowledge is needed to perform this task.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
Not applicable.
Request:
Unless otherwise specified, use ALL CAPS in any request data.
To modify optional data, the <HtlModifyMods> (6154) must be sent with the <HotelModify> (HTMX) KLR. The following elements should be considered in the request:
Prerequisite tasks:
The only prerequisite is that a hotel segment must have been sold.
Expected response:
The <HtlSegSell> (6151) returns with the <HotelSell> (HT03), <HotelOptionalData> (HT04),<HotelType> (HTTR), and <HotelRule> (HTVT) elements displaying a confirmation that the required modification was performed.
Error and Warning responses:
Errors and warnings are returned in <HotelError> (HTER) element.
Follow-on requests:
There are no follow-on requests.
|
<HtlModifyMods> |
Terminal Equivalents: |
Apollo HOMnR |
Galileo HOMnR |
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||||
|
|
HTMX |
1 – 1 |
<HotelModify> |
||||
<HtlSegSell> |
|
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
|
|
HT03 |
0-1 |
<HotelSell> |
||
|
|
HT04 |
0-1 |
<HotelOptionalData> |
||
|
|
HTER |
0-1 |
<HotelError> |
||
|
|
HTTR |
0-1 |
<HotelType> |
||
|
|
HTVT |
0-1 |
<HotelRule> |
||
See the following topics for additional information for hotel processing.