IDOC_INPUT_HRMD, it posts the document but does not update the Infotypes

[Former Member]

Hi,

I am trying to trigger the IDoc Type 'HRMD_A06'. This Idoc was posted successfully, with the status as '53' (inbound IDoc). The Processing Function Module is IDOC_INPUT_HRMD for the IDoc "HRMD_A06". However the infotypes are not updated. The infotypes I am trying to update are 0000,0001,0002,0006, & 0008.

If someone has a solution for this issue. Kindly let me know.

Regards,

Narun

[Former Member · Accepted solution]

Hi Srinivas,

Actually IDOC_INPUT_HRMD should update the records in the other end.

That too u got the status 53. Check once again through WE19 by giving the IDOC as input (Test IDOC).

[Former Member · Accepted solution]

Hi Eswar,

I have triggered the IDoc more than once but the ned result was that the infotypes were not updated. Can you suggest me any other workaround.

Thanks & Regards,

Narun

[Former Member · Accepted solution]

Hi Srinu...

Yesterday i have tried the same. But its getting updated.

I dont understand where its going wrong in your side.

Try to debug in WE19 and check whether the data is updating or whats happening in debug.

If not copy the FM and make Custom FM and use the HR_INFOTYPE_OPERATION to update INFOTYPES.

Thanks

Eswar

[Former Member · Accepted solution]

Hi Eswar,

Thanks for your input. Do you want me to use the 'HR_INFOTYPE_OPERATION' function module instead of the FM 'RH_IDOC_OBJECTS_SAVE'(This FM is used in the Standard FM 'IDOC_INPUT_HRMD'. Also, if you can let me know the parameters you are passing in the IDoc, so that I can also replicate the same.

Thanks & Regards,

Narun Srinivas

[Former Member · Accepted solution]

Hi Srinu,

Again....

Whats happening in Debug ???

Just clone the FM as it is and use the FM HR_INFOTYPE_OPERATION instead of other.

Parameters:

The following code is for infotype 15 inside custom FM which i have done. u can use for ref.

CALL FUNCTION 'ENQUEUE_EPPRELE'

EXPORTING

pernr = l_wa_p0015-pernr

EXCEPTIONS

foreign_lock = 1

system_failure = 2

OTHERS = 3.

IF sy-subrc = 0.

CALL FUNCTION 'HR_INFOTYPE_OPERATION'

EXPORTING

INFTY = c_0015

NUMBER = l_wa_p0015-pernr

SUBTYPE = l_wa_p0015-subty

• OBJECTID =

• LOCKINDICATOR =

VALIDITYEND = l_wa_p0015-begda

VALIDITYBEGIN = l_wa_p0015-endda

• RECORDNUMBER =

RECORD = l_wa_p0015

OPERATION = c_ins1

TCLAS = c_a

DIALOG_MODE = '0'

• NOCOMMIT =

• VIEW_IDENTIFIER =

• SECONDARY_RECORD =

IMPORTING

RETURN = l_i_return .

• KEY =

.

• To dequeue the selected employee

CALL FUNCTION 'DEQUEUE_EPPRELE'

EXPORTING

pernr = l_wa_p0015-pernr.

[Former Member · Accepted solution]

Hi Eswar,

That was of great help for me. However, as u said u were able to post the Infotypes using the standard FM. I believe there is something which I am missing in the IDoc segment. Below I am listing all the Segments & parameters that I am using in the IDoc HRMD_A06.

Segment- E1PLOGI

Parameters - Plan Version = '01'.

Object ID = '92000033'.

Operation = 'I'.

Segment- E1PORIG

Parameters - PLVAR = '01'.

OBJID = '92000033'.

Segment- E1PITYP

Parameters - PLVAR = '01'.

OBJID = '92000033'.

ENDDA = '12/27/2005'.

BEGDA = '12/29/2005'.

Segment- E1P0000

Parameters - Personnel No. = '92000033'.

Infotype = '0000'.

Start Date = '12/27/2005'.

Action Type = '01'.

Employment = '3'.

The above the segments and the fields that I am populating in the IDoc HRMD_A06. Kindly let me know if the above information is correct to process the IDoc.

Thanks & Regards,

Narun Srinivas

[Former Member · Accepted solution]

Hi Srinu,

I hope u are missing the field OTYPE (i.e P ) in the first three segments. ( E1PLOGI, E1PORIG, E1PITYP )

Try to fill that.

Good luck

eswar

[Former Member · Accepted solution]

Hi Eswar,

I triggered the IDoc again with the values in the field OTYPE for the three segments 'E1PLOGI, E1PORIG, E1PITYP' but of not much help. It never updated. Is it related to configuration or is it related to some process which I am missing.

Thanks & Regards,

Narun Srinivas

[Former Member · Accepted solution]

Hi Srinu,

Nothing u are missing from your end. Its really strange.

That too you are getting the status 53.

Can u tell me from where u are getting the data (The other system ).

Srinu... we have to work on this to close.

Thanks

Eswar

[Former Member · Accepted solution]

Hi Eswar,

I am triggering the IDoc from the same SAP server. I think there is something that I am missing out. Sure we would have to close this issue. Its really a gud experience for me and I would want to see this issue close with a solution.

Thanks & Regards,

Narun

[Former Member · Accepted solution]

Hi,

Means you are transferring the data between the clients.

lets take (transfer data from 600 to 002 clients).

Hope u know about the process..but still,

1) Check whether u created two LS and assigned correctly to the clients

