Exit at the Production order release

Hi every one,
    Can you please help me in finding the user exit for either CO01 or CO02 when a Production Order is released.
I.e, when a production order is changed or created and once it is released, i want the exit at that point. i want to trigger some code once the order is released.
Thanks
Rich

Hi,
ppco0007- Exit when saving production order
ppco0012 - Prod order display/change order header data
ppco0005 - Storage location/backflushing when order is created
In transaction smod, in enhancement field type a name & then press f4. In the pop up screen enter the package as co,keep the exit name field as "blank" & press enter.All the relevant exits will be displayed.
Regards,
Senthilkumar

Similar Messages

  • User exit for Production Order release

    Hi Experts,
    Any User eixt for Prouction Order Mass processing.
    Before releasing the production order i have to do some checks. Can you please provide right user exit. More reward points with best solutions.
    Thanks
    Cris

    Hi,
              check the following userexits and BADI's for Production Order
    Enhancement/ Business Add-in Description
    Enhancement
    PPCO0010 Enhancement in make-to-order production - Unit of measure
    PPCO0012 Production Order: Display/Change Order Header Data
    PPCO0013 Change priorities of selection crit. for batch determinati
    PPCO0015 Additional check for document links from BOMs
    PPCO0016 Additional check for document links from master data
    PPCO0017 Additional check for online processing of document links
    PPCO0018 Check for changes to production order header
    PPCO0019 Checks for changes to order operations
    PPCO0021 Release Control for Automatic Batch Determination
    PPCO0022 Determination of Production Memo
    PPCO0023 Checks Changes to Order Components
    STATTEXT Modification exit for formatting status text lines
    PPCO0009 Enhancement in goods movements for prod. process order
    CCOWB001 Customer exit for modifying menu entries
    COIB0001 Customer Exit for As-Built Assignment Tool
    COZF0001 Change purchase req. for externally processed operation
    COZF0002 Change purchase req. for externally procured component
    PPCO0001 Application development: PP orders
    PPCO0002 Check exit for setting delete mark / deletion indicator
    PPCO0003 Check exit for order changes from sales order
    PPCO0004 Sort and processing exit: Mass processing orders
    PPCO0005 Storage location/backflushing when order is created
    PPCO0006 Enhancement to specify defaults for fields in order header
    PPCO0007 Exit when saving production order
    PPCO0008 Enhancement in the adding and changing of components
    Business Add-in
    AFABD_CHANGE Change Relationship
    CAUFVD_CHANGE BAdI: Overall Network Scheduling with Selection
    PPPI_SEL_ORD_EXT_REL
    SIDAT_UPDATE Change date of price simulation
    Regards

  • 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

  • Problem while releasing the production order.

    Hai gurus,
    When i release the production order , SAP doesn't block when i have a deficit of stock for some materails.I checked all the customizing and found every thing is fine.
    As the materials that has defict stock has back flush indicator, is that the reason why the system is assuming the stock when releasing.

    Hi,
    You need to consider the following customization settings
    (1) OPJK - For the Plant/Order type/Availability check-2 for the material availability - Release material - set the indicator '3' No release if parts are missing
    (2) OPJJ - For availability check & checking rule - check what all elements are considered as part of ATP check.
    With these settings - in the production order if the order header has status MSPT - Missing parts (i.e. components are missing) only then system will stop the release of the order.
    I hope this addresses your query
    Warm regards,
    Umesh

  • Error when release the production order

    Hi all,
    while release the production order i am getting the error :-   Plant 1000 is not the only plant assigned to valuation area 1000 , how to resolve this error .
    & can we release the prod order without calculating the cost ?
    Thanks & regards
    satish

    Hello,
    I'm facing the same issue when trying to create a production order using tran. CO01 with inputs (Material:  P-100, Production plant: 1000, Order type: PP01. Next the total quatity of material is chosen freely, Dates/start is set to todays date, Scheduling is set to Forwards scheduling).
    Error message :
    "Plant 1000 is not the only plant assigned to valuation area 1000"
    Message no. CK238
    As explanation SAP says:
    "Diagnosis
    You are attempting to use material costing or order costing. However, the system has determined that plant 1000 is not the only plant assigned to valuation area 1000.
    Costing is only possible when each plant has its own valuation area to which no other plants are assigned.
    System Response
    It is not possible to cost in your system.
    Procedure for System Administration
    Go into Customizing for the Corporate Structure and check the valuation level. The valuation level must be the plant level"
    The error message implies that the user is not given the opportunity to create and save a production order.
    I have secured the followings:
    1. Valuation level is set to Plant level so that the valuation is now done at plant level. (The other option was at Company code level, which is not checked.)
    Question:
    Is there a solution to this problem?
    Thanks and Regards!
    Edited by: WilliamG on Feb 16, 2010 4:04 PM

  • Sap pp-releasing the production order?

    at are the activities carried out while releasing the production order?

    Hi,
    Order Release
    Use
    A production order must be released, before it can be processed. You can use the time period between creating and releasing a production order, for example, to carry out company checks and preparations. If you do not require this time period, you can automatically release the production order when it is created (see Automatic Release).
    A newly created production order initially receives the status CRTD (created). The following restrictions apply to a production order that has been created:
    Confirmations for the order cannot yet be executed.
    Shop floor papers cannot be printed.
    Goods movements for the order cannot yet be executed.
    Releasing the order lifts these restrictions.
    Features
    Order release can be executed at the following levels:
    With Release at Order Header Level all operations are released. The order and the operations receive the status REL (released).
    With Release of an Operation the operation receives the status REL and the order receives the status PREL (partially released). If all operations in an order have been released, the order has the status REL.
    Hope this helps.
    Revert if you need more information.
    Regards,
    Tejas

  • Production order released blocking the batch created

    Hello Guru,
    I have some question to ask, in production order, when we change the order via CO02, released it (production order create:classification) for batch will appear. after completing this the order "released carried out" will be the message. and when we save the order CHANGE BATCH view will display then, the production date and shelf life expiration date was automatically populated by SAP. my question is is there a possiblity that this CHANGE BATCH when will appear the production date and shelf life expiration date was unchangeble already SAP proposed date was fixed (gray-out) or instead change batch display batch will appear? is there any set-up to make this feasible?
    we want to block the production date/shelf life expiration date in modification once SAP has already computed and proposed this date for the batch on the FG material of the production order. Please help. I know this is a standard behavior, but can this be feasible?
    Any help or inputs.
    Thanks
    Edited by: Agent X44 on Mar 11, 2009 11:50 AM
    Edited by: Agent X44 on Mar 11, 2009 12:10 PM
    Edited by: Agent X44 on Mar 11, 2009 1:15 PM

    You must have to check batch Class and its characteristics. Something wrong here.
    Regards,
    RM

  • User Exit/BADI for Production Order Availability Check

    Hi PP experts,
    Is there any user exit or BADI which can be used for Production Order Availability Check during order creation/release or while running collective availability check (COMAC) to include additional check conditions such as do not commit quantity (commitment qty = 0) if storage location for a component is missing in the production order due to storage location is not maintained/specified for that component in the material master.
    Note: In this case the availability check is set (configured)  to check at the storage location level.

    Dear ,
    Availablity Check is not Plant Specific or Storage Loaction spefic .ATP does not check the stock for any particualar stock in storage loaction rather it cheks various stocks based inward and out ward movement time through PR/PO/Dependent /Planned Order /Stock Type  irrespective of any Storage Location .
    BAPI which can be used :
    1.BAPI_PRODORD_CHECK_MAT_AVAIL
    can we exclude materials of prod order in availability check
    what is availability check concept  how it is used in SAP
    Check the above if it is useful
    Regards
    JH

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

  • Disable certain changes in sales order after production order release

    We are in the MTO scenario and are also using variant configuration. The business requirement is that after a production order has been released (REL status) the preceding sales order item should be “locked” for certain changes. Such changes would include VC and some other fields (e.g. quantity and dates). Some minor changes like texts should still be allowed.
    The best idea we could come up with is to put some validation in the sales order user exits, but there are some disadvantages. It seems kind of strange though that there would be no such functionality in standard SAP (e.g. some changes in the order can’t be made after a delivery has been created). Is there by chance anything in the configuration that we missed?
    I found this old thread, but it still seems to require user exits. Unfortunately couldn't find anything specifically on the production order / SO integration.
    Thank you!

    Hi Jelena,
    Try in the userexit MV45AFZZ
      (form userexit_field_modification)
    Example:
    select * from afpo where kdauf = vbap-vbeln
    and   kdpos = vbap-posnr.        
    if sy-subrc = 0.
    select single * from aufk where aufnr = afpo-aufnr.
    if aufk-loekz = ' '.                                 
    select single * from jest where objnr = aufk-objnr
    and   stat  = 'I0002''   
    and   inact = ' '.
    if sy-subrc = 0.
    screen-input = 0'.
    endif.
    endif
    endif.
    endselect.
    .H.Terras

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

  • Confirmation of the production order qty equal to sales order qty

    Hi Experts,
    I need to control the confirmation of the production order should be equal to sales order qty.
    I'm having the scenario as follows
    If sale order qty for X material = 3
    while running the MRP, system will plan the order qty as 8 because of we maintained rounding profile in the Material master and enhancement we used for this.
    Rounding Profile Qty=5
    Total Production Order Qty=8.
    But, finally they will do the GRN for sales order qty only, remaining will be used for testing purpose.
    So, the confirmation also has to happen for only sales order qty. There, we need to control the qty based on the sales order.
    Is there any exit or Enhancement is available for this.
    Please help me.
    Naren

    Hi,
    Exit for confirmation check is CONFPP04.
    However, opening orders for quantities higher than demand and leaving pieces undelivered and unconfirmed in production orders does not make sense. I could not get the requirement of incresing production quantity by adding rounding value? Moreover, if rounding is to be used for test purposes, why not do you receive them into stock? Why don't you receive 8 pieces into stock, deliver 3 pieces to sales order and transfer 5 pieces to related department?
    If it is because of MRP and you really do not want to produce extra 5 piece immediately, you may use material reservation or any other form of demand for 5 pieces, use EX for lot size calculation and have MRP create two planned orders for sales order and testing requirement, then you can convert planned order for sales order requirement into production order and continue processing.
    Regards.

  • Serial number error while creating the production order

    Hello frds,
    I am getting the following error while creating the production order.
    "Item 000000 requires exactly 100 serial numbers for the asset".
    If i give 100 serial numbers in the order, the error is solved. But i do not want to assign 100 serial numbers, i want to assign only 2 numbers.
    I have tried using the new serial number profile also, but it is giving same error.
    Kindly guide.
    Regards,
    Narendra Bora

    Dear Narendra
    Select the serial number profile and go to serialization procedure and set the ser. usage status 02 - Optional as below.
    Procd Procedure description Ser.Usage
    PPRL PP order release 02
    since the serail number creation is optional for order relase this will allow you to relase with out error and with serail number assigned in partial.
    Regards
    Soundar

  • Error While saving the Production Order

    Dear Experts
    Pls let me know why am getting the below error while saving the production order after release..
    PSFC_STD_LAYOUT does not exist
    Message no. SSFCOMPOSER004

    Dear,
    Please check have you assigned the scheduling profile in work scheduling view of materail master?
    Then go to OPKP check the same scheduling profile where you have activited the On realese execute printing remove this tick mark and then try with new order.
    Or you can do the configuration in Tocde :OPK8 here assign the PSFC_STD_LAYOUT in forum.
    Regards,
    R.Brahmankar

  • 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

Maybe you are looking for