> 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/inventory/physical-vs-actual-stock-doc-wise-entry/physical-vs-actual-stock-doc-wise-entry-configuration/doc-prefix.md).

# Doc Prefix

**YouTube:** [How to Set the Document Prefix in Physical vs. Actual Stock Entry?](https://youtu.be/EJFKQzyCuaM?si=H0eghY36GLVfbEPb)

## How to Set the Document Prefix in Physical vs. Actual Stock Entry?

In this tutorial, we will learn how to define a document prefix in the **Physical Vs Actual Stock Document Wise Entry** module in Logic ERP. We will also see how to configure multiple document prefixes and display them in the dropdown list.

***

### Access to the Document Entry Module

* Navigate to the **Physical Vs Actual Stock Document Wise Entry** module.
* Check the document prefix field.
* Initially, no document prefix is defined in the configuration. In that case the dropdown lists the prefixes already used on earlier documents of the branch, and you can also type a new prefix.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FZaESGtXlqhAlHUuSDyTW%2FCNF.png?alt=media&#x26;token=9957bc91-ff62-4822-81e9-3acf47638546" alt=""><figcaption></figcaption></figure>

***

### Configure the Document Prefix

* Open the **Configuration** window. (The **Configuration** button is available only to the Admin user or a supervisor user.)
* Locate the option labeled as:

> **Doc Prefix**

* Enter the required document prefix.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FqjGGm4s0Lw3no3OP8H63%2FCNF%202.png?alt=media&#x26;token=7926bd27-331f-4498-9b3a-ee44f2c9636e" alt=""><figcaption></figcaption></figure>

* Save the configuration.

***

### Verify the Document Prefix

* Return to the document entry window.
* Check the document prefix field.
* The specified prefix is now displayed.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FmTIbUFnjx0u4mCzKQoA7%2FDoc%20No.png?alt=media&#x26;token=72add9df-d70d-4022-97e6-a461c50f7443" alt=""><figcaption></figcaption></figure>

* The system will use the defined prefix with the document number. Each prefix has its own number series in each branch.

***

### Define Multiple Document Prefixes

* Open the **Configuration** window again.
* In the **Doc Prefix** field, enter a comma (`,`) after the existing prefix.
* Enter the additional document prefix after the comma.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FAjRSTaFv9kJ2S8F9dnvc%2FMlt%20Doc%20Prefix.png?alt=media&#x26;token=b5493bd6-1b31-4d82-acdd-7d7e063d7400" alt=""><figcaption></figcaption></figure>

* Save the configuration.

***

### Verify Multiple Prefixes

* Return to the document entry window.
* Open the document prefix dropdown list.
* All configured prefixes are now displayed in the dropdown list.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FKO2rhWqrn8t9zImnOVUf%2FDis.png?alt=media&#x26;token=9e9c1a88-5a3a-431f-8097-a1c6cde3d152" alt=""><figcaption></figcaption></figure>

* The first prefix in the list is selected automatically. You can select the required prefix from the available options.
* Once prefixes are configured, users can only pick from this list; they cannot type a different prefix.
* A prefix must be selected. If it is left blank, the system shows **"Invalid Document Prefix"** when saving.

***

### Objective of This Feature

* Define a document prefix for Physical Vs Actual Stock Document Wise Entry.
* Automatically use the configured prefix with the document number.
* Configure multiple prefixes as required.
* Select the appropriate document prefix from the dropdown list.


---

# 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/inventory/physical-vs-actual-stock-doc-wise-entry/physical-vs-actual-stock-doc-wise-entry-configuration/doc-prefix.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.
