search

google-code-export / saplink

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

No OTR texts in exception class ZCX_SAPLINK #33

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. install SAPLink
2. provoke an error in SAPLink that will raise an exception

What is the expected output? What do you see instead?

expected output: meaningful error message
actual output: no error message.

What version of SAP are you using?
SAP_ABA Release 640 / Level: 3
SAP_BASIS Release 640 / Level: 3

What version of SAPlink are you using:
SAPlink_install-0.1.2.zip

Please provide any additional information below.

later manual edits of the texts somehow doesn't work. I observed this on
two different systems.

Original issue reported on code.google.com by nicola.f...@gmail.com on 26 Dec 2006 at 2:08

GoogleCodeExporter commented 9 years ago 
What language are you logged in when you install and then run saplink in?

Original comment by daniel.m...@gmail.com on 27 Dec 2006 at 3:28

GoogleCodeExporter commented 9 years ago 
I removed my name, from the owner box.  Not really sure how it got there.

Original comment by rquacken...@gmail.com on 28 Dec 2006 at 4:00

GoogleCodeExporter commented 9 years ago 
I put it there, figured if this is a real issue we probably want to fix it for 
the
next version.

Original comment by daniel.m...@gmail.com on 28 Dec 2006 at 4:17

GoogleCodeExporter commented 9 years ago 
I installed SAPLink while logged in in english, the same language I use to run 
it.

Original comment by nicola.f...@gmail.com on 2 Jan 2007 at 11:07

GoogleCodeExporter commented 9 years ago

Original comment by ewherrm...@gmail.com on 29 Jan 2007 at 10:22

GoogleCodeExporter commented 9 years ago 
The function module for creating OTR texts changed from 6.20 to 6.40+.  It no 
longer
supports creating OTR concepts with default guids passed in.  Because of this, 
the
OTR text was being created as a new guid, but the class wasn't being updated 
with the
new number.  Due to this change, we have changed the way OTR's are being 
created. 
Instead of trying to recreate the OTR with the old guid, we always create new.  
The
xml document for exception classes will now change the exported OTR guids to 
blank. 
This issue is fixed in 0.1.3

Original comment by ewherrm...@gmail.com on 5 Feb 2007 at 3:19

GoogleCodeExporter commented 9 years ago

Original comment by ewherrm...@gmail.com on 5 Feb 2007 at 7:25