Employment Hero Country Base
The shared registry every Employment Hero country pack plugs into, so localisation stays consistent and inspectable.
Store price is USD 107 all-in: installing this also pulls the 2 paid ERP Heritage modules it depends on.
Why this module
Employment Hero Country Base
One anchor per country
Each country pack registers exactly one eh.country.profile for its country. A database uniqueness rule on the country link means a deployment never ends up with two profiles for the same country.
See what is installed
A list and form under the suite configuration menu show every active country profile, its code and its ordering, so an operator can read off which localisations a deployment is running at a glance.
Tracked changes, split roles
The profile inherits chatter and field tracking, so edits are logged with who and when. Suite users read profiles; suite managers create, edit and archive them.
Day in the life
Where this fits on an ordinary day
You install a country pack for a region you operate in. On install it registers its country profile here, so when an administrator opens the suite configuration they see that localisation listed and active. If you wind a country down, you archive its profile rather than deleting it, keeping the record and its history intact. The base itself asks nothing of you day to day, it is the quiet registry the packs and the sync jobs reference.
Edge cases
The cases most modules quietly ignore.
In the shipped code today, each one a place where a cheaper module silently does the wrong thing.
A database uniqueness constraint on country_id blocks a second profile for the same country, so two packs cannot quietly register competing profiles for one country.
The active flag lets you retire a country profile without removing its records, and the Country Profiles screen sets active_test to false so archived profiles stay visible for review.
The country link uses ondelete cascade, so if a res.country record is removed the orphaned profile is cleaned up rather than left dangling.
The sync engine eh.mapping carries an optional country_id, so a country pack can ship a country tuned mapping and a sync job can point at that variant while the generic mapping covers the rest. This base provides the country anchor those variants reference; it ships no mappings of its own.
Changes to country_id, code, active and sequence are tracked through field tracking, so the chatter on each profile records what changed and when.
What is inside
Built to do the job, end to end.
- eh.country.profile model. One thin model with country_id (required, unique, cascade), a stable code, an active flag, a sequence and an operator note. Ordered by sequence then code, with mail.thread and mail.activity.mixin for chatter and tracking.
- Configuration screen and menu. A handle ordered list and a form under the suite configuration menu, with an empty state that prompts you to install a country pack to register its profile.
- Role based security. Two access rules: suite users get read on the profiles, suite managers get full create, write and unlink, both keyed to the existing eh_hero security groups.
- Automated test suite. Ships tests that create a profile, assert its defaults, and confirm the per country uniqueness constraint actually rejects a duplicate.
Honest about the edges
What this does not do, so nothing surprises you.
- This base is a registry only. It does not by itself add any fields to the employee record; the local identifier and payroll fields are contributed by the individual country packs that depend on it.
- It ships no eh.mapping records. It provides the country anchor that mapping variants can reference, but the mappings themselves come from the sync engine and the country packs.
- It performs no validation of national identifiers. Format checks, where they exist, live in the specific country packs.
- It does not call the Employment Hero platform, run sync, handle webhooks or queue work. Those capabilities live in the connector, sync engine and app modules of the suite.
- It depends on the Employment Hero sync engine and on mail, so those must be installed alongside it.
- Built and tested for Odoo 18 Community.
Employment Hero country base Odoo, Odoo 18 country localisation registry, employee country profile Odoo, Employment Hero localisation pack base, eh country profile model, country specific mapping Odoo sync, Odoo Community HR localisation foundation, Employment Hero suite country module
Need this fitted to the way you work?
ERP Heritage delivers end to end Odoo work: Odoo Implementation, Customization and Development, Integration, Migration, Consultation, Support and Training. We help teams put this module into production, shape it to their process, and keep it running.
We work with businesses across Australia (Melbourne, Sydney, Brisbane, Perth, Adelaide, Canberra) and the Middle East (Dubai, Abu Dhabi, Riyadh, Jeddah, Doha, Kuwait City, Muscat). Start a conversation at erpheritage.com.au or email info@erpheritage.com.au.
Languages
Available in 19 languages
The interface ships translated out of the box. Switch language in Odoo and the fields, menus, and messages follow.
Modules teams pair with this one.
Premium ERP Heritage modules that extend the same stack, each built to the same engineering bar.
A dependency free asynchronous job queue that runs long running and fan out work out of band of the request that...
Post Irish payslips to the general ledger on the Irish chart of accounts
Interactive drag and drop Gantt planner for Odoo 18 Community project tasks with a deterministic server side sche...
Employment Hero Connector is the integration core of the ERP Heritage Employment Hero suite, providing per compan...
Sync certifications, qualifications and employee document metadata from the Employment Hero people platform into...
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 3610 |
| Technical Name |
eh_hero_country_base |
| License | OPL-1 |
| Website | https://www.erpheritage.com.au/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module