topic Re: ale issue in Application Development and Automation Discussions

ale issue

Former Member — Tue, 09 Jun 2009 08:33:04 GMT

Hi All,

we have moved the data of an org unit into separate system through ALE using PFAL transaction code.

After this we have activated the change pointers for Message type HRMD_A. Now, the data is passing correctly but whenever we are creating the new positions or new org units in the system, it is not passing to the reciever system. What could be wrong?

Please suggest.

Regards,

Re: ale issue

jaideepsharma — Tue, 09 Jun 2009 09:27:29 GMT

Hi,

Check if the change pointers are activated for the respective fields and message type in the system.

Please go through BD50,BD52 tcodes. Also, check the receivers configuration in partner profiles and/or distribution model.

KR Jaideep,

Re: ale issue

Former Member — Tue, 09 Jun 2009 10:49:29 GMT

Hello,

I have already done the appropriate settings for BD50 - ticked the checkbox for message type HRMD_A.

For BD52, I have chosen message type as HRMD_A and fields as below:

HR_IT1000 HRP1000 OBJID

HR_IT1000 HRP1000 SHORT

HR_IT1001 HRP1001 OBJID.

The idocs are not being generated if i go to PO10 and create org unit or if I go to PO13 and create a position. However if I update any infotype of the employee, the idocs get created. I have only the above three mentioned entries in BD52 for hrmd_a.

Please suggest.

Regards

Re: ale issue

Former Member — Tue, 09 Jun 2009 10:49:54 GMT

I think change pointers distribute the changes to already created master data. So for new master data , I have doubts that change pointers will take care of it.

However you can analyse change pointers using transaction BD21 or report RBDMIDOC and flagged as processed. See is this can send the new records?

Cheers,

Disha

Re: ale issue

Former Member — Tue, 09 Jun 2009 11:25:35 GMT

Hello Disha,

I believe it is not like that because if i m doing a joining of any employee , then also the data is sent to the other system through idocs by change pointers. Its only that ew position or org unit is not going.

In other words, new O or new S is not going but new P is always going to the other system.

Regards,

Ribhu

Re: ale issue

Former Member — Tue, 09 Jun 2009 11:38:30 GMT

OK, so may be you can try debugging with the report and see where the issue is...

Re: ale issue

jaideepsharma — Tue, 09 Jun 2009 12:46:38 GMT

Hi,

Just one thing to bring into your notice. Every field is not capable enough to send an Idoc from SAP.

For instance material type is one such field which if you change in material master then it will not create an Idoc. We had a similar problem in our project. We then created a custom report and manually created change pointer for another fields eg. net weight. Then we scheduled standard report which then takes all the changes of material as an Idoc to another system. The Idoc also had changes in material types done. Check if the field you are changing is capable enough to send the Idoc from the system.

Also, check if a change pointer is created for the same field in BDCP and BDCPS tables.

KR Jaideep,

Re: ale issue

Former Member — Wed, 10 Jun 2009 04:39:21 GMT

Hi,

Check Change document is getting created in tables CDHDR, CHPOS, BDCP and BDCPS nor not.

Thanks,

Asit Purbey.