In our blog we regularly share our experience in SAP®, Data Analysis, ACL™, GRC and Big Data with you. I would like to mention another good way to receive valuable information, or to exchange on topics related to data analysis: The long successful ACL™ User Group for Germany, Austria and Switzerland (D-A-CH).
An accountant spends a week at his new office with the accountant he is replacing. On the last day the departing accountant tells him that he has left two envelopes in the desk draw and that the envelope number 1 should be opened if he ever encounters any sort of crisis in the job and envelope number 2 if a further crisis occurs.
When doing complex data analytic projects, you might know the feeling: You have been working hard on a certain task, and finally created this shiny result table, containing everything you have been asked for.
Changing masterdata for vendors is a process in SAP® just certain users should have access to. In addition to the possibility of restricting access to this area with the SAP® authorization concept, SAP® also provides an option to implement a simple 4-eye-principle for critical masterdata changes. As this turns out to be a bit hidden in the customizing, this blogpost has a closer look at that.
Over years we successfully established a training series which combines ACL™ analytic tool aspects with SAP® Know How (tables, fields, important transaction codes, accounting and business process details).
An auditor is hard at work auditing a manufacturing plant. He spots one worker at the end of the shift, that worker is always carrying a wheelbarrow covered with an opaque cloth. The auditor is certain something is fishy. He asks the security to check the wheelbarrow. Many surprise checks, security finds nothing. On the last day of the audit the auditor goes to the worker and asks, “Alright, I give up. I know you are taking something. I cannot prove it . I do not want to pursue it. I just want to know. What are you stealing?” The worker replies, “Wheelbarrows.”
Which topics can be covered by data analytics at all? Why is it worthwhile for example to analyze „Credit Limit Changes“ or „One time accounts (Conto pro Diverse)“? What are the risks that can be identified when performing certain analytics?
This is the second article about two ways of searching for a certain SAP® transaction code (“T-Code”) or it’s meaning in SAP®, respectively how you can create a list of all T-Codes that are available on your SAP® system.
Today I will show you the first of two tricks when dealing with SAP® transaction codes („T-Codes“). The article is about searching for a certain SAP® T-Code or it’s meaning in SAP®, respectively how you can create a list of all T-Codes that are available on your SAP® system.