> 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/banquet/banquet-module/masters/function-type.md).
# Function Type
The **Function Type** master is used to define and manage different types of banquet functions or events. This helps categorise events such as weddings, conferences, parties, meetings, and other banquet activities. It also allows linking each function type with a market segment for better reporting and analysis.
## **Steps to Create a Function Type**
Step 1: Log in to the system and navigate to the **Banquet Module**.
1. Click on the **Masters** menu.
2. Select **Function Type** from the available options.
Step 2: After selecting **Function Type**, the system will open the Function Type master screen.
Step 3: Click on the **New** button.
1. A new entry form will appear on the screen.
2. Enter the required details:
* **Function ID**
* **Function Name**
* **Market Segment**
Ensure that all details are entered correctly for proper classification and reporting.
Step 4:After entering the required details, click on the **Save** button.
* The system will save the Function Type successfully.
---
# 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/banquet/banquet-module/masters/function-type.md?ask=&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.
