> 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-library-wms/issue-material-requisition-line.md).

# Issue Material Requisition Line

## Steps

### **Enter Order No**

* Material Requisition Order Number is required and should be in status **Released**, **Partially Delivered** or **Reserved**.
* Click on the **List** button to see a list of material requisitions that satisfy the above condition.

<img src="https://3218748546-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MiW42YxFsGXIDjQJKNR%2Fuploads%2FQNT4mUp13e5lQwoFn0dF%2Funknown.png?alt=media&amp;token=07c2dae1-8597-48f9-ac02-17b4e3eeb84f" alt="" height="728" width="544">

### **Enter Part No**

* Part No is required and should belong to the requisition entered in the previous step.
* Click on the **List** button to see a list of parts that satisfy the above condition.

{% 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-apps/ifs-application-10/inventory-part-in-stock-selection.md)&#x20;
{% endhint %}

<img src="https://3218748546-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MiW42YxFsGXIDjQJKNR%2Fuploads%2FZnkQcyIZ4M7eYwuqHO52%2Funknown.png?alt=media&amp;token=6a25a01b-fd44-4833-8ca2-dec2bf4b159c" alt="" height="730" width="546">

### **Enter Release No**

{% hint style="info" %}
This step is shown only if the selected Order No in the previous step has more than one order line revision for selected Part No.
{% endhint %}

* Release No is required
* Click on the **List** button to see a list of Release No’s for the selected part.

### **Enter Qty**

* Qty to Issue is required cannot be a negative number or higher than the required quantity.&#x20;

<img src="https://3218748546-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MiW42YxFsGXIDjQJKNR%2Fuploads%2Fb0H2TlFTlBc2zKfTwaSH%2Funknown.png?alt=media&amp;token=1baaf82a-c568-4e08-ad52-84a4bca1cdd1" alt="" height="730" width="544">

### **Choose the next step**

* Only shown if the order is partially issued.
* On this screen, you can choose from 3 options.
  * Menu - Exit the workflow(app).
  * Issue Another Part - Restart the whole process from the beginning.
  * Issue Same Part - Issue the same part but from a different source.

## Pre-Validation Checks&#x20;

* A Material Requisition must exist and be in Released, Partially Delivered, or Reserved status.&#x20;
* The Material Requisition must contain at least one Material Requisition Line for the part being issued.&#x20;
* An Inventory Part must exist and be connected to the requisition line. &#x20;
* The Inventory Part must have sufficient available stock in inventory to issue the required quantity.&#x20;
* If issuing a reserved requisition line through the standard process, the requisition line must be reserved before issue.&#x20;
* The Quantity to Issue must be greater than zero and cannot exceed the required quantity on the requisition line.&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.novacura.com/marketplace-documentation/applications/explore-apps/ifs/warehouse-management/documentation-library-wms/issue-material-requisition-line.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
