This happens because we are creating a Costing Run for future periods and, so, we have to correct the period. Or else, if we are in the actual period, it means that the Material Ledger wasn’t performed for the previous period and, in that case, we have to check the reason for that and, if necessary, contact local team.
There is an inconsistency in the master data of material 32690 (Plant RBAE). This material is marked with “Price Determination: 3 Single-/multi-level” and “Price Control: S Standard price” (transaction MM03 – Accounting 1). This means that this material has to be integrated on the Material Ledger for the current month. However, as it wasn’t included on the previous one, it’s generating an error. In these cases, we have to check with locals if they want to include the mentioned material on ML for the closing month. If they don’t, the material’s master data has to be changed from “Price Determination: 3 Single-/multi-level” to “Price Determination: 2 Activity-related”. After, we have to re-start the ML for the closing month. If local team want to include this material on the Material Ledger (meaning that we should leave the master data as it is), we will have to check this situation with them and find a way to run ML for the previous period, for Material 32690 / Plant RBAE, because it had already movements on the previous month. Error Update: For this error please follow the below instructions suggested by the DT Finance Expert when sending the issue to IS by ticket: For future same issue of error message C+805, please send the links below to CGI: Beginning here, you can send the below instructions/analysis by attachment in the ticket if you prefer: IS Team, please follow the instructions:
The reason is change from Price determination (PD) was change from 2 to 3 at 1st August
In June ML closing, the PD =2 cause the material not included in ML closing
In July ML closing, the PD =3, the material is included in the material ledger, and require ML status = 70 at June to determine the price from July transaction.
July transaction
Due to the status at June is not 70, the error message appear and require IS to run the program MLHELP_SET_PP_STATUS_70 to change the status to 70 at June. After EHP8 upgrade: Z_ML_SET_PP_STATUS_70 Link How to avoid When material master accounting view is first created before any transaction posted, the price determination & Price control must be decided careful. The above example was S2, but in fact, the valuation class Z100 Finished goods manufactured, should be S3 at the beginning. You can run Z1K_CHECKMAT - CO Check MATERIALS to check the Price determination and Price control has been assigned properly. As a simplified rule, V2 for Z101 Finished goods purchase material S2 for Z049 inter plant , Z057 Waste S3 for the rest
Detailed (Costing Matrix) https://docs.google.com/spreadsheets/d/1Ptl-25A5cB9sHl62oeyuj8HxZjlyWAmL7_rbfo5mDfI/edit#gid=0 |
Differences were collected in the period to be settled and, after the recalculation, a statistical periodic unit price has been calculated with a negative price. To correct this, we must check if all production orders are settled, and settle the ones that still remain with amount. After having all the production order settled, if we remain with the same error, we need to exclude the mentioned material from the multi-level parameters:
To solve this error, we need to go to transaction KBK6 and manually change the actual price for the cost center and activity type in error:
In order not to have variance, we just copy the amount that we have on column After, we must repeat this step for ML. |
Remark: this error can also happen on other steps of Material Ledger There is someone using material 37140 and 36975 at the same time that we are running Material Ledger. We have to wait until that person leaves the materials. After, we must re-run this step for the ML.
The period is not open, so we have to go to transaction OB52 and open it.
When choosing the “parameters selection”, the field “Revaluate Material” wasn’t flagged, causing this credit / debit inconsistency. In order to correct this error, we have to reverse the ML and re-execute the last step, flagging the correct fields.
The maximum number of items for a FI document has been exceeded. To correct this error, we have to change the field “No. of Materials in ML Doc.” from 50 to 1. |