02-04-2011 4:11 AM
Hi, I have a select statement, without any restrictions/conditions on the table ERDK.This fetches some records.
But when I try to get the same records through SE16n or SE11, it says no data found. Any idea why. Because I dont want the records to show in the select statement. These records mess up the calculations.
02-04-2011 4:35 AM
Hi,
Please give details of fields of ERDK that you have used in SE16N.
Dhiraj.
02-04-2011 4:17 AM
02-04-2011 4:35 AM
Hi,
Please give details of fields of ERDK that you have used in SE16N.
Dhiraj.
02-07-2011 7:33 AM
Hi Suhas, Below is the select statement i use
SELECT opbel
stokz
intopbel
vkont
abrvorg
FROM erdk
INTO CORRESPONDING FIELDS OF TABLE i_erdk
FOR ALL ENTRIES IN i_ever
WHERE vkont = i_ever-vkonto
AND loevm = ' '
AND stokz = ' '
AND ergrd NE '03'
AND simulated = ' '.
My question is, this statement fetched a line with opbel = '61007232'.
When I try to get the line in SE16N/SE11, it says 'No values found'. I would like to know, why the line is not showing in SE16N but shows in the select statement.
Dhiraj, while running SE16N, i mention only the opbel field [61007232] for selection criteria.
In case you need further information on my queries, please do let know.
02-07-2011 8:45 AM
I suppose the line with opbel = '61007232' is for a different client (field mandt).
02-07-2011 3:25 PM
You probably used a range or pattern in SE16N. There is a conversion exit for this field.
Rob
02-08-2011 3:50 AM
Hello Joe, Now I tried with "client specified" and mandt = 100, the record is still showing.
Rob, I was not using pattern. But now tried using it... it worked!!!
02-08-2011 4:00 AM
I mean, I tries se11, with opbel = *7232, now the record is showing...
Thank you everybody for the help.
02-08-2011 7:49 AM
Strange.
But in this case I suspect there is some nonprintable character within the visible 61007232.
For example I have seen cases where due to some misconfiguration the backspace key did not work as intended, but was inserted into a database field.
Let's assume you have this:
619<backspace>007232
Then on your screen the backspace will work as intended, and you will see, you guess it:
61007232
regards
02-09-2011 3:26 AM
Strange indeed.
I tried different patterns for this document, whatever the non-printable character is, must be before the first digit.
Because, SE11 could show me the line with all these inputs , '61007232', '1007232', '007232', '07232', '7232', '232', '32', '2'. I assume the non-printable char, if any, must be in the front of the number.
Is there any way we could find what character it could be.
And thanks for your answers.
02-09-2011 7:31 AM
Hello Joshva,
an interesting problem, I think.
And of course there are ways to find what character it could be.
But not sure which way would be the most convenient.
The idea is this: Instead of strings or characters get the ascii values of the characters.
As far as I know this will be not easy in ABAP . But I may be wrong here. Actually I am not an abapper, but a basis administrator.
But anyway, have a look at your ABAP manual!
Another approach will be: Ask your database administrator for help.
The exact procedure will depend on the database your SAP system is using.
In case of Oracle it will be:
select dump(opbel,16) from erdk
where opbel like '%61007232';
hope this helps
02-10-2011 2:59 AM
02-10-2011 4:31 AM
I don't see any problem with the way you able to get the records in your ABAP or using SE11 / SE16. It is because the field OPBEL has ALPHA conversion exit, while storing the data at DB level, it would be padded with zeroes. In your case data record value (OPBEL) 61007232... try with leading zeros (field length 12) 000061007232, it should work.
ABAP, you don't have to do any thing as I see from the statement, you are using "FOR ALL ENTRIES IN" of an internal table which I believe you are reading that data from another table...
02-10-2011 6:42 AM
Hi Anjaiah. I tried padding with zeroes. Still not showing.
It is not an issue anymore because I am able to see the record now. But, I am wondering why it is not showing.