In this blog post everything is about fields for date and time entries, and the DATETIME data type intended for this purpose. The latter has been in the functionality of ACL™ since version 10.0, offering numerous advantages that the DATE data type cannot give you in earlier versions.
For 11 years now we have been offering digital data analytics by ACL™, and in this blog post I would like to tell you a few reasons why. Why is our choice ACL™? Of course it helps if you like to use the software you are working with (in our concrete case have even been selling since this year started). But must it really be ACL™. What about Microsoft Excel™ or Access™ or other data analytics tools like IDEA?
For the first time after a longish pause an IIA event with the keynote data analytics is again set to take place in Switzerland. (*By the way, the quote in the header is from Sir Arthur Conan Doyle, author of Sherlock Holmes, and is used by the organizers on the invitation flyer, which you can -> download here.)
We would like to invite you to an advanced training event by our US sales partner HWA (High Water Advisors, www.highwateradvisors.com), in the staging of which we are participating. It is a pleasure for us that HWA with its Managing Director Steve Biskie (Author of the book "Surviving an SAP® Audit") is organizing the event and has invited us to Denver to participate.
This blog post will focus on field notes in ACL™, an in my opinion very valuable but often forgotten functionality of its data analytics software tool. For audits or evaluations in general, it is important not to change the data during the analytical process.
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.