Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
271 views

few attributes are not readable from sap hr idoc


Hi,

We are using IDM 4.0.2 on windows. For our IDM, SAP HR is the user data
source, we have a SAP HR driver to read hr idoc file. The driver is able
to read the idoc file and creates user in IDM.

But the driver is not able to get the username, company, manager and few
attribute values from idoc.

We use the standard metadata file shipped with SAP HR driver
(HRMD_A05.meta) file.

Please let us know to identify the problem and to solution to fix it.

Thanks,
DK


--
dinatechmnovell
------------------------------------------------------------------------
dinatechmnovell's Profile: https://forums.netiq.com/member.php?userid=6777
View this thread: https://forums.netiq.com/showthread.php?t=51151

Labels (1)
0 Likes
9 Replies
Anonymous_User Absent Member.
Absent Member.

Re: few attributes are not readable from sap hr idoc

Hi DK,

Are you using SAP driver?

I am in the process of connecting SAP to IDM but I am doing it the XPATH
style as it turns out to be surprisingly simple way.

Pekka
On 23.6.2014 9:44, dinatechmnovell wrote:
>
> Hi,
>
> We are using IDM 4.0.2 on windows. For our IDM, SAP HR is the user data
> source, we have a SAP HR driver to read hr idoc file. The driver is able
> to read the idoc file and creates user in IDM.
>
> But the driver is not able to get the username, company, manager and few
> attribute values from idoc.
>
> We use the standard metadata file shipped with SAP HR driver
> (HRMD_A05.meta) file.
>
> Please let us know to identify the problem and to solution to fix it.
>
> Thanks,
> DK
>
>


0 Likes
Knowledge Partner
Knowledge Partner

Re: few attributes are not readable from sap hr idoc

On 6/23/2014 3:17 AM, Pekka Kuronen wrote:
> Hi DK,
>
> Are you using SAP driver?
>
> I am in the process of connecting SAP to IDM but I am doing it the XPATH
> style as it turns out to be surprisingly simple way.


What is the XPATH style? What do you mean by that specifically?


> On 23.6.2014 9:44, dinatechmnovell wrote:
>>
>> Hi,
>>
>> We are using IDM 4.0.2 on windows. For our IDM, SAP HR is the user data
>> source, we have a SAP HR driver to read hr idoc file. The driver is able
>> to read the idoc file and creates user in IDM.
>>
>> But the driver is not able to get the username, company, manager and few
>> attribute values from idoc.
>>
>> We use the standard metadata file shipped with SAP HR driver
>> (HRMD_A05.meta) file.
>>
>> Please let us know to identify the problem and to solution to fix it.
>>
>> Thanks,
>> DK
>>
>>

>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: few attributes are not readable from sap hr idoc

On 23.6.2014 12:55, Geoffrey Carman wrote:
> On 6/23/2014 3:17 AM, Pekka Kuronen wrote:
>> Hi DK,
>>
>> Are you using SAP driver?
>>
>> I am in the process of connecting SAP to IDM but I am doing it the XPATH
>> style as it turns out to be surprisingly simple way.

>
> What is the XPATH style? What do you mean by that specifically?
>
>


Please forgive my silly expression, should not have answered so promptly
in a hurry.

I am doing it with a CSV driver that translates the SAP xml directly
into IDM spec xml digested by normal policies. This turned out to be
simpler than expected and can recommend that if you do not get the SAP
HR driver working and you have the SAP xml file at hand.

I am using XPATH matching in the input transformation policy to match
work contracts and their attributes from the original SAP xml file,
turning it to IDM digestable XML for the policies further down the fishbone.

Pekka

0 Likes
Knowledge Partner
Knowledge Partner

Re: few attributes are not readable from sap hr idoc

On 6/24/2014 4:26 AM, Pekka Kuronen wrote:
> On 23.6.2014 12:55, Geoffrey Carman wrote:
>> On 6/23/2014 3:17 AM, Pekka Kuronen wrote:
>>> Hi DK,
>>>
>>> Are you using SAP driver?
>>>
>>> I am in the process of connecting SAP to IDM but I am doing it the XPATH
>>> style as it turns out to be surprisingly simple way.

>>
>> What is the XPATH style? What do you mean by that specifically?
>>
>>

>
> Please forgive my silly expression, should not have answered so promptly
> in a hurry.
>
> I am doing it with a CSV driver that translates the SAP xml directly
> into IDM spec xml digested by normal policies. This turned out to be
> simpler than expected and can recommend that if you do not get the SAP
> HR driver working and you have the SAP xml file at hand.
>
> I am using XPATH matching in the input transformation policy to match
> work contracts and their attributes from the original SAP xml file,
> turning it to IDM digestable XML for the policies further down the
> fishbone.


