topic Re: IDOC Triggering in Application Development and Automation Discussions

IDOC Triggering

Former Member — Mon, 02 Feb 2009 05:44:39 GMT

Moderator message: Do not post the same question in more than one forum. Duplicates rejected.

Hi All,

My Requirement is to send HR data from system 'A' to system 'B' and then from system 'B' to system 'A'.

1) From System 'A' to system 'B', i have to send infotype 0, 1, 2, 3, 7, 17, and 105.

2) From system 'B' to system 'A', i have to send only Infotype 105.

When i am sending data from system 'A' to system 'B' i have to generate internal range personel number in system 'B'. i should not use same personal number which is coming from system 'A'.

So to do this I used FM NUMBER_GET_NEXT in exit EXIT_SAPLRHA0_003 to generate internal personal number, and changed personel number in Idoc data. and it worked fine.

I am storing system 'A' personal number in Infotype 105 of system 'B'. and i have to send only 105 data to system A

immediately after creating internal personal number in System 'B' it has to generate an another idoc to send data to system A with the newly created internal personal number to store in infotype 105 of the systsm 'A'.

but in system 'B' through BD21 it is not generating idoc when data is updated through idoc from system 'A'. where as i am able to create idoc through BD21 when i change manually.

so i guess change pointers are not updating when the hr data created in system 'B' through idoc from System 'A' , but manually it is okay.

could you please help me to solve this problem.. i need to generate idoc immediatly in system 'B' to send IT0105 data to system 'A' after susccess full execution of IDOC from system 'A' to system 'B'

Thanks in advance,

prvn

Edited by: Matt on Feb 2, 2009 7:38 AM

Re: IDOC Triggering

matt — Mon, 02 Feb 2009 06:38:59 GMT

Do not post the same question in more than one forum.

Re: IDOC Triggering

Former Member — Mon, 02 Feb 2009 10:21:11 GMT

Try the following transactions related to change pointers:

1. BD61-Acitvate or Deactivate change pointers in the system. Check the Check box in sender system. We donu2019t have to do any thing in the Receive system.

2. BD50- Add message type, and select the check box ACTIVE. Then the change pointers are triggered for this particular message type.

3. BD52- We can specify the fields that are changed. Select the Object class(Material, Vendor, Customeru2026), then add fields that are to be send .

4.BD21- RBDMIDOC-program. To send the changed master data. Mater BDCP2 ( BDCP, BDCPS, Old version). Give the message type & execute.Check WE05/WE02 check the Idoc status.

5.BD60- CHANGE_POINTERS_READ-Function module. To process the Idoc. Create the Idocs with the changes in the master data.

6.BD22-Maintain or remove unwanted change pointes. We need to delete the unwanted change pointes. Because they recrod every change & send to other systems.

Kalyani T

Re: IDOC Triggering

Former Member — Mon, 02 Feb 2009 12:41:12 GMT

Hi prvn,

Use transaction SWEHR2 to link your outbound program to infotype update.

Cheers

Sarfaraz

Re: IDOC Triggering

Former Member — Tue, 03 Feb 2009 20:01:05 GMT

Hi Sarfaraz,

Could you please guide me how to link outbound program to infotype update.

I am updating the infotypes through inbound idoc. and again it has to generate an idoc.

Thanks,

Praveen