topic Re: issue with custom table selection screen in Application Development and Automation Discussions

issue with custom table selection screen

pashasapcha — Sat, 04 Nov 2023 13:14:37 GMT

I have created custom table and uploaded 161 entries. When I execute the table and then click on contents it gives selection screen to fetch necessary records from table. Now I have placed record which is already available in the 161 entries. I want to see one specific record. When I execute no entries found. When I see Number of entries without giving any entires it is showing 161. How to fix this issue.

when I click on number of entries in the above pic it is showing 161 entires. But when I pick one record and place it in MATNR and then F8. it is showing as below.

1020001205 do exist in the 161 records present in the table.
but it is showing as highlighted No table entries found for specific key

Re: issue with custom table selection screen

Sandra_Rossi — Sat, 04 Nov 2023 14:50:52 GMT

Classic issue concerning different internal and external values due to the Conversion Exit on MATNR.

i.e. what you are SEEING is not what is actually in the database.

Re: issue with custom table selection screen

pashasapcha — Mon, 06 Nov 2023 04:07:12 GMT

You can see that it is same as in the database table.

Re: issue with custom table selection screen

RaymondGiuseppi — Mon, 06 Nov 2023 07:03:34 GMT

The problem does not always occur at the selection or display level.

The problem may have occurred when filling the database table with records that are not consistent with the data definition. (For example, a field such as MATNR = '1020001205' + trailing space is not consistent; it should not have leading spaces but trailing zeros, zeroes which are removed when interacting with dynpro.- check for your system configuration)

Also, when you try to select this value, the entry in the selection screen is converted to a correct internal format that does not exist in the database table,

What you see in the selection screen is not what is transmitted to the program (try debug).
What you see in SE16n is not always database value, check option to deactivate conversion exit (or debug)
Look for the conversion exit in MATNR domain and perform some SE37 tests

Re: issue with custom table selection screen

Sandra_Rossi — Mon, 06 Nov 2023 08:19:58 GMT

Exactly what I said, what you are SEEING is not what is actually in the database.

By default, SE16 converts the value in database => see conversion exit.

Questions about conversion exits are probably the most common questions in the forum, no doubt that you will find links.