I like your videos :) Can I ask a question ? I created a PP order with WBS by using t-code CO10 , and posted additive cost by FB60 to this PP order, when I post goods receipt after completing this PP order , the additive cost(FB60) is not included in the price of the finished goods . The price of goods receipt is the same with the planning cost of PP order. Is there a way to include the additive cost to the finished goods while posting goods receipt? Thank you a lot in advance, I believe you have a solution :)
Thank you for your interest. but this requires testing. I don't have definitive answer. a.) are you using Moving Average? b.) have you tried Prj/Sls Ord valuated stock? if it doesn't work, then user exit on goods receipt is the only possibility. I think for your scenario, you can collect cost on WBS or Network. Result analysis for WIP, and settled to CO-PA. Thanks.
Great Video Master, Please can you show us your OKO6 and OKO7 for the Settlement Production Order, sorry I have dubts between KO88 and VA88 process, I am still facing Error Message No. KD256, Can you help me ? Thanks a lot.
Hi, thank you for your interest. Apologies, the license of the system has already expired. So I can't show the system anymore. But below may show some example. Please check them. ua-cam.com/video/kubp4XHt_Kc/v-deo.html VA88 Sales Order Settlement, Make To Order (4) ua-cam.com/video/eSM0NP2WVUE/v-deo.html CO PA configuration (Costing-Based)
Thank your for your interest. KD256 - we can't reproduce the error. In the sap community blog, somebody mentioned Posting Rule (OKG8). This is to post WIP amount, setting off cost incurred for the period. WIP will be zero off in the end when revenue recognized. In the OKG8, 1 account is WIP acct (BS), the other account should be P&L (Non operating P&L, no cost element, or CE cat 21 external settlement). These 2 accts need to be configured for the key WIPR (WIP required). We have this setting.
Nice video! Your SAP skills is so good. As a FICO consultant, I've learn a lot from your video. Thank you!
Really nice video thank you!
great video!
Didnt we miss KO88 Transaction to have 180 production order variance to sales order
I like your videos :) Can I ask a question ? I created a PP order with WBS by using t-code CO10 , and posted additive cost by FB60 to this PP order, when I post goods receipt after completing this PP order , the additive cost(FB60) is not included in the price of the finished goods . The price of goods receipt is the same with the planning cost of PP order. Is there a way to include the additive cost to the finished goods while posting goods receipt? Thank you a lot in advance, I believe you have a solution :)
Thank you for your interest. but this requires testing. I don't have definitive answer.
a.) are you using Moving Average? b.) have you tried Prj/Sls Ord valuated stock? if it doesn't work, then user exit on goods receipt is the only possibility.
I think for your scenario, you can collect cost on WBS or Network. Result analysis for WIP, and settled to CO-PA. Thanks.
Great Video Master, Please can you show us your OKO6 and OKO7 for the Settlement Production Order, sorry I have dubts between KO88 and VA88 process, I am still facing Error Message No. KD256, Can you help me ? Thanks a lot.
Hi, thank you for your interest. Apologies, the license of the system has already expired. So I can't show the system anymore. But below may show some example. Please check them.
ua-cam.com/video/kubp4XHt_Kc/v-deo.html
VA88 Sales Order Settlement, Make To Order (4)
ua-cam.com/video/eSM0NP2WVUE/v-deo.html
CO PA configuration (Costing-Based)
Thank your for your interest.
KD256 - we can't reproduce the error. In the sap community blog, somebody mentioned Posting Rule (OKG8). This is to post WIP amount, setting off cost incurred for the period. WIP will be zero off in the end when revenue recognized. In the OKG8, 1 account is WIP acct (BS), the other account should be P&L (Non operating P&L, no cost element, or CE cat 21 external settlement). These 2 accts need to be configured for the key WIPR (WIP required). We have this setting.