So instead of iDOC you use an XML interchange format? Interesting. How
do you write back to SAP?



0 Likes
Knowledge Partner
Knowledge Partner

Re: few attributes are not readable from sap hr idoc

On 6/23/2014 2:44 AM, dinatechmnovell wrote:
>
> Hi,
>
> We are using IDM 4.0.2 on windows. For our IDM, SAP HR is the user data
> source, we have a SAP HR driver to read hr idoc file. The driver is able
> to read the idoc file and creates user in IDM.
>
> But the driver is not able to get the username, company, manager and few
> attribute values from idoc.
>
> We use the standard metadata file shipped with SAP HR driver
> (HRMD_A05.meta) file.


The file you use here, needs to match the name that the iDOC declares as
its type. I.e. If the SAP system says it is HRMD_A07, then your file
needs to be renamed to match.

What infotypes have you matched to the various attributes?

I suspect the values you are looking for are referenced off other objects.

Manager for example is not stored on the User (P) object.

You need to find the S object (Position), look at it parent Org (O), and
find the Position under that O that is flagged as the managing position,
get the PENRUM of that Person (P) filling that Position (S) and find
that user by workforceID in your IDV.

Have you looked at any of my articles on the complexities of the SAP
driver? They may prove helpful in understanding, as it is quite complex.


SAP Drivers:
http://www.novell.com/communities/node/9471/sap-driver-family-idm

SAP HR:
http://www.novell.com/communities/node/4562/troubleshooting-idoc-issues-sap-hr-driver-identity-manager

http://www.novell.com/communities/node/2792/idm-sap-hr-driver-where-get-jconnect-libraries
http://www.novell.com/communities/node/6351/sap-hr-driver-and-organizational-management-part-1
http://www.novell.com/communities/node/4144/decoding-idocs-idm-sap-driver
http://www.novell.com/communities/node/4482/using-sap-hr-driver-idm-a-64-bit-os
http://www.novell.com/communities/node/9271/error-codes-sap-hr-driver-identity-manager-part-1
http://www.novell.com/communities/node/9512/sap-hr-cmp-integration-driver
http://www.novell.com/communities/node/9537/sap-hr-cmp-integration-driver-walkthough-part-1
http://www.novell.com/communities/node/9547/sap-hr-cmp-integration-driver-walkthough-part-2
http://www.novell.com/communities/node/9556/sap-hr-cmp-integration-driver-walkthough-part-3
http://www.novell.com/communities/node/10001/sap-hr-cmp-integration-driver-walkthrough-part-4
http://www.novell.com/communities/node/11274/sap-hr-cmp-integration-driver-walkthrough-part-5
http://www.novell.com/communities/node/11313/sap-hr-cmp-integration-driver-walkthrough-part-6
http://www.novell.com/communities/node/11481/sap-hr-cmp-integration-driver-walkthrough-part-7
http://www.novell.com/communities/node/11517/sap-hr-cmp-integration-driver-walkthrough-part-8
http://www.novell.com/communities/node/11518/sap-hr-cmp-integration-driver-walkthrough-part-9

SAP Business Logic:
http://www.novell.com/communities/node/11551/sap-business-logic-idm-driver-walkthrough-part-1
http://www.novell.com/communities/node/11552/sap-business-logic-idm-driver-walkthrough-part-2
http://www.novell.com/communities/node/11563/sap-business-logic-driver-walkthrough-part-3

SAP Portal:
https://www.netiq.com/communities/cool-solutions/sap-portal-matching-substrings-of-usernames





0 Likes
Knowledge Partner
Knowledge Partner

Re: few attributes are not readable from sap hr idoc

Geoffrey Carman wrote:

> You need to find the S object (Position), look at it parent Org (O), and find
> the Position under that O that is flagged as the managing position, get the
> PENRUM of that Person (P) filling that Position (S) and find that user by
> workforceID in your IDV.


And if the O holding the S for the P you look at does not have a managing
position䂪directly assigned, you'll have to walk the org tree upwards until you
find a managing position assigned to a superior org unit. All assuming you
(read: your HR dept) use this standard org model in SAP. There's also the
posibility to create a hierarchy of positions (parallel to the org tree the
positions are linked to) and then you also have different relationships for
line reporting and supervision... so depending on where you look and how you
define "manager" you might get different results, all off the same SAP
system... it's fun, though! 😉
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Knowledge Partner
Knowledge Partner

