How to see the history of the Moving Average Price
目录
There is now a SAP Standard Report to analyze the changes in the Moving Average Price.
The report is provided in the SAP Note 2198317 - Analysis report for moving average price changes: MBMAPCHANGES
Alternatively, you can use the table CKMI1 to see the variances on your Moving Average Price.
Check the information in the KBA
1506200 - Determine how Moving Average Price changed
Search for MBEW-KALN1 (Cost Estimate Number - Product Costing) of the Material :
Execute transaction SE16
Table MBEW (Material Valuation)
Enter the selection for fields
Material
Valuation Area
Valuation Type (if there is any)
Click the Execution button
Get the KALN1 entry
Get the List from table CKMI1 (Index for Accounting Documents for Material)
Execute transaction SE16
Table CKMI1
Enter the field KALNR (Cost Estimate Number for Cost Est. w/o Qty Structure) with KALN1 from step 1
Remove the entry in field "Maximum No. of Hits"
Click the Execution button
A list appeared as per the selection entered
Go to menu path "Settings" -> "User Parameters" and change to "ALV Grid display"
Select the two columns for DATUM ( Day On Which Accounting Document Was Entered) and UZEIT (Time of Entry)and sort in ascending order
Analyze the list
The list now is in chronological order
POPER indicates the posting period
LBKUM is the stock quantity before the corresponding posting
SALK3 is the stock value before the corresponding posting
VERPR is the MAP before the corresponding posting
From the list you will see how the LBKUM and SALK3 changed by the posting and this will changed the MAP as :
VERPR (Moving Average Price) = SALK3 / LBKUM
AWTYP = MKPF = price was changed by a material document
AWTYP = RMRP = price was changed by an invoice document
IMPORTANT
The fields Total Stock (LBKUM), Total Value (SALK3) and VERPR show values before posting the document (material/invoice).
So if you are using price control ‘V-Moving Average Price’. The next entry for VERPR is the result of the calculation SALK3/LBKUM.
Example from other History Tables
MARDH: history table for stock quantity at storage location level.
MBEWH: history table for stock value.
History tables are only updated for the PREVIOUS period when a change is made in the current period. Only from the first change in the current period the system will create an entry in the history table for the previous period.
See SAP note 193554 for further details.
This note explains how the history table works.
In history tables you will see that the posting in the current period always updates the previous period. If there is no any stock posting in the current period you will see a gap in this table.
Example
You change the period to September, 2010 (009 2010). This does not change anything in the stock or valuation tables.
You post then a Goods Receipt in September, 2010 (009 2010).
This will create an entry in the history table for the previous period (August, 2010 – 008 2010).
You need to compare MBEWH x CKMI1 to see this relationship.
As described into the note 193554
“These history tables can have one entry per period. The values of such an entry refer to the end of the period. For the current period, there are no entries in the history tables. An entry is not written in this history table for every period. If stock-relevant or valuation-relevant data change, the system might generate an entry in the history table. Furthermore, the fields LFMON ('Current Period (Booking period)') and LFGJA ('Fiscal Year of the Current Period') in the stock tables are no longer automatically set to the current period by the period closing program. The period is only transferred to the new period during the first movement. At the same time, the relevant history entries are also generated.”
