search

google-code-export / saplink

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

Proper treatment of development classes while exporting / importing #36

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. export an object from source system
2. import the object into destination system

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

expected: the newly imported object in the destination system is in the
same dev. class as the exported object in the source system

actual: the newly imported object in the destination system is in the dev.
class $TMP.

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:
0.1.2

Please provide any additional information below.

Original issue reported on code.google.com by nicola.f...@gmail.com on 27 Dec 2006 at 9:16

GoogleCodeExporter commented 9 years ago 
This is by design. What happens if the target system doesn't have the Devclass, 
or
worse has it with the same name as in the incoming object but, won't hold the
incoming object.

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