...
KIU SNAPSHOTS (PNR) is a service for PNR sending PNRs that will keep maintains the status of all PNRs synchronized with the PSS in real - time. Every time a PNR is created, modified, divided, or purged, a JSON file will be sent with the affected PNR(s).
...
Internally, the file contains an "event_details" object that gives details about the event that generated the change and a list of PNR[1..n] affected by it. Each object in the array represents a PNR and its structure is represented in the schema of the get_booking_information API (with the exception of except the purge event).
Example:
...
Key | Type | Possible Values | Description | Example | Comments |
|---|---|---|---|---|---|
system_from | string(2:3) | C1 or carrier code, PSS terminal or KIU GDS | Z8 | ||
company | string(4) | Company code, carrier code or agency code within KIU | 00Z8 | ||
channel | string | HOST, GDS | HOST | ||
subchannel | string | In the case of GDS, it is the gds code (C1, 1A, etc). In case of HOST, it is the value configured in the office table with the command DNO / BI STAT.SUB-CHANNEL | SALES OFFICE | ||
device | string(0:10) | Kiu device that triggered the transaction | LPB00Z8205 | ||
agent | string(0:9) | Kiu device that triggered the transaction | HDQ00Z8SM | ||
pnr_action | string | CREATE, MODIFY, SPLIT, DELETE | Identifies whether the event is to create, to modify or to split. | CREATE | SPLIT applies to both PNRs (the created and the modified one). |
transaction_type | string | DIRECT, INDIRECT | Identifies whether the modification on the pnr is given by a direct action of a user/api or if the modification is indirectly related to another process. | ||
origin | string |
| Identifies the origin that triggers the modification related to the transaction_type. If it is DIRECT, this field may be: AGENT → change from KiuCommand/some Click scenarios WEBSERVICES → change from WS/APIS/some Click scenarios FROM_EXTERNAL_MESSAGE → TTY Type B/Type A messaging processing If it is INDIRECT, this field may be: INTERNAL_PROCESS → change that affects the PNR during an internal process, for example, updates of the robot time limit, service cancellations, etc FROM_EXTERNAL_MESSAGE → TTY Type B/Type A messaging processing | ||
application | string |
| Explained under “Origin and applications” | ||
timestamp | datetime | 2023-04-20T22:02:32.750Z |
...
When this module is implemented, a RECAP process will be executed that will to go through the database generating an image of each PNR. Under this scenario there is no modification to the PNR, the event_datails will only have the key "application": "RECORD_LOCATOR_SYNCHRONIZATION".
...