We already have Material Ledger active for all Valuation Areas/Plants for parallel currencies so we have been collecting all the ML documents for many years. The price determination for all the materials has been set to 2. Now we have a requirement to use ML-Actual Costing.
Question 1.
Is there a way to set the price determination on the ML transactions from 2 to 3? The data already collected in table MLIT. When we set the materials to 3, the data in MLIT still has 2 so it is not selected for costing.
They want to parallel the costing function for the last 3 months. I find that you can only process the costing for current and prior periods. Makes sense. But even for prior period, the Price Determination was set to ‘2’ on all the materials and therefore all the transactions in table MLIT have Price Determination (field MLAST) = ‘2’. It appears this setting is how transactions are selected in CKMLCP and CKMB_RUN.
We refreshed our testing system from production but all the data is still set to ‘2’. How do you test this process?
Question 2.
What are the negatives to setting the materials to ‘3’ in production to collect the data? We do not currently perform any costing runs. We are running product cost by order and execute the CO functions for Price Calculation (KSII), Revaluation of Activities (CON2), WIP (KKAO), Variance (KKS1) and Settlement (CO88). It seems that we could just stop there and not proceed with actual costing even though the material is set to price determination ‘3’. Is that true?
This would at least collect the data properly so we could build some testing data for another refresh or we could run the Actual Costing thru multi-level costing and run a test Posting. Would that provide any useful information for validation?
Thank you for reading. Appreciate your assistance.
Debbie
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.