> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/purchasing/purchase_document_type_codes.md).

# Purchase Document Type Codes

Set up purchase document type codes for consistent behaviour and reporting.

Available on all open purchase documents and copied to posted documents, use this field to categorise your purchases for filtering and operational reporting, i.e. sample, FOC, special event. The field can also be used to manage default shipment method codes.

{% hint style="warning" %}
**Prerequisites**

Set up purchase order processing.
{% endhint %}

### Purchase Document Type codes

To create Purchase Document Type Codes:

* You can search for **Purchase Document Type Codes** page using the ![Search (Tell me) icon](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-d08791d5454211f4ad6c103dcb698478e14f0cc7%2FMGpr-9eX7JGgztXpbozcm7Yd0X9RQqP_aw.png?alt=media) button
* From Bevica Setup, navigate to More Actions, Related, Operations

| Field                        | Note                                                                                                    |
| ---------------------------- | ------------------------------------------------------------------------------------------------------- |
| Code                         | Set a unique code for each type you want.                                                               |
| Description                  | Enter a description for the record.                                                                     |
| Default Shipment Method Code | If this is set, when the document type is added to a document, it will change the Shipment Method Code. |

{% hint style="info" %}
Select **Purchase Document Type** code after entering the 'Vendor No.' and 'Order Address Code'.
{% endhint %}

### Purchase Documents

The **Purchase Document Type** field is editable on all open purchase document headers and visible on posted documents. When it's added to an open document, it is then copied to all lines on that document.

{% hint style="warning" %}
You can only apply one **Purchase Document Type** per document, meaning all lines on that document share the same code.
{% endhint %}

See also [Sales Document Type Codes](/documentation/guides/sales/sales_document_type_codes.md)


---

# 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.bevica.com/documentation/guides/purchasing/purchase_document_type_codes.md?ask=<question>&goal=<endgoal>
```

`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.