<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ddic on Abapinho</title><link>https://abapinho.com/en/tags/ddic/</link><description>Recent content in ddic on Abapinho</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2009-2026 Nuno Godinho</copyright><lastBuildDate>Mon, 24 May 2021 09:00:11 +0000</lastBuildDate><atom:link href="https://abapinho.com/en/tags/ddic/index.xml" rel="self" type="application/rss+xml"/><item><title>Change selection screen texts without hard coding them</title><link>https://abapinho.com/en/2021/05/manipula-textos-de-seleccao/</link><pubDate>Mon, 24 May 2021 09:00:11 +0000</pubDate><guid>https://abapinho.com/en/2021/05/manipula-textos-de-seleccao/</guid><description>&lt;p>Even though many ABAP programmers tend to forget this, the less texts you hard code in your program the simpler it will be to translate it.&lt;/p>
&lt;p>Here&amp;rsquo;s a simple but rather obscure way to manipulate selection screen texts while still being able to translate then. This way you can, for example, prefix them with icons.&lt;/p></description></item><item><title>The curious case of the partially protected structure</title><link>https://abapinho.com/en/2016/12/o-estranho-caso-da-estrutura-parcialmente-protegida/</link><pubDate>Mon, 26 Dec 2016 09:00:10 +0000</pubDate><guid>https://abapinho.com/en/2016/12/o-estranho-caso-da-estrutura-parcialmente-protegida/</guid><description>&lt;p>The other day I was trying (and failing) to modify a line of a SORTED TABLE.&lt;/p></description></item><item><title>DDIC structure key</title><link>https://abapinho.com/en/2016/11/definir-a-chave-de-uma-estrutura-do-ddic/</link><pubDate>Wed, 02 Nov 2016 09:00:39 +0000</pubDate><guid>https://abapinho.com/en/2016/11/definir-a-chave-de-uma-estrutura-do-ddic/</guid><description>&lt;p>Today when I want to create a SALV I always create a DDIC structure with the data elements already set to show the texts I need. This avoids the need for code to manipulate the field catalog.&lt;/p></description></item><item><title>APPEND STRUCTURES do more stuff than I thought</title><link>https://abapinho.com/en/2016/10/append-structures-do-more-stuff-than-i-thought/</link><pubDate>Mon, 17 Oct 2016 09:00:06 +0000</pubDate><guid>https://abapinho.com/en/2016/10/append-structures-do-more-stuff-than-i-thought/</guid><description>&lt;p>During all my ABAPian life I was convinced that APPEND STRUCTURES had one single purpose: to add new extra fields to an existing standard table.&lt;/p>
&lt;p>But I recently learned that they let you do two more things after all:&lt;/p></description></item><item><title>Thou shalt always use a predefined structure with ALV</title><link>https://abapinho.com/en/2015/03/usaras-sempre-uma-estrutura-pre-definida-nas-alvs/</link><pubDate>Mon, 16 Mar 2015 09:00:30 +0000</pubDate><guid>https://abapinho.com/en/2015/03/usaras-sempre-uma-estrutura-pre-definida-nas-alvs/</guid><description>It is common to find an ALV data structure explicitly defined in the code. If this is done, the field catalog has to be manually constructed. If a predefined structure (from DDIC or declared as a TYPE) is used instead, the field catalog can be automatically built. This approach is always better and results in less code, even if the field catalog needs to be adjusted here and there. https://abapinho.com/en/2011/12/automatizar-catalogo-alv/</description></item><item><title>Thou shalt consider using SM34 clusters</title><link>https://abapinho.com/en/2014/09/consideraras-usar-clusters-sm34/</link><pubDate>Thu, 11 Sep 2014 09:00:14 +0000</pubDate><guid>https://abapinho.com/en/2014/09/consideraras-usar-clusters-sm34/</guid><description>If a development requires more than one customising table consider grouping their maintenance views under a cluster. This way it will be more intuitive to maintain them. This makes even more sense if one depends on the other since in the cluster definition these relations can be explicitly defined.
Example: Como encavalitar tabelas (portuguese)</description></item><item><title>Thou shalt use a constants table</title><link>https://abapinho.com/en/2014/08/usa-uma-tabela-de-constantes/</link><pubDate>Thu, 28 Aug 2014 09:00:45 +0000</pubDate><guid>https://abapinho.com/en/2014/08/usa-uma-tabela-de-constantes/</guid><description>Whenever you feel a constant value can change and you can’t add it as a user parameter, store it in ZCONSTS. This table should never be used directly. Instead, a class like ZCL_CONSTS should be created to properly access it, like shown in this article: (portuguese only)
Resist the temptation of using T900 or similar tables for this purpose. It&amp;rsquo;s true that a lot of people do it. But it&amp;rsquo;s ugly, durty and besides these tables don&amp;rsquo;t even have an adequate key because they were not designed with this in mind.</description></item><item><title>SE16N's technical view</title><link>https://abapinho.com/en/2014/06/vista-tecnica-se16n/</link><pubDate>Mon, 30 Jun 2014 09:00:43 +0000</pubDate><guid>https://abapinho.com/en/2014/06/vista-tecnica-se16n/</guid><description>Hi. How&amp;rsquo;ve you been? How&amp;rsquo;s life? All cool? This tip is so simple that if we don&amp;rsquo;t talk for a while it will all end too quickly. The sun is shinning. It rained in the morning but now it stopped.
Moving on.
Every time I see someone still using SE16 I wonder why, since SE16N is so much better and already exists for so long. But this is not the tip.</description></item><item><title>Adding values to a standard domain</title><link>https://abapinho.com/en/2014/01/adicionar-valor-a-dominio-standard/</link><pubDate>Mon, 13 Jan 2014 09:00:58 +0000</pubDate><guid>https://abapinho.com/en/2014/01/adicionar-valor-a-dominio-standard/</guid><description>&lt;p>If you think it’s impossible to add values to a standard SAP domain without requesting an activation key, you’re wrong.&lt;/p></description></item><item><title>Compare a table across two systems</title><link>https://abapinho.com/en/2013/11/compara-uma-tabela-entre-dois-sistemas/</link><pubDate>Mon, 25 Nov 2013 09:00:45 +0000</pubDate><guid>https://abapinho.com/en/2013/11/compara-uma-tabela-entre-dois-sistemas/</guid><description>The SCMP transaction compares the content of a table across two systems. It is very useful, especially for parameterization tables.
It is very easy to use. It allows for the pre-selection of the registers and fields to compare. It also allows you to only display the differences, which is convenient for tables with lots of data. I don’t think any more explaining is required. Ite et videte.
This tip recently appeared in the ex SAPtricks blog and I think it is so useful that I have reposted it here, in case you haven’t already seen it.</description></item><item><title>SELECT comparing 2 fields of the same table</title><link>https://abapinho.com/en/2013/11/select-propria-tabela/</link><pubDate>Mon, 04 Nov 2013 09:00:00 +0000</pubDate><guid>https://abapinho.com/en/2013/11/select-propria-tabela/</guid><description>&lt;p>This tip is simple and quick, but I bet 200.482 Portuguese escudos that few know it.&lt;/p></description></item><item><title>Create RANGEs in DDIC without getting all wound up</title><link>https://abapinho.com/en/2013/03/ranges-no-ddic/</link><pubDate>Mon, 04 Mar 2013 18:26:40 +0000</pubDate><guid>https://abapinho.com/en/2013/03/ranges-no-ddic/</guid><description>&lt;p>I am using RANGEs more and more. I use them at breakfast, lunch, and dinner and outside meal times. It’s like soy sauce. A few spoonfuls and everything is instantly tastier.&lt;/p></description></item><item><title>Lock data in Z-tables without a locking object</title><link>https://abapinho.com/en/2013/01/bloquear-dados-em-tabelas-z-sem-objecto-de-bloqueio/</link><pubDate>Mon, 28 Jan 2013 09:00:54 +0000</pubDate><guid>https://abapinho.com/en/2013/01/bloquear-dados-em-tabelas-z-sem-objecto-de-bloqueio/</guid><description>&lt;p>If I needed to create locking entries in a ZCOISO table I had created, up to two days ago I would have gone to SE11 to create a locking object for the ZCOISO table so that I could then use the function module generated by the locking object to lock the data.&lt;/p>
&lt;p>But not anymore.&lt;/p></description></item><item><title>Maintaining table maintenance authorisation groups</title><link>https://abapinho.com/en/2012/11/se54/</link><pubDate>Mon, 19 Nov 2012 09:00:24 +0000</pubDate><guid>https://abapinho.com/en/2012/11/se54/</guid><description>&lt;p>There are some projects in which the authorisations group associated with table maintenance is always &amp;amp;NC;&amp;amp;, that is, Not Classified. It signals that everything there is friendly and nobody is hurting anyone else. But there are other projects where authorisation groups are taken seriously. But this is not synonymous with saying that they are organised. Serious or not, usually it all ends in a big mess, with nobody knowing who is authorised to do what.&lt;/p>
&lt;p>This tip may help.&lt;/p></description></item><item><title>Beautiful table relationships diagrams</title><link>https://abapinho.com/en/2012/09/diagrama-relacoes-tabelas/</link><pubDate>Mon, 24 Sep 2012 09:00:39 +0000</pubDate><guid>https://abapinho.com/en/2012/09/diagrama-relacoes-tabelas/</guid><description>Nice relation diagrams for standard tables. Rui Dias revealed me a site where you can check the relation between any standard table with each other.
For instance for T012. And if you try KNA1 it gets even better.
Do you like it? I do.
Thanks Rui Dias.
Greetings from Abapinho.</description></item><item><title>Dot and comma or comma and dot?</title><link>https://abapinho.com/en/2012/06/ponto-e-virgula-ou-virgula-e-ponto/</link><pubDate>Mon, 11 Jun 2012 09:00:34 +0000</pubDate><guid>https://abapinho.com/en/2012/06/ponto-e-virgula-ou-virgula-e-ponto/</guid><description>Some numbers have dots, some numbers have commas and some numbers have dots and commas. The problem is that there are also numbers that have commas and dots. The thing is, there are commas that are dots and dots that are commas, depending on where you are from, in other words, depending on user’s configurations. When importing a file with decimal numbers, these numbers’ alpha-numeric fields must be converted into numeric fields.</description></item><item><title>Client or Customer?</title><link>https://abapinho.com/en/2012/04/cliente-ou-fregues/</link><pubDate>Mon, 23 Apr 2012 10:00:05 +0000</pubDate><guid>https://abapinho.com/en/2012/04/cliente-ou-fregues/</guid><description>Wherever you use the data element KUNNR, its descriptions is “Client”. And what if we wanted to change this field description from &amp;ldquo;Client&amp;rdquo; to &amp;ldquo;Customer&amp;rdquo;? “Customer&amp;quot; is so much nicer! Or let&amp;rsquo;s suppose that the company you work for is trafficking in drugs and tells you that they want &amp;ldquo;Dealer&amp;rdquo; rather than “Supplier” to appear in the LIFNR field. Obviously we can label it as we wish on screens and Z reports but what about standard transactions?</description></item><item><title>&lt;!--:pt-->Como encavalitar tabelas&lt;!--:--></title><link>https://abapinho.com/en/2011/02/encavalitartabelas/</link><pubDate>Sat, 05 Feb 2011 16:38:20 +0000</pubDate><guid>https://abapinho.com/en/2011/02/encavalitartabelas/</guid><description>&lt;p>Às vezes temos de criar uma tabela Z. Às vezes temos até de criar várias tabelas Z. Às vezes estas tabelas estão relacionadas de alguma forma. Como quando uma contém dados de cabeçalho e a outra dados de item, por exemplo. Ora se estão relacionadas pode dar jeito que sejam editadas em conjunto. É para isso que servem os Clusters de Visão (view cluster).&lt;/p></description></item><item><title>&lt;!--:pt-->As estruturas PRE-a-porter&lt;!--:--></title><link>https://abapinho.com/en/2011/01/pre-a-porter/</link><pubDate>Tue, 11 Jan 2011 11:51:37 +0000</pubDate><guid>https://abapinho.com/en/2011/01/pre-a-porter/</guid><description>Quantas vezes não é necessária uma pequena estrutura para guardar, por exemplo, uma lista que relacione materiais e centros. Mas perder tempo a inventar a roda é sempre de evitar.
No reino do MM há uma pequena família de estruturas que uso amiúde: são elas as PRE*, uma série de estruturas que vai desde a PRE01 à PRE50, com uns saltos pelo meio. Embora sejam, na sua maioria, específicas demais para servirem algum propósito, há algumas úteis.</description></item></channel></rss>