Professional Documents
Culture Documents
2
Why this webclass?
Find out what SAP data you need to be able to audit Order To Cash
Find out what type of dashboards you could do based on that SAP data
3
Poll
Ice Breaker
4
Question
Ice Breaker
5
The order to cash process in SAP
6
The order to cash process in SAP
SD
Sales & Distribution Module
MM
Materials
A customer can be
Management Module
created either in the SD
module or in the FI Goods issue
module
FI (CO)
Finance (& Controlling)
Module
Stock movement Customer movement
Customer
7
How can we join the tables together?
A B C
8
How can we join the tables together?
A B C
(import) (format) (test)
9
How can we join the tables together?
A B C
(import) (format) (test)
11
B: Join header and footer tables
12
B: Join between different parts of the process
13
B: Join with information from the general ledger
14
B: Filter out items that we do not need
One major mistake that we can make with data from SAP, is to include too much of it!
In SAP, many different types of documents are found in the same data table.
For example, in the list of sales documents (VBAP/VBAK) we have: (See VBAK_VBTYP in
http://leanx.eu/en/sap/table/vbak.html)... We get the same for billing documents!
• A: Inquiry • Q: WMS transfer order
• B: Quotation • R: Goods movement
• C: Order • S: Credit memo cancellation
• D: Item proposal • T: Returns delivery for order
• E: Scheduling agreement • U: Pro forma invoice
• F: Scheduling agreement with • V: Purchase order
external service agent • W: Independent reqts plan
• G: Contract • X: Handling unit
• H: Returns • 0: Master contract
• I: Order w/o charge • 1: Sales activities
• J: Delivery • 2: External transaction
• K: Credit memo request • 3: Invoice list
• L: Debit memo request • 4: Credit memo list
• M: Invoice • 5: Intercompany invoice
• N: Invoice cancellation • 6: Intercompany credit memo
• O: Credit memo • …. 15
• P: Debit memo
B: Calculate useful values - currencies
Code calculations
16
B: Calculate useful values - prices
In SAP, we have the net price. Often in our tests, we want to compare the net price between
different customers for the same product, or for the same customer and product over time.
For example, to ensure that we don’t give away “near free” items.
However, we need to be careful not to use the price field “as is”. This is because the price field
(NETPR) is net for the total number of condition units (KMEIN). So first, we have to find out
the price per condition unit, but dividing by the number of condition units (KPEIN).
Once we have got the price per condition unit, we need to convert it to the price per sale
order unit of measure, using UMVKZ and UMVKN (numerator and denominator for
conversion of sales quantity into SKUs).
Once we have got the price per SKU, then we want to get the price per base unit of measure
by using the UMZIZ and UMZIN (factors for converting from SKU to base unit of measure).
Note, we can also get the factor for converting from condition units to base units from the
KONVA table (sales order conditions).
17
B: Calculate useful values – due dates
Another useful area for calculation is due dates.
However, some of your auditees will tell you that the age should not be calculated based on
the document date, but based on the due date.
We can use the payment terms (ZTERM) that are found in KNB1 (customer master data per
company code), or in VBRK (list of billing documents header) or the customer movements
(BSAD/BSID). Once we have the payment term, then we can use the payment term
configuration table T052 and descriptions (T052U) to determine the due date. The due date is
based on the baseline date (which is either the document date, input date or posting date)
based on the field baseline date type (T052_ZDART). We also need to take into consideration
whether or not there was a discount and if so what the discount percentage was (discount
amount (BSAD_WSKTO)/ amount eligible for discount (BSAD_SFKBT).
Once we have this information, from the T052 table, we choose the additional number of days
to add to the baseline date.
18
B: Put items in buckets
One of the trickiest parts of analysing data from SAP, when it comes to Purchase To Pay, or
Order To Cash, is to separate the customer invoices from the customer payments.
To easily filter a journal entry on the green rules, we can put the list of debit accounts and credit accounts
on one line for each journal entry, along with the lists of these flags, and then we can add this information 20
to the customer movements to help decide what it is.
B: Put items in buckets
This is how we split our BSAD/BSID table into buckets!
21
Create some tests!
What kinds of tests can we do?
It helps if we have a reference point and if we use the reference numbering in our data
analytics work and even in our final report:
22
Question
Ice Breaker
Let us know in
the chat!
23
Q&A
For any questions, please contact:
24
Thanks for coming!