 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SAP Watch &#187; srm</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/sap-watch/tag/srm/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/sap-watch</link>
	<description>A SearchSAP.com blog</description>
	<lastBuildDate>Tue, 21 May 2013 16:52:56 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Solving IDoc problems</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/solving-idoc-problems/</link>
		<comments>http://itknowledgeexchange.techtarget.com/sap-watch/solving-idoc-problems/#comments</comments>
		<pubDate>Thu, 14 Aug 2008 15:13:47 +0000</pubDate>
		<dc:creator>JackDanahy</dc:creator>
				<category><![CDATA[SAP]]></category>
		<category><![CDATA[srm]]></category>

		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2008/08/14/solving-idoc-problems/</guid>
		<description><![CDATA[IDoc is the SAP format in which data pertaining to business transactions gets exchanged.  SAP end users and consultants specializing in supplier relationship management (SRM), procurement, and even application development are frequently exposed to IDocs, which can pose all kinds of technical problems for end users.Recently, we&#8217;ve received a lot of expert tips that can [...]]]></description>
				<content:encoded><![CDATA[<p>IDoc is the SAP format in which data pertaining to business transactions gets exchanged.  SAP end users and consultants specializing in supplier relationship management (SRM), procurement, and even application development are frequently exposed to IDocs, which can pose all kinds of technical problems for end users.Recently, we&#8217;ve received a lot of expert tips that can help you solve IDoc problems.</p>
<p>For example, here&#8217;s a way to send <a href="http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_gci1324820,00.html" target="_blank">advanced vendor details</a> using IDoc that can help you when you need to go beyond sending address details to a trading partner. If that tip isn&#8217;t enough, ask our resident <a href="http://searchsap.techtarget.com/expert/KnowledgebaseCategory/0,289620,sid21_tax292208,00.html" target="_blank">SRM expert</a>, Sachin Sethi, follow-up questions.</p>
<p>Some of you have been wondering how to generate an IDoc after you <a href="http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_gci1323978,00.html" target="_blank">delete a purchase order</a>. There is a way to do this, but it may well be illegal because of regulatory and compliance laws, so proceed with caution. By the way, this tip illustrates why business managers should carefully train SAP end users on the risk management implications of altering business documents.</p>
<p>Another common query is how to find user exits in <a href="http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_gci1324797,00.html" target="_blank">idoc_input_orders</a>. Resident SAP NetWeaver expert Axel Angeli explains how to do this, and also addresses the issue of <a href="http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_gci1204677,00.html" target="_blank">user exits in IDoc</a> with a detailed code sample.</p>
<p>Finally, the issue of data error tables is foundational for IDoc users. Axel explains how to <a href="http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_gci1324828,00.html" target="_blank">populate error tables automatically</a> from IDoc.</p>
<p>Demir Barlas, Site Editor</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/sap-watch/solving-idoc-problems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Process manufacturers: A guide to ERP functionality</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/process-manufacturers-a-guide-to-erp-functionality/</link>
		<comments>http://itknowledgeexchange.techtarget.com/sap-watch/process-manufacturers-a-guide-to-erp-functionality/#comments</comments>
		<pubDate>Tue, 11 Mar 2008 14:08:38 +0000</pubDate>
		<dc:creator>JackDanahy</dc:creator>
				<category><![CDATA[CRM]]></category>
		<category><![CDATA[erp]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[srm]]></category>

		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2008/03/11/process-manufacturers-a-guide-to-erp-functionality/</guid>
		<description><![CDATA[A new report from Aberdeen Research discovered that best-in-class process manufacturers tend to take specific approaches to their ERP strategy by deploying: ERP that provides integrated order entry, procurement, planning and production, and financial management. CRM, logistics, and delivery management systems integrated with manufacturing operations [themselves owned by ERP]. Forward and backward traceability. Attribute-based rules [...]]]></description>
				<content:encoded><![CDATA[<p>A new report from Aberdeen Research discovered that best-in-class process manufacturers tend to take specific approaches to their ERP strategy by deploying:</p>
<ul>
<li>ERP that provides integrated order entry, procurement, planning and production, and financial management.</li>
<li>CRM, logistics, and delivery management systems integrated with manufacturing operations [themselves owned by ERP].</li>
<li>Forward and backward traceability.</li>
<li>Attribute-based rules and routing.</li>
<li>Supplier compliance and collaboration.</li>
<li>Enterprise Asset Management (EAM).</li>
</ul>
<p>Being a good process manufacturer isn&#8217;t as simple as your ERP strategy, but the best process manufacturers do indeed have a recognizable approach to ERP characterized by the action points above.</p>
<p>Aberdeen adds that sound business process discipline, knowledge management, performance management, and reporting (e.g. for regulatory reasons) also characterize best-in-class process manufacturers.</p>
<p>SAP was one of the Aberdeen report&#8217;s sponsors.</p>
<p>Demir Barlas, Site Editor</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/sap-watch/process-manufacturers-a-guide-to-erp-functionality/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The skinny on SAP SRM 2007</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/the-skinny-on-sap-srm-2007/</link>
		<comments>http://itknowledgeexchange.techtarget.com/sap-watch/the-skinny-on-sap-srm-2007/#comments</comments>
		<pubDate>Tue, 30 Oct 2007 19:52:49 +0000</pubDate>
		<dc:creator>JackDanahy</dc:creator>
				<category><![CDATA[SAP]]></category>
		<category><![CDATA[soa]]></category>
		<category><![CDATA[srm]]></category>
		<category><![CDATA[trend]]></category>

		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2007/10/30/the-skinny-on-sap-srm-2007/</guid>
		<description><![CDATA[There has been something of a slow burn recently on a couple good blogs about SAP SRM 6.0. The word around is that the product, also referred to as SRM 2007, won’t be released beyond those customers currently in the ramp-up phase. Obviously, this isn’t great news for SAP, but how bad is it? To [...]]]></description>
				<content:encoded><![CDATA[<p>There has been something of a slow burn recently on <a href="http://blogs.zdnet.com/Howlett/?p=211" target="_blank">a couple</a> good <a href="http://www.spendmatters.com/index.cfm/2007/10/19/Newsflash-Is-SAP-SRM-60-No-More-A-Rumor-that-GA-is-Called-Off" target="_blank">blogs</a> about SAP SRM 6.0. The word around is that the product, also referred to as SRM 2007, won’t be released beyond those customers currently in the ramp-up phase. Obviously, this isn’t great news for SAP, but how bad is it?</p>
<p>To clear some things up, we talked to Andrew Bartels, an SRM (supplier relationship management) analyst with <a href="http://www.forrester.com/rb/research">Forrester Research</a>.</p>
<p>SAP says between 10 and 50 companies are in the ramp-up phase for SAP SRM 6.0 (Bartels puts that number closer to 10 or 20). Bartels said these companies will be able to continue implementing the product, but SAP will not be taking any new customers. Rather, the idea is that SAP will focus on getting SRM, SCM (supply chain management) and all its “alphabet soup” products on SOA (service-oriented architecture) by the fourth quarter of 2008.</p>
<p>So, is this a disaster for SAP? Not according to Bartels.</p>
<p>On the plus side, the SRM 2007 product itself doesn’t have a lot of new features and functionality, according to Bartels. Rather, most of the improvements were in usability, and SAP may have some service packs in the offing to help in that area.</p>
<p>SAP will also continue developing the areas that have needed the most attention &#8212; spend analysis, CLM (contract lifecycle management) and e-sourcing &#8212; all of which will be available for sale separately.</p>
<p>However, with the next SRM product now likely debuting in the fourth quarter of 2008, that puts a large two and a half year gap between major SAP SRM releases. Also, some customers were counting on the usability improvements and will be disappointed. But we shouldn’t expect a mass customer exodus for SAP, Bartels said.</p>
<p>The bottom line?</p>
<p>“This is not good for SAP,” Bartels said. “But it is not, by any means, too bad for them &#8212; they still have competitive products out there.”</p>
<p>Jon Franke<br />
News Editor</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/sap-watch/the-skinny-on-sap-srm-2007/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
