We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE: [sap-security] Anyone know how to bypass the invalid entry checking in se16 debug mode?

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Posted by Dave Thornburgh (SAP JOAT)
on May 24 at 9:02 PM
Mark this reply as helpfulMark as helpful
Chow -

Don't. The error checking is there for a reason. You can do spectacular damage to an SAP installation by directly editing table data. If you need to change the data, find the correct business transaction and use it - the debug method of using SE16 to modify data is just _wrong_, and should not even be attempted by anyone who isn't a bona fide expert.

Even if this is a sandbox system, don't fall for the temptation to use the SE16 shortcut. If the document doesn't have data you need to play with a certain scenario, then abandon it and create a new document that does.

Dave

From: pereschow via sap-security [mailto:sap-security@Groups.ITtoolbox.com]
Sent: Monday, May 24, 2010 5:54 AM
To: Dave Thornburgh
Subject: [sap-security] Anyone know how to bypass the invalid entry checking in se16 debug mode?

Posted by pereschow
on May 24 at 8:53 AM

Hi All,
Anyone know how to bypass the entry checking in se16 debug mode?i try to EDIT the record through SE16 debug mode. But i cant save it because some entry of the table is invalid. Anyone know how to bypass the invalid entry checking?I try to /h again before i "save" the changed, but it didn't go to debug mode and i cant bypass the invalid entry checking.
Thanks
__.____._
Copyright © 2010 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Dave Thornburgh
SAP Security Enthusiast

Contributed 100 posts in a group to earn a Bronze Achievement
_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language