Radio button change and it's impact on existing variants

[babu_kilari4]

All -

I need little guidance on the topic below. Imagine a ABAP report having NO radio buttons in the selection screen initially and there is a variant saved and the program is running as a batch job in production system (P1)

Now, the same program has been extended to have a radio button group with two radio buttons ( say R1 and R2) and by default the first one (R1) is selected. This program is moved to one of the other production systems say (P2 meant for a different region) and since its a new implementation, user selects the correct radio button and new variant is created for Production system P2 and it works Ok.

Now, we have periodic "re-alignment" of programs to synchronize the changes done for P1 to P2. Here, the expectation is to select the second radio button (R2) and update the variant otherwise due to the nature of "Radio button group to always pick the first radio button", if we FORGET to update the variants; batch jobs will incorrectly execute with inappropriate radio button and finish the execution creating an unexpected impact.

Is there a way to catch this technically and always force the user to update a variant. This is specially an issue because always one radio button would get selected ( and it has the impact on existing variants ).

Looking forward to your response.

Cheers,
BK

[raymond_giuseppi]

You could look at report RSVARDOC_610 (suffix can change) which updates obsolete versions to get some idea on how to identify those and solve your requirement.

[Sandra_Rossi]

Babu Kilari If I understand well, you say that the first button is automatically chosen if the variant has not been adjusted. So, why wouldn't you define the first button as being the default option to limit the risks? (and still automatically adjust the variants with RSVARDOC_610).

[babu_kilari4]

Hello Raymond, Sandra -

Imagine if we introduce multiple radio buttons ( not just 2 ) and if we forget to catch this; always the defaulted one will ( usually the first one ) be picked and it will run.

So, I am wondering how to catch such cases. Are you saying the report RSVARDOC_610 can catch such cases and report the user with the screen changes ? I will try.

Thanks & Best Regards

BK

[babu_kilari4]

All -

I tested this and it does NOT work. It doesn't throw any error. Honestly speaking, if we were to run this program - we might as well update the variants. The issue really is to catch such cases and abrupt the processing "if we introduce some radio buttons and to avoid the previous variants from picking the default radio button which may not be for processing for the existing variants".

Cheers

[Sandra_Rossi]

Please use the button COMMENT. As SAP says in the "Before answering" at the right of the answer text area: "You should only submit an answer when you are proposing a solution to the poster's problem"

[Sandra_Rossi]

The standard has only one behavior when there are some changes in the definition of the report parameters. If you want another behavior, you will have to create a custom program to upgrade your variants, or put some custom code in each changed program if you want to detect such changes.

[DoanManhQuynh]

How do you "re-alignment" between 2 systems? are you transporting program and its variants? I wonder why you have to update variant in P2 system, if you want to keep it, dont overwrite it, keep the name of variant between 2 system difference. if you want the new update from selection screen in P1 but keep the radio button in P2, write a code in INITIALIZATION to load those variants and change what ever you want.