<?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>Homepage for SAP Professionals &#187; S_TABU_DIS</title>
	<atom:link href="http://home4sap.com/Blog/tag/s_tabu_dis/feed/" rel="self" type="application/rss+xml" />
	<link>http://home4sap.com/Blog</link>
	<description>SAP Community website with all sorts of interesting information related to SAP</description>
	<lastBuildDate>Mon, 21 May 2012 22:56:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<meta xmlns="http://www.w3.org/1999/xhtml" name="robots" content="noindex,follow" />
		<item>
		<title>Edit SAP tables: Your SAP Security Admin’s nightmare: &amp;sap_edit</title>
		<link>http://home4sap.com/Blog/2010/11/edit-sap-tables-you-sap-security-admins-nightmare/</link>
		<comments>http://home4sap.com/Blog/2010/11/edit-sap-tables-you-sap-security-admins-nightmare/#comments</comments>
		<pubDate>Tue, 02 Nov 2010 14:47:36 +0000</pubDate>
		<dc:creator>Webmeister</dc:creator>
				<category><![CDATA[Basis Tips]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[SAP Security]]></category>
		<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[&SAP_EDIT]]></category>
		<category><![CDATA[audit]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[delete]]></category>
		<category><![CDATA[direct update]]></category>
		<category><![CDATA[edit]]></category>
		<category><![CDATA[RKSE16N_CD]]></category>
		<category><![CDATA[sap tables]]></category>
		<category><![CDATA[se16]]></category>
		<category><![CDATA[se16n]]></category>
		<category><![CDATA[SE16N_INTERFACE]]></category>
		<category><![CDATA[SOX]]></category>
		<category><![CDATA[S_DEVELOP]]></category>
		<category><![CDATA[S_TABU_DIS]]></category>
		<category><![CDATA[tables]]></category>
		<category><![CDATA[UASE16N]]></category>
		<category><![CDATA[update]]></category>

		<guid isPermaLink="false">http://home4sap.com/Blog/?p=15</guid>
		<description><![CDATA[Last Update May 22, 2011 It does not matter what access you have for table editing (S_TABU_DIS). Just use the command &#38;SAP_EDIT in the command field in SAP and off you go: you can edit table content directly. This works if you have debug with changes access for object S_DEVELOP, but S_TABU_DIS is ignored as [...]]]></description>
		<wfw:commentRss>http://home4sap.com/Blog/2010/11/edit-sap-tables-you-sap-security-admins-nightmare/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Create custom transaction for SE16 </title>
		<link>http://home4sap.com/Blog/2010/02/create-custom-transaction-for-se16%c2%a0/</link>
		<comments>http://home4sap.com/Blog/2010/02/create-custom-transaction-for-se16%c2%a0/#comments</comments>
		<pubDate>Sat, 20 Feb 2010 18:00:51 +0000</pubDate>
		<dc:creator>Davatec Consulting</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[SAP Security]]></category>
		<category><![CDATA[SAP Tips and Tricks]]></category>
		<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[se16]]></category>
		<category><![CDATA[S_TABU_DIS]]></category>

		<guid isPermaLink="false">http://home4sap.com/Blog/?p=262</guid>
		<description><![CDATA[To create custom transaction, it is suggested that you define the naming convention as simple as possible to make sure that users will remember the transaction and do not have to second guess. If a user needs a custom transaction to browse table MARA, you can either call the transaction ZSE16_MARA or simply ZMARA. Use [...]]]></description>
		<wfw:commentRss>http://home4sap.com/Blog/2010/02/create-custom-transaction-for-se16%c2%a0/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>How to protect table extracts for end-users</title>
		<link>http://home4sap.com/Blog/2009/10/how-to-protect-table-extracts-for-end-users/</link>
		<comments>http://home4sap.com/Blog/2009/10/how-to-protect-table-extracts-for-end-users/#comments</comments>
		<pubDate>Fri, 02 Oct 2009 11:56:24 +0000</pubDate>
		<dc:creator>Davatec Consulting</dc:creator>
				<category><![CDATA[SAP Data Load & Extracts]]></category>
		<category><![CDATA[authorizations]]></category>
		<category><![CDATA[data extract]]></category>
		<category><![CDATA[extract]]></category>
		<category><![CDATA[se16]]></category>
		<category><![CDATA[se16n]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[SOX]]></category>
		<category><![CDATA[sq01]]></category>
		<category><![CDATA[sqvi]]></category>
		<category><![CDATA[S_TABU_DIS]]></category>

		<guid isPermaLink="false">http://home4sap.com/Blog/?p=219</guid>
		<description><![CDATA[There are quiet a few companies that want to give end-users access to extract table data via SE16 or SE16N. If you decide to give SE16N, please read our blog that shoes the pitfalls &#38; danger of giving SE16N &#8211; In addition, the auditors, security people and basis folks worry about using having transactions such [...]]]></description>
		<wfw:commentRss>http://home4sap.com/Blog/2009/10/how-to-protect-table-extracts-for-end-users/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

