This release corrects some minor bugs and the nugget file is better sorted to allow upload for new installs easier. There is still a bug in our SAPLINK, which requires two loads before all objects can be correctly loaded on a new system. Just execute SAPLINK twice and all object should go in for activation. If you find problems, let me know.
Bug list corrected:
- The table version check for the rfc link between systems has been removed as it was only working with connected systems.
- The error log handling as been further improved.
- Screen handling is corrected ( exit buttons)
- Refresh issue is resolved
let me know if you find any issues.
This is just a small correction for cross client table updates. The insert and update was not working correctly, if you have been trying to update data in a different client than the logon client.
You need to have 2.02 installed prior to this upgrade. This upgrade contains only class Z_C_SY6_GRID.
Version 1.20 contains only bug fixes. Only minor changes in functionality. There have been a few problems with insert and copy, which have been resolved.
To proper install the code you will need the latest daily build for saplink. This has to be revision 338 or higher.
Over the last month I have started contributing to a very interesting project I found on code.sdn.sap.com. This project has the goal to create excel files directly with abap code. There is no office integration needed through the GUI and files can be created therefore even in the background. A lot of effort has been already but in the first versions of this great idea. In the moment version 7 is in the works and version 6 has been released beginning of this year. There is a lot of work pending, but it is already very much usable and has already a big fan base (more than 300).
I can only recommend to have a look and try it out. Here you can find more info ABAP2XLSX.
Version 1.10 contains only bug fixes. No changes in functionality.
There have been several issues with the screen flow, which are now resolved and also the error handling with validated reference fields has been improved.
In SAP we have plenty variations to read and maintain tables, but as soon as you are in a production system and want to make a fast correction, than it gets complicated. The transaction ZSY666 allows you to maintain almost any table and therefore can help in these desperate situations. This means you should only do it, when there is no other choice. This transaction can help when you are in trouble, but also can bring you in a lot of trouble.
Consider yourself warned and use it with care.
You can download the code from my downloads page.
I have developed at my company Instrumentation Laboratory a textobject to solve the problem of tracking changes for text maintenance. This idea has evolved into an interface for text maintenance and several other possibilities including HTML maintenance, full text search and an interface into SAP standard text maintenance.
So here is now my first version of the text object. All the code is based on nuggets with SAPlink. If you want to get more information please checkout the following article: Tex-Editing with Notes – Logic.
To be able to make use of the code you first need to download and install SAPlink on your system. You can either go to Saplink or down load everything from my downloads page.
Let me know what you think.