> 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/production/production-vouchers/job-order/job-order-configuration/default-doc-prefix.md).
# Default Doc Prefix
**YouTube:** [How to Set the Default Document Prefix in Job Orders?](https://youtu.be/pRbAZEe7cSc)
## How to Set the Default Document Prefix in Job Orders?
In this tutorial, we will learn how to define a **Default Document Prefix** in Job Order using the **"Default Doc Prefix"** option in Logic ERP. This feature allows you to define one or multiple document prefixes and select the required prefix while creating a Job Order.
***
### Objective of This Feature
* Define a default document prefix for Job Orders
* Allow multiple document prefixes as per business requirements
* Simplify document numbering during Job Order entry
* Maintain organized and consistent document numbering
* Provide flexibility in selecting document prefixes
***
### Observe the Default Document Prefix
* Initiate a **New Job Order** entry.
* Observe the **Document Number** field.
As you can see, the system automatically displays the default document prefix **"JO"** in the Document Number field.
***
### Access to the Job Order Configuration
* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate the option labeled as:
> **"Default Doc Prefix"**
#### Define the Document Prefix
* The default prefix **"JO"** is currently configured.
* To define multiple document prefixes, enter the required prefixes separated by commas.
* For example: **JO, PRO, JOB**
* Save the configuration changes.
***
### Select the Required Document Prefix
* Initiate a **New Job Order** entry.
* Open the **Document Prefix** field.
**Result**
* The Document Prefix field now displays a **dropdown list** containing the configured prefixes.
* You can select the required prefix while creating the Job Order.
***
### Key Benefits
* Simplifies Job Order document numbering.
* Allows multiple prefixes to be configured.
* Provides flexibility during document entry.
* Helps organize Job Orders using different numbering series.
* Reduces manual effort in defining document prefixes.
***
### Best Practice Tips
* Define prefixes according to your business or transaction requirements.
* Use meaningful and easily identifiable prefixes.
* Separate multiple prefixes using commas.
* Review the configured prefixes before saving the configuration.
***
### Final Outcome
By using the **"Default Doc Prefix"** option, Logic ERP allows you to define and manage document prefixes for Job Orders. Once multiple prefixes are configured, the system provides them in a dropdown list, allowing users to select the appropriate prefix during Job Order entry.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/production/production-vouchers/job-order/job-order-configuration/default-doc-prefix.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.