MM in CE Date 700

Qty BOM/1 2
Lot di MM 30
Total Qty CE 60 https://blogs.sap.com/2020/05/27/targ
>>> Target Cost: Comparison between G
26.01.2023 >>> Plan Cost: Ideally from CE Price (in M
03.02.2023 Changes to 4

Scr Plan Cost > Ambil latest qty = 4 Qty BOM/ 2

Qty BOM/1 4 Price/1 700
Price/1 700 Total 10 14000
Total 10 28,000

Plan Cost
PUP 30,792 PRO 1
BOM Qty 0.25 POLY1
Target Qty P 10 BOM/1
76980 Frame
Break
Roda
Routing/1
010 Cutting
Labor
OH
020 Assembling
Labor
OH

RollUp/1
ogs.sap.com/2020/05/27/target-cost-calculation-in-s-4hana-cloud-part-1/
t Cost: Comparison between GR and BOM Component x MM Price * Total Plan PRO | If target cost = 0, so there is have been changes in B
Cost: Ideally from CE Price (in MM) based on CE Date
Bisa juga akan update harga di Plan Cost berdasarkan harga dari MM ketiga GI ke PRO ketika atas RM tsb di CE setelah FG atas
But if there are any changes in BOM Item after CE & already GI PRO, the Plan Cost is follow the MM Price & Target Cost = 0.

FG Cost at 01.26.23 29,975

Total 10 299750 Target Cost Conf
Plan 5,330
RM Re-CE on 02.202 30,867 533000
Total Plan Cost 308,670 Target 41000
?
Qty Target 01.09.2023 02.09.2023
2 Yield 1
Qty P (Mat Master)
1 100
2 50
2 20
Qty P (Plan Price) SPNZZ14X282003-R

1 25
1 25

0.5 15
0.5 15

305
 ere is have been changes in BOM after CE

s RM tsb di CE setelah FG atas RM tsb di CE

MM Price & Target Cost = 0.
Product Costing by Period >> Repetitive Mfg Process >> MTS Scenario
BOM/Routing
Cost Object: Menggunakan Product Cost Collector, tidak menggunakan Production Order/Process Order
RM + OH + If Any Add Exp >> PCC
GI, GR & Conf >> Back Flush

MRP 1 & 2: Explain Material Requirement Plan

MRP 3 & 4: Manufacturing Requirement
* ML Transfer Price Karanam
Step 1:
Create Material Master FG that should be concerning on the MRP 1-4
Step 2:
Create BOM
Create Routing
Create Production Version on particular Material Master FG
Step 3:
CK11N can user several costing variant to calculate each of currency (paralel currency) > Legal, Group, Profit Center Curr
Then, if each of costing variant doesn’t maintain directly release, so must do CK24 to releasing Cost Estimate
Step 4:
Create PPC > KKF6N
When saving PCC, SAP will generate Cost Estimate from the Production Version
>> Result of the KKF6N with CK11N should be same
Step 5:
Do GI, GR & Conf Backflushly > MFBF
If any Costing Sheet (OH) > CO42
If any template allocation (for additional confirmation not in routing) > CPTE (Only in Product Cost Collector)
Step 6:
Calculate Variance > KKS6
Raised form calculation of Actual Cost - Allocated Actual Cost
Step 7:
Settlement > KK87
COGM (PL) pada FG Prod Price Diff (PL)

* WIP in PCC always calculate in Target Cost

>> Caused by cost incured based on backflush (GI, Conf & GR FG at simultaneously)
https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/5e23dc8fe9be4fd496f8ab556667ea05/73c73b53f831070be10000000
Group, Profit Center Curr
ost Estimate

st Collector)

73c73b53f831070be10000000a4450e5.html
* Process Order utk manufacturing yang membutuhkan pencampuran bahan baku untuk menjadi 1 unit barang jadi.
Sehingga tidak memungkinkan jika barang jadi tersebut dipisahkan lagi atas komponen2nya
Misalnya, industri pharmasi, kimia, food dst
* Production Order utk memproduksi 1 unit FG, dengan cara menggabungkan komponen dan bisa dipecah kembali per kompo
Misalnya, otomotif, Machinery, dst
di 1 unit barang jadi.

sa dipecah kembali per komponen

https://www.youtube.com/watch?v=aHg5QoreaG4
https://www.youtube.com/watch?v=bXTcsAvg_NY&t=658s&pp=ygUdY28gcHJvZHVjdCBjb3N0aW5nIGFjY291bnRpbmc%3D
https://www.youtube.com/watch?v=SDFuYqI7Ayo

By Product: produk sampingan dari main product

Misal kursi, akan menghasilkan serbuk kayu
Serbuk kayu bisa dijual dengan harga yang rendah

Co Product: bisa diproduksi barengan dengan main product

