When analyzing data in checks or audits, you often find that not everything which looks like a problem really is one. You may frequently check whether compulsory entries in the data are missing, and then possibly deduce problems in data consistency – sometimes your conclusions prove to be false.
To avoid this and not report too many "false positives" back to a department, it is a help if you understand the system in which the data are generated, combined with the business processes.
We will take a look at this in this blog post referring to analysis of order documents from SAP® based on the case "Purchase orders without purchase order items".
This focuses on the tables EKKO (order document headers) and EKPO (order document items); data-based screenshots use the desktop version of ACL™ Analytics software.
SAP® images are based on the transaction ME23N ("See order document"). Here the user sees the major content of purchase orders (purchase order number, supplier, document type, item, goods receipt, invoice receipt, etc), or can branch to it.
Data appearing in this mask are saved in the above tables, i.e. focus on EKKO and EKPO, the purchasing document headers and the purchasing document items (plus, in the EKBE table in the case of the order history).
For a data analyst directly accessing the entire data set (the "raw data"), and not going the round-about way through the SAP® GUI, the picture is usually less of a color mixture:
Does that need to be a problem?
To get into it further, the analyst looks at one of the purchase order numbers concerned by transaction ME23N. Very clear, above the header, is the text "Held standard purchase order". That is presented as follows: