Variance Member Calculation

I want to write BPC reports that sort on variance (Actual to Budget). Perhaps an analyst would also filter on variances to make it easier to find problem areas (i.e. variances > $10,000).
I don't think I can accomplish this with evDre() without creating a new CATEGORY/VARIANCE member.
Anyone have an example of a logic file/member calculation that replicates evBet() functionality and populates a VARIANCE member?
Is this already part of ApShell? Isn't this requested all the time? Possibly I am thinking about this incorrectly...
Thanks for any insight...Marv

I can't make member as store. Also changing member formula requires lot of changes as we have many versions and scenario to handle. I got the following solution to halt two-pass calculation with the sparse member and its working fine.
Ref:http://www.network54.com/Forum/58296/thread/1078946717/%25+variance+via+@VARPER+for+%25....ughh!+Can%27t+even+explain+it!
Apply a UDA to sparse dimension members with two-pass formulas
wrap two-pass formulas in dense dimensions with IF statements checking for NOT that UDA
Steps required:
Create a UDA in the scenario dimension called "Variance", and apply it to the Var% members.
The var% member is a sparse dynamic calc two pass member with the following formula: @VARPER(Actual, Budget);
Then, modify your two pass calc ratios in the accounts dimension formulas to look like this:
IF(NOT(@ISUDA("Scenario", "Variance")))
"GP %" = "Sales" % "Gross Profit";
ENDIF;
regards,
aamir

Similar Messages

Date Based Dynamic Member Calculation Performance (MTD, YTD, PeriodsToDate)

I'm working on an SSAS 2012 cube and I have defined several dynamic calculations based on a Date (MTD, YTD, TD, Thru Previous Month, etc.).
The cube has a well defined Date dimension and I have set up a DYNAMIC calculated set in the cube as shown below.
CREATE DYNAMIC SET CURRENTCUBE.[Latest Date]
AS TAIL(EXISTS([Payment Date].[Calendar Date].[Date].Members,[Payment Date].[Calendar Date].CURRENTMEMBER,"Claim Payment"));
... and here is an example of one of my calculations.
CREATE MEMBER CURRENTCUBE.[Measures].[Face Amount Paid MTD]
AS SUM(MTD([Latest Date].ITEM(0).ITEM(0)), [Measures].[Face Amount Paid]),
FORMAT_STRING = "$#,##0.00;-$#,##0.00",
//NON_EMPTY_BEHAVIOR = { [Claim Payment Fact Count] },
VISIBLE = 1 , DISPLAY_FOLDER = 'Face Amount' , ASSOCIATED_MEASURE_GROUP = 'Claim Payment';
This calculation returns the correct results, but performs horribly. I've noticed that changing the [Latest Date] set to STATIC, performance greatly improves, but numbers are no longer accurate as they are based on the Tail of the Claim Payment measure
group without considering the filtered dates. This is because the date is evaluated at process time, but needs to be based on users date selection to be accurate. Therefore, STATIC does not appear to be an option. Is there a better way to
perform this calculation dynamically based on the filtered or unfiltered date dimension?

Typically I would just do YTD/MTD/etc off the date the user has selected. It seems like you want to do it based on the last date with data within the range they have selected. Why not just give the user what they are asking for?
In other words, why not
YTD([Payment Date].[Calendar Date].currentmember)

Member calculated with extra decimal places

Hello experts,
I import a file in which all the figures have a maximum of 2 decimal places but the problem is that the first-level parent of the accounts have 9 or more decimal places. ¿Does someone know how could I fix the problem?
Thank you very much,
Alvaro

Hi,
To set that you need to go to BPC web admin> Application parameter> There you will find SIGNED_DATA_FORMAT, If not add it and update it.
Then in second column provide the number you want before decimal and after decimal say 26 digit before decimal and 2 after decimal then it will be 26,2 and update it.
After this modify the application to rebuild indexes and process the application to have the new format.
Regards
Raman

Essbase Member Calculation

Parent (Dynamic Calc)
--Child A (Stored)
----Child A1 (Stored)
We have data stored for whole year by month. While retrieving data for Child A1, the value is coming as “0” for all the months except current month, for current month the value is shown properly. Can someone suggest what might be the problem?
I'm new to essbase and have very minimal knowledge. Any detailed explanation for this issue would be of great help.
Edited by: user8736579 on Dec 17, 2010 10:12 AM

I would check the data being loaded for previous months. If it is retrieving as a 0, perhaps it is being loaded as a 0. (Revisit your assumptions)
Check any calc scripts. If you are not sure if a calc script could be causing the issue or not, load the data then do a retrieval before you run the calc scripts and a retrieval after you run the calc script. Look at the results.

Variance Calculation In Process order

Dear All Gurus,
We have produt cost by order.
In process order variance calculation I am gatting variance being calculated on Input v/s output costs.
While settlement also same variance is being posted.
I want variance to be calculated target v/s Actual
Please advice
Thanks in advance
Bhushan

I think in production order the variance is calculated between actual costs vs planned costs which is nothing but the input costs minus the gr coss of material produced at std costs.
Is that happenning or not??

Output price variance calculation

Hello,
I have a question on output price variance calculation in SAP.
The help reads:
"Output price variances are reported in the following situations:
If the standard price has changed between the time point of delivery to stock and the time point when the variances are calculated "
I do not quite understand this as when I have a standard price change between the delivery to stock and the variance calculation, I will already have a CO-PA entry for the price change. So why do I need another CO-PA posting for the variance?
Looking at the simple example of having costs of 150 USD when producing a material of 150 USD. If nothing changes I have a variance of 0 USD.
However if I receive the finished product to stock with a value of 150 USD and then revaluate to 165 USD before the variance calculation happens, I understand SAP would post an output price variance of 15 USD? But I also get 15 USD price variance from the stock revaluation into my books, so isnt that a double count?
Thanks a lot for your help
Kai

Hi Kai Hoffmann ,
As the SAP Help says...
Output price variances are reported in the following situations:
If the standard price has changed between the time point of delivery to stock and the time point when the variances are calculated
With respect to the above point, pls follow the example and let me know if you agree or not...
Let us say, we have Standard Cost of Product X for the month of Feb as $100 per tonne.
One Production Order is created for 100 Tonnes and you made Goods Receipt for 50 tonnes during Febrauray. (50 Tonnes posted to Inventory a @$100). Now, at the month-end, you estimated the Standard Cost once again and the new Standard Cost effective for the month of March is $110 per tonne.
Revaluation of inventory is done for 50 tonnes (for GR posted alread and in stock) and $10 * 50 tonnes is posted to Price Difference Account.
Now, during the month of March, you made the GR for balance 50 Tonnes on the Production Order. Inventory is posted @ $110. Once you do TECO and do the variance calculation, the system will post $10 * 50 tonnes as output price variance, which will flow to COPA and Price Difference Account.
So, I dont feel there is a double count or duplication...
waiting for your comments
Srikanth Munnaluri

Error while calculating variances for production order

Hi Gurus,
while calculating variances for production order i am getting the following error
"Cannot calculate scrap variances" ( Error message)
" no standard value estimate for material" (Warning message"
A standard cost estimate exists for the material at the date mentioned in the error in released status.
Please give solution for the error.
Thanks in advance n Regards
Arul.

Is there an itemization, generated for the cost estimate used to calculate the target costs?
Does the material components listed in the BOM of the cost estimate used to calculate the target costs, assigned to the operations in which they are used. Otherwise it is not possible to correctly report the variances and scrap when operations are confirmed.
Does the order for which the variances are calculated have a valid variance key. ?
Does the order have the status DLV (delivered) or TECO (technically completed). If the status was withdrawn, any variances and scrap variances are canceled.

Exclusion of target cost in Variance calculation

Hi,
While calculating variance in period end closing for a process order we are getting the errors.
1) No standard cost estimate for material 400000020 in plant TSIL on 26.12.2006 Target Costs: Determine Valuation Basis
2) Only remaining var. in version 0 - no target costs for 000001000109 Variances
We do not want to include the Target cost in variance calculation.
Please advise.
Regards
Aniruddha

Hello Anirudh,
If you choose costing version in variance calculation 0, then system calculates variance based on std. cost est. and actual cost. if you select 1, then system calculates variance based on planned cost and actual cost.
Go to customization settings in variance analysis calculation and change the costing version from 0 to 1.
Please let me know if you require any more clarifications.
Reward points if helpful.
Regards,
Santosh

Query regarding the variance calculation

Hi all,
Hope all are doing well. i have an query regarding the VARIANCE CALCULATION IN Production planning module.
here i could see KKS1,KKS2,KKA1 etc,. codes they are using in sap. can any one kindly clarify these codes and uses. pls
regs,
siva-v