Misal baju seri A (main product), color Red Size M & color Red size L (Co Product)
Misalnya lagi, penggilingan batu, bisa menjadi batu ukuran 40 (main), 30 & 20 (Co Product)
HPProduksi dari Co Product ini dari approtionment atas Main Productnya
Dengan cara set di MRP 2 joint product
Then, co product harus masuk ke BOM atas main product dengan negatif sign >> untuk mengurangi total standard cost atas m
Apakah harus dimarkup qty BOM utk Main product?
Apa yg terjadi jika qty di BOM antara Main product dengan Co product sama?
Price det & Price Ctrl Material Co Product S3 atau V2?
Bagaimana alokasi WIP & Variance?

(Lanjutan if hrs dimarkup valid) Sehingga Qty BOM atas main product harus dimarkup sebesar BOM co Product
CO Product need stones 1 KG
Main Product need 2 KG
Then in BOM:
FG Co -1 KG
FG Main 3 KG
Impacted in CO (CK13N):
M Stones 3 KG RP 300
A FG Co -1
0aW5nIGFjY291bnRpbmc%3D

urangi total standard cost atas main productnya (blm clear need testing)

r BOM co Product
00 Default SAP calc variance based on actual & target >> Logic generate from Variance Key. So, function of the Var Key is only
01 in this config, SAP will get the source of target cost determined

02 KKAO/KKS2 result based on above logic (Actual compare with Target), will display all the categories variance and need to be

Plant Cost objectMaterial Descriptio Display UnCurrency Actual costs Act. costs Target costs
1000 ORD 14132AARL26SX XFRM PLG PCS IDR 1,031,622 942,020 1,029,025
PRO PRO PRO
GI 595,034 599,860
Conf 429,164 429,164
Trf Cost 7,424
GR FG 942,020

* If SAP doesn’t found the actual cost, then we have version for calc based on plan too, thus SAP will calc var based on Plan Co
So, function of the Var Key is only to get command to SAP that particular material need to be calc variance

categories variance and need to be assigned to Var Version

Var. input Variance Output sidInput qty vPlanned QuActual quanVar. (%) ta Actual costObject nu Actual fixe
2,597 89,602 87,005 338,663 30 2 9 89,602 OR000014 -
PRO PRO
2,598 89,602

SAP will calc var based on Plan Cost

