on 10-11-2013 7:41 PM
Hello all,
We've come across a new error in the 7.30 SAPGUI that is not fixed in Patch 6 Hotfix 1. If you use the standard, out-of-the-box mode for F4 search helps, certain fields cannot be sorted in the F4 'hit list'. As an example, choosing the 'Organizational Unit' field from an infoset in SAP Query as a selection field, you cannot sort the list of org units by name, nor even start or stop dates for org units. Session tracing reveals a "bad index" error in program SAPTABControl.1, module WDTTab Control, method refreshResultTable. It looks like sapwdtaocx.ocx is the offending component.
There is a workaround, which is to switch F4 mode to Modal (Dialog). However, we'd prefer to use the Amodal default.
The error is new in 7.30. It didn't occur in SAPGUI 7.20.
I've logged a Customer Message about it, but I'm wondering if anyone else has encountered this error?
Best regards,
Matt
Just confirming that the problem is fixed in Patch 7 again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Matt,
Did you try patch 7 yet?
If yes, then mark the question as answered for the benefit of other users.
If not ,then we also need F4 and Gridview traces from the GUI.
This can be captured from ALT+F12 => Options => Traces =>Session Traces
Check F4 Help
&
Gridview Control
Kindly upload the traces to the message.
Regards,
Jude
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The fix is in the works now, and will be released in Patch 7, referenced by Note 1925920 (not yet released).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Matt,
discovered the same problem with 7.30 Patch Level 6 here.
Quite sure it worked before (with PL 5).
Hopefully SAP will correct it with PL7 in a few weeks.
And thanks for mentioning the workaround - nice to know.
Best regards,
Harald
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Harald,
SAP has responded to the Customer Message and they are working on it now. They were not previously aware of the problem. I didn't verify if the problem existed on Patch 5 or not; if it's true the problem is new with Patch 6, that may be useful for SAP to know, so I passed that on to them.
Best regards,
Matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.