Division Master
Division Master - User Guide
1. Introduction đ
The Division Master is used to segment your organization into distinct functional or geographical units. It acts as a primary dimension for categorizing transactions, enabling the system to generate division-wise financial reports, stock statements, and operational summaries.
Key Objectives of Division Master:
- Organizational Segmenting: Separate business logic by department, region, or product line.
- Transaction Tagging: Link every voucher and invoice to a specific division.
- Data Integrity: Enforce strict rules on record modification and deletion to prevent data orphaned records.
2. Structural Breakdown đī¸
The Division Master is a straightforward but high-impact configuration:
- Division Code: A unique 2-digit identifier (e.g., 01, 02). This code is auto-generated by the system based on the next available sequence.
- Division Name: A descriptive name for the segment (e.g., “Manufacturing”, “Sales”, “Corporate”).
- System Rule: Names are automatically converted to uppercase for consistency.
- Owner: Indicates whether the record was created by the user (“USR”) or the system (“SYS”).
3. Business Validations & Rules đĄī¸
To maintain system performance and numbering consistency, the following rules apply:
| Field | Rule / Validation |
|---|---|
| Capacity Limit | The system supports a maximum of 99 divisions. If you attempt to create the 100th division, the system will block the save with a “Form Error”. |
| Auto-Naming | Any leading or trailing spaces are trimmed, and the text is converted to UPPERCASE upon saving. |
| Code Length | Division codes are strictly 2 digits, ensuring they can be used as compact identifiers in high-volume transaction tables. |
4. Modification & Deletion Rules đ
The Division Master includes several layers of protection to ensure historical data remains valid:
đĢ System-Generated Records (SYS)
Records marked with an owner of “SYS” are protected core configurations.
- Action: You cannot modify or delete these records. They are essential for internal ERP processes.
đĢ Deletion Prevention (In-Use Checks)
The system performs a “Deep Audit” before allowing a division to be deleted:
- Usage Check: The system scans every transaction table (Vouchers, Invoices, Production, etc.) to see if the Division Code is currently in use.
- Live Record Alert: If the division is linked to even a single transaction, the system will display the alert: “Master Record is live. You may not delete it.”
- Owner Check: User-created records can only be deleted if they have zero historical usage.
đĢ Modification Constraints
- Division Code: Once assigned, the code cannot be edited. Only the Division Name can be updated for user-created records.
5. Reports & Integration đ
The Division Master is a “Key Dimension” used across the reporting landscape:
đ Usage in Transactions
- Vouchers & Invoices: Almost every financial or inventory document in the system requires a
DivisionId. This allows for segment-level tracking of profits, losses, and stock movements. - Departmental Linking: Many other masters (like Employee or Item masters) can be optionally restricted or filtered by Division to simplify data entry.
đ Reports Filtering
- Division-wise Trials: Generate Trial Balances or Profit & Loss statements for a specific division.
- Stock Ledger by Division: Track inventory levels across different geographical segments.
6. Best Practices đĄ
- Standardize Names: Use clear, concise names (e.g., “MKTG” instead of “Marketing Division West”) to ensure they display well in compact report columns.
- Planning for Growth: Since there is a 99-record limit, use divisions for broad segments (Regions/Business Units) rather than granular entities like individual machines or projects. Use “Cost Centers” for more granular tracking.
- Check Usage First: Before attempting to rename or delete a division, run a “Division-wise Transaction Summary” to ensure you understand the historical data impact.