"The parser produced the error: "DDLANGUAGE" is not" - Error when trying to Read a table with field filter

[kacisse]

Hi,

I made a function to read from a table with pagination, rowskip etc...It works well with most field filter but some of the fields are a mystery (while confirmed existing in the table I'm trying to read).
For ex:

await foreach (var r in _sap.ReadPagedAsync("DD02T", new[] {"TABNAME","DDLANGUAGE","DDTEXT"}, null, new List<string> { $"TABNAME = '{table}'", $"DDLANGUAGE = '{_spras}'" }, _pageSize))

DDLANGUAGE has been a huge problem in table DD02T, now the only workaround that I have is to go through the hundred of thousands of lines and filter one by one using the DDLANGUAGE because it wouldn't work. We only get a truncated error: "The parser produced the error: "DDLANGUAGE" is not"
I got the same issues with one or two other fields but I can't remember.

Any experience like that before ? Any feedback or help would be much welcome.

Best.

[huysentruitw]

This doesn't look like an error coming from the library, so it's a SAP issue or the way you're calling the function. Have you figured this out yet?

[kacisse]

Hi, sorry I never saw your answer, I have never been able to solve it so the only solution for me was to extract the whole thing and filter line by line...
It happened on several filters, but mostly the language for example. I'm suspecting that the library is not able to match the exact type of the language field for ex. I'm not sure, but that would be a game changer for my project if I could filter properly :)

[tom-j-irvine]

First, I'll repeat what @huysentruitw said since it seems like you might be getting an error from your SAP function, not the library.

In addition to this, I'll point out something about DDLANGUAGE that could be your issue. In the actual SAP database, DDLANGUAGE is a single character, case-sensitive value. But, when you interact with it in SAP GUI, it goes through a conversion exit that convert two-character ISO codes to the internal single-character value stored by SAP.

If you view the table in SE16, you'll see the actual single-character value. But in something like SE16N, you'll see the converted value. You can see the mapping in table T002. As an example, SPRAS A = Arabic (LAISO AR) but SPRAS a = Afrikaans (LAISO AF). So, you might try using the single-character value for the language you need, though this really depends on what the RFC function is actually doing.

At this point, I'm just guessing about a common issue. If you would like further input, please provide additional detail about the function you are calling because your small code snippet doesn't reveal any of the necessary details.