How to settle the production order variance to 3 GL account

dear all
i met a problem in the project ,the customer need see the production order variance category detail for (material,routine,overhead variance) in FI report ,so it need to settle the variance to at least 3 GL account
i don't know how to configure it ,i try to use result analyse like wip ,but go failed
do you have some suggestion
thank you

Hi ,
Through Standard SAP .. the same it not possible . Standard SAP will post the differences to one GL account ..The variance amount is not segregated..
The way out is to use report KKO0  .( Product Costing Drill Down Reports  )  in CO . There are many reports available .. and you can compute the difference in CO Reports and manually make an entry in FI by manually reversing the original variance account and posting it to cost component wise variance accounts ..
To use the KKO0 report.. please perform the following tasks :-
1. Assign cost component structure in transaction OKN0 ( Date Extraction/Product Drill Down) tab.
2.  Product Group Type = Material group..
3. Run KKRV after period end every month to collect the data for drill down reporting..
Please revert back for any further clarifications
Regards
Sarada
Sarada

Similar Messages

  • How to settle the sales orders

    Hi experts,
    Can anyone tell me how to settle the sales orders? What is the transaction code?
    regards
    vk

    Hi VK ,
                 Being production consultant I think production order which is created with reference to sale order will be settled in ko88 or co88 after calulating variance ( and settling in variance a/c ) , Work in progress .
    Prod order should have TECO indicator before you settle .
    Neal

  • Settle the production order

    hi,
    what are steps to settle the production order( order settlement)
    thanks & regards,
    elanchi

    Hi,
    Follow below steps for order settlement. Before order settlement confirmation must be done i.e order should have CNF status.
    - After Final Confirmation of Order make GR for for order using Tcode : MIGO / MB31 for manual or at confirmation with auto goods reciept. so Production Order Status will be delivered -DLV.
    -Then complete the order technically in CO02 - Functions ( Menu)--- Restrict Processing -
    Technically Complete. TECO for multiple Orders in mass basis with COHV.
    -Next Calculate Overheads using Tcode KGI2 (Individual Processing) or CO43 (Collective Processing)
    -Then Calculate WIP using Tcode KKAX (Individual Processing) or
    KKAO(Collective Processing).
    -After that Calculate Variance by Tcode KKS2(Individual Processing) or KKS1 (Collective Processing)
    -Finally do the settlement of Order with Tcode KO88 (Individual Processing) or CO88 (Collective Processing).
    After settlement order balance will be zero & then you can do the closing of order.
    in CO02 - Functions ( Menu)--- Restrict Processing -
    Close. Close for multiple Orders in mass basis with COHV.
    Hope this will help you.

  • How to delete the production order in mass?

    Dear Experts
                 Please tell me how to delete the  old production orders?

    Raja,
    CO78 is a one stop transaction for production order setting deletion flag, deletion indicator, archiving and finally deleting.
    Generally we schedule the following programs in background in the sequence below,
    1. PPARCHP1 for Setting Deletion Flag
    2. PPARCHP1 for Setting Deletion Indicator (Once set cannot be revoked- so care should be taken in selection of orders)
    3. PPARCHA1 for archiving the production order with Deletion Indicator active. Basis should set the database/storage space for archiving/storing the records.
    4. PPARCHD1 for Deleting the records from SAP database.
    Regards,
    Prasobh

  • How to check the Production order exits

    Hi Experts
    Modification to processing of Command Orders & Tickets
    We require a modification to the processing being performed on sales data originating from the Command Concrete system and potentially from other systems yet to come online (e.g. Pinkenba Cement plant).
    The Sap process involved is ZINT_INBOUND_POLLING and within that, ZINT_CSTPORD_ROUTINES.
    The problem
    Currently there is an assumption that every sales order (and its deliveries) will include a product which is made to order, i.e. for which a production order will be required.
    In ZINT_CSTPORD_ROUTINES, a check is made to identify the production order linked to the sales order. If there is no such production order (usually because of the customeru2019s credit status) then processing of the ticket is terminated.
    This assumption would fall down if an order was to be raised (in Command) on which there is no concrete material. For example, if we sold a bag of pigment or a screed to a customer. In this case the item would be sold from stock and there would be no need for a production order.
    The solution
    In the routine which checks for the existence of a production order, modify the code as follows:
    Inspect each item on the sales order
    If (and only if) there is at least one item with a category of u201CZTACu201D then check for a production order, otherwise process the order in the usual manner.
    ----  ZINT_CSTPORD_ROUTINES -
    *&      Form  process_inbound_data
          Create prod. orders from ticket data extracted from the COMMAND
          system. Note that large portions of the code in this routine
          have been copied from the retired ZPPU_COMMAND_PRODUCTION
          interface program. This was done (1) because the old code works
          and (2) to save development time.
         -->T_ZINT_IDATA  Internal table of interface data
         -->T_ZINT_PARAM  Internal table of interface parameters
         -->T_ZINT_MSLOG  Internal table of messages
         -->P_ZINT_ID     Interface ID
         -->P_ZINT_TY     Inteface type
         -->P_ZINT_IS     IDOC group for interface
         -->P_ZINT_DL     Flag: delete IDOC group when complete
         -->P_ZINT_AL     Flag: run in standalone mode
         -->P_ZINT_NW     Flag: do not log warning messages
         -->P_ZINT_SQ     Interface sequence number
         <--P_ZINT_RC     Return code (<>0=>error)
    form process_inbound_data  tables   t_zint_idata structure zint_idata
                                        t_zint_param structure zint_param
                                        t_zint_mslog structure zint_mslog
                               using    p_zint_id    type      zint_id
                                        p_zint_ty    type      zint_ty
                                        p_zint_is    type      zint_is
                                        p_zint_dl    type      zint_dl
                                        p_zint_al    type      zint_al
                                        p_zint_nw    type      zint_nw
                                        p_zint_sq    type      zint_sq
                               changing p_zint_rc    type      zint_rc.
    program is continuing .............
    I WANT TO WRITE A CODING HERE **********************
    CHECK IF PRODUCTION ORDER REQUIRED
              IF NOT THEN GO TO PERFORM UPDATE DATA
      if production order required then check
                    for each item on sales order item list
                          with item category = 'ZTAC' then
                                     return true
                                next
                                  end function
        if there is no production code
               these has to be check from VBAP TABLE field VBELN and PSTYV (ZTAC,ZTAN Etc)
      select * from Vbap WHERE VBELN = '00000269951' and VBAP.PSTYV = 'ZTAC','ZTAN' Etc
    No production order?
        elseif lva_prodord is initial.
          clear v_messg.
          call function 'CONVERSION_EXIT_ALPHA_OUTPUT'
            exporting
              input  = lva_filemat
            importing
              output = lva_filemat.
        No production order found - log a warning message.
          concatenate 'Production Order not be found for'
                      'Command order' lva_cmdord
                      'Material'      lva_filemat
                      'Customer'      lwa_02-customer
            into v_messg separated by space.
          perform write_log_entry
            tables t_zint_mslog
            using  'E' 'ZINT_CSTPORD_ROUTINES'
                       'FIND_SAP_PRODORD'
                         v_messg
                         p_zint_nw
                         lwa_01-ticketnumber.                " RJS
          continue.
        endif.
    Production Order WAS found... Continue creating IDOCS
        lwa_hdrlevel-postg_date = lwa_01-ticketdate.
    Obtain the storage location parameter value.
        read table t_zint_param with key zint_fn = 'LGORT'.
        if sy-subrc ne c_noerr.
          perform write_log_entry
            tables t_zint_mslog
            using  'E' 'ZINT_CSTPORD_ROUTINES'
                       'PROCESS_INBOUND_DATA'
                       'Parameter LGORT is missing from ZINT_PARAM'
                       p_zint_nw
                       lwa_01-ticketnumber.                " RJS
          exit.
        endif.
        loop at l_it_05 into lwa_05
          where ticketnumber = lwa_01-ticketnumber.
          clear lwa_gm_item_create.
          lva_filemat = lwa_05-material.
          if lva_filemat eq lva_prodmat.
            concatenate 'Command ticket-' lwa_05-ticketnumber
              into lwa_hdrlevel-conf_text.
            lwa_hdrlevel-conf_quan_unit = lwa_05-unitofmeasure.
            lwa_hdrlevel-yield          = lwa_05-quantity.
    check whether the confirmed value + current delivery value is equal *
    the production order qty. If the production order value is less
    than the total delivered value, set final conf indicator  and clear
    reservations
            lva_wemng = lva_wemng + lwa_05-quantity.
            if lva_wemng < lva_psmng.
              lwa_hdrlevel-clear_res      = c_false.
              lwa_hdrlevel-fin_conf       = ' '.
            else.
              lwa_hdrlevel-clear_res      = c_true.
              lwa_hdrlevel-fin_conf       = 'X'.
            endif.
            move: 'Z1BP_PP_HDRLEVEL' to t_idoc_data-segnam,
                  lwa_hdrlevel       to t_idoc_data-sdata.
            append t_idoc_data.
            clear lva_formmat.
            lva_formmat                   = lwa_05-material.
            lwa_gm_item_create-material   = lva_formmat.
            lwa_gm_item_create-plant      = lwa_03-plant.
            lwa_gm_item_create-ref_date   = lwa_01-ticketdate.
            lwa_gm_item_create-prod_date  = lwa_01-ticketdate.
            lwa_gm_item_create-move_type  = '101'.
            lwa_gm_item_create-spec_stock = 'E'.
            lwa_gm_item_create-sales_ord  = lva_saleord.
            lwa_gm_item_create-entry_qnt  = lwa_05-quantity.
            lwa_gm_item_create-entry_uom  = lwa_05-unitofmeasure.
            lwa_gm_item_create-orderid    = lva_prodord.
            lwa_gm_item_create-move_mat   = lva_formmat.
            lwa_gm_item_create-move_plant = lwa_03-plant.
            lwa_gm_item_create-mvt_ind    = 'F'.
            clear t_idoc_data.
            move: 'E1BP2017_GM_ITEM_CREATE' to t_idoc_data-segnam,
                  lwa_gm_item_create        to t_idoc_data-sdata.
            append t_idoc_data.
          else.
            clear: lva_loggr,
                   lva_formmat.
            lva_formmat = lwa_05-material.
            select single loggr into lva_loggr from marc
              where matnr = lva_formmat
              and   werks = lwa_03-plant.
            if sy-subrc ne 0.
              clear v_messg.
              No logistics handling group - log a warning message.
              concatenate 'No logistics handling group for material'
                           lva_formmat
                          'in plant'
                           lwa_03-plant
                into v_messg separated by space.
              perform write_log_entry
                tables t_ldata
                using 'W' 'ZINT_CSTPORD_ROUTINES'
                          'PROCESS_INBOUND_DATA'
                          v_messg
                          p_zint_nw
                          lwa_01-ticketnumber.                " RJS
              clear lva_loggr.
            endif.
            if lwa_03-satsur eq 'T'.
              lwa_e1edl21-lprio = 30.
            else.
              lwa_e1edl21-lprio = 20.
            endif.
          else.
            if lwa_03-satsur eq 'T'.
              lwa_e1edl21-lprio = 10.
            else.
              lwa_e1edl21-lprio = '  '.
            endif.
          endif.
          lwa_e1edl21-berot = lwa_04-driver.
          move: 'E1EDL21'   to t_idoc_data-segnam,
                lwa_e1edl21 to t_idoc_data-sdata.
          append t_idoc_data.
          lwa_e1edl55-qualf = '001'.
          lwa_e1edl55-refnr = lva_saleord.
          move: 'E1EDL55'   to t_idoc_data-segnam,
                lwa_e1edl55 to t_idoc_data-sdata.
          append t_idoc_data.
    Loop at materials - create delivery entry for each
          loop at l_it_05 into lwa_05
            where ticketnumber = lwa_01-ticketnumber.
            clear t_idoc_data.
            lwa_e1edl24-matnr = lwa_05-material.
            lwa_e1edl24-werks = lwa_03-plant.
            lwa_e1edl24-vfdat = lwa_01-ticketdate.
            lwa_e1edl24-lfimg = lwa_05-quantity.
            lwa_e1edl24-vrkme = lwa_05-unitofmeasure.
            lwa_e1edl24-lgort = t_zint_param-zint_fv.
            clear lva_loggr.
            lva_formmat = lwa_05-material.
            clear lva_loggr.
            select single loggr into lva_loggr from marc
              where matnr = lva_formmat
              and   werks = lwa_03-plant.
            if sy-subrc ne 0.
            No logistics handling group - log a warning message.
              concatenate 'No logistics handling group for material'
                           lva_formmat
                          'in plant'
                           lwa_03-plant
                into v_messg separated by space.
              perform write_log_entry
                tables t_ldata
                using 'W' 'ZINT_CSTPORD_ROUTINES'
                          'PROCESS_INBOUND_DATA'
                          v_messg
                          p_zint_nw
                          lwa_01-ticketnumber.                " RJS
              lva_loggr = 'BBIN'.
            endif.
            if lva_loggr is initial.
              move: 'E1EDL24'   to t_idoc_data-segnam,
                    lwa_e1edl24 to t_idoc_data-sdata.
              append t_idoc_data.
            endif.
          endloop.
          clear: lva_xabln,
                 lva_vbeln,
                 l_vbfa.
    Matching ticket against a Delivery?
          select single xabln vbeln into (lva_xabln,lva_vbeln) from likp
              where xabln = lwa_01-ticketnumber.
          if sy-subrc = 0.
    If found, does this delivery match the sales order?
            select * from vbfa into l_vbfa
              where vbelv = lva_saleord
              and   vbeln = lva_vbeln.
              exit.
            endselect.
          endif.
    No matching delivery found, or Matching delivery, but for other Sls Ord
          if lva_xabln is initial
          or ( lva_vbeln <> space and l_vbfa is initial ).
            if not lva_saleord is initial.
              perform create_delivery_idocs tables t_zint_mslog
                                            using  s_idcgp
                                                   lwa_01-ticketnumber
                                                   p_zint_nw.
            else.
              concatenate 'Error finding a Sales Order for ticket "'
                          lwa_01-ticketnumber
                          '" reprocess the file AFTER'
                          ' the sales order issues have been fixed'
              into        lva_outtext.
              perform write_log_entry tables t_zint_mslog
                                      using  'E'
                                             'ZINT_CSTPORD_ROUTINES'
                                             'PROCESS_INBOUND_DATA'
                                             lva_outtext
                                             p_zint_nw
                                             lwa_01-ticketnumber. " RJS
            endif.
          else.
            concatenate 'Command Ticket "'
                        lwa_01-ticketnumber
                        '" has already been processed into delivery "'
                        lva_vbeln
            into        lva_outtext.
            perform write_log_entry tables t_zint_mslog
                                    using  'I'
                                           'ZINT_CSTPORD_ROUTINES'
                                           'PROCESS_INBOUND_DATA'
                                           lva_outtext
                                           p_zint_nw
                                           lwa_01-ticketnumber. " RJS
            refresh t_idoc_data.
          endif.
        endif.
        refresh t_idoc_data.
    Write out all messages collected so far
        perform update_data tables t_zint_mslog
                            using p_zint_id p_zint_ty.
      endloop.
    Write out all messages collected so far
      perform update_data tables t_zint_mslog
                          using p_zint_id p_zint_ty.
    endform.                    " process_inbound_data
    Thnaks
    Regards

    Thanks
    Thread closed

  • How to pull the Sale order number(sales document) to Accounting document

    Hi Gurus,
    How to pull the sale order number to the accounting document.
    Is any configuration needed to this.
    When i run the FBL5N Repoprt ,Sale order number (Sales document) is not getting updated to accounting document.It is diplaying as blank field.
    Thanks you.

    Hi Shivaji,
    In order to display the Sales document in the customer line item report, you need to add it as a special field thorugh customizing settings.
    Path - SPRO - FA-GL Accounting - GL Accounts - Line Items - Define special fields for finding and sorting data and in that select the table BSEG-and field VBEL2 (Sales document) and save/
    This will work. hope this helsp
    regards,
    radhika

  • KKAX shows WIP costs after settling the production order

    Dear experts,
    We have production order and we did the following actions in March (end of the year),
    1-     Create the order
    2-     TECO the order
    Then in May we did the following actions:
    1.     Revoke TECO
    2.     Give DLV
    3.     TECO again
    4.     Calculating the variances
    5.     Settle the order
    The problem that in KKAX we can see the WIP costs in the column (WIP (Cumul.))
    So, although the order is settled but the WIP costs not cleared,
    And as I know the settlement will clear the costs, how this happen.
    Thanks in advance

    Hi
    First u see whether u have any incomplete Production order .
    That is in any oder have u not comfirmed quantity if  in this casse please clear than now  try to run the KKAX
    Regards
    Ramanujam

  • Basic question on settlment of production order variance to FI

    Hi Experts,
    I know im asking a dumb question. I really understood the concept of variance generated in production order, to say it in simple words the difference between debits and credits. But when it comes back to FI im confused and lost, when we settle the production order variance, the following entry is posted.
    Production variance a/c                                      100
    COGM var a/c or Mfg ouput var a/c                                    100
    Now my question here is, there is a debit and credit of variance for 100, which is equal to zero, so there is no net impact of variance in my P&L, the variance is not accounted in FI at all. How is the production order variance accounted in FI?
    Could somebody please answer my question or provide me with some clarification. I know either i would have misunderstood the concept or something is wrong or may be i need to look over the entire postings.
    appreciate for your time spent.
    Thanks in advance,
    Best Regards,
    sk

    Hi SK,
    The net impact of settlement of production order on P & L is zero. The reason is actual consumption to that particular production order is  booked to P & L at the moment the activities are confirmed over that order.
    Variance is difference between Std cost of Goods recepit and actual consumption. Suppose actual material consumption is 100 Rs and your std cost of goods with which production order is credited is Rs 90. The diff is Rs 10. Now if you again book this 10 Rs to P & L as negative being excess and giving second effect NOT to P & L, you will not come to know what is actual consumption and the picture will be wrong. There will be mismatch between Actual physical consumption and what is booked to P & L.Hence the debit and credit is given to P & L to nullify the effect of variance.
    Truely speaking, the variance account is to be observed to  verify the actual consumption against standards and to correct BOM and Routing and/or to take necessary action for excess or less consumption.
    Hope the matter is clear.
    Makrand

  • Production Order Variance settling to GL Account

    Hi SAP Gurus,
    when we settle the Production Order Varainces, system posts them to FI - Price Difference Account and also settle to COPA.
    I could not find the settings that will prompt the variances to flow to FI-Price difference account
    Could any one tell me where is the setting for this??
    Points will be awarded suitably
    Best Regards
    Surya

    Hi,
    First of all you would have maintained the Cost Element for the same GL as Cost Element Category 1.
    Now you can go to OBYC - Automatic Account Assignment.
    In PRD Key - General Modification will PRA and this GL will be assigned to PRA key.
    So Whenever price diff will occur, such GL will be reflected.
    The main notable Point:
    Now go to GBB Key. U will find the GL for variance against AUA Key. So whenever variance calculation will be done, such GL will be reflected.
    This is all about the Fetching of GL Account as variance
    Now we are coming to COPA Side
    As we have created Cost Element for the same GL. Now we will assign this cost element in COPA Transfer Structure
    T Code is KEI1. Now you will find the Transfer Structure. Now select the relevant and see the source fields and Value fields asssigned to Cost Element. So COPA will take the effect of Variance from here.
    I hope you understood the flow.
    Hope to be rewarded
    Regards,
    Jigar

  • Production order variance settlement to cost centers/internal order

    Hi,
    I am looking to configure the settlement of production order variances to cost centers/internal order. Is there a way to do this in the settlement profile. Would appreciate your help.
    Thank you,
    Ram

    OKO7 will allow you to configure the Settlement Profile by selecting valid receivers.
    This should be done with/or by FICO.
    Then test, test, test
    award points if helpful
    Althea

  • Production Order Variance not posting to COPA

    Hi,
    I am hoping someone can help.
    We settle our production order variances to COPA. - usually without any problem. The production orders settle to both Material (Mat) and PSG
    However this month we had a situation where for 2 order there was no settlement to COPA for the variance.
    For these 2 production orders there was no settlement rule to PSG in the master data so this obviously explains why it didnt create a settlement document but my dilemma is understanding why there is no PSG settlement rule.
    Through testing it appears that the PSG settlement rule is not created at the time of production order creation at all but seems to be automatically created after the execution of KKS2 and CO88.
    The 2 orders that I had  issue with this month were for a new material and I am able to recreate this probelm for any new Production order against this new material. So I suspect that there is something specific to this material that is prveventing the PSG settlement rule from being created.
    But this is where I am stuck! I can't find any setting in material master or other area that would seem to impact this.
    Any help appreciated,
    Thanks,
    Tracee

    Hi,
    First you can settle these 2 orders individually with using KO88 Transaction code and see if there is any error. Also check the settlement profile of these 2 production orders.there you can check the " variances to costing-based PA" tick is there or not.If tick is not selected there,you can select the check box and run variance calculation (KKS2) and do the settlement for these 2 production orders (KO88).
    I hope this wil help you and let me know if you have any queries.
    Regards,
    Puri.

  • Settlement of Production Order to specific GL Code

    Dear All,
    During the production process we get the output of some materils as powder. If we carry the further production of the same  we are able to get some raw materils
    for example: - if the byproduct  is 2kgs. we will get the raw materials of 1.5kgs. We want to post the difference amount of 0.5 kgs to either production loss / cost of goods sold / melting loss etc gl code.
    kindly suggest the procedure of handling in CO module and we would like to settle the production order to specific gl code
    Regards
    Anilkumar

    You will have to define settlement rule first. The settlement rule configuration should allow posting to GL account. You will also have to define variance calculation. First do the variance calculation and then perform settlement. From this link check variance and settlement topics.
    http://help.sap.com/saphelp_47x200/helpdata/en/90/ba81d2446711d189420000e829fbbd/frameset.htm
    Regards
    Ram

  • Production Order Variance Configuration

    Hi Gurus,
    Would you please help me with configuring the Production order variances in product costing. I would really aapreciate if you can send me some documentation. My scenario is to configure the automatic calculation of production order variance and its settlement to Copa. I would really appreciate an early response. If you have any documentations please send it to kamkhan.sap at gmail.
    Thanks

    Hi MKR,
    You can calculate the following variances in the R/3 system:
    Planning variances
    Production variances
    Production variance of the period
    Total variance
    You control the variance calculation process by specifying a particular target cost version.
    In make-to-stock production, standard cost is calculated in the standard cost estimate for the material. In sales-order-related production with a valuated sales order stock, standard cost is determined using a predefined valuation strategy.
    During production, actual costs are collected on the order (product cost collector or manufacturing order). The actual costs that are compared with the target costs are reduced by the work in process and scrap variances (the result is called the net actual cost).
    You can determine the production variances of the period by comparing an alternative material cost estimate with the (net) actual costs. This alternative material cost estimate can be the modified standard cost estimate or the current cost estimate, for example.
    Total Variance
    The total variance is the only variance that is relevant to settlement. This means that only the variance categories of target cost version 0 can be transferred to Profitability Analysis (CO-PA).
    The total variance is the difference between the actual costs debited to the order and the costs credited to the order due to deliveries to stock. The difference between the debit and credit of the order is passed to Financial Accounting (FI) and Profit Center Accounting (EC-PCA) when the order is settled.
    The target costs for the total variance are calculated as follows:
    In make-to-stock production, the target costs are calculated using the standard cost estimate for the material and the quantity delivered to stock.
    In sales-order-related production with a valuated sales order stock, the target costs are calculated using the cost estimate relevant to the valuation of the sales order stock (such as a sales order cost estimate or a standard cost estimate for the manufacturing order) and the quantity delivered to stock.
    For the total variance, the control costs are equivalent to the following:
    In Product Cost by Order, the control costs are the actual costs less the scrap variances.
    In Product Cost by Period, the control costs are the actual costs less the work in process and scrap variances.
    The variance calculation process compares the itemization of the cost estimate on which the calculation of target costs is based with the line items in your actuals.
    The itemization contains detailed information based on the costing lot size, such as the materials to be used and the activities to be performed.
    When you release a standard cost estimate for a material, the price calculated therein becomes the standard price in the material master record of the material being manufactured. In the standard system, an itemization is always created for standard cost estimates for materials.
    The following variance categories can be reported for the total variance:
    Input price variance
    Resource-usage variance
    Input quantity variance
    Remaining input variance
    Scrap variance
    Mixed-price variance
    Output price variance
    Lot size variance
    Remaining variance
    When you settle, you can transfer the total variance to Profitability Analysis (CO-PA) broken down into variance categories.
    In CO-PA, the standard cost of goods manufactured for the product is compared with the revenues to calculate an initial contribution margin for the period. The variances between actual cost and standard cost of goods manufactured can be used to calculate a second contribution margin for the period.
    When you calculate the variances, you can transfer the difference between the debit and credit to CO-PA only as a total.
    You calculate the total variance with target cost version 0.
    Hope this helps. Please assign points and let me know if you need more information.
    Rgds
    Manish

  • Production order variance and purchase variance go to one business area.

    Hi Experts,
    I have a issue while Purchase order we have ordered 3000 qty and while goods receipt we posted 300000 qty and same was issed for prodction order instead of 3000 and got variance.  Then afterward purchase order qty was rectified with correct qty then purchase variance happed.  The production order variance is getting offsetting by purchase order variance and no effect on gross profit.
    Now my question is production variance is going one business area and purchase variance is going another business area. It should not be like that.  Both should be showed only one business area.  Please provide solution. 
    Thanks in advance.
    Balu

    Dear Balu,
    You can try OKB9 wherein you need to select the indicator 'BAlrn' against the cost elements of Purchase price difference account. Then select the line item and click the folder 'Detail for business area/valuation area' and input your business area. Thereby you can capture this variance in same business area, even if any other business area is entered or derived differently.
    Further, if your production variance account is also a cost element, you can direct the postings to the same business area, we can do the same as explained above. If not, we have to think of another configuration or work around. Pl let me know.
    Trust this helps much!
    Regards,
    Ashok SINGH

  • Get back the Production order Value

    Hi All,
    I am running BDC to create Production order , everything works fine, but i dont know how to
    captute the production order that has been created and is it true that long text can be uploaded only after creating production order ?
    Thanks,
    Siva

    LSMW - direct input method:
    Object 0001 Long text
    Method 0001 (No selection)
    Program Name /SAPDMC/SAP_LSMW_IMPORT_TEXTS
    Program Type D Direct Input
    Eg:
    Structure: Header
    OBJECT -> 'MATERIAL'
    NAME -> 000001346041002000 (material no)
    ID -> 'BEST'
    SPRAS -> 'E'
    Structure: Items
    TEXTFORMAT -> '*'
    TEXTLINE -> Long text

Maybe you are looking for