12-22-2014 7:31 AM
Hi All,
I am facing a weird issue here.
I go to SE16, put table name.
I execute table without any input in selection screen.
I get all records from table.
But if I put above highlighted VBELN on selection screen, I don't get the result.
I tried padding 0, * , nothing works.
This issue is coming with few records only, as if I chose some other single record, it works.
Please help, what could be the issue?
12-22-2014 5:45 PM
Hi Neminath
I have faced this issue earlier.
The problem was with "CONVERSION EXIT".
Although you say that you have uploaded it with leading zeroes as you can see in the table entries : But this might not be the actual case. Issue is : during uploading those entries without conversion exit or whichever way you uploaded but was not same for the one which you are facing problem.
Since mine was a quality system , I deleted all the entries and uploaded it again.(worked for me).
But in your case since it is production system.
I suggest you to find those entries in production .Upload again(Using Conversion routine) in development
system and release it to production through CUSTOMIZING TR.
Then delete the duplicate entries in production(if any).
That is the only possible solution.
Thanks
Kishan Shah
12-22-2014 7:35 AM
Hi Neminath,
Strange issue!!!
Is it working fine in SE11 and SE16N? Did you give a try?
12-22-2014 7:40 AM
Hi Archana,
Thanks for your reply.
SE11, SE16, same output.
I have already tried.
12-22-2014 7:38 AM
Hi,
Hope you are using the same Data element for VBELN, which is provided by the SAP.
Regards.
Praveer.
12-22-2014 7:41 AM
12-22-2014 7:41 AM
It seems you are finding an entry in some Z table. It might be possible that you have uploaded some data into Z table without using Conversion Exit. So, some data may not have leading zeros and some may have leading zeros. Kindly check the same.
12-22-2014 7:43 AM
Hi Viraj,
I checked that, all data have leading 0s.
I have uploaded the screenshot above.
And while searching I have tried all the possible way to search.
12-22-2014 7:45 AM
12-22-2014 7:50 AM
12-22-2014 8:50 AM
When i tried using wild char * its working
But wild card needs to be put on both side. This is again a weird thing.
12-22-2014 9:26 AM
Please delete all entries from the table and upload with proper Conversion.
12-22-2014 9:30 AM
This can be one solution but as this in production, this solution still invalid for my case.
12-22-2014 9:38 AM
Hi,
Try to Use SE14 T-Code and adjust the table once.
May be some confliction is there.
Regards.
Praveer.
12-22-2014 9:44 AM
12-22-2014 1:33 PM
Hi Neminath
Execute SE16N full table without conversion routine and see how many records have leading zeros and how many records are without leading zeros. You will definitely see the difference
12-23-2014 5:41 AM
Hi Viraj,
With or Without conversion exit, I am getting same number of records and that to with leading zeros.
12-22-2014 5:45 PM
Hi Neminath
I have faced this issue earlier.
The problem was with "CONVERSION EXIT".
Although you say that you have uploaded it with leading zeroes as you can see in the table entries : But this might not be the actual case. Issue is : during uploading those entries without conversion exit or whichever way you uploaded but was not same for the one which you are facing problem.
Since mine was a quality system , I deleted all the entries and uploaded it again.(worked for me).
But in your case since it is production system.
I suggest you to find those entries in production .Upload again(Using Conversion routine) in development
system and release it to production through CUSTOMIZING TR.
Then delete the duplicate entries in production(if any).
That is the only possible solution.
Thanks
Kishan Shah
12-23-2014 5:23 AM
Not the only solution. I'd write a fix program that scans the Z table and converts any data not loaded with leading zeros so that they have leading zeros.
12-23-2014 5:33 AM
Hi Matthew,
Possible Solution..!!
But my only concern is there will be a lot more entries since it is a production system and scanning the complete Ztable just for few records
Thanks and Regards
Kishan
12-23-2014 5:46 AM
Hi Kishan,
Thanks for your reply!
But this is the solution, I am searching for the rout cause for this.
My user has uploaded all the records in same may using table maintenance.
So why only few records have the issues.
As you said, Yes the best way to get rid of this problem is to delete and upload new entries.
How to do that is depends.
But as this is the incident reported, I need to know the rout cause of this issue.
Thanks for your reply!
12-23-2014 5:52 AM
Hi Neminath
Ask your user : file/mode through which he uploaded the entries..!!
Use them as a test cases and upload/replicate in test/development system.
Then check the issue..??
I think you will get your root cause by following this way..!!
Thanks and Regards
Kishan
12-23-2014 6:06 AM
No offence but that is a usual reply an end user would give. Whereas the reality is, he must has uploaded some of the records manually and entered the document number without leading zeros as while manual entry no one writes leading zeros.
12-23-2014 7:09 AM
How many records? If you're talking a few thousand - that's trivial. With a few million, use OPEN CURSOR to process the records (e.g.) 10'000 at a time.
It should be a one off fix - but it's the only way to get all the failures. (Other than reloading which is going to take you a long time as well).
What you must do is ensure whatever process you're using to load this data doesn't allow records without leading zeros. The original loading program should have put them in - relying on the users to get the data right is not wise.
12-23-2014 6:20 AM
12-23-2014 7:00 AM
12-23-2014 7:20 AM
12-23-2014 9:57 AM
Hi Neminath
This post is unnecessarily getting extended with the same set of solutions.
Request you to please close the thread.
12-23-2014 10:42 AM