Maintain checkbox default value as SET for the transaction SM30

[jibinmathews]

Hello all,

We created a new checkbox column for an existing table and it is maintainable using SM30. However before transporting it into Production we need to make sure that the default value of this checkbox field is 'X' (set) ie the checkbox should be ACTIVE(Set /ticked) for all entries (rows) by default.

Once imported into production, since it is a new checkbox, it will be inactive and some important functions will fail to work (have written code to ensure that some functions will work only if this new Checkbox is set to ACTIVE). The user wants to avoid manually setting the checkbox for all entries through SM30 as soon as the change is imported into production.

Apart from table maintenance events, is there any other way to do this ? We have used the domain XFELD for the new data element.

Thanks in Advance !

[raymond_giuseppi]

Create a small report to set this field in every client and add this report twice in the transport request

• R3TR PROG <report_name> to transport the report
• R3TR XPRA <report_name> to execute the report at import and update the flag in every client/mandt

You can add a message of success (or failure) to import log using FM TR_APPEND_LOG in the report. (Browse the many *XPRA* reports created by SAP)

[Sandra_Rossi]

Don't forget that the program runs in client 000 so use UPDATE ... CLIENT SPECIFIED ... and things like that.

[jibinmathews]

Thanks Raymond for your Reply. Very interesting to know about XPRA. Writing a report was suggested before for another case however since the report was to be only run once and will have to be in production without any further use or have to be deleted- this was not done.

we are trying this solution:

the recording routine is activated for the table and now any data changes in the development System will hopefully be transported to production !

[Sandra_Rossi]

Please use COMMENT to Raymond answer. The button ANSWER is only for solutions.

[raymond_giuseppi]

Insure that

• The customization request will be imported right after the Workbench request.
• No record has been created in any system other than the dev.
• You could have set the flag in the dev and manually transport the records with a R3TR TABU <table> record (E071) associated with a generic * or <client>* key (E071K) without changing the maintenance dialog

[mateuszadamus]

Hello jibin.mathews

The correct solution in this case, since you want to have the checkbox set to ACTIVE anyways, is to have the functionality NOT work when the checkbox is set to ACTIVE (in other words, work when the checkbox is set to INACTIVE).

This way marking the checkbox as ACTIVE will disable the functionality, but by default it (the functionality) will be enabled (as per your requirement).

Kind regards,
Mateusz

[jibinmathews]

Thanks Mateusz ! This could have been done but i forgot to mention that the table itself has about 10 columns (all checkboxes) and some exist since a decade. Doing it for one column may confuse users regarding other columns as, the table is maintainable by multiple users in production. Each user has an entry in the table and he can set each checkbox based on whether he wants a certain functionality to work for let us say his group. While importing into a production just wanted to make sure that the functionality is activated by default (as 'X').