<?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: CHANGEDOCU archiving in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249744#M775841</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Go to transaction SCDO to find the text for OBJECTCLAS values. This will give you an idea about the Functional area.&lt;/P&gt;&lt;P&gt;Further you can also list the affected tables for an OBJECTCLAS by choosing Change doc. object -&amp;gt; Display&lt;/P&gt;&lt;P&gt;By looking at the table list you can arrive at the archiving object&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Samanjay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Feb 2008 15:38:21 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-27T15:38:21Z</dc:date>
    <item>
      <title>CHANGEDOCU archiving</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249738#M775835</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have initaited archiving process.We are done with FI_documnt.And now thinking of changedocu.My question is ..is it OK to go ahead with changedocu in the beginning itself or should we wait till other archiving objects are done?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As 'changedocu' archives master change documents from table CDHDR and CDCLS.And other transactional datas from these tables are archived by using appropiate archiving object.So is it advisable to archive master data first and transactional data in the following?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Priya.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2008 18:30:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249738#M775835</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-04T18:30:09Z</dc:date>
    </item>
    <item>
      <title>Re: CHANGEDOCU archiving</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249739#M775836</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For the most part, the change documents are archived WITH the object they belong to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, if you look at archive object MM_MATNR, you will see that when you remove a material master, the change documents for htat material master get deleted as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unless you have specific needs to reduce the number of change document, you may not even want to use the archive object for the change documents themselves. In our case, we have never archived change documents, becuase they get archived with the materila masters, for example.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2008 18:52:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249739#M775836</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-04T18:52:38Z</dc:date>
    </item>
    <item>
      <title>Re: CHANGEDOCU archiving</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249740#M775837</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks David.&lt;/P&gt;&lt;P&gt;We were thinking of doing initially the minimum risk archiving object with minimum business impact and then proceed with others.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2008 19:50:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249740#M775837</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-04T19:50:23Z</dc:date>
    </item>
    <item>
      <title>Re: CHANGEDOCU archiving</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249741#M775838</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;just my 2 cents here, but i dont think change documents ARE minumum risk. the idea of archiving a change document without its corresponding objects is a MAJOR risk, in that the changes are no longer tied to the original object. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;using material masters again, if i archive change documents, i can no longer see these changes when i ask the material master to show me all of its changes. Also, when I DO archive the material, the change documents are NOT THERE, which means that if i need that material retrived from the archive for some reason, i will not get back ALL of the information about it, without knowing where all of the pieces of change document archives are.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;again, just my thoughts on the matter.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2008 20:48:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249741#M775838</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-04T20:48:15Z</dc:date>
    </item>
    <item>
      <title>Re: CHANGEDOCU archiving</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249742#M775839</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thankyou David for your valuable suggestion.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2008 21:05:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249742#M775839</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-04T21:05:07Z</dc:date>
    </item>
    <item>
      <title>Re: CHANGEDOCU archiving</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249743#M775840</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi David,&lt;/P&gt;&lt;P&gt;I agree with you that change documents should be pulled off using the relevant archiving objects.&lt;/P&gt;&lt;P&gt;We're live with many FI, SD and PP objects and the relevant change documents are archived accordingly.&lt;/P&gt;&lt;P&gt;However, does anyone know how to relate a CDHDR OBJECTCLAS with an archiving object (at best) or with a functional area. For example CDHDR-OBJECTCLAS value BANF is associated with PP_ORDER, etc etc.&lt;/P&gt;&lt;P&gt;There are numerous types of OBJECTCLAS and if I can link them to an archiving object then it makes my task easier. If any of the OBJECTCLAS's are NOT linked to an archiving object then I know I could archive them using CHANGEDOCU. The change doc tables are huge and I urgently need to archive as much as I possibly can.&lt;/P&gt;&lt;P&gt;Any info will be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Soyab&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2008 02:03:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249743#M775840</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-27T02:03:33Z</dc:date>
    </item>
    <item>
      <title>Re: CHANGEDOCU archiving</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249744#M775841</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Go to transaction SCDO to find the text for OBJECTCLAS values. This will give you an idea about the Functional area.&lt;/P&gt;&lt;P&gt;Further you can also list the affected tables for an OBJECTCLAS by choosing Change doc. object -&amp;gt; Display&lt;/P&gt;&lt;P&gt;By looking at the table list you can arrive at the archiving object&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Samanjay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2008 15:38:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249744#M775841</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-27T15:38:21Z</dc:date>
    </item>
    <item>
      <title>Re: CHANGEDOCU archiving</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249745#M775842</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Samanjay,&lt;/P&gt;&lt;P&gt;I was already aware of SCDO but it wasn't too useful.&lt;/P&gt;&lt;P&gt;Table TCDOB is a lot more useful in that it lists the object and relevant table.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Soyab&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2008 15:44:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changedocu-archiving/m-p/3249745#M775842</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-27T15:44:47Z</dc:date>
    </item>
  </channel>
</rss>

