Function Key defined in Application Toolbar but does not get displayed on screen

[BaerbelWinkler]

Hi Folks,

I'm trying to find the reason why a function key which seems to be properly defined still does not get displayed on the screen (and yes, I know that similar questions have been asked before but none of the responses I checked fit our particular issue).

We have a custom program via which mass changes of individual sales-order fields can be triggered. This program and the relevant PF-Status "0100" gets enhanced every once in a while to allow yet another field to be updated, usually without any issues. This time around, an option to change the ship-to address was added and it shows up and works fine in the DEV-system. The change was introduced into PROD a while ago and there the function key for this change does not show up on the screen and we are at a loss to identify why this is happening.

Here are a few comparison screenshots from DEV (greyish background) and PROD (red background):

The change was introduced with a transport-request ending with "WZL" which is the current version in PROD:

The function key shows up in the definitions in both DEV and PROD:

The code to set the PF-status hasn't been touched for this change:

*&---------------------------------------------------------------------*
*&      Module  PBO_0100  OUTPUT
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
MODULE pbo_0100 OUTPUT.

  SET PF-STATUS '0100'.
  SET TITLEBAR  '0100'.

And I didn't find anything which might hint at authorization related restrictions either.

Because our systems are currently getting the latest support packages (013) for NW750 EHP8, I can't provide comparable screenshots from our test-system but I have been told that the button was available before the system went into the upgrade process. DEV is already on SP13 while PROD is still on SP07.

So, the questions are: why doesn't the function key get displayed and why doesn't Ctrl-Shift-F1 invoke the processing associated with it? What else can I check and compare?

Thanks for any pointers you have!

Cheers

Bärbel

[SimoneMilesi]

Hi Barbel!

Did you activate the function on PF Status?

[BaerbelWinkler]

Hi Simone,

I wasn't involved with the development, I'm just trying to help find the reason for the weird behaviour. I therefore cannot answer your question. In SE80 I however don't see a difference between DEV and PROD so if something weren't properly activated, shouldn't the button be missing in DEV as well?

[SimoneMilesi]

8b889d0e8e6f4ed39f6c58e35664518f quite strange.

Did you try to re-activate the status in production enviroment?

[BaerbelWinkler]

simone.milesi

Good call, Simone! I had tried to regenerate the object-list in SE80 which hadn't helped, but hadn't yet hit the "generate" button (as that more often than not wouldn't work in PROD for us anyway). I did it just now for the affected GUI-status and it a) worked technically and b) on re-running the program, the button now shows up:

Really strange behaviour on SAP's side. We'll keep an eye on this when the next button gets imported into PROD.

Thanks for your quick help with this.

Cheers

Bärbel

[SimoneMilesi]

Happy you solved, 8b889d0e8e6f4ed39f6c58e35664518f!

Sometimes this happens if the button is inserted in a PF under Modification assistent.