> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/implementation/training-resources/user-manual/web-application-user-manual/registries/schedule-of-rates/sor-definition.md).

# SOR Definition

## **Search SOR**

**Home Page → Schedule of Rates** 

(Select the Module Name as SOR and Master Name as SOR)

The Search SOR functionality enables users to search for a particular Schedule of Rates (SOR) and subsequently open it to access and view detailed information. This feature streamlines the process of locating and reviewing specific SORs within the system.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXeIXlIXYsp5IGgFjogW99viKxXXyO3dKgoTgrmECSTTF2fRaBMTsnv7kTdRdD_AkUk-OZqQ-X5_L04n9oEX-1mxViZLALGZEkaekMe97g4mVawXpxIlE_Sxa11hr-9cpW1B5MoIQp6g8pdF9vc6GdwjML8?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXel230gx1UMicfTK431-IVc0nkiwDcn5FvXBHN-AzvZ96XxujMsATTWiAe_9Am9j6OcVb-jbP-78cSNpYidTfJzJV0J7VfRrmt4Xv3lnBVW3ozLY2p36oxvlLA0-X5y5pO6PdwKjYQ5f6Yfwm9NtfozWes?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption></figcaption></figure>

## Add SOR

**Search SOR Definition >  Add Master Data**

The "Add SOR" functionality enables users to create a new SOR.

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/Pivl5XqHMbwhaa7M2JnE/image.png" alt=""><figcaption></figcaption></figure>

## **View SOR**

The "View SOR" feature empowers users to access and review the details of a specific Schedule of Rates (SOR). This functionality provides a comprehensive view, allowing users to examine and understand the specifics of the rate structure and associated information within the SOR.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXf9OdEenVdop6R9VBD2HoevVQkUi36tZjZ68EPzPQ22xkk1G7Pf8Gc3hiNYZ6lt9RFDaD8fjUtpF4Q7ZMmGOQ_ZipVnM1jzVGRSGoZk75H_Pg8PBzociU6t1zlHv-Kdn9S4dOPERJ-SB4WVlBwqOrEBzA?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption></figcaption></figure>

## Edit SOR

**Search SOR Definition > View SOR Definition > Take Action > Edit Master**

The "Edit SOR Definition" functionality enables users to modify an existing SOR details.

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/yxsKClLcHEIxPCg4ARCL/image.png" alt=""><figcaption><p>View SOR Definition</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/DOswbBEJYfljVfqljigp/image.png" alt=""><figcaption><p>Edit SOR Definition</p></figcaption></figure>


---

# 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.digit.org/works/reference-implementations/muktasoft-v2.2/implementation/training-resources/user-manual/web-application-user-manual/registries/schedule-of-rates/sor-definition.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.