Actual variControl cosControl cosControl cosScrap Scrap, fixe Scrap, vari Scrap calcuWork in prWIP, fixed
### ### - ### - - - - -
WIP, variabWork in prCost CenteTarget fixeLSI target LSD target Activity Ty Input priceFxd input pVble input
- X - 93,220 935,805 - 50,218 - - 50,218
Business P Res-usage vResource-uRemaining Fxd RemainVble RemaiOutput pri Output pricVble outputMixed-pric
- ### ### - ### - 1 - - 1 -
Mixed-priceMxd-price vOutput qtyFxd outputVar. outputLot size va Remaining Remaining Remaining
v Alloc. fxd a
- - - - - 87,006 - - - -
Alloc.var.acTgt credit Target MxdTarget MxdVar. Input Var. Input Var. Outpt Var. OutputFixed variaVariable va
942,020 - - - - 2,597 - 87,005 - 89,602
Minor diff Operating ProductionProductionFixed inputVariable I Resource-uMinor difference
- - 100581803Rest(Produ - 338,663 ###
1. Plan

Costing Var Plan is to determines Plan Cost

1. Define Line ID RA >> use to grouping for CE input cost on the PRO

2. Assign Line ID (Group) to each of input cost

3. Update from assignment cost and group to representative cost element >> breakdown on the COMLWIPDISP is come from
4. Assign this representative CE to primary gl account (PL & BS)
 Source of Plan Cost Action per Order Type when saving:
1. POV Costing: Determine Plan when Saving & Calc Actual Co
2. POV WIP: Calc WIP based on RA Key
? RA Key >> is used to assign in Line ID. So, the RA Key will pivo
? Actual Costing Var uses case >> to read an update cost when

COMLWIPDISP is come from this config

 Variance Key on PRO, generate from Mat Master
when Saving & Calc Actual Cost

Line ID. So, the RA Key will pivot when calc wip will store to which CE & GL at the end
>> to read an update cost when do GI to pro
1. Once sudah dilakukan cost estimate, dan sudah ada trx di period tsb, maka tdk bisa release cost estimate dengan yang baru
>> Muncul error:

>>> justifikasi, karna sudah ada trx, dan tercapture. Jika ada perubahan, maka tdk bisa kecapture sbg price diff. maka dr itu, sa

2. Ini contoh material yg kita update, dan blm ada trx di bulan yg akan kita update
st estimate dengan yang baru

e sbg price diff. maka dr itu, sap merestrict hal tsb

Error:
Cost Elem Cat 01=Primary cost (GL COGS) not advisory to posting for COPA Costing Based
Caused:
Rule:
1. COPA Costing Based will update in PA ketika billing release.
2. Untuk kebutuhan COPA, secara value Revenue & Cost ini tidak berdasarkan GL Account, tetapi Value Field
3. Maka dari itu, config di KE4I sangat berpengaruh, mappingan antara Condition Type dengan Value Field
4. Condition Type harus mewakili Revenue & Cost
5. Revenue diambil dari Cond Type Revenue, dan Cond Type Revenue ini bersifat Actual >> Impact nya, harus diset sebaga
6. Sedangkan Cost diambil dari Cond Type VPRS, dan VPRS bersifat statistical >> Impactnya, auto diambil dari VPRS masuk
7. If, GL Account COGS dipost FI pd saat billing jg, maka optionnya: jangan CE Cat 1 atau Tidak set as CE
FI Costing Base
COGS pada saat PGI COGS membaca OB Tidak refl Masalah rekon, udh PGI blm Billing: FI ada COGS, di COPA blm ada CO
COGS pada saat Billing COGS membaca Reflect CO Masalah Celem 1 pada akun COGS, dibaca dari VKOA dan VPRS scr be

Case
CKMLCP
akan posting sesuai COC
jadi, ketika execute COC=1, maka Jurnal akan posting 1
tapi ketika diganti COC=2 sebelum reverse, maka ketika Jurnal reverse akan posting 2
Sehingga, ketika akan diganti, harus dipastikan firm

Excecute 4700000084
GL To Periode CE.Elem OKB9 KEI1 CKMLCP Profit Segment
500004 12/30/2022 1 Not MaintaNot MaintaSet CO AccBlank

Reverse 4700000098
GL To Periode CE.Elem OKB9 KEI1 CKMLCP Profit Segment
500003 08/30/2023 1 Not MaintaNot MaintaSet CO AccBlank

Billing 8112319515
GL To Periode CE.Elem OKB9 KEI1 CKMLCP Profit Seg Value Field
500003 08/30/2023 1 Not MaintaNot MaintaSet CO AccFilled with Tally

Billing 8112319514
GL To Periode CE.Elem OKB9 KEI1 CKMLCP Profit Seg Value Field
500002 12/31/9999 12 Maintain Maintain FISet CO AccFilled with Double
pi Value Field

act nya, harus diset sebagai Cost Element & Memasukkan CE Category
o diambil dari VPRS masuk ke Value Fieldnya. Assume best practice (COGS when PGI), maka SAP itu tidak membaca GL lagi, karna sudah

COGS, di COPA blm ada COGS

dari VKOA dan VPRS scr bersamaan. Maka dari itu, utk yg COGS ketika PGI tdk terdampak even itu pakai 1 juga

Value Field

Value Field
mbaca GL lagi, karna sudah dipost pas PGI.
1. Setelah kita pilih relevant costing var & costing version, maka yang akan muncul di f4 hanya yg memiliki key valuation varian
Sehingga, utk company code tsb, akan membaca semua ck11n dr berbagai costing variant. Misal ada 2 mat, di-ck11n yg 1 zpc1
Dan berlaku sebaliknya, jika yg sama antara costing type & val var hanya ada zpc3, maka material2 hsil ck11n yg pakai zpc1 & z
2. Marking belum release bisa cancel marking. Jadi, jika mau ada update atas costing var & costing ver bisa dilakukan di particu
3. Setelah berhasil marking, maka akan update di future period dengan periode pada saat kita marking
period pada future period itu menunjukkan akan update pada periode tersebut. Dan periode itu ditrigger atau berasal dari per
4. Setelah release maka akan masuk sbg current

5. hasil dari release itu, akan mengeluarkan document price change, muncul di ckm3n di bagian beginning. Dan bukan part of

6. ketika konteks blm ada trx, trs update tanpa ckr1 di periode yang sama
>> jika di-ck11n dengan costing var & costing ver yg sama dengan ce yg ke-1, maka error bahwa "material tsb sdh released"
jika di-ck11n dengan costing var yg sama tetapi costing version berbeda, maka bisa save. Tapi kepentok di ck24. karena pd per
? Apa fungsi costing version
>> misal ada case dalam 1 controlling area ada 2 comp code, secara pengambilan harga atas ce nya beda. Maka bisa dibuatkan
Kemudian assign costing type & val var tadi di costing version atas costing variant yg sama. sehingga, ketika ck24 bisa pilih
7. apa solusinya jika mau update setelah release?

dr valuation price accord prce control in MM > if V maka akan ambil map, jika s maka akan ambil sc
plan price > ambil plan jika ada, jika tidak akan ambil sc
sc > ambil sc
CKMLCP Profit Segment if using COC
Result for COGS cant derived to Profit Analysis into particular SO when PGI
Caused by using collective (COC), thus cant read source the original account transactions
Sample Doc 4700000070
Set as Cost Elem Cat = 12
OKB9 Maintained
KEI1 (FI) Maintained
Set CO AA
Result: Only derive the data in particular material master