2.9 KiB
FIT TA recorder 技术询问草稿（未发送）
请平台或 Oracle 技术人员提供一个明确示例：用哪个接口、把团号放进哪个参数，才能写入酒店页面的 TA Record Locator；保存后通过哪个查询字段能读回同一个值。需要同时覆盖新建和修改。有 Tour Code 时原样填写；没有时不提交此字段。用户已截图确认界面位置为 Stay Details → TA Record Locator。现有平台已提供预订新建、修改、查询接口，因此请先判断是否可以直接使用，而非假定要新增接口。
以下为可供技术人员处理的英文版本，无真实酒店、客人或凭据内容。
Draft — FIT TA Record Locator REST contract clarification
This request is prepared for review only; it has not been sent.
We need to populate the OPERA Cloud reservation UI field TA Record Locator with an agency booking reference, and verify the value through OHIP REST for both new and updated individual reservations. The same reference may identify multiple actual reservation IDs.
Reviewed on 2026-09-17: Oracle hospitality-api-docs, Property API 26.3.0.0, main commit 4bd129b455bc5e3ab0f900ac47983611e58659b4. rest-api-specs/property/v1/rsv.json is byte-identical to our previous dd631fbd revision. The middleware already passes Oracle JSON through postReservation/putReservation and returns getReservation documents; we are requesting the exact native mapping, not assuming a new middleware operation is needed.
The published searchHotelReservationsRequest defines taRecordLocatorList separately from customReference, GDS recordLocator and externalReferenceIds. We have not established the equivalent writable and readable property in the referenced createReservation, changeReservation or reservation schemas. The Block field reservationDetails.taRecordLocator is documented separately and is not assumed to apply to Reservation.
Please provide:
- Supported REST operation and exact JSON path for creating the TA Record Locator on a new Reservation.
- Supported operation and JSON path for setting it on an existing Reservation, including omission vs clearing semantics and preservation of other references.
- getReservation response path and required fetchInstructions, or another supported synchronous readback operation.
- Relevant OPERA Controls, permissions and Reservation Protection behavior; restrictions on length/characters and using the same value on multiple reservations with one guest profile.
- Minimal redacted create, update, exact-detail GET and TA-filtered search examples, plus applicable OPERA/OHIP version.
Please distinguish this field from External Reference, Custom Reference, the GDS Record Locator and the Reservation Guest Locator. A search parameter, business-event XML tag, or GraphQL field alone does not establish the required REST write/read mapping.
No real hotel identifiers, guest names, credentials or booking data are included in this request.