google-code-export / saplink

Automatically exported from code.google.com/p/saplink
1 stars 2 forks source link

SAPLink raises exception while creating a nugget file #72

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run SE38
2. Run ZSAPLINK
3. Choose "Create new nugget"
4. Nugget Name -> "test"
5. Press Execute
6. Choose c:\ as path
7. Use "NUGG_TEST.nugg" as filename
8. Press "Save"

What is the expected output? What do you see instead?
Expected: New Nugget file
Instead: ABAP Short Dunmp

What version of SAP are you using?
SAP_ABA Release / Level: 640 / 0009
SAP_BASIS Release / Level: 640 / 0009
It's a Unicode System!

What version of SAPlink are you using:
0.1.3

Please provide any additional information below.

While creating a new nugget file, SAPLink raises an exception and
produces a short dump in the method GUI_DOWNLOAD at line 67. 

Check attached file...

Best,
Konrad

Original issue reported on code.google.com by konrad.h...@tesis.de on 20 Jun 2007 at 2:52

Attachments:

GoogleCodeExporter commented 9 years ago
I had the same problem and I have the same support package level but not 
unicode.
debugging showed that DAT is not an acceptable file type. so I changed the 
following
form a bit:

form putOnMachine using fullpath type string xmlString type string.

I changed the hard-coded 'DAT' to 'ASC'. seems to work but use this on your own 
risk:

call method CL_GUI_FRONTEND_SERVICES=>GUI_DOWNLOAD
          exporting
            FILENAME = fullpath
            FILETYPE = 'ASC'
          changing
            DATA_TAB = tempTable_char.

Original comment by stefaneg...@gmail.com on 29 Jun 2007 at 8:37

GoogleCodeExporter commented 9 years ago
Hi!
In my case the filetype is ".nugg". But I will check the code if I can modify 
it like
you did so that I can export my stuff!

Thanks,
Konrad

Original comment by konrad.h...@tesis.de on 29 Jun 2007 at 9:49

GoogleCodeExporter commented 9 years ago
I think the solution proposed in issue 68 is way better.

Original comment by marcello...@gmail.com on 27 Jul 2007 at 7:09

GoogleCodeExporter commented 9 years ago
Hi!

What has issue 68 (http://code.google.com/p/saplink/issues/detail?id=68) to do 
with
this problem?

Thanks and greetings,
Konrad

Original comment by konrad.h...@tesis.de on 31 Jul 2007 at 7:56

GoogleCodeExporter commented 9 years ago
Here is the .patch file

Original comment by sandra.r...@gmail.com on 25 Nov 2007 at 12:03

Attachments: