Application Development and Automation 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: 

Strange filter problem in SE16N (wrong data domain?)

former_member504446
Participant
0 Kudos
949

Dear gurus,

I wrote a report to import data from a txt file into a Z-db-table. It works well, but I found a strange thing when viewing teh data using SE16N:

Alle entries are displayed no problem. But when I try to set a filter on any Char-field in the table, no rows are shown. But when I use a * at the end of the filter term, it works properly.

E.g. there is a field with domain CHAR020. There are several rows with value "test" in that field. Now, when I set a filter for test, no row is shown. But when I use test* instead, the filter result is correct.

Is it possibly that somehow the domain I used messes with the filter? Or any other ideas?

Cheers
Alicia

2 REPLIES 2

yogananda
Product and Topic Expert
Product and Topic Expert
0 Kudos
875

alicia.moore

Fields of CHAR data type do not support space or special characters in value help filtering. Whenever you try filtering for values that contain space, the results will not be displayed if you i...1.

You can also refer to the SAP Community post2 for more information.

I hope this helps. Let me know if you have any other questions.

RaymondGiuseppi
Active Contributor
875

Check for domain with conversion-exit (or routine)

If you do not convert the data correctly when uploading, you will encounter problems because the standard tools expect correct data format. (If you put external data in the field, the display will appear correct but many other functions such as filtering and sorting will not work properly).

  • The upload program must use the available Function Module to convert from external format to internal format.
  • If data already input in production, consider building a small report to correct data (select/CONVERSION_EXIT_*_INPUT/update) but be ready to handle problem during update for duplicate keys and the like.