topic Re: about change pointers in ale in Application Development and Automation Discussions

about change pointers in ale

Former Member — Thu, 01 Mar 2007 10:29:52 GMT

hi,

i have finished ale customization and processed idoc succesfully!

now i would like to send idoc using change pointers,

i know 3 tranasactin codes bd50,bd,......

i ahve activated change pointers ,messae tyepes,then my doubt is..

If we create a new material in outbound side will it go directly into inbound side

i mean will it need to run bd 10 or not?

i want backgorund schedulilng using change pointer...

could anybody give me some suggetions..

Re: about change pointers in ale

Former Member — Thu, 01 Mar 2007 11:27:00 GMT

Isn't that set up using transaction BD21? if i remember correctly if you schedule that one it will do the job!

Message was edited by:

Stellan Flinkfeldt

Re: about change pointers in ale

Former Member — Thu, 01 Mar 2007 11:28:16 GMT

im doing background job schdule using sm35

Re: about change pointers in ale

Former Member — Thu, 01 Mar 2007 11:29:05 GMT

Note the changes made on the transaction(i guessed on the first ones)

Re: about change pointers in ale

former_member187255 — Thu, 01 Mar 2007 14:51:20 GMT

As my understanding ur done with activating and configuring the change pointers and now u want to send the idoc to the other system.... so you need to configure the partner profile in WE20 as outbound, once ur done with configuration then you can schedule a batch job for the report RBDMIDOC(BD21) ...once you are done these then you can see the idocs in WE02.

Regards.

Re: about change pointers in ale

Former Member — Thu, 01 Mar 2007 17:49:55 GMT

Hi,

After completing the configuration of ale as well as for change pointers, v have to schedule the job. For that v have to go to either SM36 to create a job or SALE --> click on shcedule job.

There is no need for going to that BD10. consider this example, u r changing the material description for a material which is alreading existing using MM02. These changes are stored in the change documents. Change pointers in turn keep track of the changes. As per ur start condition specified in the job description(Background) that job will be automatically started and the material is transferred to the other system as per ur configuration.

First of all clear with the definition of the change pointers.

change pointers techinque is based on the change document technique which keep track of the changes made in the key documents in the sap.

Regards...

Arun.

Reward points if it helps.