Today I am going to discuss the difference between technical field names and alternate column titles and explain what the differences are and how to specify or change these texts. Therefore you will see two ways how to manage it: On the one hand with the ACL™ GUI and on the other within a script.
The last blogpost within this ACL Analytics™ series is going to get its teeth into relations between tables and wants to take up the issue described in our last entry (Relations: Simple, indirect and through combined text field). First, we will learn about different types of relations between tables and see what kind of questions can be solved very simple by using them. I am going to show you as well, what errors could happen while working with relations and how to avoid them best.
This time I would like to take a brief look at an article that my colleague Christoph drew my attention to. It appeared on www.heise.de, authored by Rudolf Jansen, and dated July 7, 2015 at 12:29 h. It is entitled "Data Scientist – ein neues Berufsbild fuer die Big-Data-Welt" [Data Scientist – a New Professional Profile for the Big Data World], and what I like even more is the add-on "Celebrate Data". [Heise]
It is pretty warm outside, so let’s keep this article short and as to-the-point as possible. I want to have a closer look at the AR (Accounts Receivables) documents in SAP® FI, to be more exact at incoming payments.
In the first two blog posts of that ACL Analytics™ series (Four practical text field functions, The Classify workaround) we have seen how text fields can be combined easily and what benefits we gain from it. Today I will show you another use case for this functionality.
In this article I will explain a fact which might sometimes be a little confusing when looking at SAP® tables using the SAP® GUI transaction SE16 compared to downloading the data using a download tool. I will explain how SAP® displays data making it look like it was in one table, but in fact the data is separated in a table containing settings and technical information (a “Customizing Table”) and a table containing the descriptions and long texts in different languages (a “Text table”). I will explain where SAP® mixes those two, but also how you can find out about where the data really is located in the database tables.
On 1st and 2nd of June, in cooperation with our subsidiary AM:DataConsult, the dab:Group was present on the DIIR - IT Conference in Frankfurt as silver sponsor. The event dealt with "current developments, methods, IT security, tools, and technology" and more than 250 participants visited the event.
Following on from our blog series on topics like terms of payment in SAP® or process mining this time I want to launch a new series of blog posts all about ACL™ Analytics.
To start we look at practical ACL™ functions on text fields, showing you how simple it is to work with and even combine these fields. In addition to the technical explanation there I want to give you some background and advice based on my daily work, which hopefully will provide some added value for you. I will use the example of “Identifying master data duplicates” for explaining the following functions. If you examine customer or vendor master data for double entries for this purpose, it is advisable to search across different columns. The field with the phone number can also be a decisive indicator. But this very seldom uses a uniform convention, so first you have to prepare and make it comparable.
This time I would like to look at an article by Kerstin Daemon headed "Big data in business — when the firm knows when you want to quit before you do", which appeared in the April 15, 2015 issue of "Wirtschaftswoche" [WiWo1] and "The great data chaos of German business" by Meike Lorenzen published April 12th, 2013 [WiWo2].
This blog post marks the end of the series on terms of payment in SAP®. In two preceding instalments I showed how terms of payment exist at different levels or between different SAP® modules, and explained what to observe when comparing master data.