How does the saphr driver work with future-date feature?

How does the saphr driver work with future-date feature?
By checking BEGDA and ENDDA? But when my driver was dealing with a
extension infotype,unexpected thing happened!
With trace log as belowing:

-------------------------------TRACE
LOG-----------------------------------------------

[03/29/12 10:12:46.473]:SAP-HR PT:ParseIDoc: File
'/Idoc/O_200_0000000000227038' renamed to
'/Idoc/O_200_0000000000227038.proc' successfully.
[03/29/12 10:12:46.474]:SAP-HR PT:ParseIDoc: INPUTHASH contains
relationships. Key: S51000730, Type: RELATIONSHIPS, Elements: 2
[03/29/12 10:12:46.476]:SAP-HR PT:ParseIDoc: Number of elements in
idocData: 1
[03/29/12 10:12:46.478]:SAP-HR PT:SAPPublicationShim: Received '1' docs
from ParseIDoc.
[03/29/12 10:12:46.479]:SAP-HR PT:SAPPublicationShim: Comm add value
check: 'P1000:STEXT:none:98:40'
[03/29/12 10:12:46.480]:SAP-HR PT:SAPPublicationShim: field value:
'yangbx1'
[03/29/12 10:12:46.481]:SAP-HR PT:SAPPublicationShim: begdate:
'20110901'
[03/29/12 10:12:46.482]:SAP-HR PT:SAPPublicationShim: enddate:
'99991231'
[03/29/12 10:12:46.483]:SAP-HR PT:SAPPublicationShim: SEQNR:
'000'
[03/29/12 10:12:46.484]:SAP-HR PT:SAPPublicationShim: Comm add value
check: 'P1000:SHORT:none:86:12'
[03/29/12 10:12:46.486]:SAP-HR PT:SAPPublicationShim: field value:
'yangbx1'
[03/29/12 10:12:46.487]:SAP-HR PT:SAPPublicationShim: begdate:
'20110901'
[03/29/12 10:12:46.488]:SAP-HR PT:SAPPublicationShim: enddate:
'99991231'
[03/29/12 10:12:46.489]:SAP-HR PT:SAPPublicationShim: SEQNR:
'000'
[03/29/12 10:12:46.489]:SAP-HR PT:SAPPublicationShim:* Comm add value
check: 'P9117:ENDDA:none:34:8'
[03/29/12 10:12:46.490]:SAP-HR PT:SAPPublicationShim: field value:
'99991231'
[03/29/12 10:12:46.491]:SAP-HR PT:SAPPublicationShim: begdate:
'01109019'
[03/29/12 10:12:46.492]:SAP-HR PT:SAPPublicationShim: enddate: '
1 2'
[03/29/12 10:12:46.493]:SAP-HR PT:SAPPublicationShim: SEQNR:
'999'*
[03/29/12 10:12:46.494]:SAP-HR PT:
<nds dtdversion="1.0" ndsversion="8.5">
<source>
<product build="20090520_004316" instance="SAP-HR"
version="3.5.4">DirXML Driver for SAP/HR</product>
<contact>Novell, Inc.</contact>
</source>
<input xmlns:sapshim="http://www.novell.com/dirxml/drivers/SAPShim">
<modify class-name="S"
event-id="SAP-HR:O_200_0000000000227038:S+51000730" src-dn="51000730"
timestamp="20120329">
<association>51000730</association>
<modify-attr attr-name="P1000:STEXT:none:98:40">
<remove-all-values/>
<add-value>
<value seqnr="000"
timestamp="20110901-99991231">yangbx1</value>
</add-value>
</modify-attr>
<modify-attr attr-name="P1000:SHORT:none:86:12">
<remove-all-values/>
<add-value>
<value seqnr="000"
timestamp="20110901-99991231">yangbx1</value>
</add-value>
</modify-attr>
* <modify-attr attr-name="P9117:ENDDA:none:34:8">
<remove-all-values/>
<add-value>
<value seqnr="999" timestamp="01109019- 1
2">99991231</value>
</add-value>
</modify-attr>*
</modify>
</input>
</nds>

-------------------------------TRACE
LOG-----------------------------------------------


Look at the highlighted text with RED: Obviously the driver get wrong
begdate and enddate values. and this will cause the future-date feature
down.
So I especially make a attr mapping with enddate to get value of
"enddate ", and "99991231" returned(look at yellow text).
In the HRMD_A07.meta file ,enddate is 'P9117:ENDDA:none:34:8'.
This makes me so confused, any one can tell me something about this?


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