on 04-02-2014 4:14 PM
Question for the good IDM people out there. I have an environment where HCM data is being handled by a VDS server to get into IDM. There's two IDS's in this environment, the main one and an HCM staging store. In the staging IDS, there's an entry type called MX_HCM_EMPLOYEE. Once a record of that entry type is entered into the system, there are add & modify tasks assigned to it that kick off the series of events that take that user out of the staging area and place them into the main IDS.
I cannot figure out how these entries are created in the first place. I don't see any scheduled jobs or anything that creates MX_HCM_EMPLOYEE entries. The only thing I can think of is that they are created directly on the backend by some outside force and, once it's there, IDM sees it and starts the process.
Has anyone else ever been in or seen a setup like this? Thanks in advance for any time and knowledge provided.
Brandon Bollin wrote:
I cannot figure out how these entries are created in the first place. I don't see any scheduled jobs or anything that creates MX_HCM_EMPLOYEE entries. The only thing I can think of is that they are created directly on the backend by some outside force and, once it's there, IDM sees it and starts the process.
If I understood your description correctly it sounds like a standard HCM-integration to me. VDS will receive the LDAP push from HCM and write the MX_HCM_EMPLOYEEs to the Staging Id Store.
regards, Tero
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK, so it's a standard deployment. I've honestly never worked in an IDM environment with HCM. I'm still fairly new to the SAP world, all things considered.
How does VDS write to the IdS? Where can I see the configuration for this setup in VDS? I'm specifically looking for the timing as the BASIS team is telling me the LDAP extractor happens at 10am and 4pm everyday but on IDM's side, we're seeing new employees get into IDM at noon and 6pm. There's always that 2 hour delay so I'm just trying to understand the nuts and bolts of this arrangement.
Browse the document titled "System Landscape Configuration Guide" first, it shows you how to connect the HCM to VDS/IdM. Once you know what to look for then it's pretty easy to figure out.
Open the VDS config with the VDS UI and you'll see the database connection from VDS to Id Store. The database URL is similar URL to the database as it is for the Java-runtime in MMC and the "scope" is the ID of the staging Id Store.
The two hour delay sounds strange. Does the task that moves the entries from staging to productive Id Store have a "delay before start" configured?
You don't need access to VDS as the software itself to see what's in the Staging Id Store, to browse the data either:
a) connect to the VDS (same port/host/credentials the HCM is using with the LDAP push) with LDAP browser (like Softerra for free) and you'll see the contents.
b) the Staging Id Store is in the same DB as the Productive Id Store, so if you have DB access just query for the data via SQL.
regards, Tero
Hi Brandon,
You can check, if the both systems(HCM and IdM) are on the same time zone. Sync manually user from SAP and check if he will come immediately or with delay, this is the easiest way.
Kind Regards,
Simona Lincheva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.