Hi Siva,
To understand the basics of variance calculation in SAP, read below threads which will provide detail information on the same,
Basics of variance calculation-Understanding Period End activities, WIP and Variances
Variance Calculation -KKS1
How production order variance get calculated
Regards,
Narresh

Product costing - Variance calculation, Information system,

Hi,
I have an issue reconciling variances in product costing when I run S_ALR_87013139 - Cumulative. For instance I am getting results like below
Tgt (Dts) Actual (Dbts) Scrap Variance WIP Control Costs
33946 183020 0 27248 -95034 0
I was expecting
Variance = (Actual Debits - WIP credited) - Target Debits.
But it is not so. Am I missing something here
Would also appreciate if someone could tell
1. What does the target cost mean/how is it different from planned costs.
2. When is the target cost calculated? Is it only after the order is complete and variance calculation in KKS2. I also fing that whenever a production order is created I dont get target costs. Only planned costs are there.
Thanks for your help.
Ram

Hi Ram
Following are explanations for clarifications u asked for
1) Target costs = Actual qty delivered X standard costs ( as per standard cost estimate for the material). This means standard costs for actual goods delivered to stock. Planned costs means standard cost for planned qty of production order
2) Variances are calculated if the status of the order is either DLV or Teco and if material is issued and activities are confirmed. WIP is cancelled and variances are calculated
3) When u create production order - system only calculated planned costs of the order for planned quantities. Target costs are calculated only when goods are delivered to stock for the order either partially or full. Even if one qty is delivered to stock target costs gets calculated
Hope the above clarifies and do your checks with above
Pls assign points for the above clarifications provided

Accounting entry - WIP, Variance Calculation & Settlement of Production Orders

Hi All,
Please explain the process of WIP calculation, variance and settlement of production orders. At each stage will there be an accounting entry generated?
1. WIP calculation: All production orders for which the status is REL at the month end will be included in WIP calculation. How the amount of WIP is derived and what will be the accounting entry.
2. Variance calculation: Production order needs to have the status TECHO in order to do the variance settlement. Will there be an accounting action and how the amount will be calculated?
3. Settlement of Production Orders: Dr. WIP A/c (Balance Sheet a/c)
                                                    Cr. Volume Variance WIP a/c (P&L Account)
    Is this the correct accounting entry? If yes, please advice how the WIP a/c is showing balance on settlement of production order, how it will get nullified? If no, please advise on the correct process?
Regards

Dear Andy
In product cost by order scenario the WIP or Variance calculation is dependent on order status. If the Order has a status of REL or PDLV, the system will calculate WIP and if the order status is DLV or TECO the system will calculate variance on this order. At the time of calculation of WIP or Variance no accounting entry i generated but when you settle the order at that time FI documents are passed in the books.
Ans1- In product cost by order WIP or variance is calculated based on the actual cost debited to the order and value of GR made to the order. System does calculation by the formula GR value-(GI value+Activity value+ Overheads)
Ans2- As I said at the time of calculation no FI entries are passed but at the time of settlement FI entries are generated. The method of calculation is the same as described in Ans1.
Ans3- Entry at WIP settlement WIP (P&L) a/c Dr and WIP Offsetting(B/S a/c) Cr.
          Entry at variance settlement : Variance a/c dr/cr and COGM cr/dr.
          and if there is already a WIP posted for this order then at settlement WIP entry is reversed provided we have calculated WIP again the the month of settlement of variance
Note for Anand: Dear Anand we need to calculate WIP again in the period when the order status is changed to DLV or TECO otherwise system will not pass reversal entry of WIP. Kindly test it in your IDES and let me know if you find something on the contrary.
Regards
Rajneesh Saxena

Product Variance Calculation

Gurus,
How do we calculate Product variance?
What is the procedure / process?
Where can the effect be seen?
Edited by: Bhatia on Oct 15, 2008 6:44 PM

