cancel
Showing results for 
Search instead for 
Did you mean: 

Could not find attribute LANGU

Former Member
0 Kudos

I have a webdynpro ABAP screen that is displaying the fields on infotype 0022.

But when I try to click on the dropdown for field SLART, I get the error "could not find attribute LANGU".

Within SAP GUI and accessing the infotype 0022 via PA20/PA30, the dropdown of course works fine. The Entry Help is trying to access check table T517T - Educational Establishment Type Designations, to display on the dropdown.

It appears that the webynpro app does not know what LANGU in order to perform the dropdown for SLART.

Anybody come across something like this?

Thanks

Johnny

Accepted Solutions (0)

Answers (1)

Answers (1)

ChrisPaine
Active Contributor
0 Kudos

Hello,

Check if the structure you are using for your screen/context has explicit links to which fields should be used to provide the search help's input fields.

You may need to create your own structure - or ensure that you populate the field your context that maps to the field referenced in the structure's search help definition.

It is strange that it is looking for the attribute "LANGU" as the search help is dependent on the T517T SPRSL field - definately check the structure you are using in your context!

Chris

Former Member
0 Kudos

Thanks for the reply, Chris.

What is odd is my context contains the field SLART and since I pulled most of the fields for infotype 0022 from the dictionary, it automatically defaults the "determined input help" property to H_T517T for the field SLART which is correct.

I just wasn't aware that I would need to supply the LANGU or in the case of the search help H_T517T with a value for SPRSL. I thought it would be automatic. I did not think I was going to have to do something to ensure the SPRSL is populated for the standard SAP search helps.

Johnny

Former Member
0 Kudos

Got around this problem by creating my own search help instead of the standard SAP search help that were automatically being called for SLART. In the context, I pointed to my custom search help which defaults to "EN" when performing the search.

There is probably many other ways to resolve this issue and my solution might not be the best, but it works for now.