Re: few attributes are not readable from sap hr idoc

On 6/23/2014 10:36 AM, Lothar Haeger wrote:
> Geoffrey Carman wrote:
>
>> You need to find the S object (Position), look at it parent Org (O), and find
>> the Position under that O that is flagged as the managing position, get the
>> PENRUM of that Person (P) filling that Position (S) and find that user by
>> workforceID in your IDV.

>
> And if the O holding the S for the P you look at does not have a managing
> position䂪directly assigned, you'll have to walk the org tree upwards until you
> find a managing position assigned to a superior org unit. All assuming you
> (read: your HR dept) use this standard org model in SAP. There's also the
> posibility to create a hierarchy of positions (parallel to the org tree the
> positions are linked to) and then you also have different relationships for
> line reporting and supervision... so depending on where you look and how you
> define "manager" you might get different results, all off the same SAP
> system... it's fun, though! 😉


And what is the Manager holds two positions? Or the person of interest
holds two partial positions?

SAP is crazy this way. It WILL drive you mad.

And we have not even mentioned future dated events and all the pain that
brings in. (Like tons and tons of pain).

SAP is the hardest driver, bar none. Would you agree Lothar?



0 Likes
Knowledge Partner
Knowledge Partner

Re: few attributes are not readable from sap hr idoc

Geoffrey Carman wrote:

> And we have not even mentioned future dated events and all the pain that
> brings in. (Like tons and tons of pain).


I tend to ignore the SAP shim's future event handling feature completely and
write the full timeline of each attribute to the ID Vault whenever an IDoc is
processed. So disable future IDocs and enable propcessing history and future
values, store all values you get from an IDoc together with their validity in
Edir. Then roll your own stuff to determine the currently valid value for each
target attribute from it's timeline and find a scalable way to evaluate and
update the whole data set in near-realtime.
Once you have such a mechanism in place, synching timelined values from SAP (or
any other timeline enabled HR system I would guess - how are Peoplesoft or
Oracle in that regard?) is almost like synching data from any other app. The
real pain comes from the lack of such a mechanism in IDM out of the box. The
workorder driver is not much relief here, it just adds to the pain,
unfortunately.

> SAP is the hardest driver, bar none. Would you agree Lothar?


Absolutely. IDocs are just the weirdest text file format imaginable to start
with, and the fact that you cannot query directly for most of the data you need
to sync and that you usually get an event/IDoc when someone *plans* a change in
SAP but *not* when the change actually takes place require a completely
different approach than most apps. And then there are those 100s of ways to set
up and use a SAP System and the HR guys are usually very restrictive with
access to their systems and data, plus there's virtually no documentation being
freely availble on the net. Did I mention personnel actions/reasons? Yes, the
hardest fun in IDM.
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: few attributes are not readable from sap hr idoc

On Mon, 23 Jun 2014 19:30:38 +0000, Lothar Haeger wrote:

> Once you have such a mechanism in place, synching timelined values from
> SAP (or any other timeline enabled HR system I would guess - how are
> Peoplesoft or Oracle in that regard?) is almost like synching data from
> any other app.


I can't speak to all PeopleSoft deployments, as the way each one works is
going to depend on how the PeopleSoft developers involved make the
Component Interface (CI) work. Ours, here, kicks out the current
information and future dated information all in one XML doc, with
different attribute names so that I can distinguish current from future.

So I get something like:

<modify-attr attr-name="EMPL_STATUS">
<remove-all-values/>
<add-value>
<value>A</value>
</add-value>
</modify-attr>

<modify-attr attr-name="DEPT_ID">
<remove-all-values/>
<add-value>
<value>FM00000</value>
</add-value>
</modify-attr>

<modify-attr attr-name="FJB_EFFDT">
<remove-all-values/>
<add-value>
<value>07/01/2014</value>
</add-value>
</modify-attr>

<modify-attr attr-name="FJB_EMPL_STATUS">
<remove-all-values/>
<add-value>
<value>A</value>
</add-value>
</modify-attr>

<modify-attr attr-name="FJB_DEPTID">
<remove-all-values/>
<add-value>
<value>FB00000</value>
</add-value>
</modify-attr>

which is relatively easy to pick apart in policy. If there's current job
info, that's really all I care about. If there's no current job info,
then I want the future dated job info. On the effective date, I'll get
another event with what was the future dated job as the current job.

But since the CI is custom PeopleSoft code, any other deployment other
than ours here could work very differently.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.