> 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/column-delimiter.md).
# Column Delimiter
**YouTube:** [How to Configure the Column Delimiter in Import PUV (Text File) Configuration?](https://youtu.be/9pc1H4qFmlY)
## How to Configure the Column Delimiter in Import PUV (Text File) Configuration?
In this tutorial, we will learn how to use the **"Column Delimiter"** option while importing a Purchase Text File in Logic ERP.
This option allows you to define the character used to separate different columns in the text file, ensuring that the system correctly identifies and imports each field.
***
### Select the Text File Import Type
* Navigate to the **Import Purchase Vouchers from External File** module.
* Open the **Configuration** window.
* Select **Text File** as the **Import File Type**.
#### Column Delimiter
* Locate the option labeled as
> **"Column Delimiter"**
* This option defines how the different columns in the text file are separated.
* The selected delimiter must match the separator used in the source text file.
* For this tutorial, we are using a **comma (,)** as an example.
***
### Review the Purchase Text File
Before importing the file, let's review its format.
As you can see, the different fields in the purchase text file are separated using **commas**.
For example:
* **Item Code, Item Name, Quantity, Rate**
* Here, the comma is used to separate each column.
***
### Import the Purchase Text File
Now, let's proceed with the import.
* Select the required purchase text file.
* Start the import process.
**System Behavior**
As you can see, the system successfully identifies the individual columns based on the configured **comma delimiter**.
Each field is correctly separated and mapped according to the text file structure.
***
### Verify the Imported Purchase Voucher
* Proceed with importing the purchase details.
* Once the import is completed successfully, open the **Purchase Voucher** module.
* Locate and open the imported document.
**Result**
As you can see, the purchase details have been successfully imported and correctly reflected in the **Purchase Voucher**.
***
### Key Benefits
* Allows the system to correctly read structured text files.
* Ensures proper separation of imported fields.
* Helps prevent incorrect column mapping during import.
* Supports flexible text file formats by allowing different delimiters.
### Final Outcome
By configuring the **"Column Delimiter"** according to the separator used in the source text file, Logic ERP can correctly identify and import each column during the Purchase Voucher import process.
---
# 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/column-delimiter.md?ask=&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.
