---
alias: user-guide-attach-as-consumable
description: "This documentation details the process of attaching a consumable material to a resource for automated assembly"
---

# Attach as Consumable

:lock: Material.**AttachConsumable**

## Overview

This operation is used to attach a consumable **Material** to a consumable feed **Resource**. This operation is normally used with Automatic Material Assembling.

!!! smart-barcode "Supports Smart Barcodes"
    You can use [[smart-barcode-scanning]] to perform this operation.

## Setup

In order to enable the attaching of a Material at a given Resource, it is necessary to:

1. Have the Resource's processing type defined as Consumable Feed and with a Consumable Feed Service associated and enabled at the Resource. The Resource must be dispatchable.
2. The Material Required Service (the Service Context is defined at the Step level) at its current Step must match the Consumable Feed Service defined in 1. - note that, the Service must also be enabled globally.  

## Preconditions

* The **Material** must be in state Queued and must be dispatchable.
* The **Material** is not *OnHold* and is not *InTransit*.
* The **Material** Expiration Date is *Null*, or if defined, it must be in the future.
* The **Material** is not referenced in any Material Transfer.
* The Resource must have the Processing Type set to *ConsumableFeed* and it must be dispatchable.
* The Resource provides the required Material Service; the Service is globally enabled and also enabled at the Resource.
* The Material Product must not be blocked or if blocked, the Material property OverrideProductBlock must be true.
* The **Material** must not be associated with any Material Transfer.
* There must not be any Material Time Constraint violated for the **Material** at the current context and transaction.
* The **Material** must not have any open defects (Open Defect Count is zero).

## Sequence of Steps

The **Material** can be attached from the perspective of the Resource or from the perspective of the **Material**.

## Perspective of the Resource

### Step 1: Material

1. Select the desired **Material** from the list by selecting its row.

### Step 2: Details

This screen captures all the necessary remaining information for the transaction.

1. Verify the **Material** and **Resource** information.
2. If the **Resource** does not auto-manage its positions, it is necessary to specify the position of the **Material** (if the **Resource** capacity is expressed in **Materials**) or the position(s) of the **Material Container(s)** (if the **Resource** capacity is expressed in **Containers**) in the **Resource**. The position(s) reflects a physical location.
3. If the **Resource** has the *Has Resource Positions* flag enabled and is configured to use Locations, select the Location.
4. Optionally, specify the **Resource** queue order. The order represents a logical sequence for processing. By default, it uses a FIFO (First-In, First-Out).
5. Optionally, enter a comment.
6. Press **Attach** to complete the operation.

![Screenshot showing a UI image of an attachment process, with a highlighted "Attach" button.](images/attach_consumable.png)

## Perspective of the Material

### Step 1: Resource

This screens presents a list of the possible **Resources** to which the **Material** can be attached.

1. Select the desired Resource from the list by selecting the corresponding row.  

### Step 2: Details

This screens captures all the necessary information for the transaction.  

1. Verify the **Material** and **Resource** information.
2. If the **Resource** does not auto-manage its positions, it is necessary to specify the position of the **Material** (if the **Resource** capacity is expressed in **Materials**) or the position(s) of the **Material Container(s)** (if the **Resource** capacity is expressed in **Containers**) in the **Resource**. The position(s) reflects a physical location.
3. If the **Resource** has the *Has Resource Positions* flag enabled and is configured to use Locations, select the Location.
4. Optionally, specify the **Resource** queue order. The order represents a logical sequence for processing. By default, it uses a FIFO (First-In, First-Out).
5. Optionally, enter a comment.
6. Press **Attach** to complete the operation.

![Screenshot showing a UI with fields for "Attach Consumable To Resource" and "Resource Details".](images/attach_as_consumable.png)