Hi,
Variance Calculation
As long the production order is not fully delivered or flagged Technical Complete the remaining order balance is treated as WIP. Otherwise the order balance shows up in variance calculation.
If a lot-based product-controlling WIP, is valuated at actual costs. The WIP is calculated as the difference between the debit and credit of an order as long as the order does not have the status DLV (delivered).
In lot-based product controlling the variances are not calculated until the order has the status DLV (finally delivered) or TECO (technically completed). This means that at the time the order has reached this status, the system no longer interprets the difference between the debit and the credit as work in process but as a variance. In lot-based product controlling orders never have work in process and variances at the same time.
Variance calculation compares the actual costs incurred for the production/process order with the target costs according to the standard cost estimate for the finished material, and assigns the individual variances to variance categories. The target costs are calculated using the quantity delivered for the order.
In this way you can find out which variances occurred between the value of the delivery and the actual costs and you can find the reason for the posting to the price difference account for materials with standard price control.
Variances from production (target version 1)
Variance calculation compares the actual costs incurred for the production order with the target costs for the production order and assigns the individual variances to variance categories. The target costs are calculated using the quantity delivered for the order.
This enables variance calculation to find out which variances occurred between the time the production order was created and the end of the production process.
Variances from planning (target version 2):
Variance calculation compares the planned costs for the production order with the target costs according to the standard cost estimate for the finished material, and assigns the individual variances to variance categories. The target costs are calculated using the quantity delivered for the order.
This enables variance calculation to find out which variance occurred between the time the standard cost estimate was created and the time the production order was created.
Variance categories:
The system assigns every variance to a variance category. The variance category indicates the cause of the variance (such as price change, lot-size variance). Variances are updated to the information system and passed on to Profitability Analysis according to variance category.
You differentiate between variance categories on the input side and on the output side:
u2022     Variances that occur because of goods issues, internal activity allocations, overhead and G/L account postings are displayed on the input side. Price variances, quantity variances, resource-usage variances and input variances are displayed on the input side.
u2022     Variances that occur because too little or too much of the planned order quantity were delivered, or because the delivered quantity was valuated differently are displayed on the output side.
Variances on the output side occur when you deliver using a price that differs from that found by dividing the target costs and the delivered quantity. If you deliver using the standard price, a variance can occur when the order lot size differs from the costing lot size. This is displayed as a lot-size variance.
For config
3.1.4.2     Variances & Settlement
Variance Calculation determines differences between the actual costs incurred on a production order and the standard costs of the material produced. Variances are calculated not at once, but for different variance categories. The variances computed are then transferred to CO-PA.
3.1.4.2.1     Define Default Variance Keys for Plants
Use
The Variance Key is part of the order header and controls variance calculation. The system selects the value set by this step as default value when a material master is created. From the material master the variance key then is transferred to the order when an order for the material is created.
Procedure
1.     Access the activity using one of the following navigation options:
Transaction Code     OKVW
IMG Menu     Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Order  Period End Closing  Variance Calculation -> Define Default Variance Keys for Plants
2.     Make the following entries:
Plant     Variance Key
BP01     000001
BP02     000001
BP03     000001
BP0X     000001
3.1.4.2.2     Define Target Cost Versions
Use
The target cost version controls various parameters related to calculation of target costs in variance calculation. In variance calculation, target costs are needed as a comparison to the actual costs incurred.
Procedure
1.     Access the activity using one of the following navigation options:
Transaction Code     OKV6
IMG Menu     Controlling Product Cost Controlling  Cost Object Controlling  Product Cost by Order  Period End Closing  Variance Calculation  Define Target Cost Versions
2.     Choose New entries and enter the following values or copy from default settings of CoArea 0001 to BP01:
CoArea     TgtCostVsn     Text     Variance Variant     Control Cost     Target Cost
BP01     0     Target Costs for Total Variances     001     Actual Costs     Current Std cost Est
BP01     1     Target costs for production variances     001     Actual Costs     Plan Costs / Preliminary Cost Estimate
BP01     2     Target costs for planning variances     001     Plan Costs     Current Std cost Est
3.1.4.2.3     Create Settlement Profile
Use
The settlement profile controls various parameters related to settlement.
Prerequisites
Allocation Structure
Procedure
1.     Access the activity using one of the following navigation options:
Transaction Code     SPRO
IMG Menu     Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Order  Period-End Closing  Settlement  Create Settlement Profile
2.     Choose New Entries and enter header data. Then for each new entry choose Details and enter remaining data.
3.     Overview of data records:
Profile     Text
YGPI00      BP Process Order w/o CO-PA
YGPP00     BP Production Order w/o CO-PA
YGPI00     YGPP00
Actual costs/costs of sales
To be settled in full     X     X
Can be settled
Not for settlement
Default Values
Allocation Structure     A1     A1
Source Structure
PA Transfer Struct.
Default object Type
Indicators
100% Validation     X     X
%-Settlement     X     X
Equivalence Nou2019s     X     X
Amount Settlement
Var. to co. bsd. PA
Valid receivers
G/L account     N     N
Cost center     O     O
Order     O     O
WBS Element     O     O
Fixed asset     N     N
Material     O     O
Network     N     N
Profit. Segment     N     N
Sales order     O     O
Cost objects     O     O
Order item     O     O
Business proc.     N     N
Real est. object     N     N
Other parameters
Document type      SA     SA
Max.no.dist.rls     3     3
Residence time     3     3
You have to assign Variance Key in material master for semi-finished and Finished goods in costing 1 tab also.
To Execute
KKS1-Collective Variance calculation
KKS2-Individual Variance calculation
CO88-Collective settlement
KO88-Individual settlement
Thanks,
Rau

