> 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/prompt-for-entering-weight.md).

# Prompt for Entering Weight

**YouTube:** [How to Make Weight Entry Prompt Mandatory in Job Orders?](https://youtu.be/_arG_MuuBrI)

## How to Make Weight Entry Prompt Mandatory in Job Orders?

In this tutorial, we will learn how to enable the **Prompt for Entering Weight** feature in Logic ERP. This feature ensures that a valid weight is entered for items before a Job Order can be saved.

***

### Objective of This Feature

* Prompt users to enter item weight
* Prevent saving Job Orders without a valid weight
* Ensure accurate weight-based transactions
* Improve data entry accuracy
* Minimize incomplete Job Order entries

***

### Access to the Job Order Configuration

* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate and enable the option labeled as:

> **"Prompt for Entering Weight"**

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

* Save the configuration changes.

***

### Create a New Job Order

* Initiate a **New Job Order** entry.
* Navigate to the **Item Details** section.
* Locate the **Weight** column.

**Note**

If the Weight column is not visible:

* Open **Setup Column Attributes**.
* Enable the **Weight** column.

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

***

### Implement Without Entering Weight

* Leave the **Weight** field blank.
* Try to save the Job Order.

<figure><img src="/files/3FGNoJk2HktzIQUfaxyG" alt=""><figcaption></figcaption></figure>

**Result**

The software restricts the transaction and displays an **Invalid Weight** error message, preventing the Job Order from being saved.

***

### Enter the Required Weight

* Enter the required weight value in the **Weight** field.
* Click **Save** again.

<figure><img src="/files/5Ru5Zov6qQnWnHVpPwim" alt=""><figcaption></figcaption></figure>

**Result**

The software validates the entered weight and allows the Job Order to be saved successfully.

***

### Key Benefits

* Ensures mandatory weight entry
* Prevents invalid or incomplete transactions
* Improves inventory accuracy
* Reduces data entry errors
* Ensures reliable weight-based reporting

***

### Best Practice Tips

* Ensure the Weight column is visible during Job Order entry.
* Enter an accurate weight value for each applicable item.
* Verify the weight before saving the Job Order.

***

### Final Outcome

After enabling **"Prompt for Entering Weight"**, Logic ERP validates the weight entered for items during Job Order processing. If the weight is missing or invalid, the system restricts saving until a valid weight is provided.


---

# 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/prompt-for-entering-weight.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.
