Time flies – the first two weeks of 2015 are over again, and we hope that you had a good start. For us, the fourth quarter of 2014 was positive and quite busy, as it was characterized by acquiring our long-term partner company AM:DataConsult and becoming the official ACL™ distributor for Germany. Having most of the organizational steps successfully solved by now, we will now continue to step up our blog content again.
This article shows a way to customize the list of selection criteria within SAP® transaction SE16 by adding additional fields. It is a little trick which can make your life easier if you need to look at table content in SAP® regularly:
Exporting data from SAP® and getting it into ACL™ manually can be painful sometimes. For doing a full scope audit, sometimes over 100 SAP® tables are needed, and to solve this challenge we developed our extraction tool dab:Exporter to do this automatically and user-friendly.
When talking about data analysis in the area of SAP®, you will inevitably come across to the big advantage of the change protocol in SAP® systems. In today's blog post I will give you the change raw tables and describe an important column - the object class of the changes (OBJECTCLASS) and where all occurrences of this field are stored.
We enjoyed attending the DIIR annual meeting again this year. The conference (“Internal Audit – The third line of defense”) took place in Magdeburg from 29th of September until October the 1st, starting with the banking forum on Monday, followed by the annual Internal Audit conference on Tuesday and Wednesday.
We are specialized in analyzing SAP® data and offering standardized Ad-Hoc and CCM (Continuous Controls Monitoring) analytic solutions. For transaction-based analytic approaches we are using mainly ACL™ analytic software like ACL™ Analytics (Desktop solution) or ACL™ Analytics Exchange (Client/Server solution).
The term “Vendor invoice” in SAP® has more than one meaning, which sometimes may cause confusion when analyzing data. In this article I will explain this in detail based on the example of an invoice from a vendor which is based on a purchase order. We will look at the same invoice, but they differ in the SAP® materials management module (SAP® MM) and the SAP® Financials module (SAP® FI). The SAP® tables which are concerned as well as the SAP® transaction codes will also be listed in that context.
Early 2014 I published a lot of content regarding SAP® Change Tables: Two Blog postings (1, 2) as well as one whitepaper were released. However one piece of the puzzle seems to be missing, and especially in trainings people keep asking me about it: It is change-related SAP® Transactions (T-Codes).