SAP B1 9.1 PL 05 Production Order Summary Screen

Hi All,
Has anyone noticed a change in the SAP B1 Production Order ? The Variance Per Product and Variance % no longer appear.
Have these fields been moved to a different location?
This may affect upgrades for clients who use production orders from older versions 8.8, 9.0.
Is there any explanation given in any of the documents?
Kind Regards,
Robinson.

Hi Nagrajan,
I already did and I was  quite surprised. That is not the reality in version 9.1 PL05.
This description is true for SAP B1 8.82 and 9.0. The fields in 9.1 are different.
See screenshot and compare.
Kind Regards,
Robinson

Similar Messages

  • Sort String Field Mandatory in Production Order Components Screen

    Hi Gurus,
    Am currently working on ECC 6.0 environment.
    When I try to assign a batch to the components of the production order, the 'Sort String' is a mandatory field.
    Can you please suggest from where is this mandatory field is picked? Is it possible to populate the field automatically? Or how to make the 'Sort String' field not mandatory?
    In order type parameters (OPL8), standard parameters for display profiles are maintained.
    Have also tried to maintain user parameters like F1F, S3F and S5F without success.
    Your guidance please.
    Thanks in advance.
    The above mentioned problem does not occur if I try to create production order without reference of planned order using T Code CO01. This problem occurs only when I am converting planned order to production order.
    Note that have tried maintaining sort string in the BoM. The sort string gets picked up when am creating manual production orders. Not copied when converting planned orders to production orders.
    Tarang
    Edited by: Tarang Machhar on Sep 28, 2010 7:23 PM
    Edited by: Tarang Machhar on Sep 28, 2010 7:28 PM

    Hi Tarang,
    I think there is a transaction/screen variant maintained for that. Ask your ABAP team member to debug and check if there is any coding done to make it mandatory. There is no customizing for this one. There must be some code written to make it mandatory.
    But you are correct, if you maintain the sort string in BOM, it gets copied on to the planned order, the reservation and the production order as well.
    Regards,
    Pradeep.

  • Where store Production order Summary Tab values like Actual Compnent cost,

    Hi Experts
    Can you tell me that where it store Actual component cost and Actual product cost value which are in summary tab of production order. I checked It is not stored in OWOR table. than where it store these values.
    Thanks
    Regards
    Gorge

    It is in the OINM table.
    Thanks,
    Gordon

  • Batch Determination in Production Order Component Overview Screen on the basis of FIFO, Thickness, Grade, width etc.

    I am facing a difficult scenario. Pl. help me out. In my Business Process I am assigning Batches in Production Order Component Overview Screen. Here I am assigning relevant batches to BOM Components manually, My Management want SAP to suggest batches automatically on FIFO basis, thickness, grade, width & first batches should automatically assign to Production order.  Can you pl. tell me how to configure this scenario.
    Or can I pull stock overview screen at Production Order Component screen to assign relevant batch to BOM Components
    Once batches assigned in Production Order component screen cannot be changed. It can be changes by specific persons only.

    Hi,
    Automatic Batch Determination for production order components is possible by configuration.
    You can also refer below discussions to map your scenario.
    Batch determination in production order | SCN
    Automatic Batch Determination in Production order
    Regards,
    Naresh

  • Automatic Batch determination at time of Goods receipt for production order

    Hi SAP experts,
                             Greetings to you all. I wish to ask a query that how batch is determined automatically at the time of goods receipt for production order .
                             I have done the following settings:
    1.Specified batch level at material level
    2.External batch number assignment
    3.Defined production order condition table '501' (plant/material)
    4.Defined production order access sequence (order type-plant -material)
    5.Defined Production Order Strategy type.
    6.Defined Batch search procedure in Production Order.
    7.Assigned Batch search procedure to Production order type for a particular plant  , batch check not activated.
    Please let me know of any more settings to be checked for the same.
    For example, a production order is being confirmed for a quatity of 5 nos . at a time . However, the GI movement (261 movement type) for the production order components  is taking place for 1 EA qty. from 5 different batches.
    So now, how the system will define the GR (movement type 101) for the production order header material for the qty. 5 nos. EA ?
    It is desired that the system should do GR for the qty.  1 EA of the header material for the 5 different batches (batches which were automatically deteremined for the Goods issue of the components).
    Thanks in advance. good day.
    Best regards,
    RB

    HI Rahul,
    As explained earlier, for e.g., if the GR is taking place for the production order for qty. 5 nos. , and in that , if the component qty. is 1 EA for 1EA of header material ; then , the GR for the header material should take place for the same different batches from which the order components were issued for the order and not for the other batches in stock for the header material as well as components.
    I am not sure if i understand your requirement 100%.
    But let me explain you standard behaviour.
    When Confirmation for production order happens and GR is posted during confirmation , All the GR happens agaist same batch number which i sassigned in production order assignment screen.
    So for all the order qty single batch would be fixed. Say batch A1 is created for Header material for 100 qty.
    Now during components issue to production order, If 100 qty needs to be issued for compoenent B it is possible to use multiple batches of componenets ( using splilt batch functionality /or manual batch number entry agaist componenet in goods movement screen) but header batch remains the same.
    Check and Revert,
    Santosh Sarda

  • How to select the correct routing for production order?

    In table PLPO i have 4 different group numbers for a particular routing. I'm wondering how a production order, created in CO01, selects which one to use. Our base quantity is dz/hr. When I create an order for a particular material, it shows up as 290 as the base quantity. The group 1 is 400dz/hr, not 200. Why does the order choose this group number and not the group number 1.
       Here is a screen from PLPO table.
       Here is a screen showing the material master.
       This is an image of the order details within the created order.

    PLPO contains operations
    The planselection would be based on PLKO entries.
    Please check online help to first get a better understanding on how routings are selected.
    Routing Selection - Production Orders (PP-SFC) - SAP Library   
    Automatically Selecting a Routing - Production Orders (PP-SFC) - SAP Library
    Definition of Base Quantity for Operation:
    "Quantity of the material to be produced to which the standard values of the
    operation refer"

  • Negative quantity in deliver field in production order - CO02

    Hi All,
    I am doing production confirmation and goods receipt for production order through back ground using standard BAPI.While doing GR for production order in background the following error occured.
      System is throughing dump - Arithmatical logical conversion problem.when we analysed through ST22 we came to know that negative quantity appearing in field of delivered in production order.
      Screen name.............. "SAPLCOKO1"
      Screen number............ 0120
      Screen field............. "CAUFVD-GWEMG"
    As per standard, delivered field in production order is always in display mode only. So there will not be any chance for user to change the delivered field.
    Pls guide me how to overcome the above issue and what is exact root cause for the above problem.
    System is throwing error in change mode ( Co02) and display mode ( CO03 ) for the respective production order number
    Thanks
    P.Srinivasan

    Hi,
    This inconsistency can be solved with the following correction report. If you want to try by yourself, then implement it manually in transaction SE38 and execute in test mode first to check if the inconsistency is found. And obviously, in a TEST system first.
    If you are NOT confident about it, I recommend you to submit a support message for SAP for further investigation since this is a database inconsistency.
    Regards,
    Marcelo
    <pre>
    *& Report  ZPCON_076B                                                  *
    *& This report checks goods receipt quantity (WEMNG) and value (WEWRT) *
    *& of an order item for consistency with the corresponding material    *
    *& documents. In UPDATE mode, the quantity and the value calculated    *
    *& from the material documents will be written to database table AFPO. *
    REPORT  zpcon_076b LINE-SIZE 90.
    INCLUDE lcokotyp.
    TABLES: afpo.
    SELECTION-SCREEN COMMENT /1(80) text1.                      "#EC NEEDED
    SELECTION-SCREEN COMMENT /1(80) text2.                      "#EC NEEDED
    SELECTION-SCREEN COMMENT /1(80) text3.                      "#EC NEEDED
    SELECTION-SCREEN COMMENT /1(80) text4.                      "#EC NEEDED
    SELECTION-SCREEN COMMENT /1(80) text5.                      "#EC NEEDED
    SELECTION-SCREEN ULINE.
    SELECTION-SCREEN COMMENT /1(80) texta.                      "#EC NEEDED
    SELECT-OPTIONS r_aufnr FOR afpo-aufnr.
    SELECTION-SCREEN ULINE.
    SELECTION-SCREEN BEGIN OF BLOCK block WITH FRAME TITLE title."#EC NEEDED
    SELECTION-SCREEN COMMENT /1(72) texty.                      "#EC NEEDED
    SELECTION-SCREEN BEGIN OF BLOCK block2 WITH FRAME.
    PARAMETERS: testmode RADIOBUTTON GROUP mode DEFAULT 'X'.
    PARAMETERS: update RADIOBUTTON GROUP mode.
    SELECTION-SCREEN END OF BLOCK block2.
    SELECTION-SCREEN COMMENT /1(72) textz.                      "#EC NEEDED
    SELECTION-SCREEN END OF BLOCK block.
    DATA: BEGIN OF ls_afpo.
            INCLUDE STRUCTURE afpo.
    DATA: END OF ls_afpo.
    DATA  lt_afpo LIKE ls_afpo OCCURS 0.
    DATA: BEGIN OF ls_mseg.
            INCLUDE STRUCTURE mseg.
    DATA: END OF ls_mseg.
    DATA  ls_mseg2 LIKE ls_mseg.
    DATA  lt_mseg LIKE ls_mseg OCCURS 0.
    DATA  ls_mkpf TYPE mkpf.
    DATA l_initial_ltrmi TYPE co_ltrmi VALUE IS INITIAL.
    DATA l_orders TYPE sytabix.
    DATA l_entries TYPE sytabix.
    DATA l_sum_wemng TYPE wemng.
    DATA l_sum_wewrt TYPE wewrt.
    DATA l_error TYPE xfeld.
    INITIALIZATION.
      text1 = 'This report checks goods receipt quantity (WEMNG) and'.
      text2 = 'value (WEWRT) of an order item for consistency with the '.
      text3 = 'corresponding material documents. In UPDATE mode, the'.
      text4 = 'quantity and the value calculated from the material'.
      text5 = 'documents will be written to database table AFPO.'.
      texta = 'Please specify order numbers of orders to be processed.'.
      texty = 'If TESTMODE is set, no database update will occur.'.
      textz = 'Set radio button UPDATE for updating the database entries.'.
      title = 'Mode'.
    AT SELECTION-SCREEN.
    orders specified?
      IF r_aufnr IS INITIAL.
        MESSAGE e889(co) WITH 'Please specify order numbers'.
      ENDIF.
    START-OF-SELECTION.
    select order items
      SELECT *
             FROM  afpo
             INTO  TABLE lt_afpo
             WHERE aufnr IN r_aufnr
             AND ( dauty = auftragstyp-fert
                OR dauty = auftragstyp-netw
                OR dauty = auftragstyp-inst
                OR dauty = auftragstyp-rma
                OR dauty = auftragstyp-bord ).
      DESCRIBE TABLE lt_afpo LINES l_orders.
    check order items
      LOOP AT lt_afpo INTO ls_afpo.
        REFRESH lt_mseg.
        CLEAR l_sum_wemng.
        CLEAR l_sum_wewrt.
        CLEAR l_error.
        SELECT *
               FROM  mseg
               INTO  TABLE lt_mseg
               WHERE matnr = ls_afpo-matnr
                 AND werks = ls_afpo-pwerk
                 AND aufnr = ls_afpo-aufnr
                 AND aufps = ls_afpo-posnr
                 AND kzbew = 'F'
               %_HINTS ORACLE 'rule'.
        IF NOT sy-subrc IS INITIAL.
        no goods movements --> nothing to do.
          DELETE lt_afpo.
          CONTINUE.
        ENDIF.
        LOOP AT lt_mseg INTO ls_mseg.
          IF ls_mseg-shkzg ='S'.
          inward movement
            IF NOT ls_mseg-dmbtr IS INITIAL.
              l_sum_wewrt = l_sum_wewrt + ls_mseg-dmbtr.
            ENDIF.
            IF NOT ls_mseg-bstmg IS INITIAL.
              l_sum_wemng = l_sum_wemng + ls_mseg-bstmg.
            ELSE.
              IF ls_mseg-erfme = ls_afpo-amein.
                l_sum_wemng = l_sum_wemng + ls_mseg-erfmg.
              ELSE.
                IF ls_mseg-meins = ls_afpo-amein.
                  l_sum_wemng = l_sum_wemng + ls_mseg-menge.
                ELSE.
                  WRITE: 'ERROR - Order', ls_afpo-aufnr COLOR 6.
                  DELETE lt_afpo.
                  l_error = 'X'.
                  EXIT.
                ENDIF.
              ENDIF.
            ENDIF.
            ls_mseg2 = ls_mseg.
          ELSE.
          outward movement
            IF NOT ls_mseg-dmbtr IS INITIAL.
              IF ls_mseg-dmbtr NE ls_mseg-bualt AND
                 NOT ls_mseg-bualt IS INITIAL.
                l_sum_wewrt = l_sum_wewrt - ls_mseg-bualt.
              ELSE.
                l_sum_wewrt = l_sum_wewrt - ls_mseg-dmbtr.
              ENDIF.
            ENDIF.
            IF NOT ls_mseg-bstmg IS INITIAL.
              l_sum_wemng = l_sum_wemng - ls_mseg-bstmg.
            ELSE.
              IF ls_mseg-erfme = ls_afpo-amein.
                l_sum_wemng = l_sum_wemng - ls_mseg-erfmg.
              ELSE.
                IF ls_mseg-meins = ls_afpo-amein.
                  l_sum_wemng = l_sum_wemng - ls_mseg-menge.
                ELSE.
                  WRITE: 'ERROR - Order', ls_afpo-aufnr COLOR 6.
                  DELETE lt_afpo.
                  l_error = 'X'.
                  EXIT.
                ENDIF.
              ENDIF.
            ENDIF.
          ENDIF.
        ENDLOOP. "AT lt_mseg
      only continue if no error in the calculation occurred
        CHECK l_error IS INITIAL.
        IF ls_afpo-wemng = l_sum_wemng AND
           ls_afpo-wewrt = l_sum_wewrt.
        values are correct, no update necessary
          DELETE lt_afpo.
          CONTINUE.
        ENDIF.
        FORMAT: COLOR 1.
        WRITE: / 'Order', ls_afpo-aufnr, 'material', ls_afpo-matnr.
        FORMAT: COLOR OFF.
        WRITE: /3 'Order item data   : quantity',
                  ls_afpo-wemng UNIT ls_afpo-amein, ls_afpo-amein, 'value',
                  ls_afpo-wewrt CURRENCY ls_mseg-waers, ls_mseg-waers.
        WRITE: /3 'Material documents: quantity',
                  l_sum_wemng UNIT ls_afpo-amein, ls_afpo-amein, 'value',
                  l_sum_wewrt CURRENCY ls_mseg-waers, ls_mseg-waers.
        FORMAT: COLOR 2.
        WRITE: /3 'Material doc.  BWART', 30 'stock qty  UoM',
               52 'entry qty  UoM', 77 'value  Curr'.
        FORMAT: COLOR OFF.
        LOOP AT lt_mseg INTO ls_mseg.
          WRITE: /3 ls_mseg-mblnr, ls_mseg-zeile, ls_mseg-bwart,
                   ls_mseg-menge UNIT ls_mseg-meins, ls_mseg-meins,
                   ls_mseg-bstmg UNIT ls_mseg-bstme, ls_mseg-bstme,
                   ls_mseg-dmbtr CURRENCY ls_mseg-waers, ls_mseg-waers.
        ENDLOOP.
        IF NOT update IS INITIAL.
        set delivery date
          IF l_sum_wemng IS INITIAL.
          initial delivery quantity --> initial delivery date
            UPDATE afpo SET   ltrmi = l_initial_ltrmi
                        WHERE aufnr = ls_afpo-aufnr
                          AND posnr = ls_afpo-posnr.
          ELSE.
          read posting date from last valid goods receipt
            SELECT SINGLE * FROM  mkpf
                            INTO  ls_mkpf
                            WHERE mblnr = ls_mseg2-mblnr
                              AND mjahr = ls_mseg2-mjahr.
            IF sy-subrc IS INITIAL.
              UPDATE afpo SET   ltrmi = ls_mkpf-budat
                          WHERE aufnr = ls_afpo-aufnr
                            AND posnr = ls_afpo-posnr.
            ELSE.
            leave LTRMI untouched
            ENDIF.
          ENDIF.
        set quantity and value
          UPDATE afpo SET   wemng = l_sum_wemng
                            wewrt = l_sum_wewrt
                      WHERE aufnr = ls_afpo-aufnr
                        AND posnr = ls_afpo-posnr.
          FORMAT: COLOR COL_POSITIVE.
          WRITE: /3 'Order item data corrected from material documents.'.
          FORMAT: COLOR OFF.
        ENDIF.
        ULINE.
      ENDLOOP. "AT lt_afpo
      WRITE: / 'Number of checked order items     :', l_orders.
      DESCRIBE TABLE lt_afpo LINES l_entries.
      WRITE: / 'Number of inconsistent order items:', l_entries.
      IF NOT update IS INITIAL    AND
         NOT l_entries IS INITIAL.
        WRITE: / 'Inconsistencies were corrected from material documents.'
                  COLOR COL_POSITIVE.
      ENDIF.
      ULINE.
    </pre>
    Edited by: Wilian Segatto on Jan 25, 2011 12:27 PM

  • How can mass creating production orders???

    In SAP ,we can use CO01,CO09,CO07 to create production order. But by these TOCDES,we only can create one production order for one finished product once a time.
    But we now need to create more then one ,may be more then 50 production orders once a time?
    It is possible in SAP?
    I know we could conver the production orders from plan orders after MRP run.But sometimes
    for some reasons we must create produciton orders manually.And I also know in SAP some TCODE can process many production orders once a time ,like COHV,CORM, can release ,TECO many production orders once a time.
    But how can mass creating production orders once a time，not by mrp run?
    How can batch create produciton orders in SAP?
    Thanks for any reply!

    Hi,
    Use the BAPI - BAPI_PRODORD_CREATE or for internal orders BAPI_INTERNALORDER_CREATE
    Take the help of your abaper, he / she can use the above BAPI to write a custom program to mass create production order.
    Hope the above helps.
    Regards,
    Vivek
    Added
    You can also use the below BAPI's in your custom program:
    BAPI_PRODORD_RELEASE to release the orders
    BAPI_PRODORD_CHECK_MAT_AVAIL for carrying out material availability
    Edited by: Vivek on Mar 22, 2009 8:27 PM

  • Error during Production Order Confirmation mfbf ( backflush)

    in my company in sap when i using mfbf for production Order confirmation of tractor then during backflush using mfbf tcode order confirm but in my store dept no metiral cunsume  so please regards this problem
    with warm regards
    pritpal singh

    Dear Pritpal,
    sorry dear,today i cant check  my inbox immediately. Anyway my mail id is [email protected]
    have checked as per my previous post.
    regards
    pradeep

  • About production order change historic records

    The users want to know about production order change historic records.how can I get it, please do me a favour. Thanks.

    Hello ,
    Look into:
    SAP NOTE: 1407961 and
    History of production order changes
    Please search the forum first for such questions.
    - Pushkar
    Edited by: Pushkar Patil on Aug 6, 2010 9:56 AM

  • Production Order Master Data tab

    Hello Guru,
    we have question, in the production order itself, in the master data tab we find weird thing, in the production version it pick PV01 (has inactive bom), in routing field all was been filled up, while in the BOM field it was been blank? why this happen? is it possible BOM is not explode since it was inactive but it create production order?
    I doubt that there were changes occured some where in the BOM or in the material master data of my material but in doc changes i cannot find, is there any way deside looking at the mat doc changes could i find the changes?
    thanks
    Edited by: Ryan on Dec 15, 2008 9:42 AM

    Hello Guru,
    I finally find why this happen to us, the order come from a planned order which converted via CO41, but why thus when i production version was indicated in creating a planned order (MD11) which has alt bom that is in inactive status already, SAP allows the conversion/creation of production order?
    Any inputs R.Brahamankar?
    Thanks
    Edited by: Ryan on Dec 15, 2008 12:09 PM

  • IMG configuration for Cancellation of production order

    Hi all SAP experts,
    where to see the production order confirmation IMG config setting ?
    Regards,
    sim

    Hi,
    Use transaction OPK4.
    Regards,
    Senthilkumar

  • Batch determination for a component material of a production order.

    I created a new production order type in SAP and I created a new production order from the new order type. When Iu2019m doing batch determination for a component material Iu2019m getting the error u201CBatch determination for 000000000002003610 without selection datau201D. I have to click [Selection criteria] and manually assign the selection criteria for the batch class.
    This is working properly for existing production orders and system automatically picking up the selection criteria.
    Is there any place in configuration to assign new production order type to batch selection criteria or how can I overcome this.

    Hi,
    Will you share steps you have completed so far for doing for Batch Determination?
    It will help us to find the missing part..
    - Check all the Batch Characteristic values are maintain in the Batches.If values are missing then also Determination will not take place.
    - Check whether you have maintain Sort rule to Batch Determination strategy or not
    Regards,
    Dhaval

  • 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 relese

    hi sap guru
    i am doing the production order relese senario, but order not relese ,system give massege ' system status WCRE is active' so the order relese has been rejected. in co40.
    thnk
    paresh

    presently the usage key that is enter is009- all task list usage
    which usage key should we use
    will it be afect to the production order
    regards
    paresh

Maybe you are looking for