Production Variances of semifinished goods in COPA

Hi,
We are using Costing based COPA, which is updated at the time of billing.
The production variances are posted to COPA when the settlement of the production orders are done.
The production variances if brought within the purview of COPA report (based on sales), the plan vs actuals can be compared. However, in case of actuals, the production variances would appear only to the extent of tha particular product sold (that too, to the extent of qty produced and not qty sold)..
I have two issues:
1. Whether system can explode the BOM and bring in the production variances of semi-finished goods into the total production variances, if I drill down only on the Finished product sold. The total actual cost would include the variances of relevant SFG also. Is this possible, if so how?
2. Whether, by bringing production qty and sales qty, the proportionate prod variances be calculated (total prod var * sales qty / prod qty). This can surely be done by inserting formulae. But is this justified from business point of view?
Please help me resolving this issue..
Edited by: Swapvik on Mar 17, 2009 7:11 AM

Hi Swapvik,
Issue No.1:
When you are using only Standard Costing in CO-PC, variances will not get rolled-up to the next level. Only costs get rolled-up. As per your requirement, when you see the report in COPA, when you see the details of FG and you want to see the variances of it's SFG also, this would be possible only if you have activated Material Ledger. If ML is active, variances also get rolled-up along with costs.
Issue No.2:
The ultimate purpose of bringing Variances into COPA and making part of them in a report is to consider COGM subject to the variances. Though it is not 100% justified, it gives you the most appropriate analysis compared to where you don't consier the variances at all. If you don't consider variances there, that means, you are considering only COGM and not taking the effect of variances, which will definitely not a correct picture of Profitability.
Pls revert back for further explanation...
Srikanth Munnaluri

Qty and Date Variance using Purchasing InfoCube

Using Purchasing Cube, I want to find out the Qty Variance and Date variance,
Iu2019m calculating these using GR Posting date and Requested Delivery Date and GR Qty and Qty in UoM.
Iu2019ve the following doubts:
1.     In order to calculate the Variance, do we need to filter the data pertaining to any particular BW Transaction Key (0PROCESSKEY) since we donu2019t want Goods Issues (can be Purchase Returns or intra company Stock Transfers ), If so what are the values for the Process Key to be considered for filter.
2.     Though the Qty key figure matches the Requested Qty, the PO status is u2018Openu2019. What could be the possible reasons?
3.     The qty. and days variance for the POs already received can be calculated. But what should be done incase of POs for which Goods are not yet received? Again in that scenario, we can have two cases: Delivery Past Due and Delivery Date in Future. How to tackle these 2 cases. As per our Requirement, we have to calculate the difference between System date and Requested Delivery Date incase of Past Delivery Date so that we can have the variance as of System Date. Like If the Delivery Date is 25th Nov, if we run the Query on 28th, it should show 3 days late and if run on 29th, it has to be 4 days if still undelivered. Please give me the code to be written in Transformations.
We have not yet decided what has to be done in the second case i.e. Future Delivery Date. Please guide me what is the best option in that case.
Thanks,
Aryaman

