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: 

Answer to Che's question about NUMC in SE16 exports from Standard Lists

Former Member
0 Kudos

Hi Che -

This is in reply to the question you asked in my blog post here:

/people/david.halitsky/blog/2010/08/04/ok--whats-the-deal-with-numc-fields-in-46c-se11se16-extracts

The answer is that the volume of data which I have to export from 4.6C prevents me from using the ALV display.

This of course raises the question of whether the problem here is really that I'm trying to use SE16 to do something it wasn't designed to do, i.e. that I should have written a "one-off" ABAP foo program to get the data out of 4.6c.

But here's where the problem gets interesting, at least "politically" . To see what I mean, check back at the blog post itself.

4 REPLIES 4

che_eky
Active Contributor
0 Kudos

David,

I did not suggest you use the ALV display, rather the SE16 standard list display. Like I said if you use the standard (classical) list display then NUMC fields appear on screen with leading zeros and these are retained when downloading to Excel.

For one off extracts I do not see a problem with using SE16, if you can make it work. As you say for large or repeated extracts then a custom extract is the way to go.

Che

0 Kudos

Hi Che -

What system did you try SE16 standard list on? (4.6c, 4.7, 5, or 6?)

Also, exactly how are you exporting the Standard List?

As I mentioned, on this 4.6C system, when I extract from it and open the file on my PC in Excel (2007) as tab-delimited and declare the field as text in advance of opening, I get no leading zeroes and an indeterminate number of spaces.

If you're doing this on 4.6C then either there IS a patch that hasn't been applied to the 4.6C system here, OR I'm not exporting the standard list the way you are ...

Thanks

djh

che_eky
Active Contributor
0 Kudos

Hi David,

My results are based on SAP ECC 6.0 using the following steps:

I am using SE16 on table ANLA with the table display restricted to the NUMC columns of interest:

ANLTP ZUJHR ZUPER ANEQK ANEQS URJHR LEJAR LEPER LRYTH AIMMO POSNR

It is important to switch the display to the standard list display (not ALV):

>Settings>User Parameters>)(o) SE16 Standard List

Here is a cut and paste from the SE16 display (paste it into Note pad to see the formatting):

ANLTP ZUJHR ZUPER ANEQK ANEQS URJHR LEJAR LEPER LRYTH AIMMO POSNR

0 2010 001 1 0 000 000 000 1

0 2010 001 1 0 000 000 000 0

0 2010 001 1 0 000 000 000 0

0 2010 001 1 0 000 000 000 0

0 2010 002 1 0 000 000 000 0

So we can see above that leading zeros are displayed as we would expect for NUMC fields.

I then download the list using:

>Edit>Download>(o) Spreadsheet

Download the data using the default .XLS file extension.

Next open Excel (Excel 2010 is what I am using) and import the file:

File>Open><your file>

I then import the file as a delimited file of type Tab with all fields formatted as type Text. Below is a cut and paste from the spreadsheet showing the columns imported (paste it into Note pad to see the formatting):

ANLTP ZUJHR ZUPER ANEQK ANEQS URJHR LEJAR LEPER LRYTH AIMMO POSNR

0 2010 001 1 0 000 000 000 1

0 2010 001 1 0 000 000 000 0

0 2010 001 1 0 000 000 000 0

0 2010 001 1 0 000 000 000 0

0 2010 002 1 0 000 000 000 0

As we can see above the NUMC fields have retained their leading zeros on import. Field ZUJHR (similar to URJHR) is imported left aligned.

Sorry for the lengthy post, not preaching, but it may help to see where things are deviating.

Che

0 Kudos

No need to apologize for all the details, Che - they wonderfully confirm what I originally suggested:

this is a 4.6c problem that was either never fixed by SAP in 4.6c, or was fixed by a 4.6c patch that my cliient never applied.

The reason your details confirm that it must be one of these two possibilities is because I have been doing exactly what you're doing, just in 4.6c, not in ECC 6.

Thanks agian for helping to make the nature of the problem crystal-clear. There may be some 4.6c users out there who will want to investigate whether they need to patch their systems, and if so, whether patch for this problem existed in 4.6c.