ይህ ገጽ ገና ወደ አማርኛ አልተተረጎመም። የእንግሊዝኛው ጽሑፍ ቀርቧል።
Predictive Stock Replenishment & Reordering Rules Copilot
Machine learning replenishment agent forecasting product demand and generating automated purchase requisitions.
1. Overview & Business Value#
The Predictive Stock Replenishment Agent combines historical inventory consumption rates, seasonal variations, and supplier lead times to prevent stockouts while avoiding overcapitalization.
1. Mathematical Replenishment Heuristic#
$$\text{Reorder Point (ROP)} = (\text{Lead Time} \times \text{Average Daily Demand}) + \text{Safety Stock}$$
$$\text{Safety Stock} = Z \times \sigma_{\text{LT}} \times \sqrt{\text{Lead Time}}$$
{screenshot:ai-inventory-replenishment-forecast}
2. Step-by-Step Execution#
- Open Inventory → Operations → Replenishment Copilot.
- Review items with projected stockout dates within the supplier lead time window.
- Click Stage Purchase Requisitions to generate purchase requests in
draftstate.
2. Prerequisites & Security Access Groups#
- Required Modules:
muk_ai, muk_mcp, smarterp_ai_suite - Security Group:
Ashewa AI / User(Technical ID:muk_ai.group_ai_user) - Master Data Dependencies: Configured AI provider credentials, active system prompts, and departmental cost centers.
3. Step-by-Step UI Execution & Verification#
Step 1: Navigating to the Operational Interface#
- Log into your SmartERP instance at
https://smarterp.et/odoo. - Open the main App Switcher and select Ashewa AI.
- Select the operational workspace corresponding to this agent suite.
{screenshot:64-predictive-stock-replenishment-agent-step1-navigation}
Step 2: Executing Agent Actions#
- Review agent prompts and execution parameters.
- Trigger the scheduled or on-demand workflow action.
- Validate output in the generated operational log.
{screenshot:64-predictive-stock-replenishment-agent-step2-execution}
4. Advanced Configuration Points#
- Scheduled Crons:
muk_ai.ir_cron_agent_health_checkruns every 30 minutes. - Multi-Company Isolation: Multi-company record rules ensure agent context is isolated to Company 1 (
Ashewa Technology Solutions S.C.).
5. Comprehensive Troubleshooting Matrix#
| Symptom / Error | Probable Root Cause | Resolution Action |
|---|---|---|
Agent unresponsive or timeout | Network latency or API endpoint outage. | Verify provider connection in Settings → AI Providers. |
Access Denied during agent execution | User lacks assigned operational permissions. | Assign user to the designated operational group. |
መጨረሻ የተሻሻለው: 2026-10-30