> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/september-2026/report/sale-register-doctor-patient-wise.md).

# Sale Register - Doctor/Patient Wise

Logic ERP has introduced an enhancement that allows you to display **Extra Item Group columns** in the **Sale Register – Doctor/Patient Wise** report. You can select the required Extra Item Groups from the report configuration and view them directly in the generated report.

***

### Step 1: Access to the Report 

* To access the report, navigate to **Reports/Queries → Sale Registers**.
* Open the **Sale Register – Doctor/Patient Wise** report.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2Fi2mMeLWi44EeSQy51G3j%2FDefault.png?alt=media&amp;token=07e813fb-f1de-4c0a-910f-ac7074fe57e7" alt=""><figcaption></figcaption></figure>

***

### Step 2: Implement Configuration

* Click on **Configuration** to open the report configuration window.
* Scroll to the bottom of the configuration window, where you will find the **Extra Item Group** columns.
* Select the required **Extra Item Groups** according to your reporting requirements.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F06rHpogzjU8pmEBQ5vcm%2FCNF.png?alt=media&amp;token=f0f3cd5a-4ffd-43ee-ac2c-ed449b0310c3" alt=""><figcaption></figcaption></figure>

* After selecting the required groups, generate the report.

***

### Step 3: Report View

* You can now see that the selected **Extra Item Group columns** are displayed in the report.
* If the selected columns are not visible, open **Column Attribute** and enable the required columns.
* Once enabled, the Extra Item Group details will be displayed in the report accordingly.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FpaG9niSxFdu8sVR7qJb0%2FFinal%20Report.png?alt=media&amp;token=9cdc978e-95fb-4a0e-b34e-0d90c818e939" alt=""><figcaption></figcaption></figure>

For more detailed information,[ <mark style="color:$success;">**Click Here.**</mark>](/logic-erp-learning-hub-tutorials-and-best-practices/reports-queries/sale-registers/sale-register-doctor-patient-wise.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.logicerp.com/logic-erp-version-release-notes/september-2026/report/sale-register-doctor-patient-wise.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.