<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>enhancements on Abapinho</title><link>https://abapinho.com/en/tags/enhancements/</link><description>Recent content in enhancements on Abapinho</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2009-2026 Nuno Godinho</copyright><lastBuildDate>Mon, 13 May 2019 09:00:00 +0000</lastBuildDate><atom:link href="https://abapinho.com/en/tags/enhancements/index.xml" rel="self" type="application/rss+xml"/><item><title>Implicit enhancements in data structures</title><link>https://abapinho.com/en/2019/05/enhancements-implicitos-em-estruturas-de-dados/</link><pubDate>Mon, 13 May 2019 09:00:00 +0000</pubDate><guid>https://abapinho.com/en/2019/05/enhancements-implicitos-em-estruturas-de-dados/</guid><description>&lt;p>We have all used implicit enhancements to add code to the beginning or end of a standard function, form or method. But you may not know that it can also be used to add fields to data structures, whether they&amp;rsquo;re declared as TYPES or directly as DATA.&lt;/p></description></item><item><title>Fix bug in SAP standard using an implicit enhancement</title><link>https://abapinho.com/en/2016/03/corrigir-erro-em-codigo-standard-com-enhancement-implicito/</link><pubDate>Mon, 14 Mar 2016 09:00:57 +0000</pubDate><guid>https://abapinho.com/en/2016/03/corrigir-erro-em-codigo-standard-com-enhancement-implicito/</guid><description>You just found a bug in a standard FORM (or FM or METHDO):
FORM EQUAL_VALUE CHANGING W_DATE TYPE SYDATUM. W_DATE = SY-DATUM - 1. ENDFORM. You report the error to SAP but you know it will take them several days, weeks or months to publish a correction. And you need it corrected right now.
You decide to act.
So you use the implicit enhancement at the start of the FORM to replace the standard code with your own (just until the correction arrives, of course):</description></item><item><title>Good program to find user-exits</title><link>https://abapinho.com/en/2012/08/encontrar-user-exits/</link><pubDate>Mon, 20 Aug 2012 09:00:00 +0000</pubDate><guid>https://abapinho.com/en/2012/08/encontrar-user-exits/</guid><description>Every now and then we’ll be looking for user-exits and BADIs, BTEs and the like. SAP doesn’t help. But programs appear here and there, almost always called Z_USEREXIT, which help with this unappreciated search. Recently I learned of another one. I share it here because it is the best I have ever seen:
https://wiki.sdn.sap.com/wiki/display/Snippets/Find+User-exits,+BADIs,+BTEs,+Etc+by+TCode+or+Program
Thanks to Bruno Esperança for the tip. And thank you rverscha for the photo.
Greetings from Abapinho.</description></item><item><title>Implementing private methods in BADIs</title><link>https://abapinho.com/en/2012/03/metodos-privados-em-badis/</link><pubDate>Mon, 19 Mar 2012 10:00:09 +0000</pubDate><guid>https://abapinho.com/en/2012/03/metodos-privados-em-badis/</guid><description>&lt;p>A little while ago I had an idea as eccentric as it was amazing that today I have decided to share here, namely, how to create private methods in BADI classes.&lt;/p>
&lt;p>Let me explain.&lt;/p></description></item></channel></rss>