SmartERP Documentation An Ashewa Technology Solutions Platform

Quick Start: Registering and Dispatching Official Correspondence

15-minute tutorial for logging an incoming letter, applying institutional metadata, and issuing an outgoing executive response.

1. Overview & Business Value#

Step-by-step tutorial on managing official institutional correspondence.

Module map showing dependencies between SmartERP Supply Chain Core, Tenders, Store Vouchers, Landed Costs, and WMS.
SmartERP Supply Chain and Sourcing architectural module map.

SmartERP Application Interface and Dashboard

1. Logging an Incoming Letter#

  1. Navigate to Letters → Incoming Letters → New.
  2. Enter the Sender Organization (e.g., Ministry of Innovation & Technology).
  3. Enter Sender Reference Number and Date of Letter.
  4. Upload the scanned letter PDF.

2. Routing to Department Head#

Select the destination department and assignee, then click Route for Review. The assignee receives an instant notification with the letter attachment.

2. Prerequisites & Access Permissions#

  • Required Modules: smarterp_documents, 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#

  1. Access your SmartERP instance at https://smarterp.et/odoo.
  2. Open the main App Switcher and select the operational application.
  3. Select the target view or configuration form.

Step 2: Executing Transactional Operations#

  1. Fill in required parameters according to institutional procedures.
  2. Validate entries and confirm execution.
  3. Review updated record state in the chatter audit trail.

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 / ErrorProbable Root CauseResolution Action
Access Rights Error: Operation not allowedUser lacks required operational permissions.Assign user to the designated security group under Settings → Users.
Document state locked or read-onlyTransaction is in validated or closed state.Reopen document if permitted or contact designated manager.
Last updated: 2026-11-15