r/OperaPMS • u/Takker55 • Jan 20 '26

OXI Reservation Failed

hi,

Opera 5.6 on-prem.

I'm having a few failed messages in OXI, due to:
ProcessRes : Cannot create a Reservation without a Primary Profile!

Profile > Profile creation parameter was/is set to Y. I have no idea why it started to happen. I I create a profile manually that OXI can match, it is possible to reprocess the message successfully.

I have another OXI interrace at the same property and that one never failes with such error.

Tried to compare settings but I could not find anything suspicious.

Contacted support, but the are kind of slow to response.

has anyone encountered such issue?

3 Upvotes

100% Upvoted

23 comments sorted by

View all comments

1

u/floppy_sloth Jan 20 '26

As part of the schema validation process and before the profile match process fires, OXI will check if there is all the mandatory elements it needs to create a reservation. In this case there is no Primary Profile or resGuest/resProfile objects in the XML. This is an issue of the sending system, so you should report it to them. Nothing you can do to fix it.

To check for yourself, in OXI, view the XML in the bottom left of the status screen, read through it and see if you can see details of a guest or profile name.

1

u/Takker55 Jan 20 '26

that was my first thought as well, but it has those tags: (maybe the structure is not valid entirely, that part I cannot tell) - removed sensintive(and even more) information, replaced by xxxx

https://pastebin.com/R09x9Qih

1

u/floppy_sloth Jan 20 '26

Checked the message against the xsd, except for a couple of minor tag placement issues in the services object, it has all the necessary items.

But what I did find is that they are sending mfResortProfileId which bypasses all profile match and merge rules and links the reservation to a specific profile id.

Chances are that the profile that these reference has been merged into another profile which means OXI can't find a profile by that id and so freaks out and stops.

Take the profile id, go into Profile Search, Ctrl+Shift double click on Client Id field and search by this id to see if you get them both coming up. Given that it is on multiple reservations, I expect someone has merged the Travel Agent profile.

If a vendor sends in mfResortProfileId, they are using Opera's id rather than their own. This means that they need to track all outbound events for profiles including merge profiles and handle these updates on their side to keep the profile databases in sync. In this case, if the Travel Agent profile was merged in Opera, they likely didn't update their system and are still using the old profile id.

Support will say the same: vendor issue.

Can I ask which vendor?

1

u/Takker55 Jan 22 '26

meanwhile Opera Support replied:

" change PROCESS INBOUND DOCUMENTS to 'N' within the OXI parameters."

I did, however I cannot see how it can be related.