> 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/bevica-select/bevica-select-data-migration/bevica_select_-_data_migration_and_go-live-templates/bevica_select_-_resources_template.md).

# Resources Template

Use this template to import **Resources**.

Resources can be used on sales lines, purchase lines, and assembly BOMs.

### Before you start

You need:

* ​[Excel Template Data Migration​](/bevica-select/bevica_select_training/bevica_select_-_excel_template_data_migration.md#excel-template-data-migration)
* [​Configuration Worksheet](/bevica-select/bevica_select_training/bevica_select_-_excel_template_data_migration.md#configuration-worksheet)

### When to use this template

Export it from **Configuration Worksheet** on the **Resource** line.

### Step-by-step

{% stepper %}
{% step %}

#### Export the template

1. Open **Configuration Worksheet**.
2. Select the **Resource** line.
3. Select **Excel** → **Export to Template**.
   {% endstep %}

{% step %}

#### Populate rows

1. Create one row per resource.
2. Format **No.** as **Text** in Excel.
3. Make sure posting group and VAT codes exist.
   {% endstep %}

{% step %}

#### Import and apply

1. Select **Excel** → **Import from Template**.
2. Fix any errors in the preview.
3. Select **Apply Data**.
   {% endstep %}

{% step %}

#### Verify

1. Open **Resources**.
2. Filter on imported codes.
3. Check posting groups and UoM on the resource card.
   {% endstep %}
   {% endstepper %}

### Field reference (template columns)

#### Field list

The template has the following fields:

<table data-header-hidden="false" data-header-sticky><thead><tr><th width="146">Field ID / Name</th><th width="145">Related Table</th><th width="132">FieldType</th><th>Note</th></tr></thead><tbody><tr><td>1 <code>No.</code></td><td></td><td>Code 20 (Mandatory)</td><td>Unique resource reference.</td></tr><tr><td>3 <code>Name</code></td><td></td><td>Text 100</td><td></td></tr><tr><td>2 <code>Type</code></td><td></td><td>Option (Mandatory)</td><td>Must be either Machine or Person. Within Bevica, this can be populated as either.</td></tr><tr><td>18 <code>Base Unit of Measure</code></td><td>(204) Unit of Measure</td><td>Code 10 (Mandatory)</td><td>Any value here must already exist in its related table. Within Bevica, this would normally be UNIT unless another unit of measure is more suitable.</td></tr><tr><td>19 <code>Direct Unit Cost</code></td><td></td><td>Decimal</td><td>This will be the cost that appears on assembly BOMs and purchase orders.</td></tr><tr><td>24 <code>Unit Price</code></td><td></td><td>Decimal</td><td>This will be the price that appears on sales order lines.</td></tr><tr><td>51 <code>Gen. Prod. Posting Group</code></td><td>(251) General Prod. Posting Group</td><td>Code 20 (Mandatory)</td><td>Any value entered here must already exist in its related table.</td></tr><tr><td>58 <code>VAT Prod. Posting Group</code></td><td>(324) VAT Prod. Posting Group</td><td>Code 20 (Mandatory)</td><td>Any value entered here must already exist in its related table.</td></tr><tr><td>999999901 ..9999999012 <code>Dimension Code</code></td><td>(349) Dimension Value</td><td>Code 20</td><td>The Excel template will specify the specific dimension code to use here. Only use this field if the dimension code relates to your resource. Any value entered here must already exist in its related dimension code table. Note: Do not populate the Duty dimension column, or the Salesperson dimension column. The Duty dimension is used internally by the system. The Salesperson dimension will flow through to the transactions from the Salesperson Code field.</td></tr></tbody></table>


---

# 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/bevica-select/bevica-select-data-migration/bevica_select_-_data_migration_and_go-live-templates/bevica_select_-_resources_template.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.