12/10/2014

CostObjectControlling(COPCOBJ)ERPFinancialsSCNWiki

GettingStarted Newsletters

Welcome,Guest

Login

Register

Store

SearchtheCommunity

Products

Services&Support

AboutSCN

Downloads

Industries

Training&Education

Partnership

DeveloperCenter

LinesofBusiness

UniversityAlliances

Events&Webinars

Innovation

ERPFinancials / / ProductCosting

CostObjectControlling(COPCOBJ)
AddedbyBrendanO'Brien,lasteditedbyOscarDiazonAug19,2014

Totalpageviews:

Definition
ProductCostPlanning(COPCPCP)isanarea
withinProductCostControlling(COPC)whereyou
canplancostsformaterialswithoutreferenceto
orders,andsetpricesformaterialsandothercost
accountingobjects.

MainAreas

Nocontentfoundforlabel(s)ERP_CO_COPC_OBJ_PCBP.
ProductCostByOrder
ThispageistobeusedtocollectallinformationrelatedtoProductCosting>CostObjectControlling>ProductCostByOrder
Nocontentfoundforlabel(s)ERP_CO_COPC_OBJ_PCBSO.

Periodendclosingproductcosting:
https://www.sdn.sap.com/irj/sdn/thread?messageID=1969478&

WhenDoYouUseProductCostbyOrder?
1.General
ProductCostbyOrderenablesyoutoanalyzecostsatproductionlotlevel.Youcanuseitformaketostockproductionandsalesorderrelatedproduction.Insalesorderrelatedproduction,youcanuse
ProductCostbyOrderforsalesorderrelatedmassproductionandasasupplementtoProductCostbySalesOrder.
InProductCostbySalesOrder,youusemanufacturingorders(productionordersorprocessorders)ascostobjects.Thecoststhatareupdatedonthemanufacturingorderareanalyzedbylotandthen
settled.Thismeansthatvariancesofthecostanalysisareonlydeterminedoncethewholequantitythatwasplannedforproductionhasbeendeliveredtothewarehouse.
YoucandothefollowingwithProductCostbySalesOrder:
Determineandanalyzeplan,targetandactualcostsforproductionordersandprocessorders
Updateordeterminetheinventoryofunfinishedproducts(workinprocess)andfinishedproducts
Determineandanalyzevariances
TransferworkinprocessandproductionvariancestoFinancialAccounting(FI)
TransferproductionvariancestoProfitabilityAnalysis(COPA)
TransferworkinprocessandproductionvariancestoProfitCenterAccounting(ECPCA)
Transferproductionvariancestoactualcosting/MaterialLedger(COPCACT)

2.TheDifferentContexts
Settlementtype
Intheplantsettingsfortheordertype,youneedtoselectsettlementtypePP1.ThismeansthatallproductionordersforthisordertypeandthisplanthavethesettlementrulewiththeFULsettlementtype.
Intheorder,thesettlementtypedeterminesinwhichofthefollowingscenariostheproductionorderisprocessed:ProductCostbyOrder(FUL)orinProductCostbyPeriod(PER).
Statuscontrol
Thestatusoftheproductionorderisveryimportantinthisscenario.Thedelivered(DEL)ortechnicallycompleted(TECO)statuscontroltheWIPdetermination(creationorbreakdown),thevariance

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=187336643

1/11

12/10/2014

CostObjectControlling(COPCOBJ)ERPFinancialsSCNWiki

determinationandtheordersettlement
Workinprocess(WIP)
Thisiscalculatedatactualcosts.WIPisonlycreatedforordersthathavebeenreleased(REL).Iftheorderhasbeentechnicallycompleted(TECO)ordelivered(DEL),thenWIPisnotcreated,butis
brokendownifitexists.However,WIPisonlypostedtoFIwhentheorderissettled.
WIPcannotbecalculatedattargetcosts.ItisonlypossibletocalculateWIPinProductCostbyPeriod.
Variancedetermination
Variancescanonlybedeterminedoncetheorderhasbeendelivered(DEL)ortechnicallycompleted(TECO),asthequantityactuallydeliveredisfixed.Thisquantitydeterminesthetargetcostsofthe
productionorderandthusthevariancesperpiece.
ThismeansthatWIPandvariancescannotbecalculatedatthesametime.WIPisonlycalculatedforreleasedorders(REL)andvariancesforordersthathavebeentechnicallycompleted(TECO)or
delivered(DEL)
IfyouareusingProductCostbySalesOrderwiththeunvaluatedsalesorderstock,youcannotreliablydetermineanyvariancesfortheassignedproductionordersandprocessorders.Therefore,inthis
case,thesystemdoesnotsupportthevariancedetermination,andyouneedtousethevaluatedsalesorderstockinstead.
Ordersettlement
Thestatusofaproductionorderinthisscenariodetermineswhetherthatproductionorderissettledandthuscreditedornot.Theactualcostsoftheproductionorderareonlysettlediftheorderhasbeen
technicallycompleted(TECO)ordelivered(DEL).Forordersthathavebeenreleased(REL),settlementonlypoststheWIPtoFI(ifanyWIPwasdetermined).
Lotsizeindependentcosts
Thesearedeterminedandcalculatedonce(only)inthisscenario.InProductCostingbyPerioditisnotpossibletoallocatethesecosts

3.WhenShouldYouUseProductCostbyOrder?
Forindividualorlotrelatedproduction.Itistypicallyusedfororderrelatedproductionorforbatchrelatedprocessmanufacturing.Productionisbasedonordersforwhichproductionandthecost
analysisofacertainlotsizearethepriority.
Fortestproduction/startupproduction(forplannedrepetitivemanufacturing)fortheexactdeterminationofplanningdata(forexample,varianceanalysis)
WhenyouwanttocalculateWIPatactualcosts
Whenyouwanttoallocateyourlotsizeindependentcosts
Whenyouwanttoscheduleyourordersaccurately.

4.WhenShouldYouNotUseProductCostbyOrder?
Forrepetitivemanufacturing(stableandcontinuousproduction),sincetheproductionofonematerialisthemainpriorityoveralongperiodoftime
WhenyouwanttocalculateWIPattargetcosts
WhenyouwanttocalculateWIP(attargetcosts)andvariancesatthesametime.

5.PeriodEndClosing
Sequenceforproductionordersduringperiodendclosing:
1.Processcostallocation
2.Revaluationatactualprices
3.Overheadcalculation
4.WIPdetermination
5.Variancedetermination
6.Ordersettlement.

