> 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/january-2026/production/receipt-against-issue-report-new-master-and-sub-job-order-wise.md).

# Receipt Against Issue Report (New) – Master & Sub Job Order Wise

**Logic ERP has introduced a new feature that simplifies the Receipt Against Issue Report for Master Job Orders and Sub Job Orders.**

With this update, users can now view both the **Main (Master) Job Order** and its **related Sub Job Orders** within the same report.

***

### Steps to View Master & Sub Job Orders in Receipt Against Issue Report (New)

* First, go to the following path:\
  **Production → Production Reports/Queries → Production Finished Goods Reports → Receipts Against Issues Report (New)**
* Once you open the report, click on **“Set Column Attribute”**
* In the column settings, you will find the newly added options:
  * **Master Job Order**
  * **Job Order**
* Tick/Select both options

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

* After selecting, **refresh the report**
* Now, the Report will display:
  * Main (Master) Job Order
  * Its related Sub Job Orders
  * Along with complete data

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

***

### Result

* You no longer need to open multiple reports to track job order data
* All related transactions are available in a **single, consolidated view**
* It becomes easier to understand the **link between master and sub job orders**

Overall, this enhancement improves **visibility**, **tracking**, and **analysis** of job order-wise Issue and Receipt transactions, making the reporting process faster and more efficient.


---

# 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://kb.logicerp.com/logic-erp-version-release-notes/january-2026/production/receipt-against-issue-report-new-master-and-sub-job-order-wise.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.