> 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/purchase/purchase-inward-workflow-process/enter-l.r.-details/enter-l.r.-details-configuration.md).

# Enter L.R. Details - Configuration

The **LR Configuration Settings** window controls how **Enter L.R. Details** behaves: which **document prefixes** are offered, whether a **G.R. No.** may be repeated, whether an L.R. may be saved **without a freight rate**, the **default document type**, the **transport modes** offered, and which fields are **hidden**.

You can keep several configurations - for example one for way-bill consignments and one for purchase-order consignments - and pick the one you need on the Enter L.R. Details screen.

***

### **Before you start**

* Only users with **modify rights** on Enter L.R. Details can open the configuration. Others see *"Modification Rights Not available........"* when they click **Configuration**.

***

### **Step 1: Open the configuration**

* Go to `Purchase\Enter L.R. Details`.
* Click **Configuration**. The **LR Configuration Settings** window opens.
* In **Configuration**, pick an existing configuration to change it, or type a new name to create one. Names are saved in capitals. When you type a new name, **Document Prefixes As** and the **Restrict Duplicate Bill No. for Same Supplier** tick keep what was shown before - check them before you save.

***

### **Step 2: The settings**

| Setting                                           | What it does                                                                                                                                                                                                                                       |
| ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Document Prefixes As**                          | The prefixes offered for the L.R. **Document Number**, separated by commas - for example *LR,LRPO*. They are added to the prefixes already used in your branch. Typed in capitals.                                                                 |
| **Restrict Duplicate Bill No. for Same Supplier** | When ticked, **G.R. No.** must be filled in, and the same G.R. No. cannot be used twice for the same party in the same financial year. It is checked when you leave the G.R. No. field and again when you save.                                    |
| **Freight Validation As**                         | **None** - the **Freight Rate** must be more than 0 to save the L.R. **Allow users to enter the Freight Rate during L.R. Entry** - the L.R. can be saved even when the Freight Rate is blank or 0.                                                 |
| **L.R Doc Type As**                               | The document type preselected on a new L.R.: **None**, **Way Bill No**, **Purchase Order**, **Sale Bill**, **Sale Return**, **Stock Transfer Out**, **Purchase Return** or **PI Category Basis**. The user can still change it on a new L.R.       |
| **Default Transport Mode**                        | The transport modes offered, separated by commas - for example *ROAD,RAIL,AIR*. When filled in, **Transport Mode** on the L.R. becomes a pick-list of just these. When blank, the user can pick a mode used before or type one. Typed in capitals. |
| **Column Locks**                                  | Hides fields you do not use. See Step 3.                                                                                                                                                                                                           |

Use **L.R Doc Type As** = **Purchase Order** or **PI Category Basis** for consignments that will go through **Gate Pass Entry Against L.R.** - only those two types can be received there.

***

### **Step 3: Column Locks - hide fields**

* Click **Column Locks**. The **Edit Column Attributes** window lists the fields under **DEFAULT NAME**.
* Tick **HIDE** for each field to hide, then click **Ok**.

The fields you can hide:

* TRANSPORTER NAME
* STATION FROM
* STATION TO
* TRANSPORT MODE
* VECHICLE NO.
* PACKING UNIT
* FREIGHT RATE
* TOTAL FREIGHT
* CHARGED WEIGHT (its unit is hidden with it)
* ACTUAL WEIGHT (its unit is hidden with it)
* INSURANCE AMOUNT
* DOCKET AMOUNT
* NUMBER OF BOXES
* DOCUMENT AMOUNT
* CHALLAN/INVOICE AMOUNT
* INSURANCE POLICY NO.
* REMARKS-1, REMARKS-2, REMARKS-3

The list also shows **TO PAY**. Ticking it has no effect.

**Hiding a field does not switch off its checks:**

* If you hide **FREIGHT RATE** (or **TRANSPORTER NAME** / **STATION TO**, which fill it in) while **Freight Validation As** is **None**, an L.R. with no freight rate cannot be saved. Set **Freight Validation As** to **Allow users to enter the Freight Rate during L.R. Entry** in that case.
* If you hide **NUMBER OF BOXES**, a **Purchase Order** or **PI Category Basis** L.R. cannot be saved, because No. Of Boxes must be more than 0 and equal the boxes in its invoice list.

***

### **Step 4: Save**

* Click **Save** and answer **Yes** to *"Are you sure you want to save"*.
* Click **Close** to leave without saving.
* Close and reopen **Enter L.R. Details** to be sure the changes are applied. A newly created configuration appears in the list next to the **Configuration** button the next time you open the screen.

***

### **Messages you may see**

| Message                                   | What it means                                       |
| ----------------------------------------- | --------------------------------------------------- |
| Modification Rights Not available........ | You do not have modify rights on Enter L.R. Details |
| Invalid Configuration                     | The **Configuration** name is blank                 |
| Are you sure you want to save             | Confirms saving the configuration                   |

***

> **Example - a configuration for purchase-order consignments**
>
> 1. In `Purchase\Enter L.R. Details`, click **Configuration** and type the name *LR FOR PO*.
> 2. **Document Prefixes As**: *LRPO*. Tick **Restrict Duplicate Bill No. for Same Supplier**. **Freight Validation As**: **None**. **L.R Doc Type As**: **Purchase Order**. **Default Transport Mode**: *ROAD,RAIL*.
> 3. Click **Column Locks**, tick **HIDE** for **INSURANCE POLICY NO.** and **REMARKS-3**, and click **Ok**.
> 4. Click **Save**, then **Yes**.
>
> Reopen Enter L.R. Details and pick **LR FOR PO**: the prefix list offers **LRPO**, the document type is **Purchase Order**, Transport Mode offers only **ROAD** and **RAIL**, the two hidden fields are gone, and a repeated G.R. No. for the same supplier is refused with *"GR No. Already Exists"*.


---

# 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-learning-hub-tutorials-and-best-practices/purchase/purchase-inward-workflow-process/enter-l.r.-details/enter-l.r.-details-configuration.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.
