Variance calculation repport (KKS2) different to variance line items (KOB3)

Hi, need your help.
I´ve run variance calculation (KKS2) for one production order, one target cost version and it has calculated correctly all cost element variances. However, when I display variance line items (KOB3) for this order with the same target cost version used in KKS2, calculation is´t correct for all cost element and if I compare it with KKS2 repport, it displays different values. Does anyone know why?
some details that may help:
WIP is customize
The company I´am working for had activated "write line Items" (OKV1) after the golive,
Scrap check box is activate in variance key,
All variance categories are activate,
etcetera
Thank you for your help.
Regards,
André

Hi
I would suggest raise an OSS msg then.. Because i dont see any possible reason why this could happen
In my case, the only discrepancy I found was variance doc was posted to FI and not to COPA because the user did not execute variance calculation in update mode.. So, variance got posted in FI, but not in COPA...
But the posted values always matched in my case,,,
Do update us incase you find solution
Regards
Ajay M

Similar Messages

  • Different currency in line items for GL posting

    Hi
    Is there any possibility of having different currency for line items, if so send me sample code for the same. This is needed for me for Inter company GL Accouting posting.
    Thanks
    Basani

    Is the GL account a recon account?
    You need to use t code FBL3N.
    However in FS00 check the settings for Line Item display in the Control Data tab.

  • 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

  • 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 calculation when using assessment to PP orders

    Hi,
    I managed to activate assessment to Production orders in BS12.
    I activated business transactiun RKIU for PP orders object.
    Now it's possible to allocate OH costs from Cost centers to production orders.
    However, I have some problem of other nature.
    When I do the standard price calculation - the Overhead costs from Production Departament CC are calculated as % overhead using costing sheet. It is done by cost element with cost element ctg 41.
    The actual OH costs from Cost centers are allocated using assessment. Other cost elements with cost element category 42 are being used here.
    How will the system calculate production variances in this case?
    Do u think it is possible to match these two different cost elements?
    Will this CE with 41 ctg be considered during variances calculation and if yes - which variance category will it be.
    I am uncertain about that, cause in normal cases - activitity CE or materials consumption CE are the same in actual and target. In my case overhead CE are different in actual and in target.
    Can u help me with that?
    Best wishes,
    Karol

    It's looks like you are right. I've made production version for configured material and production order created. Thanks.
    Due to such a behavior we have to make two different integration models - the first for KMATs and its PDSs and the second for configured variants. And we have to make production versions for all variants.
    Am I right?

  • Target cost calculation in Process Order based on Variance Calculation

    Hi all,
    I have a question on Target cost calculation in Process Order. My understanding is, the Target Costs gets calculated when the confirmation and GR is made for the Process Order.
    But if the confirmation/GR is not done, whether the target costs gets calculated for only the activity types after the Variance Calculation (KKS2).
    I have two scenarios. In one, the target costs got calculated for the activity types without the confirmation/GR after the Variance calculation.
    In another scenario, the target costs are not getting calculated for the activity types without the confirmation/GR if I try to do the variance calculation in KKS2.
    SO i want to know which scenario is correct?
    Can anyone answer this question?
    Thanks and Regards,
    Brijesh

    Hi,
    In general, the target costs are calculated once you deliver the order.
    Target costs for the components and the activities are updated only once you deliver the order and the target cost for the finished product gets updated when you do the variance calculation.
    Consider your scenario number 1 - you said the target costs got calculated for activity types without confirmation / GR after variance calculation.
    Now, if the order is not having any status like PDLV, DLV or TECO it will not calculate the variances in the first place.
    Your second scenario is correct - without GR the system does not calculate any target costs. Also it will not calculate any variances because the order status is still not DLV.
    Best Regards,
    Sameer

  • 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

  • Variance Line items not showing in KOB3 - Previous Orders.

    Hello CO Experts,
    Because of not selecting 'Write Line items' check box in Variance key (OKV1), KOB3 is not showing any line items even though variance posting exist.
    After selecting  'Write Line items' check box in Variance key (OKV1), any variance posting there on will be recorded to display as line items in KOB3.
    But my question is how to make this line item display effective for variances posted before selecting 'Write Line items' check box in Variance key (OKV1).
    Thanks in Advance
    -Sahas

    Hello Declan,
    thank you for confirmaiton.
    I think SAP would have provided some solution (may be a program) to make this line item display effective for variances posted before selecting 'Write Line items' check box in Variance key (OKV1).
    -Regards
    Sahas

  • Display Variance line items for Orders

    Hello Sapients,
    I am trying to execute Transaction code KOB3 (Display Variance line items for Orders) ( /n > Accounting> Controlling > Product Cost Controlling > Cost Object Controlling > Product Cost by Order > Information System > Reports for Product Cost by Order > Line Items > KOB3 )
    But for some reason I do not see any thing.
    Your Advise is greatly appreciated.
    Thanks and Regards
    Ravi

    There is no problem with Authorization.
    And i am checking for the correct cost elements and prorcess orders.
    Not only KOB3 but also the related reports are not working (viz: GR55-> 7KV9)
    thanks and Regards
    Ravi

  • 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

  • Line item number and ledger item number posted differently

    Hi Friends ,
      I have a BAPI for posting the documents in SAP from another system.This BAPI is using the standard BAPI -  'BAPI_ACC_DOCUMENT_POST' to post the documents.But when I post the document using this BAPI the line item number and ledger item number in the document are posted differently. ie . for line item no 1 ledger item is 24 .But when I am posting it directly it is same ie for line item no 1 ledger item no is also 1.Lot of other programs in our R/3 system is dependent in this logic.What could be the parameters in BAPI that could affect line item and ledager item ? Can anybody help me in finding out the reason for this ?
    Thanks in advance ,
    Joby

    Hi ,
    Anybody can help me on this issue ?
    Thanks in advance ,
    Joby

  • Line item dimension wont insert sid values in infoobject sid table

    Hi all,
       I have a strange problem, whenever I load data into a cube which has a line item dimension on 0customer without first loading the master data I am getting inconsistency in RSRV saying that no corresponding DIMid exists in sid table.
    So there are Dimids in the fact table but the dimension table, which is same as the sid table in the the case of line item dimension, doesnt have them.
    Can someone explain me why is this happening?  I thought if a characteristic value doesnt exist in the master data but comes in through the transaction data it inserts the same in the sid table. 
    Is there a different rule for line item dimensions? Can someone point me to some OSS or documentation?
    thanks

    Thanks all..
    To clear up a few questions:
    1. What I mean by <i>"So there are Dimids in the fact table but the dimension table, which is same as the sid table in the the case of line item dimension, doesnt have them"</i> is:
    the line item dimension table /bic/D<cubename>9 which is really a view on the sid table for characteristic /bic/s<ch. name> does have all the sid values (or all the dim values) as the fact table.
    So fact table has more entries for that dimension than the sid table.
    2. Yes we are facing reporting errors where we cannot drill down by that infoobject and LISTCUBE doesnt show us any cube data when that characteristic is chosen for display.
    3. I have checked notes where it seems to be a RSRV bug but in our case it doesnt seem to be as observed in the actual table mentioned in #1
    Now it is apparent that I am right both from help.sap.com link and what I am observing that for line item dimensions master data HAS TO BE LOADED FIRST for the characteristics used as a line item.

  • Line Item numbers out of sequence in C_T_DATA

    We are using several different data sources within include ZXRSAU01.
    For one of them, we have assigned a custom structure ZOXNRD0112 to C_T_DATA which contains two different fields for Line Item number. One of these fields is based on FAGLFLEXA-DOCLN and the other is based on BSEG-BUZEI.
    The values in these two fields should agree on each record contained within C_T_DATA, but occasionally we get a situation where they do not. BUZEI is always correct when compared to the Billing Document, but DOCLN will be out of sequence.
    For example:
    DOCLN BUZEI
    000001 001
    000003 002
    000002 003
    DOCLN & BUZEI both arrive already populated in the C_T_DATA table.
    We simply use the values as keys to read FAGLFLEXA and BSEG, the values in DOCLN & BUZEI themselves are not derived.
    They are there when entering the user exit ZXRSAU01, and they are still there when processing leaves ZXRSAU01.
    I donu2019t have a lot of experience in BI, and am not familiar with how C_T_DATA receives itu2019s data.
    Iu2019m trying to look back further in the processing to find where C_T_DATA is populated and draw some conclusions from that. I have asked a couple of our FI people to examine the documents involved to see what could be going on there.
    We are on ECC 6.0, and BI version 7.0.
    Has anyone out there run into this kind of problem before?

    Hello Dan,
    Welcome to SDN!
    The program ZXRSAU01 is an exit program for transactional DataSource extraction. Whenever the DataSource pulls data from ECC, it usually divides the data into several data packages, and for every package it will comes to that program. The internal table C_T_DATA contains all records of the data package.
    We don't use sequence to link data together, but use fields mappings. For example, I want to read FAGLFLEXA-DOCLN, I first need to find a key field say XXXX which exist both in C_T_DATA and FAGLFLEXA. Then use below statement to read FAGLFLEXA:
    loop at c_t_table into ls_structurename.
    select single DOCLN
        from FAGLFLEXA
        into ls_structurename-docln
      where XXXX = ls_structurename-XXXX.
      modify c_t_table from ls_structurename.
    endloop.
    With the code we don't need to worry about sequence. And it works for either full loading or delta loading.
    Please let us know if you have any questions.
    Regards,
    Frank

  • Line item and Ledger item difference when parking through BAPI

    Hi Friends ,
      I have a BAPI for parking the documents in SAP from another system.This BAPI is using the function module PRELIMINARY_POSTING_FB01  to park the documents.But when I park the documents using this BAPI  and post the document manually  the line item number and ledger item number in the document are posted differently. ie . for line item no 1 ledger item is 24 .But when I am posting it directly it is same.Lot of other programs in our R/3 system is dependent in this logic.Can anybody help me in finding out the reason for this ?
    Thanks in advance ,
    Joby

    Hello,
    Which BAPI you are using. Use BAPI_INCOMINGINVOICE_PARK.

  • Not displaying ship to party for second line item

    Hi All,
    When I am creating Sales order, I entered sold to pary,PO number,PO date,material (first line item)and qty.In partner functions for first line item it is displaying ship to party.But whaen I entered second line item & qty,ship to party is not displaying .
    Please guide.
    Thanks,
    GTNR

    Couple of questions !!!!
    a)  Was system allowing you to save
    b)  has the data properly configured in Set Up Partner Determination for Sales Document Item
    c)  is the ship to party different for first line item
    d)  did you check in incompletion log
    G. Lakshmipathi

Maybe you are looking for

  • GRC AC 10 - risk analysis : No rules were selected

    Hi, In GRC AC 10, when I do a risk analysis (user level for example). For each userid the result shown in the column action is "No rules were selected " any idea ? Thanks Aurélien.

  • Where is save as draft in toolbar for mail

    I know you can use save from the File pull down but it is so much easier to have it on the toolbar -where did it go? thanks for any help Theprin

  • Not able to create disaster recovery VMM -- ovm pool / repository ownership issue

    I have installed VMM and VMS and create a server pool with 3.0.2 version. To test disaster recovery, I rebuild the VMM with the old UUID by runInstaller.sh --uuid 0004fb00000100002ae..... and restore the repository database. The new VMM (same IP as o

  • Which is the best mac to buy ?

    Hey guys and gals, im looking at buying my first mac computer. i'm looking at buying one mainly for photo & video editing. I'm not sure about all the stats and parts that go into a computer i just need one as cheap as possible to get the job done. an

  • March 9 FBI to shut off the internet.

    Not sure if this is true. FBI thinks this is needed to be done. A virus needs to be cleaned, and if you have the Virus after it is cleaned you can't get in the web if you have it. Just would require you to clean your computer to connect again. Be pre