> 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/utilities/import-masters-transactions-from-external-files/import-purchase-vouchers-from-external-file/import-purchase-vouchers-configuration/overwrite-item-details.md).

# Overwrite Item Details

**YouTube:** [How to Overwrite Item Details in Import PUV Configuration?](https://youtu.be/8Cklm-k0ZwU)

## How to Overwrite Item Details in Import PUV Configuration?

In this tutorial, we will learn how to use the **"Overwrite Item Details"** feature while importing a Purchase Voucher from an external file in Logic ERP.

This feature allows the system to update existing item details with the corresponding values provided in the external file during the import process.

***

### Access to the Import Configuration

To access the required option:

* Navigate to **Import Purchase Vouchers from External File**.
* Open the **Configuration** window.
* Locate the option labeled as:

> **"Overwrite Item Details"**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FirmOw0WC8JmDRvWZz3dO%2FCNF.png?alt=media&amp;token=73b08847-2cb7-4b77-835b-afce030b2e5e" alt=""><figcaption></figcaption></figure>

Before enabling this option, let's first understand its default behavior.

***

### Review the Existing Item Details

Before importing the Purchase Voucher, let's review the relevant item in the **Item Master**.

* Open the **Item Master**.
* Search and select the required item.
* Check its existing item details.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FrwEWwwEb6iHEOy6hEocJ%2FBlank%20HS%20Code.png?alt=media&amp;token=d470e0af-daae-4340-837e-2dbf50a247f7" alt=""><figcaption></figcaption></figure>

**Current Setup**

As you can see, the **HSN Code** is currently not defined for the relevant item.

Now, let's proceed with importing the Purchase Voucher.

***

### Import the Voucher with the Option Disabled

* Keep **"Overwrite Item Details"** disabled.
* Import the Purchase Voucher using the external Excel file.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FnkoZKBv2L4S10vEZn0JQ%2FImport%20Xls.png?alt=media&amp;token=457b2bb6-2527-4953-9eb3-b60abc663ee2" alt=""><figcaption></figcaption></figure>

**System Behavior**

As you can see, the **HSN Code** provided in the Excel file is visible in the import details.

However, when the document is imported, the system does **not overwrite the existing item details** in the Item Master.

Let's verify this in the Purchase Voucher module.

* Open the imported Purchase Voucher.
* Check the HSN Code for the relevant item.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FpfMls4nMFgPfOkdofIix%2FHS%20Code%20in%20Purchase.png?alt=media&amp;token=3e96f9ad-731d-4419-ad27-bd8124376bf3" alt=""><figcaption></figcaption></figure>

**Result**

Since **"Overwrite Item Details"** is disabled, the system does not update the item's existing HSN Code with the value provided in the external file.

***

### Enable Overwrite Item Details

Now, let's enable the feature and observe the difference.

* Return to the **Import Purchase Vouchers from External File** configuration.
* Enable **"Overwrite Item Details"**.
* Save the configuration changes.
* Import the same Excel file again.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F3QunhjRCH1TMQmNlGeV4%2FNew%20Xls.png?alt=media&amp;token=0489deaf-4a99-4a78-9bfa-4c9b6e5dc600" alt=""><figcaption></figcaption></figure>

***

### Verify the Updated Item Details

Now, let's verify the result in the **Purchase Voucher** module.

* Open the newly imported Purchase Voucher.
* Check the HSN Code for the relevant item.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F9puUPBzyLYZs0vkyAYiG%2FNw%20PT%20Xls.png?alt=media&amp;token=57f1f68c-c24f-4c38-b0b7-faa818724686" alt=""><figcaption></figcaption></figure>

**System Behavior**

As you can see, the **HSN Code has now been successfully overwritten** with the value provided in the external Excel file.

The system has updated the existing item details according to the information available in the imported document.

***

### Configuration Summary

| Configuration                         | System Behavior                                                      |
| ------------------------------------- | -------------------------------------------------------------------- |
| **Overwrite Item Details – Disabled** | Existing item details are not overwritten                            |
| **Overwrite Item Details – Enabled**  | Existing item details are updated with values from the external file |

***

### Final Outcome

By enabling **"Overwrite Item Details"**, Logic ERP can update the existing item details with the corresponding information provided in the external file during Purchase Voucher import. This helps keep item information, such as the **HSN Code**, synchronized with the imported purchase data.


---

# 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/utilities/import-masters-transactions-from-external-files/import-purchase-vouchers-from-external-file/import-purchase-vouchers-configuration/overwrite-item-details.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.