ā2012 Oct 30 10:02 AM
Hi,
I would like to change the table attribute for TKA3C from the current "display/maintenance allowed with restrictions" to "display/maintenance allowed". Am i allowed to make this change since this is SAP delivered table with C delivery class?
I also noticed that another SAP delivered table T030 is having "display/maintenance allowed" status. So i believe it is okay to change the above table to this status. Please advise.
ā2012 Oct 30 12:06 PM
This Customizing table is managed via SE34 on cluster view V_TKA3 (transaction OKB9)
What is your exact purpose, if you want to be able to change the data in production, do not change table attributes but call transaction SOBJ and declare the objects of the cluster view as "Current Settings". Else could you explain the reason of your question ?
Regards
Raymond
ā2012 Oct 30 11:58 AM
Are you aware that it would be a repair? Why don't you build a small maintenance program for that table?
ā2012 Oct 30 12:06 PM
This Customizing table is managed via SE34 on cluster view V_TKA3 (transaction OKB9)
What is your exact purpose, if you want to be able to change the data in production, do not change table attributes but call transaction SOBJ and declare the objects of the cluster view as "Current Settings". Else could you explain the reason of your question ?
Regards
Raymond
ā2012 Oct 30 12:42 PM
Hi Both,
I have 2000 entries need to be updated in this table. I cannot use OKB9 because LSMW does not record the dialog structures found there. So i thought of creating an LSMW at the table level update using se16.
I have done it thru se16 for T030 because of the "display/maintenance allowed" status, however for TKA3C, the attribute is "display/maintenance allowed with restrictions" which means i cannot create new entries using se16 under this attribute.
So i am thinking of changing the attribute to "display/maintenance allowed" to create the new entries at the table level using se16 via LSMW recording.
ā2012 Oct 30 12:51 PM
IMHO creating a BDC on SE16 is not more correct than a direct OPEN-SQL statement, and will cause more effort/pain in development ?
You could try to use a FM like VIEW_MAINTENANCE_SINGLE_ENTRY (or other FMs of group SVIM) on view V_TKA3A with SUPPRESSDIALOG = 'X' and action = 'UPD' or 'INS' ?
Regards,
Raymond
ā2012 Oct 30 1:08 PM
Hi Raymond,
I tried that FM for V_TKA3C, but due to the structure of this table, it does not work.
Can i change the attribute of this table to the required setting display/maintenance allowed? Is it allowed?
ā2012 Oct 30 1:19 PM
ā2012 Oct 30 1:38 PM
Hi,
When i use the FM, the system will ask for a new entry for the input value but it asks for only one when in actual fact there are many input values that we need to enter.
ā2012 Oct 30 2:36 PM
ā2012 Oct 30 2:45 PM
okay i will try that out but are you saying changing the table attribute is not an option at all?
ā2012 Oct 30 2:53 PM
ā2012 Oct 30 3:00 PM
Hi Raymond,
But i want to change the table attribute only temporarily in the dev client and then put it back to what it was earlier after i have finished creating the 2000 entries.
So in this case is it safe to change it?
ā2012 Oct 30 3:08 PM
In this case, not much risk, but as I wrote in one previous answer, you could directly update the database table (then generate transport request via OKB9) but
- don't forget to reset the table to original state
- you will require a sscr key for the object
- you have to check yourself the validity of input data
But I would not do it myself...
Regards,
Raymond
ā2012 Oct 30 3:24 PM
Hi Raymond,
So does this mean technically we can change the attribute of the table and the system will allow us to do that?
ā2012 Oct 30 3:28 PM