on 10-01-2013 3:19 PM
Hi "SAP BS Framework" Experts,
I'm working on writing back IT0105 (0001/0010) from SAP IDM to SAP HCM, provisioning, modification and deletion work fine using
- HR Comunication function set
- HCM integration repository type
- And ABAPBusiness Suite standard FW.
- IDM 7.2 SP8
My issue is on the modification process, as my requirement is to keep the modification history in HCM...
So if I change an email address from IDM, the email is "replaced" in HCM this way :
[01.10.2012][31.12.999]new@email.com
However I'm expecting IDM to keep the old value with validity dates in the past and create a brand new value of 0010 with a valid dates, like this :
[01.10.2000][01.10.2012]old@email.com
[01.10.2012][31.12.999]new@email.com
I know that the standard BAPI deals with infotype's validity dates as it modifies mine during my test case (from today's date to 31.12.9999), but I don't know if it deals with keeping the history of the old values?
I cheched the "Extending SAP Framework document", nothing reffers to how the dates are managed by the standard BAPI's...
Have anyone already had the same requierement for this case? Or Am I missing something around?
Thanks,
Fadoua
Hi Fadoua
By default, IDM just replaces all values without validity periods if I recall correctly. As such, its not going to hold on to the validity periods. The theory is that IDM stores the values and their modification dates so that they're not required in the back end system...
I do recall seeing a SAPNote about having assignments done with validity periods but don't have the details handy. I'm not sure if it would apply to generic attributes though.
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter,
Yes that's what I also think about the default behaviour of IDM.
You said "The theory is that IDM stores the values and their modification dates so that they're not required in the back end system"
Where are they stored ? are you thinking about audit tables?
Do you have any other suggestions on how to solve it at IDM tasks level only? I'm not sure it's possible without changing the standard behaviour of identity_modify module function....
I looked for SAP notes, I could'nt find anything about assignement validity periods with ABAP BS FW .
Thanks,
Fadoua
Hi Arun,
Yes, actually IDM does manage validity dates natively through the BADI.
If you want to keep the history of modifications with validity dates in IT105, the trick is to make one change per day... which make sense.
How I did it : it's all standard, the user should have priv info set, you modify email in IDM, it triggers modify user task (business suite) and the modification happens on IT105.
If you do several modifications a day, the value of email is just replaced , if you do on modification a new entry is created.
You don't need to manage any further dates on email in IDM.
And usually you have to leave PA20 transaction and search again for the user to see the new entry.
Fadoua
Hi Fadoua,
I am able to modify the email but my new requirement is to delete the email or delimit the email from IT105 0010 subtype. So, I tried to use DeleteIdentity task but the default settings when I use with change_mode with Value 'D' I get error: Exception from Modify operation:com.sap.idm.ic.ToPassException: User D does not exist.
Do you mind sharing the screenshot of the destination task you are using to delimit the email attribute?
Thanks,
Arun A
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.