Difference between revisions of "B-Op HR Hub"
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) |
Stefanseiler (talk | contribs) |
||
| Line 1: | Line 1: | ||
With almost all ZUGSEIL setups, importing HR data is a must as larger companies typically have a HR system already in place. To integrate with these 3rd party HR systems, b-op HR Hub was created as a standard tool to integrate seamlessly with any system landscape. | |||
Please note that this topic has to be observed closely and must be aligned with the [[Dev:B-Op data ownership and privacy principles|''b-op data ownership and privacy principles'']]'''.''' | Please note that this topic has to be observed closely and must be aligned with the [[Dev:B-Op data ownership and privacy principles|''b-op data ownership and privacy principles'']]'''.''' | ||
Revision as of 20:26, 9 July 2023
With almost all ZUGSEIL setups, importing HR data is a must as larger companies typically have a HR system already in place. To integrate with these 3rd party HR systems, b-op HR Hub was created as a standard tool to integrate seamlessly with any system landscape.
Please note that this topic has to be observed closely and must be aligned with the b-op data ownership and privacy principles.
Features
- Standard integrations - connect to any 3rd party software landspace (like S4HANA or SAR HR, Azure AD, Active Directory, ...)
- Easy connectivity - If you are bound to a non-standard HR data provider (CSV, Excel, ... ) you can integrate these data sources easiliy by creating HR Hub data acquisition plugins.
- Peer-to-peer HR data supply chains - if required you may push your HR data to thrird parties without using central data brokers
- b-op multi-realm setups - In large enterprises separate applications can be run in multiple realms hosted at separate locations. Propagate HR data in this scenario seamlessly by standard HR Hub data-acquisition and HR Hub data-push plugins.