Termination of Production order

What are the necessary configuration steps for for the termination of production order if the operation sequence were not followed.
do we need any user exit or enhancement to be done?

Hi,
In OPK4, for your order type and Plant combination:
In the First tab page : Generally valid settings
Do the settings as below
Operation sequence   E Error when operation sequence is not adher
Hope this helps..
Regards,
Siva

Similar Messages

  • Error during goods receipt of Finished goods for production order

    hi friends
    pls help me iam struggle this issue and mentioned the issue .
    when i do goods receipt for production order system getting error like
    No price could be determined for material/batch FG/ plant ZTP
         Message no. CK 465
    Diagnosis
         The system could not calculate a price for material/batch FG/ in plant
         ZTP for valuation view 0, because none of the valuation strategies in
         valuation variant 007 was successful.
    System Response
         User-defined error management enables you to specify whether the message
         is an error message, a warning message or an information message.
         o   If you have defined the message as a warning message or an
             information message, the costing item will be entered in the cost
             estimate with a value of zero.
    If you have defined the message as an error message, the cost
    estimate contains an error or errors.
    -   In the case of a material cost estimate, the system sets the
        status KF.
    -   If it is a cost estimate without quantity structure, or base
        object cost estimate (that is, a unit cost estimate),  the
        system cannot proceed with costing until you have corrected the
        errors.
    If the system issues a termination message, the cost estimate cannot
    be processed, and processing is terminated.
    procedure
        o   Check the master data for material/batch FG/ in plant ZTP.
        o   If you have authorization for Customizing, check the valuation
            strategy for materials in valuation variant 007.
        Note
        If the message is a warning message or an information message, there is
        a danger that materials with errors will be ignored by the system.
        If, because of this, you issue a warning message and at the same time
        include materials with a zero value in cost estimates, you can make the
        following settings for these materials in the costing view of the
        material master:
      1.  Enter a very low price in the planned price 1, 2 or 3 fields
          manually, for instance 0.01 USD. These prices are used for costing
          purposes only; they are not read by other applications.
      2.  Enter the highest price unit possible, for example 10000.
          Note: If you enter a new price unit that is higher than the costing
          lot size, the system increases the costing lot size accordingly.
      3.  Change the valuation strategy, such as strategy 4, where you could
          enter the planned price field in which you entered the low price.
          The system now costs as follows:
          Using the valuation strategy, the system finds planned price 1, 2 or
          3. Due to the low price and high price unit, the system rounds the
          value to zero. However, the cost estimate still obtains status KA
          (free of errors), and no error message is issued.
          This procedure can be used for all materials that have caused error
          message CK465 to be issued.
    with regards
    dinesh
    Edited by: code acess on Nov 8, 2010 4:06 AM

    hi ragavendra,
    this is dinesh .i maintained the costing view and planned price. but again i have same error.so please reply me where i missed the data
    with regards
    dinesh
    Edited by: code acess on Nov 9, 2010 4:01 AM

  • Confirmation of Production order

    Hi
    Expert
    I would like to set Production profile such that Without issuing goods for the production order confirmation of operations is possible. I want to restric this. Where can we do this in configuration?
    Plase explain in details
    Thanks & Regards
    Pert

    Dear Pert,
    1) Best way is to go with user exit MBCF0002
    2) the other option would be, go to OPK4, here double click on ur order type & plant combination
    3) Make a tick mark for All Components, this ensures that all components gets backflushed in Confirmation screen
    4) Now go to second tab, here tick for incorrect goods movement  & termination for incorrect Goods movement
    5) so system will not let you go further in confirmation screen, if any missing parts exists
    Regards
    Madhu Kumar

  • Update error while creating production order (TCODE CO01)

    Hello,
    We have created new plant into development server for testing. We have created production Order few days back at that time we have not faced any problem. But from last two days , when we create new production Order , system gives following error:
    ORA-00947: not enough values
    DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB
    SAPLCOVB" or "LCOVBF10"
    HEADER_POST"
    and
    Update was terminated
    System ID....   DEV
    Client.......   500
    User.....   HPLSU
    Transaction..   CO01
    Update key...   4B6E4F48C08D027FE1008000C0A802F3
    Generated....   08.02.2010, 10:35:48
    Completed....   08.02.2010, 10:35:49
    Error Info...   00 671: ABAP/4 processor: DBIF_RSQL_SQL_ERROR
    Our work is held up.
    Please also note that If we increase the QTY in the existing Order ( already created few days back) , System accept the same and Order is saved.
    We are looking for the solution for the above.
    Early reply will be highly appreciated.
    thanks
    harish

    Hi Rishi,
    You better check with your BASIS team.
    Check this link also
    Supervisor Error ADM0015
    Regards,
    Satyajit Kumar
    Edited by: Satyajit Kumar on Feb 8, 2010 7:47 AM

  • Run time error while saving the production order in CO02

    HI Experts,
    While i am releasing and saving the production order the system is giving the runtime error. Please help.
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_SLD_API_EXCEPTION
    Error analysis is
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SLD_API_EXCEPTION', was not
    caught in
    procedure "GET_ACCESS_DATA" "(METHOD)", nor was it propagated by a RAISING
    clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    Internal error in method
    A Quick response is required.
    Regards
    Dinakar Sarma

    Hi,
    Please check below  link for your issue , it may useful
    http://forums.sdn.sap.com/thread.jspa?messageID=10815298#10815298
    Regards,
    Ram

  • Automatic goods issue of components upon creation of Production Order

    Hello gurus.
    The business would like to have the components in a Production Order automatically issued (with Movement Type 261) upon the creation of a Production Order.
    I was investigating this possibility under the Production Scheduling Profile option in IMG, but there is no automatic action for this.
    Do you know of another way this could be achieved? I'd like to do this preferably without having to implement User Exits or Batch Jobs.

    Fernando,
    Automatic goods issue is not possible.
    But you can certainly think of backflushing the components while confirming the order with CO15 or CO11N.
    Make the required settings in material master, work center or routing. It will get copied to the order.
    The same can be maintained in the order too.
    There is one more option available in 'Define confirmation parameters' T code OPK4.
    Execute the above T code.
    In 'Generally valid settings', mark 'All components' under 'Goods moveemnt'.
    Also in 'General individual entry'  under 'Error handlings/ logs' mark ''Goods movement'  & if required mark 'Termination for incorrect goods movement' so that if any problem arises with the GI/ GR, the termination would be terminated.
    Hope this helps you.
    SmanS

  • No. range issue : at the time of production order settlement

    Hi expert,
    My user is unable to settle production order due no no range issue:
    Short text of error message:
    Document number 9000 20001 2008 was already assigned
    Technical information about the message:
    Diagnosis
         Document number 20001 in company code 9000 and fiscal year
         already been assigned.
    System response
         Termination of processing.
    Procedure
         Check document number range 02 in company code 9000 and fi
         2008 and correct the number range status if necessary.
    Message classe...... "F5"
    Number.............. 152
    Variable 1.......... 9000
    Variable 2.......... 20001
    Variable 3.......... 2008
    Variable 4.......... 02
    Variable 3.......... 2008
    Variable 4.......... 02
    Pl advise.
    Regards,
    Samar

    Hi experts,
    Thaks for the reply.
    Pl advise what is the configuration/T code to be maintained for no range
    Regards,
    Samar

  • 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

  • Input routing on production order creation using BAPI_PRODORD_CREATE

    Hi experts,
    I have created one program for creating production using BAPI_PRODORD_CREATE it is working fine. I am trying to input the routing and alternate grp counter along with this but it is not updated in production order.
    How to input the routing details for production order ?
    Is there any BAPI/FM to update the routing details in production order ?
    Thanks & Regards,
    Karthi

    Hi Sree,
    Routing for the material already exists. I don't know the reason why its not picking.
    If i maintain routing as mandatory in OPL8 tcode.
    BAPI_PRODORD_CREATE giving error as "Order type YG01 requires a routing (transaction terminated)"
    Thanks & regards,
    Karthi
    Edited by: karthi keyan on Aug 24, 2011 10:51 AM

  • Backflushing production order

    Hi all,
    I have a question about vendor consignment stock in bill of material.
    I have a bill of material where one component is manage in vendor consignment stock.
    My question is:
    During confirmation (ex trn CO11) is it possible to issue this component (backflushing) from vendor consignment stock. Does the environment propose me the K special stock?
    What is the correct customizing?
    Many thank

    1 Our requirement is that during, production order confirmation, even if materials are not available, system should allow us to confirm the order. Later will issue GI through COGI.
    This setting is enough for above Requiremnt
    In OPK4, in the tab "Individual Entry General" we have not checked the boxes in 1) Goods Movements & 2) Termination for Incorrect movements.
    2)   we are making use of the functionality "Back Flushing". Iam afraid system should support our requirement?
    No, Backflushing is not a problem,  System will support your requirement.
    There is no configuration is reqd to meet your requiremnt
    Regards,
    Sundaresan

  • Block Production Order Confirmation

    Hi Team,
    I am having below scenario.
    Today i have created the production order & performed the availability check. The availability check is passed & all the required materials are available in the storage location Z001. Now the Order status is : REL & MACM.
    Note: I have two BOM items namely A1 & A2. In storage location Z001, i have stock of A1 & A2 as 10 & 20 respectively.
    But due to some emergency reasons, the stock of A1 (10 qty) is transferred from Z001 to Z002.
    Now i am again performing the availability check, now i am getting MSPT status since the stock of A1 is ZERO in Z001.
    Now i would like to control the confirmation in CO15 that, if the order status is MSPT, the confirmation should not be posted.
    The system status for MSPT is "I0004". I am searching for relevant business transaction for "Confirmation"in BS22 against the status "I0004". I have found many business transactions like "AM21 - Confirm", CU02-Partially Confirm CU", "CU03 - Confirm CU". etc. But i could not able to understand the correct business transaction for "Confirmation" & "Partial Confirmation".
    Q1: Can anyone help me to identify the correct business transaction for "Confirmation" & "Partial Confirmation" in BS22?
    Q2: While executing the BAPI "BAPI_PRODORDCONF_CREATE_HDR", the confirmation to be terminated if the order status is MSPT. Is this possible?
    Note: I have activated the check box "Termination of Incorrect Goods Movements" in OPK4?
    Q3: In OPK4, i have noticed the check box "Termination of Incorrect actual costs". In what situation, i need to activate this check box?
    Thanks

    Hi
    The system status for CNF is I0009 and for PCNF is I0010.
    The confirmation through  standard BAPI will result in COGI entries and it wont check the OPK4N settings, these settings are valid for single screen confirmation only CO11N,  but  with Good programmer you can write down you code and the confirmation will take as per your requirement through the BAPI
    Regards,
    Anupam Sharma
    Message was edited by: Anupam Sharma

  • Production Order  Start Date

    Hello All,
    I am facing a problem in a Production order.When I am trying to change the  Production order Start date  and saving the changes I am getting a termination error (program termination).
    The error message is as below
    Nested call of PERFORM ON COMMIT: NESTED_PERFORM_ON_COMMIT caller: SAPLMCEX program: SAPLMCEX form: MCEXLOG_WRITE_04_DIA
    Regards
    Dhananjay

    Hi
    Check for the order scheduling parameters and confirm that the order in past are also allowed.
    Krishna

  • Error message while confirming production order.

    Hi Gurus,
    I would like to know if it is possible to get an error message when we try to confirm a production order if there is not a cost for each component.
    Please provide details if any.
    Thanks for your understanding.
    Naveen.A

    Hi,
    You can have setting for error message for incorrect costs in confirmation as below :
    Go to OPK4 ( Parameters for order confirmation) select plant & order type--> General individual entry ( tab)-> Error handling/logs
    Maintain tick in check box for Termination for Incorrect ActCosts.
    This will fulfill your requirement.
    Revert in case any doubt.
    Regards,
    Tejas
    Edited by: Tejas  Pujara on Apr 6, 2009 7:17 AM

  • Production order-Project system

    Hi
    How can planned order can be converted into production order in project system
    Regards
    Suresh

    Hi
    With manual selection the system lists all the valid task lists that exist for the material at the time of copying and that should be selected according to the selection ID. You can select the required routing from this list.
    Working Without a Routing
    When you work without a routing the system automatically generates an operation. It proceeds as follows:
       If default values have been maintained for the automatic generation of an operation the system uses these values to generate an operation automatically in the order.
       If no default values are specified in Customizing the system generates an operation with the control key 0001 and the operation number 0010.
    <b>If a routing must be selected but no routing can be selected then the system reacts with a termination message and you must carry out order creation again.</b>
    Further information please refer the link
    http://help.sap.com/saphelp_47x200/helpdata/en/b1/c04182439a11d189410000e829fbbd/frameset.htm
    Regards
    Ramakrishna

  • Production order no. is different in co02 & co82

    hi, all SAP experts,
           when i create production order by co01, production order no. 1045100261 is generated but at same time when i saw in co82 it shows current no. as 1045100260.
         Again when i create production order , 1045100262 is generated but in co82 it shows 1045100260.
    Finally when i create production order , 1045100263 is generated but error shows " update was terminated " , at that time when i saw in co82 , it shows current no. as 1045100280.
               So how it is possible and show different current no. in co82 ?
    Please tell me any setting is there in customization for same ?
    regards,
    Nitin Nerkar

    Hi
    Need not to do any settings. Its common phenomena. The Current no showing in CO82 is the Prod ord no  saved successfully. In the next instances  as the order is not getting updated due to some technical Problem and when trying to create in CO01 it Proposes the next sequence no. Once save the Production order then only the Current no in CO82 get updated. Pl look out for the Updation error
    Regards
    Brahmaji

Maybe you are looking for

  • Battery life, only 3 hours?

    Hello everyone I come to you tonight with a question regarding my Macbook Pro's battery life. This computer is fairly new, it was purchased in September of 2011. At the time I was getting the advertised 6-7 hour battery life. As time goes on, I do un

  • Times in Messages

    Hi, What controls the display of message sent/received times in Messages? I'm in a conversation at the moment, and there are times before each exchange until the middle of the afternoon, nothing after. Where can I find more about this? I can't seem t

  • No! Java 1.5 is all different!

    Ok I'm totally not impressed by the new version of java! Everything has like, changed! There's lots of new stuff we have to learn and I'm like, still learning java 1.4! Why did they have to change stuff? Java is like, totally difficult enough already

  • Reg . sql statements in r/3

    what is the query used to fetch all fields from table with out using select* ?

  • Migrating from ibook (10.4.11) to new macbook with 10.6

    I'm writing this to hopefully be informative for someone else with similar problems. Have had an ibook for many years. Lots of documents; mostly MS word. Bought new macbook (white) and started it up. It asked about migrating but I decided to use it f