UOM, currency, material master, cost codes, approval matrix, custom fields, holiday calendar, notification templates, and sequence configuration.
Master Data Governance ensures consistent reference data across all InfraTraq modules. Unit of Measurement (UOM) standardization prevents conversion errors. Material master provides a single source of truth for material codes. Cost codes enable uniform project cost tracking. Approval matrix defines approval levels by amount and document type. Custom fields extend entity schemas without database changes. Notification templates standardize system communications.
| Status | Description | Allowed Actions | Next States |
|---|---|---|---|
| Active | Master record in use across system | Edit, Deactivate | Inactive |
| Pending Review | New/changed record awaiting approval | Approve, Reject | Active, Rejected |
| Inactive | Record deactivated, not available for selection | Reactivate | Active |
| Draft | Record being prepared | Submit for Review | Pending Review |
material_id — PKtenant_id — FK → organization.tenantmaterial_code, material_name — Unique identificationcategory, sub_category — Classification hierarchyuom_id — FK → master_data.uomhsn_code — GST HSN/SAC classificationis_active — Availability flagcost_code_id — PKcode, description — Cost code identifier and meaningcategory — material | labour | equipment | overhead | subcontractparent_cost_code_id — FK → self (hierarchical)is_active — Active flagmatrix_id — PKdocument_type — po | mr | payment | budget | change_ordermin_amount, max_amount — Amount range for this levelapprover_role_id — FK → admin.rolelevel_order — Sequential approval level (1, 2, 3...)is_active — Active flaguom_id — PKuom_code, uom_name — e.g., MT (Metric Ton), CUM (Cubic Meter)category — length | area | volume | weight | countbase_uom_id, conversion_factor — For UOM conversiontemplate_id — PKevent_type — po_approved | grn_received | invoice_due etc.channel — email | sms | push | in_appsubject_template, body_template — Templates with {{variables}}is_active — Enabled/disabledfield_id — PKentity_type — project | vendor | material etc.field_name, field_type — text | number | date | dropdownoptions_json — Dropdown options if applicableis_required, is_active — Validation flagsDefine UOMs, currencies, cost codes, and material categories following industry standards (IS codes, HSN/SAC). Establish naming conventions and code structures.
Configure multi-level approval matrix per document type and amount range. Higher amounts require higher authority. Matrix reviewed quarterly as org structure changes.
New materials added through approval workflow. Duplicates detected by name/code similarity. Inactive materials hidden from selection but retained for historical reference.
Administrators extend entity forms with custom fields. Field types include text, number, date, and dropdown. No database schema changes needed — stored in JSONB columns.
All master data changes logged in audit trail. Bulk changes (e.g., HSN code update) go through approval workflow. Version history maintained for compliance.
-- Find approval chain for a purchase order amount SELECT am.level_order, r.role_name, am.min_amount, am.max_amount FROM master_data.approval_matrix am JOIN admin.role r ON r.role_id = am.approver_role_id WHERE am.document_type = 'po' AND am.is_active = TRUE AND :po_amount BETWEEN am.min_amount AND am.max_amount ORDER BY am.level_order;