Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Tabstrip: Protected title for tab index

Former Member
0 Kudos
1,361

Hi all,

This is the first time I am trying my hand on tabstrips so the problem may be elementary but I am unable to solve it. I've defined a tabstrip using the wizard with 6 tabs and when I run the program the tabstrip appears fine. But I also get a success message (00-119) 'Protected tab titles are not supported (tab & title &)'. And since this message is called dynamically, i cant determine the error cause. The tabs have name 'TABSTR01' to '06' and have been defined 'output fields' so no text(although i've tried with texts as well).

could you please help me get rid of this message?

Thanks

cheers

9 REPLIES 9

ssimsekler
Active Contributor
0 Kudos
154

Hi Gaurav

As you might have realised tabstrip pushbuttons are screen elements. So, it may be because you try to process those elements while you are looping screen elements, i.e. trying to make those buttons input off. Add neccessary condition statements to prevent screen loop to process those buttons.

Regards

*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

0 Kudos
154

Thanks for replying Serdar,

I have added no code of my own in the screen. I hae also checked the screen code and no reference to any of the tabs has been made in the code. It simply keeps giving the message 'Protected tab titles are not supported (tab Z_TAB_9008 title Z_TAB1)' ( i changed names to Z_* in hope that it may affect something ).

Any more suggestions?

cheers

0 Kudos
154

Hi Gaurav


LOOP AT SCREEN .
"No conditions to filter fields to traverse"
  screen-input = 0 .
  MODIFY screen .
ENDLOOP .

I guess, the above code may cause the message you mentioned. As you see there is no reference to tab name.

Regards

*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

Former Member
0 Kudos
154

I hope you'd have fixed your problem by now.

I also came up with a similar problem while creating a new infotype in HR(PD).

I realised the cause for the problem was a call to a routine 'change_format' in program 'FH5AMF30' which is called in via the module 'Init' which is a required module in the PBO of the infotype processing screen. So I included the following code in the module 'init_9nnn' after the init module:

module init_9nnn output.

loop at screen.

if screen-name = 'TAB_STRIP1_TAB1'.

screen-input = '1'.

modify screen.

endif.

if screen-name = 'TAB_STRIP1_TAB2'.

screen-input = '1'.

modify screen.

endif.

if screen-name = 'TAB_STRIP1_TAB3'.

screen-input = '1'.

modify screen.

endif.

endloop.

endmodule.

That solved the problem.

The bottom line being--the Tabstrip should have a screen-input = '1' immediately before calling the subscreen in the PBO.

Hope this helps someone in future.

Cheers,

Sanjay

0 Kudos
154

Hi Sanjay,

Thanks for the code, I'm also a tabstip newbie with the same problem and this fixed it for me

Cheers,

Richard

0 Kudos
154

Wow Sanjay,

It solved my problem too.

Thanks a lot.

Regards

<i><b>Raja Sekhar</b></i>

0 Kudos
154

Thanks a lot Sanjay....

Your solution solved our problem too

0 Kudos
154

I encountered this problem and the solution helped me.  Thanks a lot!!

0 Kudos
154

Thanks a lot~

I was able to fix the warning message with your solution.