> 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-learning-hub-tutorials-and-best-practices/production/production-vouchers/job-order/job-order-configuration/bom-expenses-entry-as.md).
# BOM Expenses Entry As
**YouTube:** [How to Restrict Job Order Saving When BOM Expenses Are Missing?](https://youtu.be/ojCTRm2d_VY)
## How to Restrict Job Order Saving When BOM Expenses Are Missing?
In this tutorial, we will learn how to enable **BOM Expenses Entry Validation** in Job Order using the **BOM Expenses Entry As** option in Logic ERP. This feature helps ensure that required BOM expenses are defined before a Job Order is saved.
***
### Objective of This Feature
* Validate BOM expenses during Job Order saving
* Prompt users when BOM expenses are not defined
* Restrict saving when required BOM expenses are missing
* Ensure complete BOM expense details
* Improve accuracy in Job Order processing
***
### Access to the Job Order Configuration
* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate the option labeled as:
> **"BOM Expenses Entry As"**
***
### Understand the Available Options
The **BOM Expenses Entry As** option provides three choices:
#### None
* This is the default option.
* The software does not validate whether BOM expenses have been defined.
* The Job Order can be saved without BOM expenses.
#### Prompt If Not Exists
* The software prompts the user if BOM expenses are not defined.
* The user can choose whether to continue or return and define the expenses.
#### Do Not Allow Saving If Not Exists
* The software completely restricts saving the Job Order when BOM expenses are not defined.
* BOM expenses must be entered before the Job Order can be saved.
***
### Configure "Prompt If Not Exists"
* Select **"Prompt If Not Exists"** from the dropdown.
* Save the configuration.
* Initiate a **New Job Order** entry.
* Transact an item and enter the required details.
* Click **Save**.
**Result**
If BOM expenses have not been defined, the software displays a confirmation prompt asking whether you want to continue without defining them.
* Click **Yes** to save the Job Order without BOM expenses.
* Click **No** to return to the entry and define the required BOM expenses.
***
### Configure "Do Not Allow Saving If Not Exists"
* Return to the **Configuration** window.
* Navigate to **Other Settings**.
* Set **BOM Expenses Entry As** to **"Do Not Allow Saving If Not Exists"**.
* Save the configuration.
* Initiate another **New Job Order** entry.
* Enter the required item details.
* Click **Save**.
**Result**
The software displays a warning and restricts the transaction because BOM expenses have not been defined.
The Job Order cannot be saved until the required BOM expenses are entered.
***
### Define BOM Expenses
* Click on **Raw Material Details**.
* Open the **BOM Expenses** window.
* Enter the required expense details.
* Save the BOM expense information.
* Return to the Job Order and click **Save**.
**Result**
The software allows the Job Order to be saved successfully because the required BOM expenses have now been defined.
***
### Key Benefits
* Ensures BOM expenses are properly defined
* Prevents incomplete Job Order entries
* Provides flexible validation options
* Reduces accounting and costing errors
* Improves control over BOM-related expenses
***
### Best Practice Tips
* Use **Prompt If Not Exists** when users should have the option to continue without BOM expenses.
* Use **Do Not Allow Saving If Not Exists** when BOM expenses must always be defined.
* Review BOM expense details before saving the Job Order.
***
### Final Outcome
After configuring **BOM Expenses Entry As**, Logic ERP can either **prompt the user or restrict saving** when BOM expenses are not defined. Once the required expenses are entered, the Job Order can be saved successfully, ensuring more accurate and controlled Job Order processing.
---
# 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-learning-hub-tutorials-and-best-practices/production/production-vouchers/job-order/job-order-configuration/bom-expenses-entry-as.md?ask=&goal=
```
`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.