All tables
tables · table

CompanyConfigMenu

The CompanyConfigMenu table serves as a metadata repository defining the hierarchical menu structure and user interface navigation for specific companies within the ERP system. It maps menu internal identifiers (MenuName) to human-readable labels (caption), associates them with specific application forms (mainform), and controls their visibility. This table is primarily used by the application's UI engine to dynamically render modules such as "Masters," "Transactions," and "Store Receipt Notes" based on company-specific configurations.

Row count
120
Last entry
Source
tables

Columns

7
ColumnTypeNullableMeaning
indexintegerNoPrimary Key: Unique row identifier
compcodestringNoCompany Code
mainformstringYesThe parent application form containing this menu
mtypestringYesMenu Type category
captionstringYesDisplay text shown to the user
MenuNamestringYesInternal technical name of the menu control
visiblestringYesToggle flag for UI display status

Full documentation

### 1) Overview
 The `CompanyConfigMenu` table serves as a metadata repository defining the hierarchical menu structure and user interface navigation for specific companies within the ERP system. It maps menu internal identifiers (`MenuName`) to human-readable labels (`caption`), associates them with specific application forms (`mainform`), and controls their visibility. This table is primarily used by the application's UI engine to dynamically render modules such as "Masters," "Transactions," and "Store Receipt Notes" based on company-specific configurations.
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Primary Key: Unique row identifier | | `WHERE index = 10` |
 | **compcode** | string | No | Company Code | e.g., "DAS" | `JOIN` on `compcode` |
 | **mainform** | string | Yes | The parent application form containing this menu | e.g., "frmcstore1" | Filtering by module |
 | **mtype** | string | Yes | Menu Type category | e.g., "T" | Categorization |
 | **caption** | string | Yes | Display text shown to the user | e.g., "Vendor Master" | UI Labels |
 | **MenuName** | string | Yes | Internal technical name of the menu control | e.g., "mnuvendmas" | `JOIN` on Menu Names |
 | **visible** | string | Yes | Toggle flag for UI display status | "Y", "N" | `WHERE visible = 'Y'` |
 
 ### 3) Relationships & Join Map
 
 The `CompanyConfigMenu` table acts as a master definition for menus, which are then assigned permissions in various user rights tables.
 
 #### Primary Joins (SCHEMA_MAP Verified):
 * **dbo.userrights**: Join on `compcode` and `MenuName` (maps to `userrights.menuname`). This relates menu definitions to user-specific access levels (addition, deletion, etc.).
 * **dbo.userrightsmain**: Join on `compcode` and `MenuName` (maps to `userrightsmain.menuname`). Similar to userrights, often used for global or template permissions.
 * **dbo.UserrightsHdr**: Join on `compcode` and `MenuName` (maps to `UserrightsHdr.vbmenuname`).
 
 #### Likely Joins (Inferred):
 * **dbo.Form_Active_Status**: Join on `mainform` (maps to `form_name`) and `compcode` to check if the parent module is active for the company.
 * **dbo.Deletion_Log**: Join on `mainform` (maps to `FormName`) to audit deletions occurring within specific menu contexts.