Skip to content
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

Error message EC473 (SAP note 2159455) #3

Closed
jormun-pluxml opened this issue Sep 12, 2018 · 6 comments
Closed

Error message EC473 (SAP note 2159455) #3

jormun-pluxml opened this issue Sep 12, 2018 · 6 comments
Assignees
Labels

Comments

@jormun-pluxml
Copy link

@jormun-pluxml jormun-pluxml commented Sep 12, 2018

some recent NW version cannot import anymore SAPLINK files...
see https://blogs.sap.com/2016/03/22/fix-saplink-regarding-message-ec473-sap-note-2159455/

@mkysoft mkysoft self-assigned this Sep 12, 2018
@mkysoft mkysoft added the bug label Sep 12, 2018
@mkysoft
Copy link
Contributor

@mkysoft mkysoft commented Sep 13, 2018

We can use abapgit for newer system, we are updating this repo for old systems.

@jormun-pluxml
Copy link
Author

@jormun-pluxml jormun-pluxml commented Sep 13, 2018

Thanks for your reply. This quick answer is correct, but a little restrictive.
abapgit does not cover all the scope of saplink :

  • It is not possible to import/export a single program/project if it dont have a dedicated package. Some customer dont allow package creation for any new dev... (i found a way to export a single object or a transport request, but not a list of single objects inside 1 file like a nugg)
  • abapgit is online oriented. Very few SIMPLE possibilities for offline configuration. Some of my users (people that use .nugg i give them) find that it is already "not easy" to install saplink before upload of the NUGG in their system. So, ABAPGIT, with server or local repo configuration (with sometime sap admin auth to ask or it auth...) is not an option.
    So, even if abapgit is wonderfull for lot of reason, it is not a full replacement for saplink :-(
@gregorwolf
Copy link
Contributor

@gregorwolf gregorwolf commented Sep 13, 2018

Then I would suggest that you help to develop the missing features in abapGit or providing a pull request to fix the issue in SAPlink.

@mkysoft
Copy link
Contributor

@mkysoft mkysoft commented Sep 13, 2018

Then I would suggest that you help to develop the missing features in abapGit or providing a pull request to fix the issue in SAPlink.

I am working on it. I can't find correct version for getting testing which is described in note.

@jormun-pluxml
Copy link
Author

@jormun-pluxml jormun-pluxml commented Mar 8, 2019

Thanks a lot :)

FoxAhead added a commit to FoxAhead/SAPlink-plugins that referenced this issue Jun 26, 2019
This is the same fix as was done for ZSAPLINK_PROGRAM class. It is related to PF-status inconsistency due to incomplete ADM-structure.
sapmentors/SAPlink#3
@pokrakam
Copy link

@pokrakam pokrakam commented Oct 30, 2019

@jormun-pluxml

  • abapgit is online oriented. Very few SIMPLE possibilities for offline configuration. Some of my users (people that use .nugg i give them) find that it is already "not easy" to install saplink before upload of the NUGG in their system. So, ABAPGIT, with server or local repo configuration (with sometime sap admin auth to ask or it auth...) is not an option.
    So, even if abapgit is wonderfull for lot of reason, it is not a full replacement for saplink :-(

I know it's a little unrelated to this issue and it's already closed, but I though it's worthwhile to respond to this comment.
It's _very_easy to work with abapGit offline. Create a report, paste the code and run. Create offline repo (it will even create the package for you) and upload your zip. Takes all of 2 minutes.
Yes you do need a package but really it's hardly a dealbreaker. just create a local one. This is usually a good thing.

pokrakam added a commit to pokrakam/SAPlink-Git that referenced this issue Mar 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants