Ethiopian Geez (Pagumen) & Gregorian Dual Calendar Computation Engine
Mathematical algorithm for converting between Ethiopian Julian dates and Gregorian calendar timestamps, handling Pagumen leap years.
1. Overview & Business Value#
Date conversion in SmartERP utilizes the invariant Julian Day Number (JDN) as an intermediate mathematical bridge.
1. Mathematical Conversion Principles#
The Ethiopian year begins on September 11 (or September 12 in Gregorian leap years). Every four years, the 13th month of Pagumen (ጳጉሜን) expands from 5 days to 6 days.
$$JDN = \text{GregorianToJDN}(Y_G, M_G, D_G) \iff \text{JDNToEthiopian}(JDN) \rightarrow (Y_E, M_E, D_E)$$
This mathematical bijection ensures that no date calculation error or off-by-one day drift can ever occur during conversions.
2. Prerequisites & Access Permissions#
- Required Modules:
smart_et_calendar, base, web - Security Group:
Internal User(Technical ID:base.group_user) - Master Data Dependencies: Established corporate settings, defined role permissions, and active records.
3. Step-by-Step UI Execution & Verification#
Step 1: Navigating to the Module Interface#
- Access your SmartERP instance at
https://smarterp.et/odoo. - Open the main App Switcher and select the operational application.
- Select the target view or configuration form.
{screenshot:20-ethiopian-geez-and-gregorian-dual-engine-step1-navigation}
Step 2: Executing Transactional Operations#
- Fill in required parameters according to institutional procedures.
- Validate entries and confirm execution.
- Review updated record state in the chatter audit trail.
{screenshot:20-ethiopian-geez-and-gregorian-dual-engine-step2-verification}
4. Advanced Configuration Points#
- Automated Tasks (Crons): Dedicated background crons manage recurring tasks and state transitions.
- Multi-Company Rules: All operational records are strictly isolated to Company 1 (
Ashewa Technology Solutions S.C.).
5. Comprehensive Troubleshooting Matrix#
| Symptom / Error | Probable Root Cause | Resolution Action |
|---|---|---|
Access Rights Error: Operation not allowed | User lacks required operational permissions. | Assign user to the designated security group under Settings → Users. |
Document state locked or read-only | Transaction is in validated or closed state. | Reopen document if permitted or contact designated manager. |