What is the correlation between the production cost collector and the standard cost evaluation?

1. Why do we need to create a standard cost estimate before creating a production cost collector?

Cost collector is used for repetitive manufacturing. at ordinary times, production order is not enabled, and mfbf is used only when finished products are produced.
Cost collector collects and compares the differences between target cost and actual cost. The so-called target cost is the standard cost. The standard cost of finished products includes the material (taken out from the production version, usually corresponding to a BOM, in fact, when you use ck11n to estimate the unit price and quantity of all raw materials at that time, if the material master data or BOM has scrap, this will also be calculated. If the BOM component has a group, calculated based on a certain percentage), work (activity type job price, usually corresponding to the production staff's salary), fee (generally referred to as various manufacturing costs ), at that time, the sum of the three will be regarded as the current planned cost (target cost ). generally, ck24 is used to update the finished product master data, which is the standard cost.

2. After the Work Center of the process route is changed, it will be reversed, but the cost of the job type will still go to the cost center of the original work center. If I delete the original standard evaluation and reverse the original credential, the system will prompt "no usable process ". Does the Standard Cost Assessment have something to do with time?
After the work center of the process route is changed, the cost of the type will still go to the cost center of the original work center, why?
First, you can use ck84_99 to check that ck11n will record the prices of all raw materials at that time, MAF and lab prices (from routing's work center ).

The result is analyzed at the bottom layer of SAP. after ck11n is used, an internal order starting with "7" is generated first. SE16 can be found in the onr00 table or0000007xxxxx. All internal orders are here ,. then ckis will record the price and quantity (ck84_99) of the labor charge during your estimation ). the total TGT shown by kkf6n is the data here. We know that the difference between kkf6n is only the difference in quantity and price. Then ck11n and kkf6n will write down two comparison records in the keko table. generally, the lab and MAF obtained from routing are automatically generated internally, and the price is recorded in the table Coss. The prefix or0000007xxxxx must be added before the internal order, the actual raw material consumption is in the mseg (material creden). You can also see COSP (the Co creden are consistent ). keko and aufk are passed through prod. process number Association. ckis and keko are associated through cost estimate no.

Total production variance = standard quantity * standard price-actual quantity and actual price
So after you change the work center, as long as the ckis data is not changed, you must use ck11n for re-calculation, and this action is not just done, generally, the estimation starts next month after the end of the month. Otherwise, the difference in the current month ............., In addition, when ck11n is used in the current month, you will be prompted that the material master data already has TD cost. You must delete it before it will take effect.

If the original standard evaluation is deleted, the current cost variant of ckis and keko is out of the Standard Cost variant (cost collector is Prem ), of course, mfbf or reverse will fail (standard cost is required for mfbf ).

III. in addition, if sap is set to deprecate and reverse based on the standard cost evaluation process route and Bom, rather than reverse Based on the changed routing and Bom, how should such logic be explained?
After you change the routing or Bom, unless: 1, you create another production version for c223 and create a cost collector for it. 2. the original STD cost of ckr1 is the update ckis and keko records, and then ck11n. Otherwise, it will always capture the original data.

I think the above logic should be clear. I have written reports in this regard and studied the cost collector process from the database layer.
I also encountered a problem, kkbc_pko and kkbc_ord are used (for cost collecot, in fact, and kkf6n). If cost collector is used for a year, but the STD cost of finished products is changed every month, view the report. For example, if no settlement is made on April 9, 11.1, the target cost cannot appear on April 9, 11.1, and the settlement result is OK. Later, the patch "OK" is found in notes 540376. the problem is, if I look at the cumulated total TGT cost for the whole year, whether it is to use the target cost * Total qty of the current month or to accumulate the target cost * Monthly Total qty of the current month,