This website is not affiliated with, sponsored by, or approved by SAP AG.

STVARV vs Maintaining Directly in SE16

SAP-OTHER (SAP Components and all other issues that do not fall under above categories)

Moderators: Snowy, thx4allthefish

Post Reply
sapfanatic.com
Posts: 475
Joined: Mon Oct 09, 2006 6:09 pm
Location: Cebu

STVARV vs Maintaining Directly in SE16

Post by sapfanatic.com » Wed Aug 01, 2012 1:04 am

Just a question, we know that we can maintain a variable via transaction STVARV (table TVARVC). But we can also do this via SE16 creating variable with several records.

Can you tell me if there is a different effect if maintaining via STVARV and maintaining via SE16? We have one variable maintained in SE16 by the project team long time ago. and now i need to add a record but i am not able to do because we are not allowed to access SE16 anymore. We are only allowed to do via STVARV. i am afraid to add the record in STVARV because all existing records maintained via SE16 before will be deleted.

Snowy
Posts: 28789
Joined: Mon Oct 21, 2002 2:33 pm
Location: 3.1415926535

Re: STVARV vs Maintaining Directly in SE16

Post by Snowy » Thu Aug 02, 2012 1:34 pm

1. SE16 does not create transports

Am unsure about STVARV

Post Reply