> For the complete documentation index, see [llms.txt](https://docs.novacura.com/marketplace-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/marketplace-documentation/applications/explore-apps/ifs/warehouse-management/documentation/ifs-cloud/procurement/attach-receipt-to-handling-unit.md).
# Attach Receipt to Handling Unit
## Overview
Attach a receipt to a handling unit. During the process, users can enter a quantity to attach an inventory part in stock with 0 handling unit id to a handling unit.
*The complete overview of the flow(app):*
{% file src="/files/y5YlGJPaaMnfNBMe53VA" %}
## Steps
### Enter Source Ref 1
* Source Ref 1 is required
* Click on the **List** button to see a list of orders which you can attach its receipts to a handling unit
{% hint style="info" %}
**Pin Step:**
Display the user default Site ID and its description.
{% endhint %}
| |  |
| :-----------------------------------------------------------------: | :------------------------------: |
| Flow Connect | Flow Classic |
### **Enter Handling Unit ID**
* Handling Unit ID is mandatory, and it should belong to the user default site (Or the site should be empty)
* Handling Unit should not be connected to any shipment and the “In Transit” checkbox should not be checked in the Handling Unit
* Click on the **List** button to see a list of Handling Unit ID’s which satisfy the above conditions
| |  |
| :-----------------------------------------------------------------: | :------------------------------: |
| Flow Connect | Flow Classic |
### **Enter Part No**
* Part No is mandatory
* Click on the **List** button to see a list of parts connected to the Order No entered in the first step
{% hint style="info" %}
*Based on the selected Part user might be prompted with additional user steps as described in the rest of this document*.
{% endhint %}
| |  |
| :-----------------------------------------------------------------: | :------------------------------: |
| Flow Connect | Flow Classic |
{% hint style="info" %}
*Based on the selected Part user might be prompted with additional user steps to filter out* **Inventory Part In Stock** *records until a unique stock record is selected. For more info about these additional steps please refer* [*Inventory Part In Stock Selection*](/marketplace-documentation/applications/explore-apps/ifs/warehouse-management/documentation/ifs-application-10/inventory-part-in-stock-selection.md)*.*
{% endhint %}
### **Enter Qty To Attach**
* Qty to Attach is required
* Click on the **Save** button to complete the process
{% hint style="info" %}
**Pin Step:**
Display information about the selected inventory part in stock record.
{% endhint %}
| |  |
| :-----------------------------------------------------------------: | :------------------------------: |
---
# 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://docs.novacura.com/marketplace-documentation/applications/explore-apps/ifs/warehouse-management/documentation/ifs-cloud/procurement/attach-receipt-to-handling-unit.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.