No T-Code in SAP can damage your data, all t-code has initial screens?

[Former Member]

As per my understanding there is no SAP standard t-code in SAP which can damage SAP or data in database when you run from SAPGUI (do not execute once you are in t-code). What's your thinking?

[Former Member]

Well i think there are some transactions that create or fill tables at the first call. Example: you should not call RSA1 (BI admin) in a non BI system...

It won't screw your system, but creates unnecessary stuff.

Cheers Michael

[kiran_k8]

I don't understand why RV80HGEN is without a selection screen.

Why not have a selection screen and let the developer choose which routine he wants to activate or deactivate.

Why there is a need to run RV80HGEN in the target clients again.

K.Kiran.

[ThomasZloch]

Julius would have reported such T-codes to SAP long time ago.

I once accidentally wrote a program like this, but that's also a loooong time ago.

Thomas

[Former Member]

There is a tcode which blows your asset accounting customizing away, even if the client is closed. It has a selection screen with default test_mode = 'X'.

However, a typo could execute a parameter transaction for it with test_mode = ' ' AND SKIP FIRST SCREEN !

At least it makes an authority-check now, but I still won't mention the name because I know you all have SAP_ALL ...

[JPReyes]

but I still won't mention the name because I know you all have SAP_ALL ... 

Thats the problem when speaking with Basis fellas... we are curious people with lots of authorizations.

Regards

Juan

Edited by: Juan Reyes on Nov 12, 2010 2:49 PM

[Former Member]

 There is a tcode which blows your asset accounting customizing away, even if the client is closed. It has a selection screen with default test_mode = 'X'. 

i guess Nathan Genez would run after you ..... lol ....