2) RFC destination, port & partner profiles

3) In partner profiles check the inbound and outbound parameters in both clients.

4) Distribution model and then hire an employee in 600 client (or u can take already created one).

5) try to send through PFAL by passing required parameters.

6) now check the status (surely u will get 03) in 600 side.

7) check the status in 002 client (u will get the status 53---if u gets the status 64,run the RBDAPP01 program by giving the IDOC..this time surely it returns the status 53).

😎 now check that entries are updated in PA0000 table (002 client side).

I know that u already got the staus 53. But check it once.

In my case 600 (sending system)

002 (Receiving system).

All the BEST.

Thanks

Eswar

[Former Member · Accepted solution]

Hi Eswar,

Thanks a lot for being so kind and your helpful suggestion. However, there is no success. I followed the steps you had mentioned in your earlier threads, however the infotypes are not updated.

Let me know if there is anything you could help me more on this issue.

Thanks & Regards,

Narun Srinivas

[Former Member · Accepted solution]

Hi,

did you trigger the IDOC with an custom report?

If you do so thread

may give you a hint to the right IDoc structure.

Regards

Bernd

[Former Member]

hi

did you find any solution, i am getting the same error

any help would be appreciated

cheers

[Former Member]

What you are passing the operation field on the E1PLOGI segment? If you do 'I' it will delete all existing infotypes and recreate the employee from the new idoc. If you pass a 'U' if will read the begin and end date for each infotype header segment from E1PTYP and if it overlaps it will attempt to delimit the existing record and create the new one. You need to do the date and time constraint validation in advance.

[Former Member]

Hi All,

I got the info from Suresh that it wil do the delimition, but we need to give the Operation Parameter as "LIS9".

Can you please tell to which parameter I should map this value or if you have any sample code, appreciate your help.

Thanks,

bhavani

[Former Member]

Hi ALl,

I am also using the same function mopdule of rthe inbound IDOC I received from BIZTALK System.

I am performing some logic after recieving the values of the IDOC and changing the IDOC data as per my requirement and if there is an existing record for the same PERNR it should delimit the existing one and inserts the new one.

Dows it do this part, Because when I checked the Function Module it is direlty iserting the record and there is part of the code I can see that it delimits the record also.

Did Any body tested this FM on delimition part?

Thanks,

Bhavani

[Former Member]

Hi Bhavani,

I never tried the delimit part..but u can do this while updaing the data..better use BDC method in this case.

Thanks

Eswar

[suresh_datti]

Hi,

There is no need for a BDC.. I have used this function module to delimit infotypes.. just use 'LIS9' as the operation parameter.. it works perfect..

Regards,

Suresh Datti

[Former Member]

Hi Suresh,

Thanks a lot for this info, nut can you please tell me what is Operation parameter? wil it be there in any of the IDOC segments?

Regards,

Bhavani