Reprocessing In Production Order

Dear Friends,
                       I'm implementing SAP B1 in one of Chemical Plant. There I have one scenario in production. Scenario is like I have to do the production of finished product by issuing the same finished product have old lots of material. Means its a kind of reprocessing of finished material.
                      Can you please help me to resolve such kind of production in SAP B1 production module?
Regards,
Rahul Moundekar

Dear Sirs,
              We can always make anything possible using addons but generally Add ons
has very short life or we can say tht anytime it can stop to work. But most of the things
are possible functionally. But it takes time to think over and take out some right solution
  but ultimately we get solution. Such kind of solution I would like to suggest here if I'm
wrong then please tell me.
            My Solution is not to create Goods Issue and Goods receipt direct from inventory
transaction, My Solution is not to create the additional semifinished level item,
My solution is not to reject the material and again receipt it.
            My Solution is that we need to create only one item extra in whole database whose valuation
Method should be Standard so that we can easily update the item cost manually.
            Now first create the disassembly production order in which our parent level item would be Finished
product which we need to issue and take this newly created item on child level. Now Plan it and the release it.
Then dont touch this disassembly production order. (Note: Before creating the disassembly production order
change the item cost which would be equal to finished product.)
            Now create one special production order where parent item should be same as in disassembly
production order. And On child level put this newly created item with the same planned quantity which we need to
issue during disassembly item and if req. take another raw material also.
            Now do issue for production and first click disaasembly production order button and selct disassembly
order reference which we just released. and then click production order button and selct the special
production order reference and select the another raw materials excluding newly created item.
            After doing this our costing will come out for components. In disassembly order we get the loss of
finished product qty as we are only issuing the material & simultaneuosly if we observe the special order costing
tab then we get some value in component cost field which will be because of issue of other raw material in
special order.
            Now go to receipt from production and again press receipt from production button and select the
special production order reference. After receiving the finished product just observe the costing. It will show
the extra gain as much we lost in disassembly production order.
            In this way we can issue the materials and can receipt the matrials and we get proper costing too.
Thanks & Regards

