SAP HCM & Organisational Management
For Nova, SAP HCM is the authoritative HR source: the personnel master drives the joiner/mover/leaver process, and Organizational Management supplies org units, positions, and their holders straight from the SAP tables HRP1000 and HRP1001.
What Nova does with SAP HCM & Organizational Management
- Reads personnel master data with SAP validity periods: Nova understands infotype values with date ranges and distinguishes current values from future-dated changes
- Simulation preview before every sync: you see joiners, movers, and leavers with the exact field changes before Nova writes anything
- Detects rehires by personnel number and email and reactivates the existing profile instead of creating a duplicate
- Future-dated changes, such as an upcoming department transfer or a leave date, are stored and take effect automatically on their due date
- Synchronizes the org tree from SAP Organizational Management: org units, positions, and position holders, optionally scoped to a subtree
- Field mapping between SAP attributes and Nova fields is configured in the admin interface, including your own custom fields
Technical integration
Personnel data arrives as SAP infotypes through a virtual directory server (LDAP) or a staging table; the organizational structure is read via RFC directly from HRP1000 and HRP1001, with an RFC ping as the connection check. Access to Organizational Management is read-only by design: Nova writes nothing into your HCM.
In the identity lifecycle
This source sets the pace of the lifecycle: new hires create users, changes of department or position trigger the mover routine, and leave dates deactivate accounts automatically through a daily scan; access requests and recertification work with the current org and position data from SAP.
All product names, logos and brands mentioned are property of their respective owners. They are referenced solely to describe compatibility and do not imply any partnership or endorsement.