Question:
We are in 4.7. The business identified a few standard tables that cannot be maintained in a closed production system. Therefore they asked if we could change the table to be a "current setting", so that it can be maintained in a closed system (value OBJH-CURSETTING).
Questions:
1. Do you know how to maintain that setting. SM30 did not work.
2. What would be the impact of that change of a standard table? Would that be overwritten with every new patch/update?
Thanks, Franz
Answer:
These 'few' standard tables - what are they and why would they want to be maintained directly ???
Maintaining standard tables using something like SM30 is not a good idea unless SAP allows you to do this via a view or some such.
Depending on whether the table is a standalone table or has dependant tables the effect of maintaining a table bypassing standard SAP transactions can vary from nothing to trashing your entire system.
You will also invalidate your SAP Earlywatch facility if you update SAP standard tables manually that require a transaction (and have a transation) to do so.
This simple answer is "don't do it" unless you really do know what the impact will be - and without knowing what the tables are no one can give you that information.
_________________
Regards
R
Abap KC
SFMDR
Answer:
Thanks for the anwer. Right, we checked that these tables are stand alone and would assign specific maintenance transactions instead of risky SM30.
I agree to all your objectives, however the decision was taken and the specific tables will be discussed with audit as well.
There is still one question open: How can I maintain the OBJH-CURSETTING value? I would like to test a change to some dummy tables but just cannot find out how. As I said SM30 does not work, neither for OBJH, nor for V_OBJ_H. I also did not find a maintenance transaction in TSTCP.
Thanks !
Answer:
Thanks for the anwer. Right, we checked that these tables are stand alone and would assign specific maintenance transactions instead of risky SM30.
I agree to all your objectives, however the decision was taken and the specific tables will be discussed with audit as well.
There is still one question open: How can I maintain the OBJH-CURSETTING value? I would like to test a change to some dummy tables but just cannot find out how. As I said SM30 does not work, neither for OBJH, nor for V_OBJ_H. I also did not find a maintenance transaction in TSTCP.
Thanks !
Answer:
Have a look at Transaction SE03, Administration->System Change Option.
_________________
Regards
R
Abap KC
SFMDR
Answer:
Sorry but could you please be a bit more specific? I changed the system change option to "modifiable" in our sandbox but still could not maintain OBJH-CURSETTING.
Thanks!
Answer:
In that case have a look at Transaction SCC4.
_________________
Regards
R
Abap KC
SFMDR
Answer:
SCC4 is the transaction to open/close the client but does not help to maintain table OBJH. I am in a DEV system that is already open for any changes.
I would like to know if there is a transaction/function where I can maintain the field CURSETTING of the table OBJH. As I said, SM30 does not work and I did not find another maintenance transaction for OBJH or V_OBJ_H.
Thanks again!
Answer:
Just found out that OBJH can be maintained with transaction code SOBJ. Just in case that some of you did not yet know.
Answer:
We also used "current settings" to allow users access to certain tables which were maintained in SPRO but really should have been master data - for instance - the master list of tariff numbers.
What we found was that the current-setting setting was relevant only for productive clients - ie - our sandbox, development and quality systems did not recognize this setting - only our production client.
Therefore for testing - we had to have basis change the designation of our development client to "productive" before our testing would work. (Same with our quality client). The basis change was temporary of course.
Hope this helps.
Charlie