CO11 quantity "Expected yield variance"

Dear Gurus,
when we confirm the operation of the production order whit the selection "Automatic final confirmation" the system generate the quantity in the field "Expected yield variance" in the production order also the quantity confimed are same the quantity to confirm.
I try set the parameters in the custozing OPK4, but the problem is present yet.
Thanks a lot for your help.
Daniele

Hi ,
I am facing the same issue would u let the me soultion how u have done , is it program error or any note
is there for AFS 6.00
Thanks and Regards
Mohan

Similar Messages

  • Expected yield variance in production order

    Hello,
    The issue is when we confirm the order operation wise, an error Message no. RU139 is coming, however the production order "expected yield variance" field is 4 and the order quantity is 1.
    GR is not taken place, hence delivered qty field is 0.
    The solution i have proposed is to check the "Unlimited Overdelivery " check box in production order screen to allow the excess confirmation.
    please suggest, How the field "Expected yield variance" is filled up in production order? because of this field, the error RU139 is encountered though we have not entered yield in confirmation (ZERO yield is given).
    The confirmed quantity is 5 (here thre is uncertaininty that how the system allowed to enter 5 when the check for over delivery is set as an error)
    please suggest or close the thread
    Regards,
    Santhosh
    Edited by: SANTHOSHCH on Jul 31, 2010 7:10 AM
    Edited by: SANTHOSHCH on Aug 6, 2010 5:38 AM

    dear santhosh,
    Check in opk4 confrmation parameter, In the genereal valid setting tab, over delivery, Change the over delivery not checked to Error when over delivery tolerance is exceeded. If U make this setting, system won't allow the overdelivery while confirmation
    Regards,
    Sundaresan

  • Expected yield variance in  production order creation

    Dear sir
    pl tellme ,where i have to capture the expected yeld variance.
    for thisbelow given reasion i have to capture the expected yeld variance
    Total confirmation quantity not equal to planned confirmatio.
    The confirmed quantity for this operation is not equal to the planned quantity to be confirmed
    The quantity confirmed until now for this operation is greater that the planned quantity to be confirmed.
    pl tell me
    thanks and regrds
    Baswaraj

    Hi raj,
    At the time of order creation system shows Delivery tolerance in goods receipt tab since you maintained at Material Master level But Expected yield variance will be Zero (System doesn't know how much you are going to confirm).
    After Doing Final confirmation with clear reservations indicator and goods movements, System calculates the difference between actual order quantity and confirmed quantity at operation level in percentage. System updates the same in Production order. In your first order you got 0.2-.   That means based upon operation yield confirmation, your expected yield i.e. GR quantity is 0.2% less than the order quantity. At the time of GR, system proposes the quantity you confirmed at operation level, but not the order quantity.
    Where as coming to second order your conformed quantity is same as your order quantity. Hence system is not showing any expected yield variance in production order.
    Check it with different order quantities.
    Regards,
    Venkat.V
    Note: At the time of operation final confirmation in CO11n, if you select Confirmation Type Final confirmation and the Indicator Clear Open reservations, Irrespective of operation quantity UOM system proposes Expected yield variance in CO02 after conformation.
    Edited by: Venkat V on Nov 13, 2008 10:48 AM

  • Operation scrap and expected yield variance

    Hello guys,
    I have a question on the operation scrap and the expected yield variance.
    I have a product which has four operations, and on one of the operations (2nd operation) the operation scrap of 10 % is maintained.
    So, I have created a production order for 100 Pcu2019s.
    For the confirmation, I confirm first operation with the total order qty (100Pcs). After the confirmation the expected yield of variance of 10 Pcu2019s is set on the order.
    I just wanted to understand why the expected yield variance is set with planned operation scrap. According to my understanding, the expected yield variance is only set if a scrap value is mentioned in the confirmation.
    I am having a problem because my 4th operation is a milestone operation ( I confirm 2Nd, 3rd and 4th operation at a time.
    I donu2019t use the back flushing option coz I do my GR in MIGO.
    So here is the situation.
    I created and order for 100 Pcu2019s and I confirm the first operation for 100 Pcu2019s
    Second milestone confirmation (2nd, 3rd, 4th ops) for 40 Pcu2019s u2013 GR is done after that.
    Third milestone confirmation (2nd, 3rd, 4th ops) for 40 Pcu2019s u2013 GR is done after that.
    Fourth milestone confirmation (2nd, 3rd, 4th ops) for 15 Pcu2019s but I can only receive 10 Pcu2019s because of the operation scrap and expected yield variance.
    Thanks,
    sashi vardhan

    Dear Shashi,
    Since you have maintained 10% as operation scrap system considers that 10% of your total qty in the opration is scrap material and hence system allows only confirmation of 90 components only.
    This is std SAP behaviour.
    Regards
    Suri

  • Expected Yield Variance Calc

    Hi
    Does anyone know how the "Expected Yield Variance" is deteremined
    on PP orders. I can't figure out how it gets to the values and the SAP help
    doesn't go into much detail as to how the formula works

    All I want to know is the logic that is used by SAP to determine the values.
    I tried to work it out to understand it but I can't follow there logic. As I understand
    it, it is based on the final confirmation qty vs the planned qty of the next operation
    but that does not seem to coruspond to the smaples I have gone through.
    Example
    Order Qty: 110ea
    Variance: 8
    Op 10 Planned Qty 110 = CNF 109ea
    Op 20 Planned Qty 108 = CNF 108ea
    Op 30 Planned Qty 106 = CNF 108ea
    Op 40 Planned Qty 104 = CNF 108ea
    Op 50 Planned Qty 104 = CNF 108ea

  • Plan material/labour quantity and total variance issue

    in KKBC_ord report, the plan cost of :
    raw material plan cost  is 3000,000 MYR, actual is 29600,000, variance is 400,000 MYR, with raw material A plan qty 9700, actual quantity is 10000, I want to know how the 9700 is calulated, any formula and how it is calulated in table CKIS?
    labour plan cost is 1386,000 MYR, actual is 1356,000, variance is 30,000 MYR, with labour  plan qty 38, actual quantity is 36, I want to know how the 38 is calulated, any formula and how it is calulated in table CKIS?
    we use process order, costing bom and  receipe
    except raw material and labour activity, we have no other cost.
    our raw material variance+labour variance is 430,000
    when we do goods receipt, actual qty is less than plan qty, thus yield variance is 700,000
    but our sap total vriance is 750,000 in settlement, I want to know why 750,000 is not equal to 430,000+700,000=1130,000
    what is relationship between 750,000 and 1130,000, we don't have remaining variance or scrap variance. thanks

    Hi
    1. Plan cost is calculated based on the Prod Order BOM and recipe
    2. Variance is a difference between Actual Dr and Actual Credit... Plan cost has no role to play in variance calculation
    Though Actual Cr is more or less equal to the target cost, the actual variance in the order is always equal to Actual Dr-Cr (COGM)... Whats the difference between Actual Dr and Cr (COGM) in your case?
    Before settlement, if the Order is marked as "Delivery Complete", then the Order balance would be equal to Variance
    there are many other categories of variance like Lot Size Variance, Usage var, etc.. Plug in the all the columns of variances in COR3 and the sum should be equal to the Variance settled.. I have never seen a case of mismatch in this
    Br, Ajay M

  • Process Order Yield Variance Report

    Hai All,
               I am working on a report which displays the Average Values of---- "Standard Yield , Batch Size, Order Activity Yield, Variance Qty, Activity Yield and Variance Value".
    Now the requirement is that, I have to display all these data for only those Process orders for which the Technical Confirmation is given.
    I need to know the field name of the Technical Confirmation and in which Table it is stored.

    hi
    use this function module
    STATUS_TEXT_EDIT

  • Co03 quantity and price variance

    Hi in Co03,
                     give order number enter then goto->cost->analysis in the out put
    i want to know how the quantity variance and price variance are being calculated please let me know

    Hi Revanth
    Please find the Help From SAP
    [SAP HELP|http://help.sap.com/saphelp_dimp50/helpdata/EN/90/ba6228446711d189420000e829fbbd/content.htm]
    [SAP HELP|http://help.sap.com/saphelp_dimp50/helpdata/en/90/ba6b15446711d189420000e829fbbd/content.htm]
    Hope they are Useful
    Thanks
    Kalyan

  • GI,GR and yield

    I would like to know which table stores the qty and amount of goods issue and goods receipt to process order?
    also I fcan't explain SAP expected yield variance , if production quantity is 40, actual goods delivered is 38, then expected yield var is -2. but for non-DLV order(REL order), delivered=0, production quantity=40, why expected yield = 0?

    For this
    You can find the GR  & GI price  value in  MSEG-  DMBTR, No need to take the data from Costing view, because, this is value while posting the material for that quantity
    Check in COOISPI  list confirmation , You can find the confirmed qty in that
    also If can't explain SAP expected yield variance , if production quantity is 40, actual goods delivered is 38, then expected yield var is -2. but for non-DLV order(REL order), delivered=0, production quantity=40, why expected yield = 0?
    You Have confirmed for 40 but Gr is happened for 38 that why the variance is 2-
    for non delivery order you haven't confirmed none that  there is no variance thats why zero
    Instead of COiO, use COOISPI, I feel COIO is a  old version Report
    Edited by: Sundaresan . E. V on Nov 1, 2010 7:42 PM

  • Due to MODIF ID, SELECT query in START-OF-SELECTION not getting triggered

    Dear SAP Gurus,
    I'm stuck with this program, where, my program is not being executed, as in, my SELECT query in my event START-OF-SELECTION is not getting triggered. Since i hav used MODIF ID, for SELECT-OPTIONS, even after putting the entries in select-options...................when i click on the execute button, or press F8, the program still goes into the AT SELECTION-SCREEN OUTPUT event..........but i want it to goto START-OF-SELECTION event where my SELECT query is........what should i do??????????????
    Please find the notepad file having the code, n exucse me for any selection-texts absence.
    Need help from u in this issue.
    Thanks in advance.
    REPORT  ZPPR_CONVSTAT NO STANDARD PAGE HEADING.
    INCLUDE ZPPR_CONVSTAT_TOP.               " data declaration
    INCLUDE ZPPR_CONVSTAT_SEL_CRITERIA.      " selection criteria
    INCLUDE ZPPR_CONVSTAT_PBO.               " event at selection-screen output
    INCLUDE ZPPR_CONVSTAT_START_SELECTION.   " event start-of-selection
    INCLUDE ZPPR_CONVSTAT_F_START_OF_SEL.
    *&  Include           ZPPR_CONVSTAT_TOP
    TABLES  : VBUK,
              VBUP,
              VBAK,
              VBAP,
              VBEP,
              VBPA,
              TVAK,
              EKUB,
              LIKP,
              LIPS,
              MARA,
              MAKT,
              MARC,
              PLAF,
              AUFK,
              AFKO,
              AFPO,
              AFVC,
              AFVV,
              CRHD,
              PBIM,
              KNA1,
              T134,
              IOHEADER,
              IOITEM.
    TYPE-POOLS  : slis.
    TYPES : BEGIN OF ty_final,
            werks   TYPE vbap-werks,  "Plant
            auart   TYPE vbak-auart,  "Sales Order Doc. type
            erdat   TYPE vbak-erdat,  "Sales Order Creation date
            vbeln   TYPE vbak-vbeln,  "Sales Order No.
            posnr   TYPE vbap-posnr,  "Sales Order Item No.
            aedat   TYPE vbak-aedat,  "Sales Order Change Date
            kwmeng  TYPE vbap-kwmeng, "Sales Order qty.
            vdatu   TYPE vbak-vdatu,  "Requested Delivery Date
            lfimg   TYPE lips-lfimg,  "Sales Order Delivered Qty.
            matnr   TYPE vbap-matnr,  "Material ID
            arktx   TYPE vbap-arktx,  "Material Description
            strgr   TYPE marc-strgr,  "Planning Strategy
            vrkme   TYPE vbap-vrkme,  "UOM
            plnum   TYPE plaf-plnum,  "Plan Order No.
            gsmng   TYPE plaf-gsmng,  "Plan Order Qty.
            auffx   TYPE plaf-auffx,  "Plan Order Firming Indicator u2013 Qty.
            stlfx   TYPE plaf-stlfx,  "Plan Order Firming Indicator - Component
            erdat2  TYPE aufk-erdat,  "Production Order Creation Date
            aufnr   TYPE aufk-aufnr,  "Production Order No.
            prdqty  TYPE afko-gamng,  "Production Order qty.
            pckqty  TYPE lips-lfimg,  "Packed Delivered Qty.
            psamg   TYPE afpo-psamg,  "Allotted scrap
            igmng   TYPE afko-igmng,  "Confirmed Yield Qty.
            iasmg   TYPE afko-iasmg,  "Confirmed Scrap Qty
            iamng   TYPE afpo-iamng,  "Expected Yield
            wemng   TYPE afpo-wemng,  "Delivered Qty.
            altscrp TYPE c LENGTH 6,  "Allotted Scrap %
            actscrp TYPE c LENGTH 6,  "Actual Scrap %
            umrez   TYPE afvv-umrez,  "Ups (from Prd. ORD)
            ups     TYPE clobjdat-ausp1,  "Ups (from Material Master)
            crtnstl TYPE clobjdat-ausp1,  "Carton Style
            ppopr   TYPE clobjdat-ausp1,  "Pre-Printing Operation
            brdtyp  TYPE clobjdat-ausp1,  "Board Type
            lsdim1  TYPE clobjdat-ausp1,  "Layout Size u2013 Dim 1
            lsdim2  TYPE clobjdat-ausp1,  "Layout Size u2013 Dim 2
            lsgsm   TYPE clobjdat-ausp1,  "GSM
            inktyp  TYPE clobjdat-ausp1,  "Ink Type
            foiltyp TYPE clobjdat-ausp1,  "Foiling
            wintyp  TYPE clobjdat-ausp1,  "Window Type
            lamin   TYPE clobjdat-ausp1,  "Lamination
            fsvrnsh TYPE clobjdat-ausp1,  "Front Side Varnish
            bsvrnsh TYPE clobjdat-ausp1,  "Back Side Varnish
            emboss  TYPE clobjdat-ausp1,  "Embossing
            punch   TYPE clobjdat-ausp1,  "Punching
            paste   TYPE clobjdat-ausp1,  "Pasting
            oprno   TYPE afvc-vornr,      "Operation No.
            wrkcntr TYPE crhd-arbpl,      "Work Centre
            oprtxt  TYPE afvc-ltxa1,      "Operation Text
            oprqty  TYPE afvv-mgvrg,      "Operation qty.
            yield   TYPE afvv-lmnga,      "Yield
            scrap   TYPE afvv-xmnga,      "Scrap
            jobtyp  TYPE vbak-augru,      "Job Type
            prordst TYPE bsvx-sttxt,      "Production Order Status
            solinst TYPE vbup-lfsta,      "Sales Order Line Item Status
            sldprty TYPE kna1-name1,      "Sold to Party Name
            shpprty TYPE kna1-name1,      "Ship to Party Name
            shpcity TYPE kna1-ort01,      "Ship to party - City
            END OF  ty_final.
    TYPES : BEGIN OF ty_vbak,
            auart   TYPE vbak-auart,
            erdat   TYPE vbak-erdat,  "Doc creation date
            vbeln   TYPE vbak-vbeln,
            aedat   TYPE vbak-aedat,  "Doc change date
            vdatu   TYPE vbak-vdatu,  "Requested delivery date
            kunnr   TYPE vbak-kunnr,
            augru   TYPE vbak-augru,  "Job Type
            END OF ty_vbak.
    TYPES : BEGIN OF ty_vbap,
            vbeln   TYPE vbap-vbeln,
            posnr   TYPE vbap-posnr,
            werks   TYPE vbap-werks,
            matnr   TYPE vbap-matnr,
            arktx   TYPE vbap-arktx,
            kwmeng  TYPE vbap-kwmeng,
            vrkme   TYPE vbap-vrkme,
            END OF ty_vbap.
    TYPES : BEGIN OF ty_pbim,
            pbdnr TYPE pbim-pbdnr,  "Requirements Plan Number
            bdzei TYPE pbim-bdzei,  "Independent requirements pointer
            matnr TYPE pbim-matnr,
            werks TYPE pbim-werks,
            END OF ty_pbim.
    TYPES : BEGIN OF ty_pbhi,
            bdzei TYPE pbhi-bdzei,  "Independent requirements pointer
            pdatu TYPE pbhi-pdatu,  "Requirement date
            laeda TYPE pbhi-laeda,  "Date of Last Change
            END OF ty_pbhi.
    TYPES : BEGIN OF ty_ekko,
            ebeln TYPE ekko-ebeln,  "STO doc no
            bsart TYPE ekko-bsart,
            reswk TYPE ekko-reswk,  "Supplying plant
            aedat TYPE ekko-aedat,  "Doc creation date
            END OF ty_ekko.
    TYPES : BEGIN OF ty_ekpo,
            ebeln TYPE ekpo-ebeln,
            ebelp TYPE ekpo-ebelp,
            aedat TYPE ekpo-aedat,  "Doc change date
            menge TYPE ekpo-menge,
            meins TYPE ekpo-meins,
            matnr TYPE ekpo-matnr,
            txz01 TYPE ekpo-txz01,
            END OF ty_ekpo.
    TYPES : BEGIN OF ty_eket,
            ebeln TYPE eket-ebeln,
            ebelp TYPE eket-ebelp,
            eindt TYPE eket-eindt,  "Requested delivery date
            END OF ty_eket.
    TYPES : BEGIN OF ty_lips,
            vbeln TYPE lips-vbeln,
            posnr TYPE lips-posnr,
            vgbel TYPE lips-vgbel,
            vgpos TYPE lips-vgpos,
            lfimg TYPE lips-lfimg,
            END OF ty_lips.
    TYPES : BEGIN OF ty_plaf,
            plnum TYPE plaf-plnum,
            matnr TYPE plaf-matnr,
            gsmng TYPE plaf-gsmng,
            auffx TYPE plaf-auffx,
            stlfx TYPE plaf-stlfx,
            kdauf TYPE plaf-kdauf,
            kdpos TYPE plaf-kdpos,
            pbdnr TYPE plaf-pbdnr,
            END OF ty_plaf.
    TYPES : BEGIN OF ty_aufk,
            aufnr TYPE aufk-aufnr,
            erdat TYPE aufk-erdat,
            objnr TYPE aufk-objnr,
            END OF ty_aufk.
    TYPES : BEGIN OF ty_afko,
            aufnr TYPE afko-aufnr,
            gamng TYPE afko-gamng,  "Total order quantity
            gasmg TYPE afko-gasmg,  "Total scrap quantity in the order
            igmng TYPE afko-igmng,  "Confirmed Yield Qty
            iasmg TYPE afko-iasmg,  "Confirmed Scrap Qty
            aufpl TYPE afko-aufpl,  "Routing number of operations in the order
            END OF ty_afko.
    TYPES : BEGIN OF ty_afpo,
            aufnr TYPE afpo-aufnr,
            plnum TYPE afpo-plnum,
            matnr TYPE afpo-matnr,
            pgmng TYPE afpo-pgmng,  "Plan Order Qty
            kdauf TYPE afpo-kdauf,
            kdpos TYPE afpo-kdpos,
            psamg TYPE afpo-psamg,  "Allotted scrap
            iamng TYPE afpo-iamng,  "Expected Yield Variance
            wemng TYPE afpo-wemng,  "Delivered Qty
            END OF ty_afpo.
    TYPES : BEGIN OF ty_afvc,
            vornr TYPE afvc-vornr,
            aufpl TYPE afvc-aufpl,  "Routing number of operations in the order
            aplzl TYPE afvc-aplzl,  "General counter for order
            arbid TYPE afvc-arbid,  "Object ID of the resource
            ltxa1 TYPE afvc-ltxa1,
            END OF ty_afvc.
    TYPES : BEGIN OF ty_afvv,
            aufpl TYPE afvv-aufpl,  "Routing number of operations in the order
            aplzl TYPE afvv-aplzl,  "General counter for order
            umrez TYPE afvv-umrez,
            mgvrg TYPE afvv-mgvrg,
            lmnga TYPE afvv-lmnga,
            xmnga TYPE afvv-xmnga,
            END OF ty_afvv.
    TYPES : BEGIN OF ty_mdvm,
            mdkey TYPE mdvm-mdkey,
            disst TYPE mdkp-disst,
            matnr TYPE mdkp-matnr,
            plwrk TYPE mdkp-plwrk,
            END OF ty_mdvm.
    DATA :  it_final  TYPE STANDARD TABLE OF ty_final,
            it_vbak   TYPE STANDARD TABLE OF ty_vbak,
            it_vbap   TYPE STANDARD TABLE OF ty_vbap,
            it_lips   TYPE STANDARD TABLE OF ty_lips,
            it_pbim   TYPE STANDARD TABLE OF ty_pbim,
            it_pbhi   TYPE STANDARD TABLE OF ty_pbhi,
            it_ekko   TYPE STANDARD TABLE OF ty_ekko,
            it_ekpo   TYPE STANDARD TABLE OF ty_ekpo,
            it_eket   TYPE STANDARD TABLE OF ty_eket,
            it_plaf   TYPE STANDARD TABLE OF ty_plaf,
            it_aufk   TYPE STANDARD TABLE OF ty_aufk,
            it_afko   TYPE STANDARD TABLE OF ty_afko,
            it_afpo   TYPE STANDARD TABLE OF ty_afpo,
            it_afvc   TYPE STANDARD TABLE OF ty_afvc,
            it_afvv   TYPE STANDARD TABLE OF ty_afvv,
            it_mdvm   TYPE STANDARD TABLE OF ty_mdvm.
    DATA :  wa_final  TYPE ty_final,
            wa_vbak   TYPE ty_vbak,
            wa_vbap   TYPE ty_vbap,
            wa_lips   TYPE ty_lips,
            wa_pbim   TYPE ty_pbim,
            wa_pbhi   TYPE ty_pbhi,
            wa_ekko   TYPE ty_ekko,
            wa_ekpo   TYPE ty_ekpo,
            wa_eket   TYPE ty_eket,
            wa_plaf   TYPE ty_plaf,
            wa_aufk   TYPE ty_aufk,
            wa_afko   TYPE ty_afko,
            wa_afpo   TYPE ty_afpo,
            wa_afvc   TYPE ty_afvc,
            wa_afvv   TYPE ty_afvv,
            wa_mdvm   TYPE ty_mdvm.
    DATA :  it_object TYPE hum_object_t,
            wa_object TYPE hum_object,
            it_item   TYPE hum_hu_item_t,
            wa_item   TYPE vepovb,
            count1(6) TYPE n.
    DATA :  gv_objek TYPE ausp-objek.       "Put matnr for use in FM u2018CLAF_CLASSIFICATION_OF_OBJECTSu2019
    DATA : BEGIN OF it_sclass OCCURS 0.
            INCLUDE STRUCTURE sclass.
    DATA : END OF it_sclass.
    DATA : BEGIN OF it_clobjdat OCCURS 0.
            INCLUDE STRUCTURE clobjdat.
    DATA : END OF it_clobjdat.
    *&  Include           ZPPR_CONVSTAT_SEL_CRITERIA
      SELECTION-SCREEN FOR 'PLANNING STAGE'
    SELECTION-SCREEN BEGIN OF BLOCK main WITH FRAME TITLE text-001.
      PARAMETERS: mrpntdn RADIOBUTTON GROUP sel                    DEFAULT 'X' user-command flag,
                  pldord  RADIOBUTTON GROUP sel,
                  prdord  RADIOBUTTON GROUP sel.
    SELECTION-SCREEN END OF BLOCK main.
      SELECTION-SCREEN FOR 'SELECTION BY PLANT AND PLANT DATA'
    SELECTION-SCREEN BEGIN OF BLOCK plant WITH FRAME TITLE text-002.
      PARAMETERS      : p_werks   LIKE  ioheader-werks OBLIGATORY  DEFAULT '1100' MATCHCODE OBJECT H_T001W.
      SELECT-OPTIONS  : so_matnr  FOR   ioitem-matnr                              MATCHCODE OBJECT MAT1.
      PARAMETERS      : so_mtart  TYPE  t134-mtart     OBLIGATORY  DEFAULT 'ZFIN' MATCHCODE OBJECT H_T134.
      SELECT-OPTIONS  : so_plnum  FOR   ioitem-plnum                              MATCHCODE OBJECT plnum  MODIF ID pld,
                        so_aufnr  FOR   ioheader-aufnr                            MATCHCODE OBJECT orde   MODIF ID prd.
      PARAMETERS      : p_prdsta  LIKE  tj02t-txt04                                                       MODIF ID prd.
    SELECTION-SCREEN END OF BLOCK plant.
      SELECTION-SCREEN FOR 'SELECTION BY REQUIREMENT TYPE'
    SELECTION-SCREEN BEGIN OF BLOCK reqtyp  WITH FRAME TITLE text-003.
      PARAMETERS      : cb_so     TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag,
                        cb_sto    TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag,
                        cb_pir    TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag.
    SELECTION-SCREEN END OF BLOCK reqtyp.
      SELECTION-SCREEN FOR 'SELECTION BY DATE AND REQUIREMENT TYPE NOS'
    SELECTION-SCREEN BEGIN OF BLOCK dtreqtypno WITH FRAME TITLE text-004.
      SELECT-OPTIONS  : so_crtdt  FOR vbak-erdat                                                                MODIF ID gen,
                        so_vbeln  FOR vbap-vbeln                                  MATCHCODE OBJECT WTY_F4_VBAP  MODIF ID rso,
                        so_posnr  FOR vbap-posnr                                                                MODIF ID rso,
                        so_ebeln  FOR ekub-ebeln                                  MATCHCODE OBJECT MEKKM        MODIF ID rst,
                        so_ebelp  FOR ekub-ebelp                                                                MODIF ID rst,
                        so_pbdnr  FOR pbim-pbdnr                                                                MODIF ID rpi,
                        so_reqdt  FOR vbep-edatu                                                                MODIF ID gen.
    SELECTION-SCREEN END OF BLOCK dtreqtypno.
      SELECTION-SCREEN FOR 'SELECTION BY OTHER PARAMETERS'
    SELECTION-SCREEN BEGIN OF BLOCK othrparam WITH FRAME TITLE text-005.
      SELECT-OPTIONS  : so_kunnr FOR kna1-kunnr                                   MATCHCODE OBJECT debi   MODIF ID rso,
                        so_auart FOR tvak-auart                                   MATCHCODE OBJECT H_TVAK MODIF ID rso,
                        so_lfsta FOR vbup-lfsta                                                           MODIF ID rso.
    SELECTION-SCREEN END OF BLOCK othrparam.
    *&  Include           ZPPR_CONVSTAT_PBO
    *&   Event AT SELECTION-SCREEN OUTPUT
    AT SELECTION-SCREEN OUTPUT.
      IF mrpntdn = 'X'.
        LOOP AT SCREEN.
          IF ( screen-group1 = 'PLD' OR screen-group1 = 'PRD' ).
            screen-active = 0.
            MODIFY SCREEN.
          ENDIF.
        ENDLOOP.
      ELSEIF pldord = 'X'.
        LOOP AT SCREEN.
          IF screen-group1 = 'PLD'.
            screen-intensified = 1.
            MODIFY SCREEN.
          ENDIF.
          IF screen-group1 = 'PRD'.
            screen-active = 0.
            MODIFY SCREEN.
          ENDIF.
        ENDLOOP.
      ELSEIF prdord = 'X'.
        LOOP AT SCREEN.
          IF ( screen-group1 = 'PLD' OR screen-group1 = 'PRD' ).
            screen-intensified = 1.
            MODIFY SCREEN.
          ENDIF.
        ENDLOOP.
      ENDIF.
      IF ( cb_so = ' ' AND cb_sto = ' ' AND cb_pir = ' ' ).
        LOOP AT SCREEN.
          IF ( screen-group1 = 'GEN'
          OR screen-group1 = 'RSO'
          OR screen-group1 = 'RST'
          OR screen-group1 = 'RPI' ).
            screen-active = 0.
            MODIFY SCREEN.
          ENDIF.
        ENDLOOP.
      ENDIF.
      IF cb_so = 'X'.
        LOOP AT SCREEN.
          IF screen-group1 = 'RSO'.
            screen-active = 1.
            MODIFY SCREEN.
          ENDIF.
        ENDLOOP.
        IF cb_sto = ' '.
          LOOP AT SCREEN.
            IF screen-group1 = 'RST'.
              screen-active = 0.
              MODIFY SCREEN.
            ENDIF.
          ENDLOOP.
        ENDIF.
        IF cb_pir = ' '.
          LOOP AT SCREEN.
            IF screen-group1 = 'RPI'.
              screen-active = 0.
              MODIFY SCREEN.
            ENDIF.
          ENDLOOP.
        ENDIF.
      ELSEIF cb_sto = 'X'.
        IF cb_so = ' '.
          LOOP AT SCREEN.
            IF screen-group1 = 'RSO'.
              screen-active = 0.
              MODIFY SCREEN.
            ENDIF.
          ENDLOOP.
        ENDIF.
        IF cb_pir = ' '.
          LOOP AT SCREEN.
            IF screen-group1 = 'RPI'.
              screen-active = 0.
              MODIFY SCREEN.
            ENDIF.
          ENDLOOP.
        ENDIF.
      ELSEIF cb_pir = 'X'.
        IF cb_so = ' '.
          LOOP AT SCREEN.
            IF screen-group1 = 'RSO'.
              screen-active = 0.
              MODIFY SCREEN.
            ENDIF.
          ENDLOOP.
        ENDIF.
        IF cb_sto = ' '.
          LOOP AT SCREEN.
            IF screen-group1 = 'RST'.
              screen-active = 0.
              MODIFY SCREEN.
            ENDIF.
          ENDLOOP.
        ENDIF.
      ENDIF.
    *&  Include           ZPPR_CONVSTAT_START_SELECTION
    *&   Event START-OF-SELECTION
    IF mrpntdn = 'X'.
      PERFORM start_of_selection_mrpntdn.
    ELSEIF pldord = 'X'.
      PERFORM start_of_selection_pldord.
    ELSEIF prdord = 'X'.
      PERFORM start_of_selection_prdord.
    ENDIF.
    *&  Include           ZPPR_CONVSTAT_F_START_OF_SEL
    *&      Form  START_OF_SELECTION
          Subroutine for MRP NOT DONE
    FORM start_of_selection_mrpntdn.
        SELECT mdkey INTO TABLE it_mdvm FROM mdvm
                     WHERE GSAEN = 'X'
                       AND AKKEN = 'X'.
          IF sy-subrc = 0.
            LOOP AT it_mdvm INTO wa_mdvm.
              wa_mdvm-disst = wa_mdvm-mdkey(3).
              wa_mdvm-matnr = wa_mdvm-mdkey+3(18).
              wa_mdvm-plwrk = wa_mdvm-mdkey+21(4).
              MODIFY it_mdvm FROM wa_mdvm INDEX sy-index TRANSPORTING disst matnr plwrk.
            ENDLOOP.
          ENDIF.
    ENDFORM.
    *&      Form  START_OF_SELECTION
          Subroutine for PLAN ORDER CREATED
    FORM start_of_selection_pldord.
    ENDFORM.
    *&      Form  START_OF_SELECTION for PRODUCTION ORDER CREATED
          Subroutine for PRODUCTION ORDER CREATED
    FORM start_of_selection_prdord.
    ENDFORM.

    You need to mention START-OF-SELECTION explicitly in your code.
    Change your code as below:
    *& Event START-OF-SELECTION
    START-OF-SELECTION.
    IF mrpntdn = 'X'.

  • What is material Yeilding report

    hi ,
        what is material yeilding report , is there any standard program for determing the same . If any one has the sample code for the same it will be of great use for me .
    thanks in advance ...

    Hello
    I am not sure if you saied "ExpectYieldVar" in production order/process order, you can Press F4 this field for SAP help, saied"Expected yield variance
    Specifies whether a yield variance is to be expected when the finished product is delivered to stock, as the result of confirmations that have already been entered.
    A yield deficit occurs during final confirmation of operations, as soon as a yield quantity is confirmed that is smaller than the planned order quantity. The confirmed scrap is not taken into account.
    A yield increment occurs during partial confirmation or final confirmation of operations, as soon as a yield quantity is confirmed that is greater than the planned order quantity. The confirmed scrap is not taken into account."
    also you can use COOIS report for order Yield in header level .
    Benny

  • WHAT IS MATERIAL YEILDING?

    Hi ,
        what is material yeilding ? , is there any standard report for the same , kinldy let me know about the same.
    thanks in advance ,
    regards,
    vikram

    Hello
    I am not sure if you saied "ExpectYieldVar" in production order/process order, you can Press F4 this field for SAP help, saied"Expected yield variance
    Specifies whether a yield variance is to be expected when the finished product is delivered to stock, as the result of confirmations that have already been entered.
    A yield deficit occurs during final confirmation of operations, as soon as a yield quantity is confirmed that is smaller than the planned order quantity. The confirmed scrap is not taken into account.
    A yield increment occurs during partial confirmation or final confirmation of operations, as soon as a yield quantity is confirmed that is greater than the planned order quantity. The confirmed scrap is not taken into account."
    also you can use COOIS report for order Yield in header level .
    Benny

  • Process Order fields

    Hello
    I'm basically new to PP-PI and could anyone explain me the process flow.
    1.when we create process order what the fields  Total quantity, Delivered and Expected Yield Variance means.
    2. should we do confirmation of process order to get in to process(production) or when we save process order means that it can go in process(production).then why do we need to confirm or is it like a goods receip in MM for Purch Order?
    3. where do the data stores(table and field) for the output for the process order.
    4. If we want to check that how much quantity was scheduled to produce and how is actually produced and whats the variance......where do we look this data.
    Can you please explain me ASAP as it very urgent and important to me.
    Thank you in Advance
    Mittu

    Hi Mittu,
    The Process flow for PP-PI is the Order is created from MRP/Planned orders or Manually. The order is scheduled, planned cost is determined and capacity is calculated during creation or during release or during saving the order based on the setting we maintain in Production scheduling profile.
    Then based on the reservations materials are issued for the order. After the operation/phases are completed we confirm the production order. Confirming production order is nothing but we tell the system that the production is completed. and we give information about how much man power or machine hours spent. Material usage will be calculated from the Goods issue to the order. By using these informations the system calculate the cost of the order.While Confirming the order the Yield quanity is given. If quality inspection is very much extensive then PI Sheet is maintained.The cost is calculated from the confirmations. After that the WIP- work In progress, Variance are calculated. And finally the order is settled,Technically completed and closed.
    Once the GR for order is done the Quantity Delivered field isautomatically get updated. And if the quantity delivered is different from order quantity i.e scheduled quantity then the expected Yield variance is calculated. If the yield is more then the value of yield variance is "+" and if the yield is less then the quantity is "-".
    Your doubt is what are the fields
    1.Total quantiy -  this is the order quantity you enter during order creation i.e
      scheduled quantity.
    2.Delivered - This is the quanitity gets automaically updated from the Goods 
       Receipt for Order transaction
    3.Expected Yield Variance- This is the yield variance calculated after the 
      confirmation of order.
    4."AFRUD" is the table used for storing output informations.
    5. To see the scheduled quanity ,produced quanity and yield variance go to transaction "CORT"  Display Process order confirmation and input the  Process order number and press enter.
    Hope the above clarifies your queries. Kindly revert back for any more clarifiations.
    thanks and regards
    Murugesan Thangathurai

  • Wip on Process order

    Hi Guys,
    i have a process order in status: REL  PRT  CNF  DLV  PRC  BASC BCRQ GMPS
    now i have run tcode kkaxthe amount is in wip (period) column and not in WIP.
    Cost Object     Typ     Material     Crcy      WIP              WIP (Period)
    ORD xxxxx          xxxx     USD      0,00     -1000
    can you please suggest what can be the cause?
    the order status should allow us to perform the t code.
    thx
    C.

    >
    cmarrone wrote:
    > Hi,
    >
    > this is the situation in the order:
    >
    > Total Qty     1.682              KG         ExpectYieldVar  71,400-
    > Delivered     1.610,600
    >
    > the order has been made in July.
    >
    > did you mean that due to the fact that has been produced more than the expected the wip is negative?
    >
    > thanks
    > C.
    I was wondering, How come the status DLV.
    If the total quantity is  equal to delivered then only the status is set to DLV
    Expected yield variance only comes  because,
    You are confirmed the operation 1682
    BUt you have done the GR only for 1610,600
    That the reason the expected yield variance is 71,400
    Check in COGI, any unprocessed goods movement is there are not
    If the actual prdn is 1682, then post the GR for 71,400
    Also
    check the Value of The Posting For 261
    and for 101  movement
    Check the value of 101 movement -  value of 261 movement, it will come in minus
    Edited by: Sundaresan . E. V on Nov 4, 2010 8:04 PM

  • Under delivery & Over delivery maintenance in production order

    Hi,
    Could you please suggest is it possible to maintain under delivery & over delivery tolerance in Quantity basis instead of percentage basis.
    Thanks,
    Ramu

    Hi,
    Only for positive values, it is possible to change expected yield variance by maintaining scrap portion in production order header. Not the same field but it could als suit your requirement. Actually as far as I know it is not possible to maintain the yield variance in percentage, however it is calculated by the system according to the quantity you enter in scrap portion.
    Regards.

Maybe you are looking for

  • N73 ME SERIOUS ISSUE - PLEASE HELP!!!

    Hi, I have an N73 Music Edition - purchased it in Jan, 2008. It was working fine until recently I removed the memory card to clean it. Ever since my gallery doesn't show any items from the memory card. I've set my phone to save all new and downloaded

  • Master Detail in an Accordian - Spry

    I am trying to use multiple datasets (1 to populate each accordian tab) and those data to be used to populate 1 detail region. The accordian tabs work, but the detail region does not seem to pull the data and populate correctly. Below is the code, an

  • Creating Enhancement Implementation for the  Enhancement spot in ECC 6.0

    Hi All, I have an urgent requirement of creating an Enhancement implementation for the existing Enhancement Spot in ECC 6.0 .. I never worked on enhancement in ECC 6.0. There is an existing enhancement spot called "ES_SAPLIQS0" in the package " IWOC"

  • Problems with burning a copy of a dvd pro show gold

    I made a slide show dvd and I can't figure out how to make a copy so that my dvd player will work.. I get it burned but my dvd player says it cannot play it. ???

  • Integration of Spring, JSF as a view through portlets...

    I am trying to integrate Spring and JSF as a View. Furthermore I am trying to run this combination within a Portlet environment. I have got as far as been able to display the components by the url on the form post is not the portlet action URL as it