Table maintenance strategy
I would like to know what are the different strategies followed in different projects for table maintenance.
We have access to SM30 in our QA system for table maintenance. There have been instances, where we forgot to maintain entries in Prod when we moved the related development to Prod. As a result, the desired functionality did not work in Prod and clients started complaining.
Hence we want to put some restrictions/discipline around table maintenance -
Some thoughts were -
1) Lock SM30 in QA, so that developer can transport entries from Dev, to QA, and Prod since TRs will not be ignored generally
2) For tables, whose entries cannot be transported, but maintained directly in each individual system, the business user should be given a txn code specific for table maintenance of particular table(s).
Request you to share your thoughts and strategies followed in your systems.
Thanks in advance!!