Maintaining data in standard table

[Former Member]

Hi experts,

We have a requirement in which we have to maintain a standard customizing table in production. Currently user is maintaining entries through SPRO, including them in transports and getting it moved to Production. He want to overcome the current process.

We thought of two ways as below : -

1. Creating a T-Code for SM30 of that table and moving it to Production. Later user can use this T-Code and maintain entries. But here is a challenge that production client always remains closed for changes. So we have limitation on maintaining data with this way.

2. Creating an upload program with database query updating this table but ideally it is not suggested to update a standard SAP table using database query.

So if there is any other way, please do let me know.

Thanks

Siddarth

[Sandra_Rossi]

Hi Siddarth,

You may also change the "current settings" of the standard table maintenance dialog, as explained in the following documents:

- Note 135028 - Transfer IMG activity to current setting

- Note 523213 - Set maintenance view in production system to changeable

- [SAP Library - Customizing in a Productive System|http://help.sap.com/saphelp_nw70/helpdata/en/d2/b73c885b8a11d395da00a0c930dcc1/frameset.htm]

BR

Sandra

[Former Member]

Please never touch a SAP DB table with direct OPEN SQL OR NATIVE SQL stmnts.

U may use:

1. ANY BAPI if available.

2. TMG

I have a idea why not create a TMG, create a BDC for the TMG and then run it thru a report by first collecting all the data that u wish to update and then in the report call the batch job this report can be run in batch mode na dyou may even code it to interface with a idoc

[sushil_taneja]

create a custom 'maintainance view' on this table(s) and give access of this view (only) to the user in production. this should help.

rgds

[madhu_vadlamani]

Hi Siddarth,

We have a requirement in which we have to maintain a standard customizing table in production. Currently user is maintaining entries through SPRO, including them in transports and getting it moved to Production

This is the right process. If you do all directly in production client then there is no use of landscape. Try to avoid this and follow what you are doing now.

Regards,

Madhu.

Edited by: madhurao123 on Jul 24, 2011 10:21 AM

[kumud]

Hi Sid,

Is the question answered?

If I understand the question, you want to give maintenance view of standard table to the end users so that they can update entries directly and entries need not be transported from development client.

1. You have not mentioned the name of table. Can you please share the table name.

Regards,

Kumud

[SureshRa]

Hi Sid,

Please get access key from SAP and modify the "Standard Recording Routine" to "No recording" in the table maintenance generator (SE54) - for the subject maintenance view. Once this change is moved to Production. The users would be free to modify entries without getting constraints about client closed.

I really don't like the idea of modifying customizing tables directly in Prod. However it is your requirement...

Regards

Suresh