> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/material-management/material-management-module/mm-transactions/faq-on-material/how-to-view-report-for-further-supplier-tracking-and-procurement-analysis.md).

# How to view report for further supplier tracking and procurement analysis?

Here is how you can view both reports for supplier tracking and procurement analysis:

1\. Receipt Analysis

This report provides information on all receipts processed within the Inventory Module, including bill numbers, bill dates, and other supplier-related receipt details.

* Navigation: Go to Analysis > Receipt Analysis.
* Steps:
  1. Use the Funnel Filter or Group By drop-down options to filter or group specific information.
  2. Click the Option button to apply additional filter criteria if needed.
  3. Click the Display button to load the report.

***

2\. Supplier Wise Receipt:

This report details the receipt of goods, materials, or services categorized individually for each supplier. It tracks delivered quantities, delivery dates, purchase order references, and other key details to assist with vendor reconciliation, inventory management, and payment processing.

* Navigation: Go to Analysis > Supplier Wise Receipt.
* Steps:
  1. Go to Analysis > Supplier Wise Receipt.
  2. Use the Funnel Filter and Group By drop-down options to filter or search for specific suppliers and parameters.


---

# 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://help.rbsgo.com/material-management/material-management-module/mm-transactions/faq-on-material/how-to-view-report-for-further-supplier-tracking-and-procurement-analysis.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.