<?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 Experts: VMware Virtualization &#124; Consulting &#124; Integration - DataXstream &#187; RSTS_WRITE</title>
	<atom:link href="http://www.dataxstream.com/tag/rsts_write/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dataxstream.com</link>
	<description>SAP Certified Consultants</description>
	<lastBuildDate>Tue, 07 Feb 2012 23:57:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Taxes and TemSe</title>
		<link>http://www.dataxstream.com/2010/04/taxes-and-temse/</link>
		<comments>http://www.dataxstream.com/2010/04/taxes-and-temse/#comments</comments>
		<pubDate>Tue, 27 Apr 2010 13:00:00 +0000</pubDate>
		<dc:creator>Wess Tobler</dc:creator>
				<category><![CDATA[SAP Basis Blog]]></category>
		<category><![CDATA[Basis/Netweaver]]></category>
		<category><![CDATA[FB_CALL_HANDLE]]></category>
		<category><![CDATA[NetWeaver]]></category>
		<category><![CDATA[PU19]]></category>
		<category><![CDATA[RAISE_EXCEPTION]]></category>
		<category><![CDATA[RSTS_WRITE]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP Security]]></category>
		<category><![CDATA[SAPLSTMS]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[TemSe]]></category>
		<category><![CDATA[Wess Tobler]]></category>

		<guid isPermaLink="false">http://www.dataxstream.com/?p=4555</guid>
		<description><![CDATA[Recently while supporting my current client, I was tasked with solving a rather puzzling issue an end user was experiencing. While using T-Code PU19, the user would receive: This would, in turn, generate a short dump: My initial thought was that this was a TemSe issue, meaning it was a true BASIS issue.  Upon further [...]]]></description>
			<content:encoded><![CDATA[<p>Recently while supporting my current client, I was tasked with solving a rather puzzling issue an end user was experiencing.  While using T-Code PU19, the user would receive:</p>
<p><a href="http://www.dataxstream.com/wp-content/uploads/2010/03/TemSe-error-PNG1.png" rel="shadowbox[sbpost-4555];player=img;"><img class="alignnone size-full wp-image-4554" src="http://www.dataxstream.com/wp-content/uploads/2010/03/TemSe-error-PNG1.png" alt="" width="454" height="167" /></a></p>
<p><span id="more-4555"></span>This would, in turn, generate a short dump:</p>
<p><a href="http://www.dataxstream.com/wp-content/uploads/2010/03/TemSe-shortdump-PNG3.png" rel="shadowbox[sbpost-4555];player=img;"><img class="alignnone size-full wp-image-4550" src="http://www.dataxstream.com/wp-content/uploads/2010/03/TemSe-shortdump-PNG3.png" alt="" width="657" height="618" /></a></p>
<p>My initial thought was that this was a TemSe issue, meaning it was a true BASIS issue.  Upon further examination, I came to the conclusion that it was actually a security/access issue.  The user did not have create rights for TemSe.  Find the Role path Basis: Administration -&gt; TemSe: Actions on TemSe objects -&gt; TemSe: Action ID for Authorization and make sure that the user has the value &#8220;CRE&#8221; (for create).</p>
<p><a href="http://www.dataxstream.com/wp-content/uploads/2010/03/Authorizations-PNG2.png" rel="shadowbox[sbpost-4555];player=img;"><img class="alignnone size-full wp-image-4553" src="http://www.dataxstream.com/wp-content/uploads/2010/03/Authorizations-PNG2.png" alt="" width="555" height="289" /></a></p>
<p><img src="/DOCUME%7E1/wtobler/LOCALS%7E1/Temp/moz-screenshot.jpg" alt="" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dataxstream.com/2010/04/taxes-and-temse/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

