<?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 Distributing Master Data in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/distributing-master-data/m-p/6713356#M1454105</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When we create master data, how ALE gets triggered internally.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Mar 2010 07:45:46 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-03-02T07:45:46Z</dc:date>
    <item>
      <title>Distributing Master Data</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/distributing-master-data/m-p/6713356#M1454105</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When we create master data, how ALE gets triggered internally.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Mar 2010 07:45:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/distributing-master-data/m-p/6713356#M1454105</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-03-02T07:45:46Z</dc:date>
    </item>
    <item>
      <title>Re: Distributing Master Data</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/distributing-master-data/m-p/6713357#M1454106</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;Will you please elaborate your question? I can't understand what exactly you want to know. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But what i guessur answer as below. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Change Pointer: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ALE provides powerful capabilities to capture changes occurring to master data using Change pointers. These R/3 objects mark changes to SAP master data. ALE configuration facilitates the relation between Change Document objects and change pointers. This feature can be used to keep two or more systems synchronized with respect to master data. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In conclusion, ALE is a simple add-on application that relies heavily on the customizable distribution scenario. Every time a data object (described in an ALE scenario) changes, an IDoc is triggered. Application Link and Enabling (ALE) is one of the most common and effective technologies available for distributed SAP systems. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Abhijit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Mar 2010 07:29:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/distributing-master-data/m-p/6713357#M1454106</guid>
      <dc:creator>Abhijit74</dc:creator>
      <dc:date>2010-03-03T07:29:31Z</dc:date>
    </item>
  </channel>
</rss>