ProductCostCollectorandRepetitiveManufacturing/
ProductCostbyPeriod
General
YouuserepetitivemanufacturingintheR/3Systemifyouareproducingamaterialoveralongerperiodoftimeinlargerquantities.Unlikeproductionusingproductionordersorprocessorders,thereisno
predefinedlotsizeinrepetitivemanufacturing.Repetitivemanufacturingiscontinuallyanalyzedonaperiodicbasis.ProcessingissupportedbyrunscheduleheadersuptoRelease4.5B.Theseare
normallylinkedtoProductCostCollectors.FromRelease4.6A,backflushingisdoneviatheproductionversionfortheproductcostcollector.
Sincethereisnodefinedlotsizeinrepetitivemanufacturing,therearealsonoplancosts.Thepreliminarycostingoftheproductcostcollectorusesthecostinglotsizefromtheproductionprocess.Thisis
onlyanoperandanddoesnotcorrespondtothequantityactuallyproducedorplanned.
Asrepetitivemanufacturingisanalyzedonaperiodbasis,workinprocess(WIP)andscraparealwaysvaluatedattargetcosts.WIPandvariancescanalwaysbecalculatedatthesametime,withoutthe
orderstatusoftheproductcostcollector(unlikeproductionordersinfullsettlement).
Thefollowingscenariosarenotpossibleinrepetitivemanufacturing:
Manufacturingofcoproducts

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=187336643

2/11

12/10/2014

CostObjectControlling(COPCOBJ)ERPFinancialsSCNWiki

Collectiveorders
Rework
Ordersplitting
Reportingpointsinalternativeorparallelplansequences.
Thisdocumentmakesextensiveuseoftheterm"productcostcollector".ThistermiscorrectfromRelease4.5Aonwards.Itisalsoused(regardlessoftherelease)whentalkingaboutcostcollectors.
"Productioncostcollector"isthetermthatwasusedbeforeRelease4.0B,andisonlyusedifthecontextrelatessolelytoareleasebefore4.5A.

