Re: [sap-security] Anyone know how to bypass the invalid entry checking in se16 debug mode?
Posted by
Admin at
|
Share this post:
|
|
0 Comments
 | Posted by anjan.pandey on May 25 at 12:29 AM |  Mark as helpful |
Hi
Direct table updates should not be allowed in production environment. If
there is any such requirement then create a custom transaction for the same.
Thanks.
Anjan
On Tue, May 25, 2010 at 7:32 AM, Sonia via sap-security <
sap-security@groups.ittoolbox.com> wrote:
>
> Posted by Sonia (Sap Bas and
> Security Design Consultant)
> on May 24 at 10:01 PM
> Chow,
>
> I hope,what ever changes you are doing will be in development system.
>
> Thank you,
> Sonia
>
> On Mon, May 24, 2010 at 9:44 PM, pereschow via sap-security <
> sap-security@groups.ittoolbox.com> wrote:
>
> > Posted by pereschow
> > on May 24 at 9:47 PM
> > Hi Dave,
> > I found a t-code that able to change the MSEG-SGTXT. "MB02". Hope this
> > t-code can help me. :)
> >
> > ---------------Original Message---------------
> > From: pereschow
> > Sent: Monday, May 24, 2010 8:57 AM
> > Subject: Anyone know how to bypass the invalid entry checking in se16
> debug
> > mode?
> >
> > > 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
__.____._ Direct table updates should not be allowed in production environment. If
there is any such requirement then create a custom transaction for the same.
Thanks.
Anjan
On Tue, May 25, 2010 at 7:32 AM, Sonia via sap-security <
sap-security@groups.ittoolbox.com> wrote:
>
> Posted by Sonia (Sap Bas and
> Security Design Consultant)
> on May 24 at 10:01 PM
> Chow,
>
> I hope,what ever changes you are doing will be in development system.
>
> Thank you,
> Sonia
>
> On Mon, May 24, 2010 at 9:44 PM, pereschow via sap-security <
> sap-security@groups.ittoolbox.com> wrote:
>
> > Posted by pereschow
> > on May 24 at 9:47 PM
> > Hi Dave,
> > I found a t-code that able to change the MSEG-SGTXT. "MB02". Hope this
> > t-code can help me. :)
> >
> > ---------------Original Message---------------
> > From: pereschow
> > Sent: Monday, May 24, 2010 8:57 AM
> > Subject: Anyone know how to bypass the invalid entry checking in se16
> debug
> > mode?
> >
> > > 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
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Related Content
In the Spotlight
White Papers
In the Spotlight
Toolbox.com for iPhone: Ask Questions & Get Answers Anywhere. Use the New iPhone App
View this thread online
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
