<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: SAP ABAP: Dead or alive?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/sap-watch/sap-abap-dead-or-alive/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/sap-watch/sap-abap-dead-or-alive/</link>
	<description>A SearchSAP.com blog</description>
	<pubDate>Sat, 28 Nov 2009 15:48:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Harsha jadhav</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/sap-abap-dead-or-alive/#comment-623</link>
		<dc:creator>Harsha jadhav</dc:creator>
		<pubDate>Fri, 16 Nov 2007 15:48:01 +0000</pubDate>
		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2007/11/14/sap_abap_dead_or_alive/#comment-623</guid>
		<description>It is of my opinion that ABAP is very alive and why does it not matter to the outer world. If I am a customer and if I am going to use SAP for my work I would obviously prefer people who know SAP better. 
When it comes to this question whether or not if anything is to be newly written in ABAP would surely be a question from the TCO point of view as JAVA is still not as close to SAP as ABAP (I hope this is picked in the right way). Hence any new SAP implementation would not be possible without a ABAP programmer at site. Hence it is up to the JAVA community who would want to be faithful to SAP to learn the depths of the SAP application and architecture instead of putting lots of bespoke things at the helm of the customer from just a programming language perspective. Having said that it is now to the old and large ABAP developer community to clinch upon the newest offerings from SAP to fortify its faith and nearness and hence get polished.</description>
		<content:encoded><![CDATA[<p>It is of my opinion that ABAP is very alive and why does it not matter to the outer world. If I am a customer and if I am going to use SAP for my work I would obviously prefer people who know SAP better.<br />
When it comes to this question whether or not if anything is to be newly written in ABAP would surely be a question from the TCO point of view as JAVA is still not as close to SAP as ABAP (I hope this is picked in the right way). Hence any new SAP implementation would not be possible without a ABAP programmer at site. Hence it is up to the JAVA community who would want to be faithful to SAP to learn the depths of the SAP application and architecture instead of putting lots of bespoke things at the helm of the customer from just a programming language perspective. Having said that it is now to the old and large ABAP developer community to clinch upon the newest offerings from SAP to fortify its faith and nearness and hence get polished.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ABAPer with Java Flavor</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/sap-abap-dead-or-alive/#comment-622</link>
		<dc:creator>ABAPer with Java Flavor</dc:creator>
		<pubDate>Thu, 15 Nov 2007 17:29:37 +0000</pubDate>
		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2007/11/14/sap_abap_dead_or_alive/#comment-622</guid>
		<description>SAP is implementing new technologies in all the new areas as it see to it fits.  For the new emerging SOA, Web Services, XI and Java/NWDI, SAP has made significant improvements for the SAP SW.  Also it's not just Java but there's also .net as well. Which means for the SAP to work seamlessly among all the alphabet soup of technology the technologies SAP needs to develop these new areas.  But for the core modules, SD, CRM, SCM, there's nothing better than the ABAP since the BASIS layer is built up on this ABAP language.  For example to make SAP Ecommerce more appealling and robust to it's customer, J2EE has been chosen which is one of the core standard as well as the .net so SAP is going that way but SAP also built BSP so ABAPer can also build it's own Ecommerce or HTTP thin client applications.  Only one thing that seems to lagging is the way all this new technology communicates with ABAP backend; RFC needs to be improved and it shouldn't be so much depend on the performance of ERP Backend work load.</description>
		<content:encoded><![CDATA[<p>SAP is implementing new technologies in all the new areas as it see to it fits.  For the new emerging SOA, Web Services, XI and Java/NWDI, SAP has made significant improvements for the SAP SW.  Also it&#8217;s not just Java but there&#8217;s also .net as well. Which means for the SAP to work seamlessly among all the alphabet soup of technology the technologies SAP needs to develop these new areas.  But for the core modules, SD, CRM, SCM, there&#8217;s nothing better than the ABAP since the BASIS layer is built up on this ABAP language.  For example to make SAP Ecommerce more appealling and robust to it&#8217;s customer, J2EE has been chosen which is one of the core standard as well as the .net so SAP is going that way but SAP also built BSP so ABAPer can also build it&#8217;s own Ecommerce or HTTP thin client applications.  Only one thing that seems to lagging is the way all this new technology communicates with ABAP backend; RFC needs to be improved and it shouldn&#8217;t be so much depend on the performance of ERP Backend work load.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->