> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/summary-view/entitlement-summary-view.md).

# Entitlement Summary View

Entitlement metrics come from two places:

* The `beneficiary_list_summary` portion of the API response, specifically fields like `total_disbursement_quantity`, `average_entitlement_per_registrant`, and any mapping of `benefit_code_id` to value. These are processed with `summary_type='entitlement'`
* The `registry_summary` dictionary entries may also be tagged with `summary_type='entitlement'`, especially when they contain *entitlement* statistics (e.g., `entitlement_amount_q1`, `entitlement_amount_male_q3`).

The same formatting logic applies as for eligibility lines: numeric formatting, measurement units looked up using benefit\_code mapping, title-cased “key”.

### Storage & UI linkage

* Records with `summary_type='entitlement'` are inserted into the `g2p.api.summary.line` model.
* In the UI, the summary view (for example the wizard’s results page) aggregates or lists these entitlement lines—allowing users to inspect disbursement quantities, averages and quartiles for each benefit code.

### Customizing new fields

For entitlement fields (e.g., a new benefit code metric or multiplier-based value) you can follow a similar path:

1. Include the new entitlement metric in the `beneficiary_list_summary` or in the `registry_summary` as a dictionary keyed by `benefit_code_id`.
2. Extend your model to capture that metric (you may add fields to `BeneficiaryListSummaryFarmer` or a custom summary model). Keep in mind that the logic for calculation and handling of this metric must also be created in the extensions.
3. The generic loop in `_compute_summary_lines` handles dictionary-values: benefit\_code\_id → value. So no change is needed to logic. You only need to ensure your benefit code shows up in `g2p.benefit.codes` so `benefit_mnemonic` resolution works.
4. If you need to display a new measurement unit, update the `measurement_unit` in `g2p.benefit.codes` rather than altering the loop logic.
5. Again, bundle your additions in a separate Odoo module (inherit models, extend views) so core code remains untouched and upgradeable.


---

# 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://docs.openg2p.org/products/pbms/developer-zone/tech-guides/summary-view/entitlement-summary-view.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.