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.
One day there was a fire in a wastebasket in the Dean's office and in rushed a physicist, a chemist, and a statistician. The physicist immediately starts to work on how much energy would have to be removed from the fire to stop the combustion. The chemist works on which reagent would have to be added to the fire to prevent oxidation.
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).
We are looking forward to participating in the DIIR annual meeting again this year. The conference will take place in Magdeburg on 30 September and 01 October. The venue is the Hotel Maritim, Otto-von-Guericke-Str. 87, 39104 Magdeburg.
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.