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​
• ​Configuration Worksheet

When to use this template

Export it from Configuration Worksheet on the Resource line.

Step-by-step

1

Export the template

1. Open Configuration Worksheet.
2. Select the Resource line.
3. Select Excel → Export to Template.

2

Populate rows

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

3

Import and apply

1. Select Excel → Import from Template.
2. Fix any errors in the preview.
3. Select Apply Data.

4

Verify

1. Open Resources.
2. Filter on imported codes.
3. Check posting groups and UoM on the resource card.

Field reference (template columns)

Field list

The template has the following fields:

Field ID / Name	Related Table	FieldType	Note
1 No.		Code 20 (Mandatory)	Unique resource reference.
3 Name		Text 100
2 Type		Option (Mandatory)	Must be either Machine or Person. Within Bevica, this can be populated as either.
18 Base Unit of Measure	(204) Unit of Measure	Code 10 (Mandatory)	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.
19 Direct Unit Cost		Decimal	This will be the cost that appears on assembly BOMs and purchase orders.
24 Unit Price		Decimal	This will be the price that appears on sales order lines.
51 Gen. Prod. Posting Group	(251) General Prod. Posting Group	Code 20 (Mandatory)	Any value entered here must already exist in its related table.
58 VAT Prod. Posting Group	(324) VAT Prod. Posting Group	Code 20 (Mandatory)	Any value entered here must already exist in its related table.
999999901 ..9999999012 Dimension Code	(349) Dimension Value	Code 20	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.