Highlighted
Absent Member.
Absent Member.
213 views

I have some trouble with sap-hr driver feature future-dating


Hi !
A unexpected situation meet when I use sap-hr driver(Publish-only) to
sync from idoc.
Firstly let me show you the content of idoc :
EDI_DC40 2000000000000225190700 3012 HRMD_A07
ZRMD_A07 HRMD_A
SAPHHD LS HHDCLNT200
SAPHR LS IDMSYSTEM

20120227080919

20120227080917
E2PLOGI001 20000000000002251900000090000000201P
01120351 I
E2PITYP001 20000000000002251900000100000090301P
011203510000 1800010199991231
E2P0000001
200000000000022519000001100001004011203510000
999912312012020500020120203HAIER_SUNP 1002131
E2PITYP001 20000000000002251900000140000090301P
011203510002 1800010199991231X
E2Q0002002
200000000000022519000001600001505011203510002 9999123119880201000





E2PITYP001 20000000000002251900000170000090301P
01120351018501 1800010199991231
E2P0185001
20000000000002251900000180000170401120351018501
999912312012020500020120203HAIER_SUNP
01371002198802014521
0000000000000000
21 00000000000000000 01000000000

Idoc publish time: 20120203d
Over the idoc we can find some messages below:
Object type is : P (match to User in eDir)
object modify time: 20120203 (marked with bold)
BEGDA-ENDDA: 20120205 -99991231(marked wth bold and red BG color)

The driver configured as “Publisher-only” and "future-dated Event
Handling" option configured as "Publish on a Future Date".

After SAP-HR driver dealed with the idoc above,user with id 01120351
was created in eDirectory(identity vault) on 20120203(YYYY-MM-dd).
But actually I want the driver dealing with it on 20120203 and turning
it to be O_****20120205.futr file,then create the user(01120351) on
20120205.
The result is that O_****20120205.futr file has been generated but the
user also has been created.

So summarily my question is:
How can the driver create the user(01120351) on its BEGDA (20120205)
but not the idoc publish date(20120203)?

Any idea welcome! thanks.


--
wxcn
------------------------------------------------------------------------
wxcn's Profile: http://forums.novell.com/member.php?userid=6738
View this thread: http://forums.novell.com/showthread.php?t=452653

Labels (1)
0 Likes
2 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: I have some trouble with sap-hr driver feature future-dating

On 2/27/2012 2:06 AM, wxcn wrote:
>
> Hi !
> A unexpected situation meet when I use sap-hr driver(Publish-only) to
> sync from idoc.
> Firstly let me show you the content of idoc :
> EDI_DC40 2000000000000225190700 3012 HRMD_A07
> ZRMD_A07 HRMD_A
> SAPHHD LS HHDCLNT200
> SAPHR LS IDMSYSTEM
>
> 20120227080919
>
> 20120227080917
> E2PLOGI001 20000000000002251900000090000000201P
> 01120351 I
> E2PITYP001 20000000000002251900000100000090301P
> 011203510000 1800010199991231
> E2P0000001
> 200000000000022519000001100001004011203510000
> 999912312012020500020120203HAIER_SUNP 1002131
> E2PITYP001 20000000000002251900000140000090301P
> 011203510002 1800010199991231X
> E2Q0002002
> 200000000000022519000001600001505011203510002 9999123119880201000
>
>
>
>
>
> E2PITYP001 20000000000002251900000170000090301P
> 01120351018501 1800010199991231
> E2P0185001
> 20000000000002251900000180000170401120351018501
> 999912312012020500020120203HAIER_SUNP
> 01371002198802014521
> 0000000000000000
> 21 00000000000000000 01000000000
>
> Idoc publish time: 20120203d
> Over the idoc we can find some messages below:
> Object type is : P (match to User in eDir)
> object modify time: 20120203 (marked with bold)
> BEGDA-ENDDA: 20120205 -99991231(marked wth bold and red BG color)
>
> The driver configured as �Publisher-only� and "future-dated Event
> Handling" option configured as "Publish on a Future Date".
>
> After SAP-HR driver dealed with the idoc above,user with id 01120351
> was created in eDirectory(identity vault) on 20120203(YYYY-MM-dd).
> But actually I want the driver dealing with it on 20120203 and turning
> it to be O_****20120205.futr file,then create the user(01120351) on
> 20120205.
> The result is that O_****20120205.futr file has been generated but the
> user also has been created.


Once you turn on Publish on Future date, what you describe should happen.

Watch the RL trace as it reads the iDOC, realizes it is future dated and
show us that trace?

Then paste some of the engine side trace showing the user being
processed. Start at the beginning, which would show how it gets into
the channel.


>
> So summarily my question is:
> How can the driver create the user(01120351) on its BEGDA (20120205)
> but not the idoc publish date(20120203)?
>
> Any idea welcome! thanks.
>
>


0 Likes
Highlighted
Absent Member.
Absent Member.

Re: I have some trouble with sap-hr driver feature future-dating


geoffc, thanks for you reply,you are always so kind.But I 'm off and can
not get trace log now.
In this case I have not use RL and just configured the sap-hr driver to
read idoc file from a local directory on engine side server.
I can't decide when the driver to create the user int to edir.It looks
like a feature of it and does not matter of the BEGDA and ENDDA in a add
event.


--
wxcn
------------------------------------------------------------------------
wxcn's Profile: http://forums.novell.com/member.php?userid=6738
View this thread: http://forums.novell.com/showthread.php?t=452653

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.