In the production order for 1 of the component material no 261 movement

Hi SAP Gurus,
In the production order out of 8 components for 1 of the component material 261 movement is not happening ( Not getting backflushed) Please give some input on this issue.
Thanks and Regards,
SHARAN.

Hi Dhaval,
In MRP2 view the backflush indicator has been set. But in the parent material BOM setup this material itself not there I informed the user about this, please refer the below user comment ( In BOM the material:Q7829-60184 is appearing and mat:Q7829-60140 not there in BOM, in production order for both the materials 261 movement not happened ) Please give your input on this issue.
Hi Sharanappa
We just did a PCO roll  PCO #4619999R3 on Tuesday 30th Dec.
From Q7829-60140 to Q7829-60184
All options for Q7840A, Q7829A, Q7830A (except #ACJ, already completed), Q7831A.
That's why you are not able to see the part in BOM
How can we rectify this from here?
Thanks and Regards,
SHARANAPPA.

Similar Messages

  • Costing the production order for the configured material

    We are trying to cost the production order for a configurable item.  But the system is not calculating any cost in the production order.  Sales order related to this configurable material is costed.  What additional setting I need to cost the production order for the configured material ?

    Hi Niki
    If your SO is costed, thats enough from a System's perspective... Planned cost will be the sales order cost estimate because SO saves the Chars required for the Configurable material
    Planned cost in Prod order depends on the Costing variant you have assigned in the order type... Check the error log if there is any error in cost calculation in prod order
    br, Ajay M

  • Goods Issue Production Order for Confirmed Qty Component

    Dear PP Gurus,
    Here is my case :
    Stock Qty for Sparepart A : 100 un
    First production will require 80 un A, and availability check confirmed. Second Production Order will require 70 un A, where 20 un confirmed and 50 un is not confirmed on availability check. When i try to goods issue the second production order, it is allowed to consumed all 70 un because unrestricted stock is 100. How can i forbid goods issue in second production order only for 20 un A which is confirmed before.
    Thanks,
    Arman Lie

    Dear
    First of all what ever qty u release during production it well get copied in confirmation so as u said first production order is 80 so the balance qty is 20 out of 100 units so for 20 production order is confirmed so u need another production order for 70 in that case u have deflicit stock of 50 so for that reason ur production order not get confirmed for 50 in order to confirm this order u need t make a stock of 50.
    1. check in the OPK4 enable the actual qty
    2.check t-code OPJK Checking Rule and check when material availability when saving the order
    and please check in the material master what availability check u have maintained in mrp
    [http://help.sap.com/erp2005_ehp_04/helpdata/EN/cf/70124adf2d11d1b55e0000e82de178/frameset.htm]
    With Regards
    Pushpalas

  • How to update the condition price in the sales order for all the items

    Hi,
    How to update the condition price for all the itmes in the sales order to carry out the new price automatically through a stand alone program, for all the orders in the billing due list table?
    Thanks,
    Balaram

    Hi,
    There is a change in the requirement.
    Scenario:
    I have created a sales order with some 4 condition types, in that 2 condition types are of class A & B and the other two is of class C. Here I need to update the condition price of class A & B only and the remaining condition types should not get update even though there is an updated price is available.
    For the above scenario, I need to write a standalone program. Do we have any function modules to update the price of the single condition in the sales order? Please tell me how we can update the sales order at item condition level.
    Thanks.
    Balaram

  • SD-PP Availability to include the production orders

    Dear All,
    Our client has a production plant which produces for 3 differennt sales departments as below
    1) Distriibution
    2) Retail
    3) KSA
    The production for each department is done seperately with seperate production orders whcih have seperate MRP Areas.
    I have 3  sales order types for each depatrtment
    ZOR1 - Distriibution Sales Order
    ZOR2 - Retail Sales Order
    ZOR3 - KSA Sales  Order
    The production orders are included in the availability scope but when i do the availablity in any of the above SALES orders  it is including all the production orders for all the departments
    How can i restrict the availabilty in each sales orders to respective production orders of each departments.
    Kindly Advise
    With Regards
    Mohammed Raees

    I faced the same issue in my previous projects..
    As my understanding, there s a conflict between SD and PP module.. If you use MRP area, the ATP checking scope in PP side can be split into at least 3 levels, plant level, MRP area level and storage location level.. But in SD side, only 2 level are aviliable, plant level and storage location level, since you can not input MRP area directly into sales order, while what you can do is just to input plant (this is mandatory) and storage location (optional) and the MRP area is determined by the storage location you input in the sales order.. But once you identify a storage location in sales order, actually, the ATP scope is against storage location instead of MRP area..
    In 2 of my previous projects, this requirement was raised.. But I m luckly enough..
    The products / inventory management is not complicated in one of the progects that user can accept storing their finish goods into a 'fixed' storage location for each for MRP areas, i,e. for storage location 1001 is the only storage location for finish goods for MRP area 001, while 1010 is for MRP area 010...In the other project, they need to store their finish goods seperately based on different requested storage enviroment..But we use WM in this project that the storage locations for finished goods are still 'firmed' for each MRP area..
    Based on this pre-condition, my solutions is to use a user-exit in SD to populate the storage location in sales order accordingly..
    Hope above helps.. And kindly share with me if you find out the solution for 'multiple storage location in the same MRP area'

  • How can read BOM component date before save the production order??

    Hi Experts,
    In our company, we need to develop a program to read the BOM component data of the production order
    before we save the production order.
    That for example ,when we create and release a production order , before we save the production
    order,we want a porgram to read the BOM component data. If some component data can meet our
    requriement (may be if there is material requirement quantity>100 EA),then the system will pop up a
    small dialog box to remind us.
    There is user exit PPCO0007 and PPCO0007.But it seems they only can read the head data of the
    production order before we save the production order. And the BOM component data of the production
    order are saved in the RESB(Reservation Table).So if we do not save the production order,all the BOM
    component data are not saved in the RESB table.
    So how can slove the problem??
    How can read component date before save the production order??
    Are there any other user exit we can use???

    Hi Just wanted to check am I right that you are trying to check if you have enough Materials Available before you release or Save the order right ? if this is your business objective then when you create order you have material availability tab which checks and gives error if shortage is there. Please let me know if is this wht you asking for ?

  • How the material PRT issue/receipt to the production order can be handled?

    Hi PP Gurus,
            For one of our clients, the handling of PRT is to be controlled with the issue/receipt for the production order.
    1. What is the procedure for issue/receipt of PRT material in the SAP?
    2. What is the procedure to block the PRT for the creation/release of production order when it was already assigned to the other production order during the same time?
    3. The PRT is to be available automatically once the assigned production order operation is confiremd.How it can be handled in the SAP?
    Appreciate your early response.
    Thanks,
    Reddy.

    Hi Ramanujam,
            Thanks for your response.
         1. The dies can be used for the production of Pressing, Casting and Forging etc. These dies will be managed in the stores. The stores representatives will issue the die to the shop floor for an operation of a production order.They will return back the die once the production is completed at that operation using the die. How to map this process in the SAP.
            Typically, these dies can be treated as PRT materials in the SAP system.
         2. OPJK configuration is not sufficient. The same PRT will be assigned to the many production orders during the same time.The system won't block with only this setting. There are some other steps involved to complete the process.
                     I would like to know the complete procedure with all the steps to block the PRT once it was assigned to the production order operation. The same PRT is to be available for other production orders automatically once the operation is confirmed after production.

  • 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

  • In the Production Order, Sales Quotation is displayed not the Sales Order

    Hello to All,
    I need a kind help from you.
    My scenario is as follows
    There is a Configurable Material (Finished Product)
    Sales quotation (VA21/2/3) were made for this material.
    Sales Order (VA01/2/3) with reference from the Sales Quotation were made for this same material.
    Now when I run the MRP (MD02) for this material, Planned Orders were created.
    Planned orders were converted to the Production Order.
    In the Production Order (say in Display mode), under the 'General' tab, there is a segment called 'Sales order'. In this segment, the sales order is being displayed if the Production Order is created for a sales order (MTO scenario).
    But, in my case, the Sales Quotation number is being displayed instead of the Sales order.
    My Issue which need your answers:
    Is it a standard SAP scenario?? I mean, if the production order is created for a sales order and again if the sales order is created earlier with reference to a sales quotation, then in the production order, the Sales quotation is displayed. Is it a standard?? Or it is showing wrongly? I mean, is it like that, always the sales order should be displayed in the Production order and not the sales quotation??
    Please suggest so that I can overcome this problem, if at all it is a problem.
    Some More Inputs (For your analysis/research):
    1. After the MRP run of the material the Planned Order is created. I have checked the planned order, and found tha the assignment of sales document (in this case Quotation) is done in the Planned order itslef. It is visible wthin the "Assigmnet" tab of the Planned Order.
    2. For the analysis purpose, I created one stand-alone Sales Order for the same material. I mean, without reference from any Sales Quotation. Then, when I run the MRP (md02), the Planned Order and then production order were created normally, with reference to the Sales order. This just for your kind information.
    3. I have checked the pegged requirement of the Production order in the MD04. It is showing the Sales order itself. But, if I see the production order (CO02/O03), it shows sales quotation.
    User Requirement:
    Evenif, the sales order is created with reference to a Sales Quotation, after MRP run, in the Planned and thereby subsequent production order, the Sales Order should display and not the Sales quotation.
    Please suggest.
    Thanks and Regards,
    Supriyo

    Hi
    Since your scenario is configurable material,  the system takes the reference of sales quotation only. Because the in case of configurable materials the sales quotation is the base and based on the sales quotation the sales order is created and subsequent production order.
    This is std SAP and for configurable materials the sales quotation is deciding factor
    Krishna

  • Restricting production order qty while the converting planned order

    Dear all Hi,
                     I have a planned order for 10 qty. While converting it to production order the system is allowing me to increase the qty to more than 10 (eg 11 qty) & it is saving the production order.
    But the clients requirement is that system should not allow the user to create the production order for qty more than palnned order qty.
    Please help/suggest how to get this restriction from the system.
    Thanks in advance.

    Hi,
    If that is the case, then eliminate the Process of manual conversion of Planned Order to production order.
    You can use the Program PPBICO40.
    Schedule this Program as a background job, after the MRP Run.
    Authorization management with strict monitoring will eliminate this type of process.
    Regards,
    Siva

  • Confirming the production Order

    hello,
    i am using BAPI_PRODORDCONF_GET_TT_PROP and BAPI_PRODORDCONF_CREATE_TT to confirm the production order.
    well..the issues are :
    1. for eg: i am confirming only 40 from the total qty 45, but in the result, it takes the total qty - 45. it doesn't take 40.
    2. if i am confirming the same order for different operation, the first one is executed well whereas for the second opt, its giving the error msg as "the Po 'XXXX' is processed by other user" even after using the commit work.
    provide me some solution.
    thanks in advance,
    eti.

    hi..
    i hope you din't get any question properly...when i do the confirmation of PO for operation eg : 10, it is doing fine. for operation 20, it is not confirming...it doesn;t mean that PO is processed by other users, it must be locked as it had been confirmed for the 1st operation 10.

  • MIGO Proposes Quantities even when the Production Order has DLV status

    Hi,
    In ECC 6.0 after my last operation has been confirmed with AUTO GR. MIGO proposes the planned Scrap quantity against the Production Order for Goods Receipt. Is there a way to stop this.
    Here is the scenario that I am facing this issue.
    I have a production order with Qty 103 with 3 QTY as planned Assembly scrap.
    At the last operation I do 98 yield, 2 rework and 3 scrap. My Rework Reason Code inserts a rework operation using trigger point in the production order. Now after I confirm Rework Operation when I got MIGO for Goods Receipt it proposes me 5 (i.e. 3 Planned Scrap plus 2 rework).
    Is there a way this behavior be stopped.

    Hi Aravind,
    I have a suggestion. Instead of having assembled scrap if you follow below way you can overcome from this issue.
    To produce 100 quantity, goods should be issued for 103 quantities. You should maintain this in BOM. So during production confirmation, if your yield is 98 then GR will happen only for 98 and you can enter 2 piece as scrap quantity. GR will not happen for scrap quantity. When you confirm the rework operation, system will propose only 2.
    Currently we are following this way. Try it out and see.
    If you need more information, do reply.
    Regards / US

  • Batch determination in the production order header

    Hi,
    I'm trying to determine the batch for the production order header (AFPO-CHARG). I've set up the search strategy, added the procedure to the relevant plant/order type combination in OPL8 and created the batch search strategy to default the batch, however, when I create the order the batch does not default. Am I missing anything obvious?
    Thanks in advance!

    Hi
    Batch Search strtaegy is used to get the batch numbers of the components in the production order or get the batches in the delivery of the sales order.
    These batches can be selected based on the selection criteria and the sort rules.
    I do not completely understand what you mean by batch at heaser level.
    If you mean to say the batch number for the header material then you can not search that batch since it has to be created first.
    Hope this helps.
    Cheers

  • PP scenario to complete the production order without GR and No stock update

    Hi Experts,
    I have a very typical PP scenario here. Let me explain,
    I want to create a production order (CO01) add operations to it and do the confirmation. As set, the cost will get updated against the production order. This is perfect.
    Now the trick is, i actually DONT want to update the stock of the material. That is, the goods reciept should not happen. But at the same time, I need to have the count of how much is delivered in the production order.
    I was thinking of having new movement type created (that would statiscally do the goods reciept without updating the actual stock of the material). Would this suffice, or do you guys have any other way of getting the count in the production order without having the goods reciept done.
    Thanks for your early reply.
    Beatle

    Dear ,
    If you want to avoid inventory issues as well as cost issue , i think  you can bring the Confirmation -Yeild field as Delevered quianity in a Z-report  .You can also utilise COOIS-Select Confirmation -Standrad Profile -Enter Order Type and Plant Code .Here you can select the change lay out option and bring the  confirm yeild qty  field from Hidden column  to diplay colmn for all these  orders .
    You can use following tabel  for your custom report or utlise coois for the same
    1.AFRU -Confiramtion
    2.GMNGA-Yeild Confirmed
    3.LMNGA-Yeild to confirm .
    Regards
    JH

  • Modifying the production order from VBAP

    Hi Expers
    I need some modification and write a code so how to proceed with the following comments as below
    Modification to processing of Command Orders & Tickets
    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:
    u2022     Inspect each item on the sales order
    u2022     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.
    Regards
    Piroz

    Thread closed

Maybe you are looking for