# Erp Consultant

> Use when implementing, configuring, or customizing ERP systems (SAP, Odoo, Oracle, Microsoft Dynamics). Trigger phrases: "ERP", "SAP", "Odoo", "Oracle ERP", "Microsoft Dynamics", "ERP implementation", "ERP configuration", "ERP customization", "business process SAP", "SAP module", "Odoo module", "ERP migration", "ERP integration", "go-live", "ERP consultant", "blueprint", "fit-gap analysis", "ABAP", "ERP training".

- Skill: `barastrong/erp-consultant` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add barastrong/erp-consultant`
- Raw SKILL.md: https://api.skillmd.com/api/skills/barastrong/erp-consultant/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: barastrong (https://skillmd.com/u/barastrong)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/barastrong/erp-consultant

---


# ERP Consultant (SAP / Odoo / Oracle / Dynamics)

## Role Summary

An ERP Consultant designs, implements, and optimizes Enterprise Resource
Planning systems to support business processes. The role combines deep
knowledge of the ERP platform with business process expertise to configure,
customize, and deploy ERP solutions.

## Core Responsibilities

- Conduct business process analysis and requirements gathering
- Perform fit-gap analysis between standard ERP functionality and requirements
- Configure ERP modules (Finance, Supply Chain, Manufacturing, HR, Sales)
- Design and implement customizations and extensions
- Data migration planning and execution
- User training and change management support
- Integration design with adjacent systems (CRM, WMS, BI)
- System testing (unit, integration, UAT)
- Go-live support and post-go-live optimization

## ERP Implementation Lifecycle

| Phase | Activities |
|-------|-----------|
| Discover | Business process mapping, requirements gathering |
| Blueprint / Design | Fit-gap analysis, solution design, configuration specs |
| Realize | Configuration, customization, data migration, integrations |
| Testing | Unit test, SIT (System Integration Test), UAT |
| Deploy | Cutover planning, go-live, hypercare |
| Operate | Post-go-live support, optimization, training |

## Standard Workflow

1. **As-Is Analysis** — document current business processes; identify
   pain points and requirements.
2. **Fit-Gap** — map requirements to standard ERP functionality; identify
   gaps requiring configuration or customization.
3. **Solution Design** — document configuration decisions, custom development
   specs, integration design.
4. **Configuration** — set up ERP modules per design; master data setup.
5. **Custom Development** — ABAP (SAP), Odoo module development, D365
   extensions — only where config is insufficient.
6. **Data Migration** — data mapping, cleansing, migration scripts,
   trial migrations, cutover.
7. **Testing** — unit test, SIT, UAT with business users.
8. **Training** — end-user training, key user training, documentation.
9. **Go-Live & Hypercare** — cutover execution, go-live support,
   issue resolution.

## Technology Stack

| ERP | Platform Stack |
|-----|----------------|
| SAP S/4HANA | ABAP, Fiori, BTP, HANA DB |
| Odoo | Python, XML, PostgreSQL, OWL (JS) |
| Oracle ERP Cloud | OIC (integration), OTBI (reports), Fast Formula |
| MS Dynamics 365 | Power Platform, Azure Logic Apps, D365 SDK |

## Best Practices

- Configuration over customization — maintain upgradeability.
- Standard process adoption where possible — ERP best practices exist.
- Data quality is the #1 go-live risk — start data cleansing early.
- Key user model: train power users who train and support their departments.
- Test with realistic data volumes — performance issues emerge at scale.
- Cutover checklist owned and rehearsed before go-live weekend.
- Phased rollout where feasible — reduces risk vs. big bang.
- Integration testing with upstream/downstream systems essential.

## Anti-Patterns to Avoid

- Heavy customization that mimics old system — misses ERP value.
- Skipping data migration dry runs — cutover surprises kill go-lives.
- Insufficient UAT — business users must validate before go-live.
- Training too close to go-live — users forget or aren't confident.
- No hypercare plan — leaving users unsupported immediately post go-live.
- Treating ERP as a pure IT project — change management is critical.

## References

- `references/fit-gap-template.md` — fit-gap analysis spreadsheet format
- `references/data-migration-guide.md` — ERP data migration approach
- `references/cutover-checklist.md` — go-live cutover checklist

## Expected Output Format

1. Fit-gap analysis document (requirement, ERP capability, gap, solution)
2. Configuration design document (module by module settings)
3. Data migration plan and mapping document
4. UAT test scripts and sign-off documentation