> For the complete documentation index, see [llms.txt](https://cee-systems.gitbook.io/cee-fare-builder/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cee-systems.gitbook.io/cee-fare-builder/fare-builder-user-manual/examples/pnr-created-by-ek-and-stored-via-claim-pnr-functionality.md).

# PNR created by EK and stored via „Claim PNR” functionality

<figure><img src="/files/1Js5GPqNrF3qRvMmhJuR" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/DuOzciMSAK54iC8Zgfxx" alt=""><figcaption></figcaption></figure>

After clicking the **Retrieve PNR** button, the segments and passenger names are automatically loaded into the Fare Builder mask. Even if all passengers are adults, the **Confirm Selection** button must still be activated to proceed.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdj1FjtU4JeUPeYtZ3MhJk1wUwy9mw85Qy6OxpcFYg4euuwH08bEVITorPD0Qf055qlfnPfHVW0VqtUCTzgjvw5nXybHuQk4Wc_xi4nsVTqR2oYMejIX7RuH2LeZe30eo7YcU5ICg?key=K69gCO3qdKM_QTIzDuLFm2Rn" alt=""><figcaption></figcaption></figure>

Current taxes are added automatically but must be reviewed and checked for accuracy.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeHcJv8ctQcetev6XDvOcCoiYsCBRhAOTolbWWTL2Jitw9TXLUIadeK052UtAUYlaT-Wucv1nOC9TRPfnT7hIyKkWK2xsRjnZgi2niMVCNLZaLMwWRtwi-080PEsnKwJ6lmAEmjJw?key=K69gCO3qdKM_QTIzDuLFm2Rn" alt=""><figcaption></figcaption></figure>

An optional change of the Fare Calculation Date evaluates all taxes once again based on the changed selling date:

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcqPf1H0PSzcH8YkAjJSu9tshCSJCl1Cmyx9f_d7UK30shfboqpA0qeeVZrauy-3l-YPmQY9S71E786zSziSIsHTCOAAj9_MONTEAtin4Z9CqIae0JRZvCYTdpTruUz-fr2Jfrayw?key=K69gCO3qdKM_QTIzDuLFm2Rn" alt=""><figcaption></figcaption></figure>

According to the carrier’s instructions, the following Fare Basis and Ticket Designator should be used: **`GE1YPCZ5/GRP5`**

<mark style="color:red;">**`GE1YPCZ5`**</mark> = Fare Basis / <mark style="color:green;">**`GRP5`**</mark> = Ticket Designator 🡪 different fields

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd5NkROyM3eNwOPgsjUPfX4VdmlqmDmVGCKr5hj1kFE1WvFmPTT8PRucfshAKDQhDlw1il1rwScQXztnAW2iQmpr3DhmjJlRrVaOFQt1-NhGQnoDeT8UJb6uvj5bEM2XkmKURStvw?key=K69gCO3qdKM_QTIzDuLFm2Rn" alt=""><figcaption></figcaption></figure>

After reviewing, click the **Create Filed Fare Mask** button to store the data in the PNR.

After completing all required steps, a final confirmation message appears. Acknowledge this message to finalize the process.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdKsSKNSgA5Ug4L51jZH3QBXE1rYyASYwFPVVA2j0MfB93nW25KpmyXM1RD-lymVF01Wcb_xV2YLAJRe-OuNo-ZM2d7n4ypME3LwF8lf8Yr7PioeJWlgsMrvmEAoQ8Odt4xy9gx0Q?key=K69gCO3qdKM_QTIzDuLFm2Rn" alt=""><figcaption></figcaption></figure>

The FF Filed Fare mask stored in the PNR and prepared for ticketing:

<figure><img src="/files/EJQuvZkh0KWf8o0mukSS" alt=""><figcaption></figcaption></figure>

Fare basis and Ticket designator shown on the ticket are: **GE1YPCZ5/GRP5**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cee-systems.gitbook.io/cee-fare-builder/fare-builder-user-manual/examples/pnr-created-by-ek-and-stored-via-claim-pnr-functionality.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.