> 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/october-2026/production/raw-material-processing/issue-assigned-raw-material.md).

# Issue Assigned Raw Material

Logic ERP now checks **Issue Assigned Raw Material** against the Job Order's BOM when the issue is saved, the same way raw material issues against a Job Order are checked.

***

### **What it does**

* Navigate to **Production\Raw Material Processing** and open **Issue Assigned Raw Material - Internal** or **- External**.
* When **Compare Issues against BOM** is **Job Order Wise BOM Defined** in **Issue Register Configuration**, saving compares each raw material's total issue on its Job Order - earlier issues plus this one - with its BOM quantity.
* Raw materials that go beyond the BOM are listed, for example "Job Order JO-25: Quantity \[23] Exceeded...Maximum For Specfication is 20". A raw material that is not in the BOM is listed too.
* If **Do not allow Issues beyond BOM Scope** is ticked, the issue is not saved. Otherwise it is saved after the list is shown.
* With any other Compare Issues against BOM setting, the screen saves as before, without the check.

> **Example - Job Order JO-25**
>
> The BOM of JO-25 needs 20 kg of thread and 10 kg is already issued. Meena issues 13 kg more: the list shows thread with 23 kg against a maximum of 20 kg. With Do not allow Issues beyond BOM Scope ticked, the issue is not saved; without it, the issue is saved after the list.

***

For more detailed information, [Click Here](/logic-erp-learning-hub-tutorials-and-best-practices/production/raw-material-processing.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/october-2026/production/raw-material-processing/issue-assigned-raw-material.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.