Hi,
1. In order to calculate the Variance, do we need to filter the data pertaining to any particular BW Transaction Key (0PROCESSKEY) since we donu2019t want Goods Issues (can be Purchase Returns or intra company Stock Transfers ), If so what are the values for the Process Key to be considered for filter.
You need to add Z-Keyfigures and then write Routines based on Process Keys in Update Rules/Transformations and filter the required Process Keys, you need to find required Process Keys in ECC, SPRO-->Reference IMG an dthen search for BW Transactional Key and see it disuss with MM FUnctional COnsultant and Identify it.
2. Though the Qty key figure matches the Requested Qty, the PO status is u2018Openu2019. What could be the possible reasons?
I faced the problem with 2LIS_02_* datasources so I created new generic data source and used it. Just take only one record with that you track in ECC. You must take MM Consultants help, they will guide you.
3. The qty. and days variance for the POs already received can be calculated. But what should be done incase of POs for which Goods are not yet received? Again in that scenario, we can have two cases: Delivery Past Due and Delivery Date in Future. How to tackle these 2 cases. As per our Requirement, we have to calculate the difference between System date and Requested Delivery Date incase of Past Delivery Date so that we can have the variance as of System Date. Like If the Delivery Date is 25th Nov, if we run the Query on 28th, it should show 3 days late and if run on 29th, it has to be 4 days if still undelivered. Please give me the code to be written in Transformations.
We have not yet decided what has to be done in the second case i.e. Future Delivery Date. Please guide me what is the best option in that case.
Once you have Qty and Dates from Transactional Data then it is easy to calculate the Date Varience and Qty varience, see the follwoing URL it is having one article How to Calculate Meterial Aging whcih will give how to calculate the differnce..
http://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
Thanks
Reddy

Target sost calculation not considered Current cost estimate in KKBC_ORD

Hi All,
We have an case wherein it observed that target cost calculation on SFG is wrong
in KKBC_ORD where system does not considered the current cost estimate.
We have all the necessayry customisation in place for Target cost version 0 for current cost estimate.
Below is detailsed case.
1 Process Order created in Dec 2011
2 Price Released to Mat master on 01.01.2012
3 Goods movement,Operation confirmad Material Issues, FG qty delivered @ std cost 0n 04.01.2012
4 Order Technically completed (TECO)
5 KKS1/KKS2 will be done at month end.
We know that In Process order, after deliver of FG the target cost on FG is not getting calculated,target cost will be updated only after calculating variance. it does
not calculate after delivery of finished goods, On Execution of KKS1/KKS2 variance will be calculated the target cost on FG and will be updated.
In process order (COR3 --> Cost analysis) Target cost ,Actual cost and Planned cost are calculated based on the following:
Total Plan Cost = Std Cost the material required to Produce X Planned Qty of the required material
Target Cost = Std Cost the material planned to Produce X Std Qty of material required to produce, for Produced Actual Qty
Actual Cost = Std Cost the material planned to Produce X Actual Qty of material consumed, for Produced Actual Qty
The variance is calculated on SFG and assemblies based on the difference between actual and target cost in KKBC_ORD. During creation of process order, the plan cost
will be updated with the valid standard cost upon the creation.
The target cost on SFG and Assemblies is only generated when there is good receipt from production order into inventory.
The target cost is generated using the valid / recent costing run for the correspondence SFG in KKBc_ORD.
All other target costs showed in COR3 (Menu Go to > Costs > Analysis) or KKBC_ORD before doing KKS1/2 is only statistical- However in our case Traget cost calculated
on SFG in KKBC_ORD not relevant with current cost estimate.
However Actual cost and Planned cost Calculated correctly.
Actual Cost= Current Standard costof the materilal(5.624,88)X Actual Qty (13.693)=77.021,48
Planned cost= Std Cost the material required to Produce (6.572,12) X Planned Qty (12.415)= 81.592,87
However Target cost is not considering the current cost estimate;It should be - Current Standard cost of the materilal(5.624,88)X Target Qty(13.958,124)=78512.07.
But Errorneously Target cost is showing 67.383,59 which causing unfavorable variance to standard.
It should be 78512.07-77.021,48= 1490.59 favourable var to standard in KKBC_ORD.
Any help,suggestion and input would be highly appreciated.
Thanks with Regards
Subrata

hi
target cost is your standard cost* actual confirmed quantity, not the standard quantity required
the variance calculated will be always the actual debit to the production order- actual credit of the production order
your actual credit for the process order is std cost* actual quantity delivered to the inventory= Current Standard costof the materilal(5.624,88)X Actual Qty (13.693)=77.021,48
actual debit to the process order is total actual cost which you can see in COR3 report .
By the way for which period you have calculated variance, target cost will be calculated based on that months standard cost
krishna

Variance Member Calculation

Similar Messages

Maybe you are looking for