> 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/raw-material-issues-against-job-order.md).

# Raw Material Issues Against Job Order

Logic ERP has added **F8: Fill Balance Quantity as per BOM** to raw material issues against a Job Order. **F8** can now fill only the raw material still due on the Job Order's BOM, and three new columns show how much of the BOM has been issued.

***

### **Step 1: Switch it on**

* Navigate to **Setup\Configurations** and open **Issue Register Configuration**.
* On **Raw Material Issue Settings**, set **Compare Issues against BOM** to **Job Order Wise BOM Defined**.
* Tick **F8: Fill Balance Quantity as per BOM**. The option can be ticked only with Job Order Wise BOM Defined; choosing another Compare setting clears it.

***

### **What it does**

* Navigate to **Production\Raw Material Processing** and open **Raw Material Issues Against Job Order - Internal** or **- External**.
* Select the Job Order and press **F8**. Each raw material is filled with its **BOM quantity less what has already been issued** against that Job Order, and lots are picked for that quantity only. The excess % allowance is not added while this option is on.
* A raw material that is already fully issued is left out. When you save the F8 window, a message such as "2 Raw Material(s) left out - BOM quantity already issued for this Job Order." tells you how many.
* Pressing F8 again in the same issue does not add the balance twice - the rows already on screen are counted.
* With the option off, F8 fills the full BOM quantity as before.

> **Example - Job Order JO-25**
>
> The BOM of JO-25 needs 20 kg of thread. 8 kg was issued last week. Ravi opens a new issue for JO-25 and presses F8: the thread row is filled with **12 kg**. After he saves it, F8 on another new issue for JO-25 leaves the thread out, because nothing is due.

***

### **New columns**

* **BOM QTY** - the raw material's quantity in the Job Order's BOM.
* **ISSUED BEFORE** - already issued against the Job Order in earlier issues. When an issue is modified, that issue itself is not counted.
* **BOM BALANCE** - BOM QTY less ISSUED BEFORE.
* The columns are hidden at first: tick them in the grid's column settings. They are filled for issues against a single Job Order and stay blank otherwise.
* The option is also available in the web configuration.

***

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/raw-material-issues-against-job-order.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.
