<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: regd. change pointers and notifications in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/regd-change-pointers-and-notifications/m-p/1031346#M83904</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I haven't done this in a while, so please check my answer!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) You activate change pointers in general in one transaction (I think it was BD61, but I'm not sure)&lt;/P&gt;&lt;P&gt;2) Then you activate them for certain master data (i. e. material, customer, ...) in another transaction which I don't recall atm.&lt;/P&gt;&lt;P&gt;3) Every time one of those master data objects is changed, the system generates a "change pointer", which you can basically just think of as an entry in a transparent table, which includes the type and key of your master data object (such as e. g. the material number).&lt;/P&gt;&lt;P&gt;4) You plan a background job which will go through those change pointers and which will generate a master IDoc (e. g. MATMASxx) for this data object. The change pointers are then reset (i. e. every item will only be sent once).&lt;/P&gt;&lt;P&gt;5) Depending on your ALE customization this master IDoc will be sent to a remote system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can refine this scenario using quite a bunch of different techniques. One of them is filtering (e. g. only materials with a certain material group, or based on classification etc.). Other options are reducing the Master IDoc, e. g. sending only relevant data instead of the whole master IDoc. There are even a few customer exits, if that doesn't suffice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps (please reward me if it does)!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Joerg&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 09 Oct 2005 08:59:39 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-10-09T08:59:39Z</dc:date>
    <item>
      <title>regd. change pointers and notifications</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regd-change-pointers-and-notifications/m-p/1031345#M83903</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The question might sound a little too broad.&lt;/P&gt;&lt;P&gt;But bear with me...Just give me a brief overview,&lt;/P&gt;&lt;P&gt;of how do I go about using change pointers....&lt;/P&gt;&lt;P&gt;Just correct me if I am wrong.&lt;/P&gt;&lt;P&gt;We create a change document object in the system, or use an existing one. About pointers I am not sure.&lt;/P&gt;&lt;P&gt;Then, through SPRO and ALE we activate the change pointer for some message type. then....??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 08 Oct 2005 14:04:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regd-change-pointers-and-notifications/m-p/1031345#M83903</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-08T14:04:11Z</dc:date>
    </item>
    <item>
      <title>Re: regd. change pointers and notifications</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regd-change-pointers-and-notifications/m-p/1031346#M83904</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I haven't done this in a while, so please check my answer!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) You activate change pointers in general in one transaction (I think it was BD61, but I'm not sure)&lt;/P&gt;&lt;P&gt;2) Then you activate them for certain master data (i. e. material, customer, ...) in another transaction which I don't recall atm.&lt;/P&gt;&lt;P&gt;3) Every time one of those master data objects is changed, the system generates a "change pointer", which you can basically just think of as an entry in a transparent table, which includes the type and key of your master data object (such as e. g. the material number).&lt;/P&gt;&lt;P&gt;4) You plan a background job which will go through those change pointers and which will generate a master IDoc (e. g. MATMASxx) for this data object. The change pointers are then reset (i. e. every item will only be sent once).&lt;/P&gt;&lt;P&gt;5) Depending on your ALE customization this master IDoc will be sent to a remote system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can refine this scenario using quite a bunch of different techniques. One of them is filtering (e. g. only materials with a certain material group, or based on classification etc.). Other options are reducing the Master IDoc, e. g. sending only relevant data instead of the whole master IDoc. There are even a few customer exits, if that doesn't suffice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps (please reward me if it does)!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Joerg&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 09 Oct 2005 08:59:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regd-change-pointers-and-notifications/m-p/1031346#M83904</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-09T08:59:39Z</dc:date>
    </item>
    <item>
      <title>Re: regd. change pointers and notifications</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regd-change-pointers-and-notifications/m-p/1031347#M83905</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have generated an IDOC using a stand alone program.&lt;/P&gt;&lt;P&gt;The idoc shows status as generated. But then when I give the IDOC number in RSEOUT00 it says no idocs are ready for processing. What's is this RSEOUT00 program doing?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Oct 2005 12:17:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regd-change-pointers-and-notifications/m-p/1031347#M83905</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-10T12:17:53Z</dc:date>
    </item>
    <item>
      <title>Re: regd. change pointers and notifications</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regd-change-pointers-and-notifications/m-p/1031348#M83906</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The report will process all IDocs that have a certain status and then send them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is used in conjunction with the radio box "Collect IDocs / Transfer IDocs immediately" in the partner profile.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However - the report is not really connected to the master data repliction you talked about in the previous post...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps (please reward me if it does...)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Joerg&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Oct 2005 12:36:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regd-change-pointers-and-notifications/m-p/1031348#M83906</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-10T12:36:15Z</dc:date>
    </item>
  </channel>
</rss>