Similar Messages

  • Reprocessing of Production order/Process order

    Hi friends,
    Can anybody explain me what is reprocessing of production order.
    Plz explain me in a step by step manner.
    Thanks very much.
    Kind Regards

    Hi Arun Kumar,
    Reprocessing
    Use
    In the area of confirmation, you can separate confirmation entry from processing. As a result, errors may occur when confirmations, or the processes that follow them, are posted. You can eliminate these errors by reprocessing them. The following reprocessing functions are available:
    Confirmations
    Actual costs
    Goods movements
    Reprocessing Confirmations :
    Use
    You use this function to process confirmations for which errors occurred as they were being automatically processed. With this function, you can either delete or, if possible, eliminate the errors and post the confirmations again.
    Confirmations with errors can arise if they were entered in one of the following ways:
    Upload from a PDC system (see Upload)
    Online entry ( Fast Entry or Mass Processing)
    Entry via BAPI interface
    Possible errors include:
    Order does not exist (for entry via PDC system, BAPI interface)
    Order was locked
    Sequence of time events incorrect
    Individual capacity does not exist
    Work center or personnel number does not exist
    Features
    Reprocessing has the following advantages:
    Selection
    On the initial screen, you can enter your selection criteria for selecting the confirmations that you want to reprocess. Possible selection criteria are: Production order, plant, confirmation, WBS element, sales order, MRP controller, work center, created by, created on.
    Navigation
    The screen for reprocessing confirmations is split into two areas:
    Overview list of the confirmations
    Detail screen for the selected confirmation
    In the standard setting, the overview list is on the left and the detail display of the confirmation is on the right. To change the position of the overview list, choose  (move the list in an anti-clockwise direction, select the position of the overview list). This last setting is saved for the particular user who created it and is used again the next time the function is called up.
    Reprocessing
    The confirmation that you have chosen from the overview (cursor position) is displayed in the detail screen. In the detail screen, you can remove the error in the confirmation.
    The following confirmations can be reprocessed:
    Order confirmation
    Operation confirmation
    Time event confirmation
    Activity confirmation
    The layout of the detail screen is determined by the confirmation that you are currently processing. The layout can be set up flexibly for an operation confirmation (see Single Screen Entry).
    Display error
    To display a long text about the error for each confirmation, position the cursor on the confirmation and choose .
    Check confirmation
    You can check one or more confirmations. To check confirmations, select them and choose . In the Status field on the overview list, the result of the check is displayed with a symbol.
    Delete confirmation
    If a confirmation is not to be posted because, for example, it has entered the SAP System by mistake, you can delete it. To do this, select the confirmation and choose . The confirmation is flagged for deletion and is deleted when you save.
    Delete a line
    To delete confirmations from the overview that you do not want to process at the moment, choose . The confirmation is, however, retained for reprocessing at a later stage.
    2.Cost Determination Error Processing
    Use
    You use this function to gather information about errors in cost determination and if necessary to repeat it.
    If errors occurred when determining actual costs online, you can decide whether or not the confirmation and the error records are saved. If you are using Decoupling Confirmation Processes, the errors are recorded during the execution of the background job or during updating.
    Features
    This function includes:
    An error log which displays the cost determination errors in detail
    Errors are, for example: missing activity prices, invalid cost centers or incorrect assignment of an activity type to a cost center.
    Rerunning cost determination
    Starting a New Costing Run
           1.      Choose either
    ¡        Production orders: Logistics ® Production ®  Shop Floor Control ® Confirmation ® Reprocessing ® Actual Costs
    ¡        Process orders: Logistics ® Production u2013 Process ® Process Order ® Confirmation ® Recalculate Actual Costs
           2.      Enter your selection criteria.
           3.      Choose  (Execute).
           4.      Select the confirmation in question and choose  (Error Log).
    Analyze the errors.
           5.      If necessary remove the errors.
    To remove the errors, you have to exit the reprocessing function.
           6.      Choose Production ® Shop Floor Control ® Confirmation ® Reprocessing ® Actual Costs or Production u2013 Process ® Process Order ® Confirmation ® Recalculate Actual Costs or open a new session.
           7.      Enter selection criteria for the confirmations for which you want to restart the actual cost calculation.
           8.      Choose  (Execute).
           9.      Select the confirmation and choose  (Save).
    Failed Goods Movements Processing :
    Use
    This function allows you to process goods movements that failed when posting confirmations. After correcting any errors that occurred, you can then post the goods movements a second time.
    Features
    This function includes:
    Detailed display of errors
    Errors can be caused by insufficient information such as missing storage locations or missing batch numbers. Errors can also include locked material data, insufficient stock, or attempts to post goods movements in the wrong accounting period.
    Opportunity to correct failed goods movements
    Option of posting goods movements a second time
    Reprocessing Goods Movements
           1.      Choose either
    ¡        Production orders: Logistics ® Production ®  Shop Floor Control ® Confirmation ® Reprocessing ® Goods Movements
    ¡        Process orders: Logistics ® Production - Process ® Process Order ® Environment ® Material Movement ® Failed Goods Movements.
           2.      Enter your selection criteria:
           3.      Choose  (Execute).
           4.      Select the goods movement that you want to reprocess.
           5.      Choose  (Display Errors) to display the errors that have arisen, in detail. To leave the message, choose  (Continue).
           6.      Select the required goods movements and make the necessary changes (for example, Edit ® Replace ® Storage location).
    For example, you can delete incorrect goods movements.
    When incorrect goods movements are deleted, the system does not carry out an automatic adjustment of reservations.
           7.      Choose  (Save) to restart the execution of goods movements.
    When you are reprocessing the goods movements for the confirmation, you can go to the goods movements overview.  Choose  Change Details, to change the goods movements.
    Hope this details is enough for clearing your doubt.
    Revert if any doubt and reward if useful.
    Regards,
    Tejas

  • Reprocessing old production orders

    I've been working with transaction CP01 to fix old production orders that contained components that were not properly backflushed or posted. How can I remove items from the CP01 log that have already been posted? There are items on the list from the past 3 years that are out of the current fiscal/posting period. How can I remove those errors?
    In other words, how can I remove errors in CP01 without reprocessing them?

    CP01 refers to creating Business Processes that comes under Activity Based Costing. Probably you are refering to COGI errors. Please refer to [documentation here|http://help.sap.com/saphelp_erp60_sp/helpdata/EN/b1/c04d1b439a11d189410000e829fbbd/content.htm] for dealing with such errors. The treatment for individual errors depends on each case.

  • IDOC/BAPI for Production order creation from Legacy system

    Hi all
    We are using an interface to create Production orders from legacy to SAP. Would you recommend an IDOC or a BAPI to create Production orders. If IDOC or BAPI then could you please mention which one?
    thanks a bunch

    Hi John,
    For your purposes, please use BAPI for production order creation from legacy system. There is no standard inbound IDoc available to use. SAP has an IDoc for outbound interface only (message type LOIPRO).
    If there is an inbound IDoc available, I would recommend to use an IDoc.
    IDoc technology has excellent error handling and will allow you to reprocess an error (if any).
    BAPI is also good approach to use and fast in term of  processing.
    For BAPI approach, you can use BAPI BAPI_PRODORD_CREATE.
    Hope this will help.
    Regards,
    Ferry Lianto

  • 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

  • Production order-rework

    Hi friends,
        My strategy is Make to stock production. I have created my production order of quantity 100. Then i have deliverd the same quantity of 100 to store in t.code MB31 (against my order). Then i closed my order
    My order status is:
    CLSD CNF DLV PRC MACM GMPS SETC.
    I have stocked my quantity in my store. Afrer 3 months, our people wants to sell the product through sale order. Now they find some damages in that final product. Now sales is returning the final product to production for rework.
    How to reprocess the closed order again? How to go about with this scenario?
    please guide me
    Thanks
    kumar

    Hi Senthil,
    Good afternoon and greetings,
    Made to stock in production term is called as Repetitive Manufacturing and the cost object for the same would be Product Cost Collector.  The Product Cost Collector doesnt have the concept of closing fully basically because the product cost collector would be a replica of the material itself.
    In your case, a rework for production order is applied through by adding an additional work centre in the routing called REWORK.  Re-opening a production in a different period may lead to confusion basically because the planned cost at the time of creating the order say before 3 months would have been £100 per PC.  Now the standard cost estimate is £125 per PC and reopening the order will redetermine the planned cost again and when it is settled it will hit your profitability very badly because the variance would be £25 + rework cost.  Thereby it is advisable to use the concept of standard REM.
    Alternatively, if you want to use the Production Order only, then follow the sequence as below
    1. Move the material from one code to another rework code
    2. Create a new routing with REWORK work centre for the rework material code.
    3. Create a production order for the rework material code
    4. Transfer the material from rework code to main material code.
    5. Settle the production order for the rework material code and thereby your P&L would be intact for the additional cost involved on the Rework.
    Please reward points if found useful.
    Thanking you
    With kindest regards
    Ramesh Padmanabhan

  • Production Order TECO

    Hi All
    I am trying to TECO the confirmed production order at that I am receiving the info
    THERE ARE STILL REPROCESSING RECORDS. SET ORDER TO TECHNICALLY COMPLETE.
    so I am unable to TECO the production order.
    The order which I am trying to TECO has two operation one with Assembly and QM verification.
    Assemply operation status : CNF.
    QM verification                   : REL
    The Error I am receiving is POST PROCESSING for the ORDER prevents TECO.
    please help me to TECO the order.
    Thanks in Advance

    Hi Madhan,
    Clear the Error records using  below t.code for that Prod  order Number and try to set TECO status.
    COGI
    COFC
    CO1P
    Regards
    Pradeep

  • Settlement  in production order

    Dear firends,
    I have a settlement rule in the reprocess production order. where it settles the order cost to the original production order. It 100% works fine.
    there is a  cost element which collects all the cost on the order.
    Can i ignore one cost element from it.
    Please advice.

    Hi,
    Thanks alot for your help.
    my consern is this
    72204     Stock Transfer Fnished Goods          0.00     0.06-     0.06-          USD
    72204     Stock Transfer Fnished Goods          0.00     576.11     576.11          USD
    100     Reprocess order settlement     1380100     0.00     620.24-     620.24-          USD
    90091     Lab Testing     QUALITY/M00013     0.15     0.00     0.15-     100.00-     USD
                   0.15     44.19-     44.34-          USD
    90010     Machine Cost Preperation     KNITTING/M00003     0.00     1.43     1.43          USD
    90060     Finishing MachineCost Stenter     FINISHING/M00007     0.00     42.76     42.76          USD
    Finishing Prod Cost               0.00     44.19     44.19          USD
                   0.15     0.00     0.15-          USD
    to my cost elsement 100, I want to ignore the cost of 72204 cost.
    How can i do this.
    PubuduS

  • Production order confirmation using CO15

    Hi ,
    When i am confirming production order with reference to sales order using CO15 , material document is being posted only for assembly material , but not for components.
    Please let me know how i can correct this.
    Thanks in advance.
    Regards,
    sudheer

    Sudheer,
    You can display confirmation using transaction CO14, here you click the goods movement tab, and if you find GI items highlighted in Blue then these goods movement error needs to be reprocessed. Execute transaction CO1P and save the records there, then execute transaction COGI and clear the error records.
    Regards,
    Prasobh

  • Production Order Cancel

    Hi,
    I have AUTO GR set for production orders.But when i do the cencellation of prodcution order GR reversal is not happening but only the confiramtion is getting reversed.
    Please let me know what is the Issue.
    Regards
    Ramesh

    Dear ,
    There are so many reason why Auto GR is not getting canceled .Please note the following :
    1.If you have confirmed order by CO15 or CO11n  and if Auto GR is activated then material document will not be cancled
    by MBST or MIGO. Cancle confirmation by CO13,your material document will be cancled  automatically.You can frist try to cancel it through MBST with movement type 102 and then cacel operation in CO13.While cancelling the confirmation check the goods movement tab page by clicking on that then save the cancellation.The material document will be cancelled.Please note that the document won't be reversed if the qty is invoiced , delievered after production completed or  settled , WIP , FY period is closed , Material period is closed etc .
    2.If confirmation for order is cancled but Auto GR reversal does not happen then you need to find the error record in COGI,if you find in COGI clear the error record based on the error message.If you do not found error in COGI then execute transaction CO14 for the order and select the cancelled confirmation for display, here in the display confirmation click the goods movement button, you can find the 102 movement (Gr reversal) highlighted in Blue color and you would be getting a message in task bar "Highlighted items needs to be reprocessed".For this condition you need to execute transaction CO1P,as followed...
    you can find the record (reason)in CO1P. Execute CO1P for the order by activiating all the checkbox for GI,GR,Activites, you would find the record here, just select the record and save the transaction. Some time the data gets posted directly or you may now find the error record in COGI.
    3.Analysis in OMJJ with Movement Type -102 , wether , Reversal is activated by CO13 and farther set up for CO11N, CO12
    Hope this will help you to figure out the issue .
    Regards
    JH

  • Open Production Order

    Hi have to create a report that has open sales order , open po , open pur req , open planned order and open Production order.
    I need the logic for OPEN PRODUCTION ORDERS.
    The status of the production orders are maintained in JEST Table .
      I need logic to elimate the completed production orders during my selcet . Since JEST Table has multiple entries and for some orders that are released the 'DELV'  status wil not be maintained at all at that time.
    I wil really appreciate your help , if you can tell me how to emliminate the completed production orders during my select query to get the open prod orders.
    Is there any fun moduel or bapi that wil give the Open prod orders ?? or any std report that gives open PO??
    Thanks

    for this you can use the Function STATUS_TEXT_EDIT , for this pass Objnr (get the objnr from AUFK table using the production order) it will give you the status in the LINE exporting parameters.
    Import parameters               Value
    CLIENT                          100
    FLG_USER_STAT
    OBJNR                           QM000200000010
    ONLY_ACTIVE                     X
    SPRAS                           EN
    BYPASS_BUFFER
    Export parameters               Value
    ANW_STAT_EXISTING
    E_STSMA
    LINE                            OSNO NOTE   "this is the status text
    USER_LINE
    STONR                           00
    if line CS 'DELV'
    "ignore the Order
    endif.

  • Error while raising Production Order

    Experts
    I get an error for a particular Item while raising a PRODUCTION ORDER
    'Location Input does not match the warehouse location of Item'
    I work in SAP B1 2007B - PL 18
    It will be great if someone can give me the reason/solution for the above ERROR.
    REGARDS
    KARTHIK

    Hi,
    Parent item and child items warehouses location should be same.......
    Regards
    Deepak Tyagi

  • How to find out the list of Production orders created for sales orders

    Dear All,
    Our company wants to generate a report for a List of Materials sold out in a particular Product Hierarchy. Along with that we want to know the list of Production orders created for the sales orders.
    How to identify the production orders which are created based on Sales orders.
    Kindly suggest.
    Regards,
    Mullairaja

    Check these threads
    [Sale Order & Production Order|Sale Order & Production Order;
    [Re: Linking Production Order against a Sale Order MRP run|Linking Production Order against a Sale Order MRP run;
    thanks
    G. Lakshmipathi

  • Creation of Production order in Past dates using RFC

    Hi all,
    I am using RFC to Create a production order based on the datas available from MES systems.Here the process flow is From MES system datas are passed to interface in file format then from interface will calll the RFC so that the RFC will do the function of Creating the Production order & release in SAP.
    Here i face an issue that i have 3 shifts at the end of every shift i have to tranfer the datas from MES to SAP .Which means i have to create 3 Production orders for a day.My issue here is the third shift datas will be availble for me in the next day morning after that only i am able to transfer theses datas to SAP.In this case i want the SAP to create th Production order  for third shift in the Previous day time.
    Ashift - 7AM t0 3PM
    BShift-3PM to 11PM
    CShift-11 PM to Next day morning 7 AM
    I need SAP to create Production order for Shift C on 11 PM of the Previous day when i transfer it on next day morning 7AM.
    Is this possible.
    Thanks in Advance,
    MBN

    Hi,
    I mean the Production Created date as the basic date only.
    My requirement is for the C shift i will get the output from the MES on the next day morning.After that i wwill transfer the production datas to SAP throgh Interface at that time i need the basic start date & time  of the production order to be the C shift starting time that is previous day night 11.00 PM.
    Eg.
    C shift  date 12.04.2010 night 11PM to 7AM
    i transfer the c shift production datas from MES to SAP on 13/04/2010 Morning 7AM.But i want these datas to create basic start date & time of the production order on 12/04/2010  11PM.
    What should be done to get these.
    Thanks in advance,
    MBN

  • Creation of a new costing variant to cost production orders

    Hi all,
    Currently the business is only able to cost a vehicleu2019s production order at the standard cost value which is determined at the start of the year.
    During the year a number of the purchasing values will be updated with a new contract price, this increase will not be reflected in the standard cost until the end of the year.
    The business would like a new costing variant which will cost an already created vehicle in SAP by its production order at the u201CCurrent Costu201D (current purchasing info record value).
    It will need to be calculated in the following way:
    u2022Purchased material - at purchase cost from info record (see below for applicable exchange rate).
    u2022Manufactured material - child material to be at purchase cost (from info record). Routing cost (labour\overhead, etc) at current criteria.
    u2022No allowance for CPI.               [WHAT_ DOES_CPI_MEAN_?]
    u2022Exchange rate: ideally, fields are provided to input exchange rate. If this is not possible then apply current monthu2019s exchange;
    u2022FRAu2019s - current rate from the info record.
    u2022Summary of total material cost by origin code with ability to drill down to line level.
    u2022The output of the report will need to be similar to the layout of a production order but with only the current value displayed.
    We have some problems to understand this request: we don't know the transaction which is used by the users to costificate a production order and what does it mean "CPI". We are not sure on the feasibility of the costing variant requested because it must consider both actual costs and standard costs.
    It should costificate in this way:
    (Actual Cost of Row Material * Bom's standard qty) + (Standard price * Standard production time (in the routings).
    Could you help us?
    Many thanks to all of you, best regards.
    Alanis

    You can create a new costing variant with  a valuation variant that points to inforecords for material prices. Go to OKKN t-code and create the required configuration and start using the new costing variant to measure the current cost of making vehicles.

Maybe you are looking for

  • How to get data from hard drive in dead iMac?

    I have an old slot-loading iMac (350Mhz G3 blueberry) that just died, probably a dead power supply or something. Won't turn on at all. I don't care about restoring it, I just want to take the hard drive out and grab data from it. I've found instructi

  • Populate two poplist items on when-new-form-instance trigger

    Hello! I have a simple form with some text-items, datetime items, two poplist items and two buttons (exit and save to database). Everything works well except the second poplist wont get populated. After wrote the code for the first i just wrote a sim

  • How to put a SQL Agent Job wait in the trigger while the job is running.

    Hello! I am not a geek in writing t-sql code so I am seeking forum help in completion of my task. I have a trigger which fires upon a action and with in that code, I am starting a job via t-sql like EXEC msdb.dbo.sp_start_job N'JobName'; Now, I want

  • Pb unicode with function CONVERT_OTF_2_PDF

    Hello, I have a problem. I have to convert a smartform on PDF. I'm using the function CONVERT_OTF_2_PDF like this :   CALL FUNCTION 'CONVERT_OTF_2_PDF'     IMPORTING       bin_filesize           = p_filesize     TABLES       otf                    =

  • How to stretch and shrink with browser resize

    Is there a simple way to force stretch and shrink all components and text as the browser window resizes? I tried 100% width and height in the application tag but that only resizes the main container. I want to also resize eveything inside the main co