New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ABAP SDK For Azure installation with 750 version #89
Comments
are you using the latest abapGit version? SUCU is natively supported in abapGit since https://github.com/abapGit/abapGit/blob/master/changelog.txt#L448 |
I followed the installation guide here. Install standalone version step1 - points to code for ZABAPGIT_STANDALONE - I opted this as i am not looking for developer version Also, from abapgit client, used online option. |
Any thoughts on how to resolve this one? |
are you using the latest abapGit version? the version is listed in the bottom of each abapGit screen, please do a screenshot and paste it here, |
https://github.com/abapGit/abapGit |
okay... does the class |
No, it doesnt. |
Any suggestions here? |
Ok, Are you planning to fix that, and how long it would take? |
so, @microsoft has not updated https://github.com/microsoft/ABAP-SDK-for-Azure/blob/master/src/zadf/zsdk%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20s_tabu_dis.sucu.xml to use the native abapGit SUCU handler as raised as issue 2 years ago, https://github.com/microsoft/ABAP-SDK-for-Azure/issues?q=is%3Aissue+SUCU+is%3Aclosed so, try installing https://github.com/abapGit/abapGit-Plugins to the local system |
Installing developer version of gitclient and abapgit handlers resolved the above issue |
Hi, I tried to install ABAP SDK for AZURE for users version. after connecting to Online repo, the objects got pulled into system and see below error after all the objects were activated.
"Object type SUCU not supported, serialize import of object ZSDK S_TABU_DIS failed."
not sure of which functionality effected by not importing the above object. Could you please tell wat are the next steps to address it?
The text was updated successfully, but these errors were encountered: