creation / in progress
AKA ERP — Inventory & Procurement Contributions
Enmasys client work around product and asset data, purchasing screens, inventory-adjacent flows, and business reports.
about this build
The mission
Context and ownership. AKA is a client implementation at Enmasys. My assigned focus was the inventory area and its neighboring purchasing/product-data flows, not the entire company ERP or a complete WMS.
Concrete tasks visible in the supplied list: product master fields for analytic/cost accounts and import templates; asset-code visibility and search; a code-exchange price issue; product-name filtering on purchase-order detail; and accounting/reconciliation report corrections. The list also includes a vehicle-booking request in the fleet module.
These are scoped feature, data-field, search and defect-fix contributions. Most visible AKA rows are in a BA-test stage, so I do not present them as all released or claim warehouse throughput gains. The AKA corporate website identifies the client, not a public demo of its internal ERP.
Role: Contributed assigned Odoo changes around inventory/product data, purchase-order behavior and reports within an Enmasys client project.
technology
Primary GitHub language: Python
system highlights
- Product and asset fields, search and imports
- Purchase-order filtering and price-lookup fixes
- Accounting and reconciliation report adjustments
HOW IT WAS BUILT
Skills & technology in this project
Skills applied
- Inventory-adjacent ERP customization
- Product master-data modeling
- Procurement workflow debugging
- Business report fixes
Languages
- Python
- XML
Tools & platforms
- Odoo ERP
- Python models
- XML views