PIR is replenished when the Production order GR is cancelled.

In a Make to Stock scenario(Gross requirements planning - Strategy 11) with Forward/Backward consumption mode , the system adds the PIR qty when the GR from Production order is reversed for some reason , is there way to prevent this from happening. If the answer is "no" what is the best practice to delete these unwanted PIR's for ex. manual /t.code MD74. Is there a best practice document existing for this ? Thanks in advance.

, the system adds the PIR qty when the GR from Production order is reversed for some reason
this is the behavior of strategy 11
In MD62 - change the qty manually or remove the active tick ( this will remove the requirement from MRP)

Similar Messages

FOR MTO & MTS scenario when the Production order shows the Sysy status DLV?

Hi ALL,
In the MTO & MTS scenario when the Production order system status become DLV ?
Regards
Satish

Hi Satish,
For both the planning strategies (MTO/MTS)..
The status of the production order becomes DLV ,
when you do GR for the order with 101 movement type.
(OR)
At the time of final confirmation if automatic goods receipt is activated.
Regards,
Anil

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

Error KO115 when closing production order

Hi all,
when I close the production order, I get the error message:
Balance of ORD 3331403 is not zero
Message no. KO115
The cost balance for this order is 3000 USD.
We are doing a monthly settlement.
When the production order has status NOT TECO and NOT DEL, the KKAX shows 500 USD and the KKS2 shows 0 USD.
When the production order has status DLV, KKAX and KKS2 both show 0 USD.
COFC and COGI are empty.
How can we close the order?
Thanks
Anne

Dear Anne,
check in KKBC_ORD, whether order is carrying any cost or not
if it is showing balance then you cannot close
first calculate, overheads, WIP, Variance, then settlement of order
Then check the result
Regards
Madhu

How to stop the prodution order creating when the product is not valued?

Hi guyes:
How to stop the prodution order creating when the product is not valued using CO01?
I hope that when i create the production order,the system will check the product is valued or not,if not
the system will show an error or warning message!
How to config for this?
Thank you!

Dear Zhao Gang,
Check with this user Exits mentioned in this link,
Prevent Production Order from "Release" if there is no Cost Estimate
Re: User Exit at Production Order Release
Check and revert back.
Regards
Mangalraj.S

Want to select the Order type automatically when creating production order

Hi Gurus,
Please help to select the order type automatically while creting the production order..??
Please what configuration settings are avialble to make this happen to me.
THank you in advance.
Naveen.

Naveen,
First priority is the order type defined in the Production schedulling profile(OPKP), assigned to that particular material in workscheduling view. If this is not maintained then,
Second priority is configuration at MRP Group parameters in transaction in OPPR, this MRP Group if assingned to Material master MRP1 view.
Third priority is Configuration at Plant level parameters in transaction OPPQ, this defines the order type when convert planned order to Production/Process order.
Regards,
Prasobh
Edited by: Prasobh Karunakaran on May 28, 2009 8:49 PM..added MRP group paramters also

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

Reverse the production order even when some quantity has been invoiced

Dear Sapgurus,
How to reverse the production order when the some quantity of that production order has been sent through invoice.
regards
muralidhar.t

Dear,
In that case you can not reverse the the full order quantity you can only reverse the quantity which are in unrestricted storage loaction as a stock.
You can cancle it through MB31 with 102 movement. If auto GR is there then you need to cancle it through CO13. After that also check the COGI and CO1P.
Hope clear to you.
Regards,
R.Brahmankar

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.

Sales Order Schedule line not populating in the Production order

Queation: Is there a way to tell the system to look at the sales order, line item AND schedule line. It is displayed in MD04 but it doesn't carry over to the Production Order. We are a MTO and this information is relevant in a number of ways.
Please Help.

Vickie,
If you are using MTO scenario then when you run the MRP for the material, it will create a planned order for that sales order based on the dates calculated from the sales order schedule line (Shipping tab)...
So now when you convert the planned order to production order, all the sales order details will get copied.
try and revert back.
Swapnil

Field "GR Non-valuated" in tab "Goods receipt" of the production order

Hi,
When creating a production order, the field "GR Non-valuated" in tab "Goods receipt" is checked by default, due to my assessment customizing.
This field indicates to the system that it should not create any accounting document, whereas I would like to create one. Does anyone know how to withdraw this automatically check?
FYI, I do not use COPA and the very basic of CO-PC and I would like to create automatically a default assessment rule (cost center).
Thanks for your help.
Ronan

Hi,
please note that this is not an MM, but a PP-SCF related issue. It does not belong to the forum ERP MM.
The indicator AFPOD-WEUNB is set automatically as soon
as you do not settle your production order to category 'MAT' (see
settlement rule). If the order is not settled to a material, then the
Goods Receipt will not be valuated and the flag G/R Non-valuated (WEUNB)
is set. Only when you settle to a Material is the G/R Non-valuated not
set, and you will receive FI postings in the case of such a movement.
This is standard system behaviour.
Please review the following notes relating to settlement rules: 518496,
400400.
To make sure that the GR-Nonvaluated flag is not set in the
production order, field KZBWS must already be filled with 'M' in the
customer requirement. For that, please set the field KZBWS='M' for the
requirement class that is used (see 'General Customizing' in note
459734). PLAF-KZBWS (indicator:valuation of special stock).
Regards,
Edit

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

Doubt about the settlement rule of the Production ORder

The only default distribution rule allowed for a PP order is PP1 or PP2. We would need to change that to allow settlement to multiple receivers as a default. If that is the case, we may want to look into a user exit to update the settlement rule during production order creation instead so that the G/L account is correct from the beginning.
Currently when we create the production order, the settlement rule will default the below, I am not sure if a user exit is able to maintain the Source as 200 (Materials)?
If yes, we can then add the second rule for Source 100 (Labor and Mfg) via the user exit as well.
In this case, SAP will not prompt us error of settlement with 200%, as they are from difference Sources.
now anybody can explain me about the User EXit we have to correct this

any help on this.. please its very urgent
thanks in advance

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

Report based on Serial Number generated in the Production Order

Hi,
I wish to generate a Customized report, which shall include the total consumption based on Sales Order/Line Item/Serial Number/Production Order matching the Serial Number generated in the Production Order where in we can get the required data.
Need your help and suggestions in creating this report..
Thanks in advance..
Ashok Vardhan
Edited by: Ashok T Vardhan on Jan 19, 2012 11:38 AM

Hello Tman,
This is a slightly tricky question. The reason being, the report options like the report path etc, are set before you see the serial number prompt when you run your UUT. There might be other ways of getting around this, but a quick solution would be modifying the process model.
I modified the PreUUT callback to set the report options. I passed the reportOptions as a parameter to this sequence. In the PreUUT sequence, I set the following fields:
Parameters.ReportOptions.GeneratePath=False
Parameters.ReportOptions.ReportFilePath= "c:\\"+ Locals.SerialNumber +"\\report.xml"
I hope this would give you an idea.
SijinK

PIR is replenished when the Production order GR is cancelled.

Similar Messages

Maybe you are looking for