<?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: seperate client for ABAP dev in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/seperate-client-for-abap-dev/m-p/4565536#M1077474</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Kumar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is exactly the point why some customers have separated ABAP development and customizing into different clients on the DEV system.&lt;/P&gt;&lt;P&gt;The ABAP developers may disturb the work of the people doing the customizing yet customizing changes will not affect immediately the ABAP developers.&lt;/P&gt;&lt;P&gt;Of course customizing and ABAP development have to "meet" in the same client of the QAS system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another advantage of separating ABAP development and customizing into different clients is "segregation of duties": This way you can (partially) prevent ABAP developers from doing customizing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: I have seen this kind of segregation in the system landscape of one of the biggest customers of SAP Switzerland.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Oct 2008 10:55:12 GMT</pubDate>
    <dc:creator>uwe_schieferstein</dc:creator>
    <dc:date>2008-10-02T10:55:12Z</dc:date>
    <item>
      <title>seperate client for ABAP dev</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/seperate-client-for-abap-dev/m-p/4565534#M1077472</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can anyone pls list out the advantages to have abap dev client seperated with the configuration client?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Oct 2008 08:49:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/seperate-client-for-abap-dev/m-p/4565534#M1077472</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-10-02T08:49:00Z</dc:date>
    </item>
    <item>
      <title>Re: seperate client for ABAP dev</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/seperate-client-for-abap-dev/m-p/4565535#M1077473</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I see no pros::&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;how will you develope a program in a client with different customizing to QA / PROD ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Oct 2008 10:29:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/seperate-client-for-abap-dev/m-p/4565535#M1077473</guid>
      <dc:creator>andreas_mann3</dc:creator>
      <dc:date>2008-10-02T10:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: seperate client for ABAP dev</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/seperate-client-for-abap-dev/m-p/4565536#M1077474</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Kumar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is exactly the point why some customers have separated ABAP development and customizing into different clients on the DEV system.&lt;/P&gt;&lt;P&gt;The ABAP developers may disturb the work of the people doing the customizing yet customizing changes will not affect immediately the ABAP developers.&lt;/P&gt;&lt;P&gt;Of course customizing and ABAP development have to "meet" in the same client of the QAS system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another advantage of separating ABAP development and customizing into different clients is "segregation of duties": This way you can (partially) prevent ABAP developers from doing customizing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: I have seen this kind of segregation in the system landscape of one of the biggest customers of SAP Switzerland.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Oct 2008 10:55:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/seperate-client-for-abap-dev/m-p/4565536#M1077474</guid>
      <dc:creator>uwe_schieferstein</dc:creator>
      <dc:date>2008-10-02T10:55:12Z</dc:date>
    </item>
    <item>
      <title>Re: seperate client for ABAP dev</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/seperate-client-for-abap-dev/m-p/4565537#M1077475</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Oct 2008 08:10:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/seperate-client-for-abap-dev/m-p/4565537#M1077475</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-10-03T08:10:49Z</dc:date>
    </item>
  </channel>
</rss>

