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

Existing data are not found when filtering on a particular field in SE16N

0 Kudos

Hello,

We have created DB table with append structure while an existing data is not found when filtering on a particular field from this table in SE16N. What could be the reason?

Data extraction without filter:

{1-succeed 2-failed}

Data extraction with filter{1}

Data extraction with filter{2}

Relevent field details:

1 ACCEPTED SOLUTION

raymond_giuseppi
Active Contributor

As already written, this is a conversion-exit problem. Note that your database data are now no longer consistent with ddic definition.

You MUST:

  • Correct the program[s] that created those records without respect for the expected internal format. (some upload/move/insert fast written program?)
  • Correct current/legacy data (should be easy as this field does not appear to be some unique key)

Hint: FM CONVERSION_EXIT_ALPHA_INPUT (External format -> Internal format)

5 REPLIES 5

Tomas_Buryanek
Active Contributor
0 Kudos
  • Is it the same in SE16?
  • Maybe there is "Non-breaking space" in second value? Because it has only 8 characters visible but LIFNR can have up to 10. (check value in debuger in hexadecimal view)
-- Tomas --

0 Kudos

Yes Tomas this could be true, this could be possible certainly. I faced a similar issue once and the issue was with the invisible non-breaking spaces.

Probably before data entry into the table (if done through a program), the variable with LIFNR value can be cleared of any spaces with a CONDENSE statement with or without the addition of NO-GAPS

JL23
Active Contributor

go back to the main screen of SE16N, click the settings button (Ctrl+F12) and activate the box for output without conversion exit. Then repeat the Data extraction without filter. Maybe the numbers are differently maintained, e.g. one with leading zeros the other without leading zeros.

Tomas_Buryanek
Active Contributor
0 Kudos

True. LIFNR has conversion exit ALPHA.

-- Tomas --

raymond_giuseppi
Active Contributor

As already written, this is a conversion-exit problem. Note that your database data are now no longer consistent with ddic definition.

You MUST:

  • Correct the program[s] that created those records without respect for the expected internal format. (some upload/move/insert fast written program?)
  • Correct current/legacy data (should be easy as this field does not appear to be some unique key)

Hint: FM CONVERSION_EXIT_ALPHA_INPUT (External format -> Internal format)