> 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/setups/configurations/sale-voucher-configuration/other-settings-1/other-settings/defaults-2/map-so-fields.md).

# Map SO Fields

**YouTube:** [How to Map Sale Order Fields to Sale Bill Fields During Sale Order Retrieval?](https://www.youtube.com/watch?v=qauiKWgwoCs)

## How to Map Sale Order Fields to Sale Bill Fields During Sale Order Retrieval?

This tutorial demonstrates how to map **Sales Order (SO)** fields to **Sales Line (SL)** fields in Logic ERP, enabling seamless data flow from the sales order to the billing screen.

***

### **Step-by-Step Configuration:**

* Open the **Sales Voucher Configuration**.
* Select the relevant **Billing Series**.
* Click on **“Other Setting 1”**.
* Click on the **“Other Settings”** button.
* Navigate to the **Defaults 2** tab.
* Locate the option labeled: **"Map SO Fields".**
* The mapping interface will appear with two columns:
  * **SO Field (Left Side):** Fields from the Sales Order such as **Tax Discount**, **Scheme**, **Remarks**, **Adjustments**, etc.
  * **SL Field (Right Side):** Corresponding Sales Line fields to which SO data can be mapped.
* To map, press the **Space Bar** in the SL Field cell to view a dropdown list.
* Select the appropriate target field (e.g., **Adjustment**, **Freight**, **Scheme**, **Excise**, **Item Description**).

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FVGqdhvsAdrTuNXDBnKv3%2FSetup%20SO%20Firlds.png?alt=media&amp;token=7ccfeeab-7a89-4d4e-9f8a-25a36354917b" alt=""><figcaption><p>As mentioned above, follow the given steps and select the appropriate option from the dropdown as per your requirement.</p></figcaption></figure>

* Example: Map **Remarks** from the Sales Order to **Item Description** in billing.
* Click **Save** to apply and store your field mapping settings.

***

### **Generate and Test a Sales Order:**

* Navigate to the **Sales Order Entry** screen.
* Before entering items, enable the **Remarks** column via **Setup Column Attributes**.
* Enter your sales items and include remarks for each item.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FCkKzBYrZLcNJZczFBo72%2FItem%20remark%20in%20SO.png?alt=media&amp;token=746580ab-387c-4aa2-9101-e1bbb405ed74" alt=""><figcaption><p>As shown in the picture, add remarks in the Sales Order (SO).</p></figcaption></figure>

* Save the Sales Order.

### **Retrieve Sales Order in Billing:**

* Navigate to the **Billing Screen**.
* Enable the **Item Description** column using **Setup Column Attributes**.
* Retrieve the previously created Sales Order.
* The **Remarks** from the Sales Order are automatically transferred and displayed in the **Item Description** field during billing.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FHea6lbPJAnYQHWiw4RUw%2FItem%20Discription%20in%20Sale%20Bill.png?alt=media&amp;token=8b032f31-2922-4e95-9479-59abbf924c6b" alt=""><figcaption><p>The Remarks from the Sales Order are automatically transferred to the Item Description field during billing.</p></figcaption></figure>

* This ensures consistent data flow and minimizes manual entry or oversight.


---

# 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/setups/configurations/sale-voucher-configuration/other-settings-1/other-settings/defaults-2/map-so-fields.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.
