on 12-22-2016 8:41 AM
Hi all i got a dump in SEGW transaction during the following scenario:
i debugged the standard a bit and i found out that there is some kind of issue in retrieving the Transport Request correct when a newer one is create for some different object.
The solution i found (more a workaround) is to release the cr (which will go wrong during the import into Test and Prod systems) and re-generate again the service, creating a new CR.
I tried to search for OSS notes but i cannot find anything related this (or maybe i'm putting the wrong keywords in search....).
Anyone experienced the same?
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.