PrerequisitesforRepetitiveManufacturing
MaterialforRepetitiveManufacturing
Toproduceamaterialinrepetitivemanufacturing,youneedtomeetthefollowingrequirements:
YouneedtoswitchontheindicatorforrepetitivemanufacturingintheMRP4view(caution:Ifyouwanttousestandardcostestimateforbackflushingofproductionactivityinrepetitivemanufacturing,
thentheswitchmustbesetbeforethestandardcostisestimated.Ifthisisnotdone,thentheerrormessageRM175"Existingstandardcostestimatecannotbeused"isdisplayedduringbackflushing.
YouneedtoenterarepetitivemanufacturingprofileintheMRP4view.
Youneedtocreateatleastoneproductionversionforthematerial(MRP4view,costingview,fromRelease4.6alsotransactionC223).
Youneedtosettheindicatorfortheplannedrepetitivemanufacturingofproductionversions.

ProductionVersion
Intheproductionversion,thequantitystructure(BOM,routing)isenteredthatisusedinrepetitivemanufacturing.Youcanenterthreedifferentroutingsintheproductionversionforthefollowing:
Detailedscheduling
Ratebasedplanning
Roughcutcapacityplanning.
Ifaroutingisenteredunderdetailedscheduling,thenthesystemusesthisforrepetitivemanufacturing.Ifitisnotenteredunderdetailedscheduling,thesystemusestherouting(ifentered)fromtherate
basedplanning.Routingsenteredunderroughcutcapacityplanningarenotusedforrepetitivemanufacturing.

RunScheduleHeader
Caution:FromRelease4.6A,runscheduleheadersarenolongeravailable.Itisnowsufficienttohaveanallowedproductionversionforrepetitivemanufacturing,andtocreateaproductcostcollector
(KKF6N,KKF6M).
UptoRelease4.5B,youneedtoworkwithrunscheduleheaders.Thesecannotbecomparedtoother"orders"(suchasproductionorders,processorders,productcostcollectorsorinternalorders),as
theyarepurelylogisticalobjectsanddonothavetheirownCOobject.Therefore,youalwaysneedtolinkthemtoaCOobject.Thisisnormallyaproduct(ion)costcollector(inrareexceptions:ordertype
SA:runscheduleheaderwithproductionorder).
Youcanusethefollowingtransactionsformaintainingrunscheduleheaders:
MF01CreateRunScheduleHeader
MF02ChangeRunScheduleHeader
MF03DisplayRunScheduleHeader
MF04CreateRunScheduleHeaders:SelectionScreen
MF21RunScheduleHeaders(overview)
Whenyoucreatearunscheduleheader,aproductcostcollectoriscreatedatthesametime(PKSA,untilRelease4.0Bonly),accordingtotherunscheduleheader(seeRepetitiveManufacturingProfile).
Otherwise,youneedtocreateaproduct(ion)costcollectormanuallyfirst(PKMN).
RunscheduleheadersareonlysavedintheSAFKtable(notinAUFK,AFKO,AFPO).Theordernumber(AUFNR)isusedastheonlykey.
Thequantitystructuredataistransferredfromtheproductionversionwhentherunscheduleheaderiscreated.Thecorrespondingproductcostcollectoriskeptintherunscheduleheader.
ForrunscheduleheadersthathavetheordertypePKSA,thereisa1:1connectiontotheproductioncostcollector.Inthiscase,theordernumberoftherunscheduleheaderisrecordedinthemasterdata
oftheproductioncostcollector.Ascheduleheaderisnotenteredinthemasterdataoftheproductcostcollector,ifitwascreatedmanuallyusingtheKKF6,KKF6NorKKF6Mtransactions.

ProductCostCollectors
Productcostcollectorsarespecialordersfromordercategoryfive.Productcostcollectorscanbeusedforcollectingcostsinproductionforthefollowingproductiontypes:
Repetitivemanufacturingwiththefollowing:
oMaketostockproduction(fromRelease3.0A)
oMaketoorderproductionwithvaluatedsalesorderorprojectstock(fromRelease4.0A)
KANBAN(fromRelease3.0A)
Productionorders(fromRelease4.5A)
Processmanufacturing(fromRelease4.5A)
TheproductcostcollectoralwayshasaperiodicsettlementruletoMaterial.Tocreatetheproductcostcollector,youcanusethetransactionforeditingtheproductcostcollector(KKF6NfromRelease
4.6A,previouslytransactionKKF6)and"CreateMultipleProductCostCollectorsforProductionVersions"(KKF6MfromRelease4.5B).Itisonlypossibletocreatemultipleproductcostcollectorsin
repetitivemanufacturing.Productcostcollectorsarecreatedforallselectedproductionversionsforwhichthe"Repetitivemanufacturingallowed"flaghasbeenset.UptoRelease4.0B,itwaspossibleto
createdproductcostcollectorsinthebackgroundwhilecreatingarunscheduleheader(MF01)(ordertypePKSA).Duringcreation,aproductcostcollectorisautomaticallyreleased.
FromRelease4.5A,productcostcollectorsarealwayscreatedwithreferencetoaproductionprocessfromthequantitystructuretool.Aproductionprocessiscreatedforamaterialanddescribestheway
inwhichthatmaterialisproduced(inotherwords,whichquantitystructureisused).Thewayinwhichaproductionprocessisformed,dependsonthecontrollinglevelofthematerial(upto4.5B:naming
rule).Thefollowingcontrollinglevelscanbeusedforproductcostcollectors:
Productionversion(recommended):Theproductionversionisnotedduringtheproductionprocess.Thequantitystructure(billofmaterial/routing),istakenfromtheproductionversion.Theproduction
processisdeterminedbythefollowingcharacteristics:material,productionplantandtheproductionversion.Oneproductionprocesscanbecreatedforeachproductionversion.

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=187336643

3/11

12/10/2014

CostObjectControlling(COPCOBJ)ERPFinancialsSCNWiki

Billofmaterial(BOM)/routing:Thequantitystructureisstoreddirectlyintheproductionprocess.Theproductionprocessisdeterminedbythefollowingcharacteristics:material,productionplant,planning
plant,billofmaterialandrouting.ItispossibletocreateaproductionprocessforeachcombinationofBOMandrouting.The"BOM/routing"controllinglevelisnotrecommendedforusewithrepetitive
manufacturing,sinceyoualwayshavetoworkwithproductionversionsinrepetitivemanufacturing.
Productionplant/planningplant:Noquantitystructureisstoredintheproductionprocess.Theproductionprocessisonlydeterminedbythefollowingcharacteristics:material,productionplantandplanning
plant.Itisnotpossibletocreateapreliminarycostingfortheproductcostcollector.Forthisreason,the"productionplant/planningplant"controllinglevelisnotrecommended.
Theexactcontrollinglevelisspecifiedonthemateriallevel,meaningthatamaterialcanonlybeassignedtoacontrollinglevel,andallproductionprocessesarecreatedforthiscontrollinglevel.
Ifyoucreateaproductcostcollectorforamaterialthathasnotyetbeenassignedtoacontrollinglevel,thentherequiredcontrollinglevelisinitiallyqueried(whencreatingmultipleproductcostcollectors
usingKKF6M,the"productionversion"controllinglevelisalwaysused).Moreover,theproductcostcollectorfortheproductionprocessiscreatedinthebackground.Youcanalsocreateproductcost
collectorsforexistingproductionprocesses.However,onlyonevalidproductcostcollectormayeverexistforaproductionprocess(thismeanswithoutadeletionflag).Productionprocessescanbe
processedusingthetransactionforeditingproductionprocesses(CKML_FPR1N,untilRelease4.5B:CKML_FPR1).
ThecontrollinglevelcanbechangedfromRelease4.6A,usingthetransactionforeditingcontrollinglevels(CKMLMV_CA).Todothis,allexistingproductcostcollectorsassignedtoaproductionprocessof
thematerialmustbedeleted.InRelease4.5A/B,itisnotpossibletochangethecontrollinglevel.
ThenumberoftheproductionprocessisnotedintheAUFKPROCNRfieldintheproductcostcollector.Ontheinterface,theproductionprocessisrepresentedbyanappropriateshorttextratherthanthe
processnumber.Thisshorttextisautomaticallygeneratedbythesystem,butcanalsobedefinedbytheuser.Toselectaproductcostcollectorintheperiodendclosingtransactions(individual
processing)andinreporting,youalwaysneedtospecifythematerial,(production)plantandproductionprocess(shorttext).
Acostinglotsizecanbestoredintheproductionprocess.Thislotsizeisusedforthepreliminarycostingoftheproductcostcollector.Ifalotsizehasnotbeenstoredintheproductionprocess,thecosting
lotsizefromthematerialmasterisused.Productionprocessesarealsousedtodeterminetheassignmentinacostobjecthierarchy.
Productcostcollectorshaveanunlimitedruntime(theruntimeendswhenyousetthedeletionflag).Thefollowingparametersaretransferredasdefaultvaluestothemasterdataoftheproductcost
collectorwhenyoucreateproductcostcollectors:
Theprofitcenteristakenfromthematerialmaster
Thebusinessareaistakenfromthematerialmasterusingthedivision.FromRelease4.6C,thebusinessareaisalwaystransferredtothemasterdata,evenifnobusinessareafinancialstatementhas
beenactivated.
Theplancostingvariantisdeterminedfromtheplantparametersfortheordertype(transactionOKZ3).Itisusedforthepreliminarycostingoftheproductcostcollector.
Theactualcostingvariantisdeterminedfromtheplantparametersfortheordertype(transactionOKZ3).Itisusedfortheactualcosting(valuationofactualmaterialwithdrawnandactualactivities).
Thecostingsheetisdeterminedfromtheplancosting(ifthisexists,otherwisetheactualcostingvariantisused).Until4.6B,thecostingsheetwasdeterminedfromtheactualcostingvariant.Thechange
wasmadetoadapttheproceduretothatofproductionorders.
Theoverheadkeyisdeterminedfromtheoverheadcostgroupforthematerial.
Theresultsanalysiskeyisdeterminedfromtheplantparametersoftheordertype(transactionOKZ3)fortheproductcostcollector.
Thevariancekeyistransferredfromthecostingviewofthematerialmaster.
Thefunctionalareaistransferredfromtheordertype(KOT2_PKOSA).
Features:
Actualdebits(activitiesandgoodsissue)andactualcredit(goodreceipt)canbepostedbymeansofbackflushing(backflushingforrepetitivemanufacturingortheassignedproductionorprocessorder).It
isnotpossibletopostanymaterialmovementstothecostcollectorexceptbyusingbackflushing.Activitiescanalsobepostedtotheproductcostcollectorbymeansofanactivityallocation(forexample,
fromacostcenter).Forproductcostcollectors,youcanuseoverheadapplicationandatemplateallocation.
Productcostcollectorsdonothaveaplanquantity,andtherefore,noplancostseither.However,youcancreateapreliminarycostingfortheproductcostcollector(upto4.0B:costingbyproduction
version).Thecostinglotsizethatisusedmustnotberegardedastheplanlotsizeoftheproductcostcollector.Thepreliminarycostingfortheproductcostcollectorusestheplancostingvariantthatis
storedinthemasterdataoftheproductcostcollector.Thesystemalwaysusesthequantitystructurestoredinthecorrespondingproductionprocess(until4.0B:fromthequantitystructureinthe
productionversion).Thepreliminarycostingisusuallyonlycarriedoutwithonelevel(from4.5A,itcanonlybedoneusingonelevel).Thepreliminarycostinghasthefollowingfunctions:
Valuationbasisfortargetversiononeandpossiblythree
FromRelease4.0A,valuationbasisforWIPandscrap(accordingtovaluationvariantWIPandscrap.Itisrecommendedthatyouusethepreliminarycosting).
Determinationoftheactivityquantitiesthataretobepostedinversely(accordingtotheRepetitiveManufacturingProfile)
FromRelease4.0A,adjustmentofthereportingpointstructureforroutingchanges
YoucanonlydetermineWIPontheproductcostcollectorifreportingpointsweredefinedorproductionorprocessorderswereusedfortheproductcostcollectorthathavetransactionbackflushing.Inthe
followingscenarios,itisnotpossibletodefinereportingpoints,therefore,itisalsonotpossibletocalculateWIP:
Repetitivemanufacturingwithvaluatedsalesorderstock,sincethequantityofreportingpointsneededfordeterminingWIPcannotberecordedbysalesorder.
KANBANproduction.
Variancescanbecalculatedintargetversions0and1,andinrepetitivemanufacturing,alsoinversion3.Targetversion2isnotpossible.
SinceRelease4.5A,youcanusetheproductcostcollectornotonlyinrepetitivemanufacturing,butalsoinProductCostbyPeriodontheproductlevelinrelationtomanufacturingorders(=productionand
processorders).Inthisscenario,themanufacturingordersarepurelylogisticalobjectsthatare,forexample,usedforcapacityplanningandscheduling.Backflushentriesarestillenteredinthe
manufacturingorders,butthedebitsandcreditsareposteddirectlytothecorrespondingproductcostcollectorsbythesystem.ForthepurposesofCO(periodendclosingandreporting),onlytheproduct
costcollectorisanalyzed.Thefollowingmanufacturingorderscannotbeassignedtoaproductcostcollector:
Manufacturingorderswithmanufactureofcoproducts
Manufacturingordersthatwerecreatedforasalesorder
Manufacturingordersincollectiveorders
Toassignamanufacturingordertoaproductcostcollector,youneedtocreateasuitableproductcostcollectorfirst.Whenyoucreatethemanufacturingorderyoumustuseasuitableordertype
(transactionOPL8,defineordertypedependentparameters).Intheordertype,the"costcollector"flagmustbeset.Inaddition,theordertypemustcontain"PP2"(periodic)asitsdefaultrule.
Note:Manufacturingordersarenotsettledtoproductcostcollectorsastheydonotcarryanycosts.Thismeansthatthedefaultruleintheordertypeisnolongerusedforanythingelse.Forbackflushing
bytransactionofthemanufacturingorderstoproductcostcollectors,youcanconfirmeachtransactionthatcanbeconfirmedonamanufacturingorderwithoutproductcostcollectors.Thetransactionsto
beconfirmedarenotrestrictedtomilestones.
Whenproductcostcollectorsarecreated,asettlementrulewith100%tomaterialiscreated.FromRelease4.5A,thereisalsoanewruleforthiswithmethod5"deliveryvalueforproductcostcollector".
Thisdistributionrulecannotbesubsequentlychanged.Duringsettlement,the"deliveryvalueforproductcostcollector"methodmeansthatthedistributionofthecoststobesettledtothevariousvaluation
segmentsistakenintoaccount(MBEWsegmentsformaterialswithseparatevaluation,EBEWsegmentsforvaluatedsalesorderstock).Adistributionruleisdynamicallydeterminedforthisduring
settlement,foreachvaluationsegment.Itisdeterminedfromthedeliveryvaluespostedintheperiod.Ifthereisnodeliveryintheperiodtobesettled,thensettlementismadetothepricedifferenceaccount
PRP.

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=187336643

4/11

12/10/2014

CostObjectControlling(COPCOBJ)ERPFinancialsSCNWiki

Theassignmentofthegoodsreceiptdocumentstothevaluationsegmentsismadeusingtheprocurementalternativesenteredinthegoodsreceiptdocuments(seequantitystructuretool).Youcanuse
thesetodirectlydeterminethematerial,valuationarea,andifappropriate,thevaluationtypeandthesalesorderposition.Thisinformationuniquelydeterminesthevaluationsegment.
UpuntilRelease4.0B,settlementwasonlymadetomaterial,withouttakingintoaccountthevaluationsegments.Forsalesorderstock,itwaspossibleinRelease4.0A/Btocreateyourownproductcost
collector(set"Salesorderstock"flag),althoughhere,settlementwasonlymadetothepricedifferenceaccountPRD.Thistypeofproductcostcollectordoesnothaveasettlementrule.In4.0A/B,a
materialcannothaveanyotherproductcostcollectifaproductcostcollectorexistsforthesalesorderstock.
Formoreinformationonsettlementofproductcostcollectors,seenoteno.388457.
ItisalsopossibletoprocessproductcostcollectorswiththeKKF2transaction(COproductionorder).However,itisstronglyrecommendedthatyoudonotdoso.Thechangesmadetothemaster
dataorthesettlementruleofaproductcostcollectorusingtheKKF2transactionleadtodatainconsistencies.Itisplannedtopreventmaintenanceoftheproductcostcollectorwiththis
transactioninfuture.
Whenupgradingfromareleaseolderthan4.5Ato4.5Aorhigher,theexistingproductcostcollectorsareconvertedusingtheXPRAprogramRK_PKOSA_MLMV_X1.Thismeansthatproductionprocesses
arecreatedforproductcostcollectors,andtheyreceivethenewsettlementrulewithmethod5.Duringconversion,thecontrollinglevel"productionversion"isassignedtothecorrespondingmaterial
(exceptions:productcostcollectorsforKANBANthatdonothaveaversion,andproductcostcollectorsforsalesorderstock.The"productionplant/planningplant"controllinglevelisusedforthis.
FromRelease4.5A,itisonlypossibletohaveonevalidproductcostcollectorforaproductionprocess.Previouslyitwaspossibletohavemorethanone(ifseveralmanufacturingordersexistfora
productionversion,butnotoverlapping).Inthiscase,onlyoneoftheproductcostcollectorsfortheproductionversionisconverted.Theproductcostcollectorthatisassignedtotherunscheduleheader
atthetimeoftheupgradeistheonethatisconverted.Anyexistingfuturerunscheduleheadersareassignedtotheconvertedproductcostcollector.Ifthereisnorunscheduleheaderatthetimeofthe
upgrade,thentheonebeforeorafteritissearchedforandthecorrespondingproductcostcollectoristhenconverted.Theexistingproductcostcollectorsforsalesorderstockdonotgetany(new)
settlementrule(settlementtoPRDonly,evenaftertheupgrade).

QuantityStructureTool
SinceRelease4.5A,productcostcollectorsarealwayslinkedwithaproductionprocess.Productionprocessesareobjectsfromthequantitystructuretool,whichisaMaterialLedgertool.Thequantity
structuretoolcontainsprocurementalternativesandproductionprocessesasitsobjects.
Procurementalternativesspecifythewayinwhichamaterialisprocured(forexample,externalprocurement,inhouseproductionorstocktransfer).Forproductcostcollectors,youcanonlyhave
procurementalternativesfromthe"BF=Production"category(processcategory).
ProductionprocessesaremetaobjectsthatenableacertainseparationbetweenLogisticsandAccounting.Theycontainreferencestothelogisticalquantitystructuretermssuchasbillofmaterial/routing
orproductionversion.
Thewayinwhichproductionprocessesandprocurementalternativesarecreated(whichlogisticaltermsareusedinthem)isdeterminedonthemateriallevelbytheassignedcontrollinglevel(see:Product
CostCollectors).
Inasimplecase(maketostockproductionwithoutmanufacturingofcoproducts)thereisa1:1relationshipbetweenprocurementalternativesandproductionprocess.However,m:nrelationshipsbetween
procurementalternativesandproductionprocessesaregenerallypossible.Ifamaterialisproducedusingacertainproductionversionforthevaluatedsalesorderstockthenthereis,forexample,a
procurementalternativeforeachsalesorderstock(EBEWsegment),butonlyatotalofoneproductionprocess.Thesameappliestoamaterialthathasaseparatematerialvaluation.Inthiscase,thereisa
procurementalternativeforeachMBEWsegment.
Thefollowingordercategoriesarelinkedtoproductionprocesses:
Productcostcollectorsarealwayslinkedtoproductionprocesses
Productionandprocessordersarelinkedtoproductionprocessesif:
oMaterialLedgerisactivated
oTheyarelinkedtoaproductcostcollector(thentheyarelinkedtothesameproductionprocessastheproductcostcollector)
oTheyareassignedtoacostobjecthierarchywhoseobjectsareindividuallyassignedbasedonproductionprocesses.
Procurementalternativesarealsoneededtospecifythemixingrationofmixedcostings.Thereisafieldforthisinthemasterdataoftheprocurementalternativesorproductionprocessescalled"costinglot
size".Thisfieldisalsousedasthecostinglotsizeforthepreliminarycostingofproductcostcollectors.Sinceitisusedintwoapplications(preliminarycostingandmixedcosting),thisfieldcanonlybeset
onceinthemasterdatamaintenanceoftheproductcostcollector,afterwhichitcannotbechanged.Youcanonlymakeasubsequentchangetothecostinglotsizeinthemaintenanceoftheproduction
process(transactionCK91N).

RepetitiveManufacturingProfile
Therepetitivemanufacturingprofilecontrolsrepetitivemanufacturing.Itisenteredinamaterialthatistobemanufacturedusingthisprocess(MRP4view,uptoRelease3.X,MRP2view).
Therepetitivemanufacturingprofileisreadduringbackflushingfromthematerialmaster.Itssettingscanbepartlyoverriddeninthebackflushingtransaction.Caution:Changestotherepetitive
manufacturingprofileinthematerialmasterorinCustomizinghaveadirecteffectontheoperatingproductivesystem.
YoudefinerepetitivemanufacturingprofilesinCustomizing(transactionOSP2).Thefollowingsettingsareimportant:
InversegoodsissueforGRposting:Ifthisisactivated,goodsissuesareinverselypostedduringbackflushingofrepetitivemanufacturing,otherwise,thegoodsissuesmustbemanuallyposted(itis
recommendedthatyouactivatethisindicator).UntilRelease4.5B,theindicatorwascalled'GRandGI'withthefollowingvalues:1/blank=GRandGI,2=onlyGR.
Reportingpointbackflush:Ifthisisactivated,thebackflushingisenteredonthereportingpointlevel.Otherwiseitisonlypossibletoentergoodsreceiptbackflushing.Thereisachoicebetween
"required"and"optional".If"required"isset,thereportingpointsmustbeposted."Optional"(rarelyused)isusedifyouonlypostgoodsissuesduringtheperiod,andwanttopostthephysicallyexistingWIP
attheendoftheperiodtothesystem,usingreportingpointbackflushes.ReportingpointbackflushesareaprerequisiteforcalculatingWIPinrepetitivemanufacturing.UntilRelease4.5B,theindicatorwas
called"withreportingpoint",withthefollowingvalues:blank=noreportingpoints,1=requiredreportingpoints,2=optionalreportingpoints.Itisrecommendedthatyouuserequiredreportingpoints.
AutomaticGRpostingforactualdataentryatthelastreportingpoint:Ifthisisactivated,thenthesystempostsagoodsreceiptduringbackflushingatthelastreportingpointintheroutingusingthe
backflushingquantity(exceptforscrap).Otherwise,thegoodsreceiptmustbeenteredmanually.Ifthisindicatorisset,thentherearenoWIPquantitiesatthelastreportingpoint.UntilRelease4.5B,the
indicatorwascalled"automaticGR"withthefollowingvalues:blank=noautomaticGR,1=automaticGR.
Postactivities:Ifthisindicatorisactivated,thentheproductionactivitiesareinverselypostedduringbackflushing.Theactivityquantitiestobepostedaredeterminedusingacosting.Youcandetermine
activitiesusingthestandardcostestimateformaterialorthepreliminarycostingfortheproductcostcollector(untilRelease4.0:Costingbyproductionversion).Itisrecommendedthatyouusethe
preliminarycostingforthis.Thisindicatoronlycontrolsthecalculationoftheactivityquantities.Theactualcoststhataretobepostedfortheproductionactivitiesaredeterminedusingthesequantities,
basedonthevaluationvariantoftheactualcostingvariantintheproductcostcollector.UntilRelease4.5B,theindicatorswerecalled"Activities"withthefollowingvalues:1=noactivityposting,2=activity
posting,and"Costing"withthefollowingvalues:blank=standardcostestimate,1=preliminarycosting.
Reduceplanorders:Determineshowexistingplanordersarereducedinagoodsreceiptpostingforrepetitivemanufacturing.Thefollowingvaluesarepossible:
o0:noreductionofplanorders
o1:reductionofplanordersorrunschedulequantitiesforthematerial,thatareassignedtothespecifiedproductionversion.
o2:asin1,butalsoreduction(ifrequired)oftheplanordersandrunschedulequantitiesforthematerial,thatarenotassignedtoaproductionversion.
o3:asin2,butalsothereduction(ifrequired)oftheplanordersandrunschedulequantitiesforthematerial,thatareassignedtoproductionversionsotherthantheonespecified.

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=187336643

5/11

12/10/2014

CostObjectControlling(COPCOBJ)ERPFinancialsSCNWiki

Reductionperiod(indays):Reductionoftheplanordersandrunschedulequantitieswhosedatefallsbeforethepostingdateplusreductionperiod.
Planorders:Determineshowthereducedplanordersarecreatedagainifagoodsreceiptisreversed.Values:
oBlank:noplanordersarecreated
o1:planordersarecreatedforthecurrentdate.Thesamenumberofplanordersarecreatedasthequantitythatwasreversed.
o2:planordersarecreatedbyasynchronousMRPduringthereversal.
Movementtypes:Thedifferentmovementtypesfordifferentgoodsmovements(GI,GR,scrap,reversaletc.)arestoredintherepetitivemanufacturingprofile.Youcanchangetheseduring
backflushing.
UpuntilRelease4.0BCustomizinghastwotransactionsforrepetitivemanufacturingprofiles:"Definerepetitivemanufacturingprofiles"(OSP2)and'Specifycontroldataforrepetitivemanufacturingprofiles"
(OSP3).IntheOSP2transaction,youassigntwoordertypestotherepetitivemanufacturingroles:
Therunscheduleheadertype(nottobeconfusedwiththeordertypeforproductionordersorproductcostcollectors)Thishasthreepossiblevalues:
oPKSA:whenyoucreatearunscheduleheader,anewproductioncostcollectorisalwayscreatedinthebackground.Thereisa1:1relationshipbetweencostcollectorandrunscheduleheader.This
ordertypeisnotrecommendeduptoRelease4.0B.FromRelease4.5A,thisordertypeisnolongeravailable.
oPKMN:beforeyoucreatearunscheduleheaderyouneedtomanuallycreateaproductioncostcollector.Youcanlinkmorethanonerunscheduleheaderwithacostcollector.
oSA:Runscheduleheadersarenotlinkedtoproductioncostcollectorsbutproductionorders.Thisscenarioisveryrareandisnotrecommended.
Theordertypefortheproductioncostcollectorthisisautomaticallyusedwhenacostcollectoriscreated,andisnormallytheRM01type.Itcontainsdefaultvaluesfortheplanandactualcostingvariant,
andtheresultsanalysiskey(alwaysplantdependent),aswellasforthesettlementprofile,and(from4.6C)thefunctionalarea.Youcanalsoentertheresidencetimesforarchivingandthenumberrange
fortheordernumber.
FromRelease4.5A,onlytheOSP2transactionisavailable.FromRelease4.5A,ordertypePKSAisnolongeravailable.FromRelease4.6A,theordertypefortherunscheduleheaderisobsoletesincethe
runscheduleheaderisnolongeravailable.
FromRelease4.5A,theordertypefortheproductcostcollectorisspecifiedwhenthecostcollectoriscreated,andnolongerdeterminedfromtherepetitivemanufacturingprofile.

DefinitionoftheReportingPoints
Intherepetitivemanufacturingprofile,ifreportingpointprocessingisactivated,thenyouneedtodefineoperationsintheroutingspecifiedbytheproductionversionforrepetitivemanufacturing.Youcan
(optionalreportingpoints)ormust(requiredreportingpoints)makeyourbackflushtothese.ReportingpointbackflushesareusedfordeterminingWIP.Inaddition,assemblyscrap,andcomponentand
activitypostingscanalsobeenteredforthereportingpoint.Reportingpointbackflushesareonlypossibleformaketostockproduction.
Reportingpointsaredefinedintheroutinginthetransactionoverview.Theoperationsthataretobeusedasreportingpointsmusthaveacontrolkeywithmilestoneprocessing(flag:Backflushingwith
controlkey=1).Notalloperationshavetobedefinedasreportingpoints.Reportingpointsarealwaysdefinedintheplansequence000000.
Thefollowingoperationscannotbedefinedasreportingpoints:
Operationsinparallelsequences
Operationsinalternativesequences
Suboperations

BackflushinginRepetitiveManufacturing
FromRelease4.6A,youcanusetheMFBFtransactionforbackflushinginrepetitivemanufacturing.ThisreplacesthetransactionsthatwerevaliduntilRelease4.5B:
MF40(goodsreceiptbackflushformaketostockproduction)
MF44(goodsreceiptbackflushforsalesorders)
MF4S(goodsreceiptforproductionlot)accountassignmenttoWBSelement,nolongertakenintoaccounthere
MF43(reportingpointbackflush)onlyformaketostockproduction
MF4U(goodsissuebackflush)
MF4A(componentscrap)inCOterms,thisleadstoextrauseofthecomponent,nodifferencetoMF4U
MF48(backflushingactivities)
MF4R(resetreportingpoints)postsexistingWIPquantitiesasscraptosettheWIPquantitiestozero.Thistransactioncanbeusedifaproductcostcollectoristobedeleted.WIPneedstobeatzerofor
deletion.Notethatifyouresetreportingpoints,nocostsarepostedtotheproductcostcollector.
YoucanonlybackflushinrepetitivemanufacturingduringMMperiods(currentandlast).
Ifappropriate,duringbackflushinginrepetitivemanufacturing,thegoodsissuesandactivitiesareinverselypostedaccordingtothesettingsintherepetitivemanufacturingprofile.Duringreportingpoint
backflushing,goodsissuesarepostedfortheBOMcomponentsthatareassignedtotheconfirmedreportingpoint,aswellasallcomponentsthatareassignedtotheoperationsthatarenotreportingpoints
andarebetweentheconfirmedreportingpointandthepreviousone.Componentsthatarenotassignedtoatransactionarepostedwhenthefirstreportingpointisconfirmed.Iftransactionsthatarenot
reportingpointscomebeforethelastreportingpointtransaction,thentheassignedcomponentsarepostedduringgoodsreceipt.Theassignedactivitiesarepostedinthesameway.Setuptimesarenot
inverselypostedaslotfixedcosts.Thishasitsownfunctioninthebackflushtransaction.
Example:
Routing:|
Operation|
Milestone|
Activity|

0005

0010

ACT1

ACT2

0015

ACT3

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=187336643

6/11

12/10/2014
0020

CostObjectControlling(COPCOBJ)ERPFinancialsSCNWiki
ACT4

BOM:

Item

Component

Assignedtooperation

0010

KOMP1

0005

0020

KOMP2

0010

0030

KOMP3

0015

0040

KOMP4

notassigned

Backflushtoreportingpoint0010:
Thefollowingareposted:componentsKOMP1,KOMP2andKOMP4aswellasactivitiesACT1andACT2.
Backflushtoreportingpoint0020:
ComponentKOMP3andactivitiesACT3andACT4areposted.
Thecomponentsandactivitiesarevaluatedaccordingtothevaluationvariantthatisstoredintheactualcostingvariantinthecorrespondingproductcostcollector.
Iftherearenoreportingpointpostings(asperrepetitivemanufacturingprofile),thenallcomponentsandactivitiesarepostedduringthegoodsreceipt.
Duringbackflushinginrepetitivemanufacturing,youcanchangethecomponentsandactivityquantitiesthataretobeinverselyposted,andentermorecomponentsoractivities(postingwithcorrection
function).Thiscreatesinputquantityandresourceusagevariances.
Workinprocess(WIP)
Ifyouenterbackflushingwithareferencetoreportingpoints,thenworkinprocess(WIP)iscreated.TheconfirmedreportingpointquantitiesareupdatedintheCPZPtable(PZPPandPZPStablesbefore
Release4.0A).DuringWIPdeterminationonthecorrespondingproductcostcollector,theseWIPquantitiesarevaluatedusingacosting(withthecurrentstandardcostestimatebeforeRelease4.0A,after
whichaccordingtothevaluationvariantforWIPandscrap)tocalculatetheWIPvalue.
IfareportingpointbackflushisenteredwithalargerquantitythaninthepreviousreportingpointintheWIP,thenthesystemissuesawarningmessage.Ifyoustillcontinuewiththeposting,thiscausesa
negativeWIPquantityforthepreviousreportingpoint.NegativeWIPquantitiesareignoredinWIPdetermination.Thesystemdoesnotcreatereservesformissingcosts.
Scrap
Backflushinginrepetitivemanufacturingcanalsopostassemblyscrapwithorwithoutreferencestoreportingpoints.Forassemblyscrapthatreferstoreportingpoints,thesamecomponentsandactivities
arepostedastheyareforacorrespondingyieldbackflush.Ifscrapispostedwithoutareferencetoreportingpoints,thenallcomponentsandactivities(similarlytogoodsreceipt)areposted.TheWIP
quantitiesarereducedaccordingtothescrappostings.
Itisalsopossibletomakeapostingwithacorrectionforscrap.ThepostedscrapquantitiesareupdatedintheCPZPtable(beforeRelease4.0A,tablePZPP).Duringvariancedeterminationonthe
correspondingproductcostcollector,thepostedscrapquantitiesarevaluated(inthesamewayastheWIPquantities)andthedifferenceofthedeterminedscrapcostsandtheplanscrapcanbedisplayed
asscrapvariances.
Theconfirmedcomponentscrapisnotincludedinitsownvariancecategoryinthevariancedetermination,butflowsintotheinputquantityvariances.
Reversal
Reportingpointbackflushescanbereversedbydocument(transactionMF41orMF12documentlogoverview).ThistypeofreversalisonlypossiblefordocumentsthatarestillintheopenMMperiods.If
areportingpointisdeleted,thedocumentsthatwerepostedtoitcannotbereversedanylonger.
Inadditiontothedocumentreversal,youcanalsopostbackflushingwithareversedmovementtype(function:reversemovementtype).Thismeansthatgoodsreceiptsbecomegoodsissuesandvice
versa.Thisenablesyouto"reverse"anyreportingpointquantitywithoutadocument(forexample,ifthedocumentstobereversedarenotintheMMperiods,andthusmakereversalimpossible).Until
Release4.0B,thisisonlypossibleforgoodsmovements.Activitiesmustbepostedmanuallyusingactivityallocation(transactionKB21)fromtheproductcostcollectorbacktothecorrespondingcost
centers.FromRelease4.5A,activityisalsoincludedinbackflushingwithareversedmovementtype.
Documents
Inbackflushinginrepetitivemanufacturing,materialdocuments(forgoodsreceiptandissue)andreportingpoints(forreportingpointposting)arecreatedinadditiontotheaccountingdocuments(FIand
COdocumentswithactivitydocuments).ThesedocumentsarecollectedinadocumentlogrecordandcanbedisplayedusingtheMF12transaction.

FlexibleReportingPoints
FromRelease4.0A,flexiblereportingpointsareavailablethatallowachangetothereportingpointstructureintheroutingduringrealtime.Possiblechangesarethedeletionandinsertionofreportingpoints
andthechangetotheunitofentryforareportingpoint.ExistingWIPandscrapquantitiesareadjustedaccordingtothenewreportingpointstructure.Theadjustmentismadebypreliminarycostingofthe
appropriateproductcostcollector,orautomaticallyduringbackflushinginrepetitivemanufacturing.

ReleaseUpgrade
Notethefollowingscenariosandspecialfeaturesineachreleaseorupgrade:

Release3.0/3.1:
Thereportingpointstructureisreadfromtheroutingandstoredwhenyoucreatearunscheduleheader.Subsequentchangestothereportingpointstructureintheroutingarenotpossible(workaround:
closethecurrentrunscheduleheader,changethereportingpointstructureintherouting,createanewrunscheduleheaderwiththenewreportingpointstructure).

Release4.0:
Introductionoftheflexiblereportingpoints.Changesinthereportingpointstructurearenowpossibleduringrealtimewithoutanewrunscheduleheaderhavingtobecreated.Thechangeismadeinthe

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=187336643

7/11

12/10/2014

CostObjectControlling(COPCOBJ)ERPFinancialsSCNWiki

systemusingacostingbyproductionversion(from4.5A:preliminarycostingforproductcostcollector).
TovaluateWIPandscrap,youcanusedifferentcostingsusingthevaluationvariantforWIPandscrap.
Youcancreateproductcostcollectorsforthevaluatedsalesorderstock(settlementtopricedifferenceaccountPRDonly).

Release4.5:
Interimbetweenproductioncostcollectorandproductcostcollector.Theproductcostcollectorisnolongerassignedtotheproductionversion.Insteaditisassignedtotheproductionprocess(toolthat
belongstothequantitystructuretool)accordingtothenamingruleassignedtothematerial(from4.6:Controllinglevel).OnlythePKMNordertypeisavailable,whichmeansthatallproductcostcollectors
mustbecreatedmanually.YoucanusetheKKF6Mtransactionformultiplecreationoftheproductcostcollectors(equivalentofmultiplecreationofrunscheduleheadersMF04).
Thesettlementoftheproductcostcollectorstomaterialnowincludesthedistributiontothedifferentvaluationsegments(MBEWformaterialwithseparatevaluation,EBEWforsalesorderstock).Thereisa
newsettlementruleforthiswithadistributionrulethataredynamicallydetermined.
Individualobjectsarenowassignedinthecostobjecthierarchyfortheproductionprocessinsteadoftheproductionversionorrunscheduleheader.
TheCostingbyproductionversionisnowcalledthepreliminarycostingfortheproductcostcollector.
ExistingproductcostcollectorsandcostobjectassignmentsareconvertedduringthereleaseupgradeusingXPRAsRK_PKOSA_MLMV_X1.

Release4.6:
Therunscheduleheaderisnolongeravailable.Backflushinginrepetitivemanufacturingtakesplacedirectlyviatheproductionversion,usingtheXPRAPPREM_XPRA_NO_RSHprogram.
Newinterfaceforprocessingproductcostcollectors(KKF6N)insteadoftheKKF6,KKF7andKKF8transactions.
Replacementoftheproductionprocessnumberbytheshorttextforalltransactionsinwhichyouhavetoenteraproductcostcollector.
Renamingofthenamingruletocontrollinglevel.
ThefunctionalareaistransferredasadefaultvaluefromCustomizingtotheproductcostcollectors(4.6C).

MMRelatedconfig:
OMS2materialtypesmakesurethat"costingrelevant"isactive(fieldT134EKALR)Materialiscostedwithquantitystructure
Thisindicatordetermineswhetherthematerialiscostedusingcostingwithorwithoutaquantitystructure.
Use
Ifyouusuallycostmaterialsusingcostingwithquantitystructure,
turnonthisindicator.
Ifyouusuallycostmaterialsusingcostingwithoutquantitystructure,
donotturnonthisindicator.
Youcanchangetheindicatorinthematerialmasterrecordatalater
time.
Procedure
Ifyoualwayscostyourmaterials(includingrawmaterials)using
costingwithquantitystructure,youshouldturnonthisindicator.
Thisimprovesperformance,becausethesystemdoesnotsearchinvainfor
existingcostestimateswithoutaquantitystructureforeverymaterial
whenitexplodestheBOM.Therefore,onlyturnonthisindicatorifyou
normallycostthematerialsusingcostingwithoutquantitystructure.
Regardlessofthesetting,youcancostasinglematerialwithor
withoutquantitystructure.However,youshouldbearinmindthatthis
settingisalwaysusedinthecostingrunandinmixedcosting(creating
procurementalternatives).
Dependencies
Foreverycostestimate,thesystemsearchesforexistingcostestimatesthathavethematerialsintheirstructure.Ifareleasedcostestimateexists,thesystemcopiesit.
Ifthisindicatorisset,thematerialiscostedusingcostingwitha
quantitystructure.
Thesystemsearchesforanyexistingcostestimateswithquantity
structurefortheindividualmaterialsitignoresexistingcost
estimateswithoutquantitystructure.Ifthesystemdoesnotfind
anyvalidcostingdataforthematerials,itcoststhematerialor
accessesthepriceinthematerialmaster.Seealso:
Transfercontrol
Ifthisindicatorisnotset,theplannedcostsforthematerialarecalculatedusingthecostestimatewithoutquantitystructure.In
thiscase,youuseunitcostingtocreatethequantitystructure
manuallybyenteringcostingitemsformaterialsandactivitytypes,
forexample.

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=187336643

8/11

12/10/2014

CostObjectControlling(COPCOBJ)ERPFinancialsSCNWiki

Thesystemnowsearchesforanyexistingcostestimateswithoutquantitystructure.Ifacostestimatewithoutquantitystructure
existsforamaterial,theresultsofthiscostestimateareincludedinacostestimatewithquantitystructure.Ifthereisnocostestimatewithoutquantitystructure,thecostestimatewithquantitystructure
accessesthepriceinthematerialmasterrecord.Theplannedcostsforthismaterialthengointothecostestimatewithquantitystructureasrawmaterialcosts.
ThisdoesnotapplyiftheindicatorIgnoreprodcostestw/oqty
structureissetinthecostingvariant.

OS20Indicator:itemrelevanttocosting
Thisindicatorcontrolswhetherand,ifso,towhichextentBOMitemsarerelevanttocosting.
Forexample,itemsthatarerelevanttocostingaretakenintoaccountforpricinginproductcosting.
Inaccordancewiththeusagekey,youdefineforallitemswhetherthey
omustbemaintainedincosting
ocanbemaintainedincosting(.)
ocannotbemaintainedincosting
KO88ActualSettlement:Order

Configuration
OPN2CreateValuationVariantforManufacturingOrders(PP)
OPL1CreateCostingVariantforManufacturingOrders(PP)
OPL8DefineGoodsReceivedValuationforOrderDelivery

WIPandRAconfig
OKG1RAKey
OKG2orOKG9RAVersion
OKGCValuationMethodOrderRelated(actual)
OKGDValuationMethodOrderRelated(plan)
SM31viewV_KKAXDefineLineIDs
OKGBorOKG5DefineAssignment(incomingchargesbyCEtoLineID's)
OKG4DefineUpdate(canbeusedtosegregateWIPcreation/accrualfromusage)
????DefinePostingRules(VariousTransactions)
OKG6NumberrangesforRA

Variances&Settlement
OKVWDefineDefaultVarianceKeysforPlants
OKV6DefineTargetCostVersions
OKOACreateSettlementProfile(w/oCOPA)

DevelopmentClasses

Dev.cl.

Shorttext

CK

R/3Applicationdevelopment:PPProductCosting

CK_ECP

CKAL

CKAPP

EasyCostPlanning

CostingALEfunctions

MiniAppsfortheCalculator

CKAZ

R/3Applicationdevelopment:PPCostingdispl.costcomponents

CKBA

Procurementalternativesandmixingratiosformixedcosting

CKBK

R/3applicationdevelopmentPPcostingvaluation

CKCO

R/3Applicationdevelopment:PPTransfertoCOobject

CKCORE

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=187336643

9/11

12/10/2014
CKCY

CostObjectControlling(COPCOBJ)ERPFinancialsSCNWiki
Treatmentofcyclesincosting

CKDS
R/3Applicationdevelopment:PPProductCostingDialogCtrl.

CKEK

Multilevelunit/simulationcosting

CKEXECUTION

E@syExecution

CKJ1

Customizingproductcostaccounting

CKJ2

LayerbetweenapplicationandCustomizing(costing)

CKJ3

Archivingandreorganizationinproductcostaccounting

CKJ4

Markingandreleaseforproductcosting

CKJ5

Customizing:flexibleerrorcontrol

CKJ6

USERexitsinproductcosting

CKJ8

BAPIsinProductCosting

CKKA

Interfaceforproductcosting<>customerorder

CKKT

R/3Applicationdevelopment:PPCostingdriver
program

CKMC

Customizingmaterialledger

CKML

Materialledger

CKMLCCS

ActualCostComponentSplit

CKMLCUMREV

CKMLDUV

CumulationandRevision

DistributionofUsageVariances

CKMLGRIR

AccountMaintenanceoftheGR/IRAccount

CKMLLA

UpdateofActivityConsumptioninQuantityStructure

CKMLMV

Quantitystructuretool

CKMLRUN

CKMLSIM

CKMP

CKMPC

CostingRuninMaterialLedger

Simulation

R/3Applicationdev.:PPCostingmanualmaintenance

MaterialPriceChanges
(ML)

CKR1

R/3Applicationdevelopment:PPCostingReporting1

CKSA

R/3applicationdevelopmentCOPCPCPquantitystructuretool

CKST

Quantitystructuredeterminationfromproductcostingdoc.

CKWB

ProductCostbyProductionLot(PreplannedSEIBAN)

CKWBREPORT

CKXX

CostReportsProductionLots

R/3Applicationdevelopment:PPCostingbasicproduct

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=187336643

10/11

12/10/2014

CostObjectControlling(COPCOBJ)ERPFinancialsSCNWiki

Stepstobefollowedforproductcosting
Twoaspects:
1.Calculatingstandardcostestimate
2.Ordercosting
1.Creatematerials
a.Fiverawmaterials(Twoforcreationofsemifinished,threeforfinished)ROH
b.OnesemifinishedmaterialHALB
c.OnefinishedmaterialFERT
2.Createsecondarycostelementsfordefiningactivitytypes
3.Createsecondarycostelementsfordefiningcreditelementsincostingsheet
4.Createactivitytypes(usecategory1&pricecalcas3fornow)
5.DefinepricesforcombinationofcostcenterandactivitytypeinKP26
6.Definecostingsheet
7.Definecostcomponent
8.Definecomponentsofcostingvariant
a.Datecontrol
b.Valuationvariant
c.Costingtype
9.Definecostingvariant
10.Next,createstandardcostestimate
UseeitherCKUC(formultiunitcosting)orKKPAN(formaterialwithoutquantitystructure)
Incaseofcsotingwithquanitystructure(meanswithBOM)weuseCK11N(forindividualmaterialcosting)&CK24forupdatepriceinmaterialmaster&CK40Nformasscosting&updatematerialprice.
ifwanttocaptureOVERHEADthenoverheadgroup&OHkeytobedefined,OHgroupisdefinedinMATERIALMASTER.whileratesaremaintainedforOHkeywithvaliditydates.ThisOHratesarethen
capturedincostsheetandthenrollupinmaterialcostthruuseofcostingvariant.
11.Nexttoupdateprices,usethebelowtransactionCK24forpriceupdate
First,MARK
Then,RELEASE

erp_co_copc_obj

2ChildPages
ProductCostByOrder
UnderstandingResultsAnalysisforWIP

2Comments
Guest
PleasereferPoint2.DifferentContexts>WorkinProcess:Thelastlinesays"WIPcannotbecalculatedattargetcosts.ItisonlypossibletocalculateWIPinProductCostbyPeriod."Iguess
youmeanttosay"ItisonlypossibletocalculateWIPatTargetCostsinProductCostbyPeriod".

NathanGenez
Rajanfeelfreetoeditthepageyourselfifyoufeelitisincorrect.

ContactUs
Privacy

SAPHelpPortal
TermsofUse

LegalDisclosure

Copyright

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=187336643

FollowSCN

11/11