Prevent entering result recording after the production order closed.

Hi QM Gurus,
I want to prevent entering the result recording (we used inspection point) after the corresponding production order was closed.
Please help.
Cheers,
Sun

hi all,
Enhancement QEEM0015 is only used for individual result, it can not be used for summerized result.
Enhancement QEEM0011 is the right one for my case.
It works before the system valuates the inspectoin characteristics' result for both individual and summerized result.
Thanks all for your help.
Regards,
Sun

Similar Messages

Why does my Elements 12 ask me to enter Program Key after the product has been used and registered

I have had Elememts 12 for several months ... when I bought it ...I downloaded the program and registered it ... now ... every once in a while the program asks me to enter the Key number as if I never registered it ... also sometimes I get a message about my 30 day trial ...

I purchased Elements 12 not the Premier addition .... the disk Elements 12 comes with a trial version of Premier ... I did not install the 30 day trial version .... maybe t is Adobe trying to sell me the Premier addition ... I will pay more attention the next time the message comes up ... after reading some of the posts, I think that is what is happening ... I will have to wait ... someone wrote that they had the same problem and after a while, the message stopped appearing .... as I indicated .... I will look more carefully the next time I see the message...
Thanks again
Date: Tue, 1 Apr 2014 16:22:01 -0700
From: [email protected]
To: [email protected]
Subject: Why does my Elements 12 ask me to enter Program Key after the product has been used and registered
    Re: Why does my Elements 12 ask me to enter Program Key after the product has been used and registered
    created by A.T. Romano in Premiere Elements - View the full discussion
JEROMESTEINER
I am trying to get through all your recent replies to go back to your post numbered 8.
1. Go to Control Panel/Programs and determine if you have Premiere Elements 12 and Photoshop Elements 12 installed.
2. When you have gotten the try out dialog, what program is mentioned in the dialogs - Premiere Elements 12 or Photoshop Elements 12?
3. The fundamental question is what did you purchase
a Photoshop Elements 12
b. Premiere Elements 12
c. Photoshop Elements 12 and Premiere Elements 12
From what you wrote it sounds like Photoshop Elements 12. Premiere Elements 12 seems to have come along as a tryout.
4. If Premiere Elements 12 is a tryout, after 30 days from first install of it, you should not be able to use it without a purchased serial number specific for Premiere Elements 12.
5. If you have no interest in Premiere Elements 12 tryout, uninstall it if it is installed. If it is not installed, then it is not the cause of your trial messages. But, I offer you this thought. Are these really License This Product/Continue Trial messages or are they really promotional dialogs (ads) put on your computer by Adobe who knows you have Photoshop Elements 12 and are trying to get you interested in Premiere Elements as well?
Please review and consider.
Thanks.
ATR
Add On...All my encountered with tryout pop ups have been as described and restricted to purchase Photoshop Elements 12 and Premiere Elements 12 purchased as bundle.
     Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/6262855#6262855
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/6262855#6262855
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/6262855#6262855. In the Actions box on the right, click the Stop Email Notifications link.
           Start a new discussion in Premiere Elements at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

Upgrade the production order after the save.

Dear Gurus,
i need of modify the production order quickly after the save.
Can you help me?
I must run the Bacht input custom for upgrade the order.
How i can run the Bach input quickly after the save order?
There are the others method for my problem?
Thanks a lot for your help.
PP Team
Daniele Pistilli

Hi,
Not sure what you're trying to update as you're post is not quite clear.
Anyways you can use the user exit - ppco007 or badi - WORKORDER_UPDATE method AT_SAVE. These enhancements are called at the time of saving the production order, so you can do your custom programming in them, take the help of your abaper.
Regards,
Vivek

How to settle the production order variance to 3 GL account

dear all
i met a problem in the project ,the customer need see the production order variance category detail for (material,routine,overhead variance) in FI report ,so it need to settle the variance to at least 3 GL account
i don't know how to configure it ,i try to use result analyse like wip ,but go failed
do you have some suggestion
thank you

Hi ,
Through Standard SAP .. the same it not possible . Standard SAP will post the differences to one GL account ..The variance amount is not segregated..
The way out is to use report KKO0 .( Product Costing Drill Down Reports ) in CO . There are many reports available .. and you can compute the difference in CO Reports and manually make an entry in FI by manually reversing the original variance account and posting it to cost component wise variance accounts ..
To use the KKO0 report.. please perform the following tasks :-
1. Assign cost component structure in transaction OKN0 ( Date Extraction/Product Drill Down) tab.
2. Product Group Type = Material group..
3. Run KKRV after period end every month to collect the data for drill down reporting..
Please revert back for any further clarifications
Regards
Sarada
Sarada

Priority field in the production order

Hi folks,
i want to use the priority field in the production order header screen.
when i read the help text. i saw that the information can be passed from the sales order for an assembly order.
so
where shoul i enter a value for this priority field in the sales order,
my order type is PP04 so its an assembly order,
so my question is where should i enter a particular value for the priority field in the sales order
so that it gets passed down to production order,

Hi Deepu
The delivery priority is coppied to production order.
you can define delivery priorites according to the need.
During sales order processing, the system proposes the delivery priority from either
1 - The customer master record, or
2 - The customer-material info record.
If both records exist, the system proposes the delivery priority from the customer-material info record. You can change the proposed value for each item.
hope this is clear.
Regards
Mahesh

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.

GR for create the production order without material(co07)

Hi all,
I am creating the production order without material (T-Code :co07), After creating this order i want to get the Material from W/H and after dismantling how to do GR for this Prod.order, What is the Movement type to be used?Please advice me

Dear Kumar,
CO07 specially meant for Rework order (Production order
without material) or for dismantalling the Customer returns or
Inhouse rejected,for the components which re good to reuse
again,their quantity will be entered in -ve and so 531 movement
takes place.
On the other hand,if you want to use for rework purpose and
want to consume some components,using MB1A T code ,the
materials required are issued.
Already our Forum member(Krishnamohan) has given clearly in his first reply.
Regards
Mangalraj.S

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

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.

Open TRs not getting deleted after TECO production order

Hi,
We're having an issue. We're using WMPP interface to supply the production line for the production orders. The auto TRs are generated when the production orders are released.
After TECO the production orders, the open TRs are not getting deleted automatically.
Could anyone know if these TRs get deleted automatically when we do the TECO production order?
If yes, do we have any restriction or condition based on this, the TRs get deleted?
Please explain.
Thank you.
with regards,
Muthu.

Hi Abhijit,
Thank you for your reply. It does not help me.
The auto TR creation is happening now as required. No issue on this.
When you do the TECO, it also cancels the TRs. I tested this also.
There're some scenario this open TRs cancellation is not happening. I do not know when these open TRs are not cancelled. If you know answer for this, please let me know.
Thank you for your help and time.
with regards,
Muthu.

Open the reservation for the Production order

Hi,
I have post the GI for Production order MB1A with movement type 261 from 100 peaces components. I would like to cancel a partial quantity of components from this posting (about 30 peaces). After cancel it the reservation for the production order has to be open for 30 peaces of components.
I've canceled it through MB1A and mtype 262 but the reservations weren't open and in the PO (component overview there is always the sign"the Final Issue for This Reservation").
Which T.code and mtype could I use.
Thanks
Dede

Hi,
Have you cancelled the movement (of 30 pieces) by selecting the "with reference" option from the menu?
If not, then reverse the current cancellation document. Then again cancel the 261 movemtn by selecting the with refernce button from the menu. It will sove the problem.
Check & revert.
Regards,
Rohit.

How to delete the production order in mass?

Dear Experts
Please tell me how to delete the old production orders?

Raja,
CO78 is a one stop transaction for production order setting deletion flag, deletion indicator, archiving and finally deleting.
Generally we schedule the following programs in background in the sequence below,
1. PPARCHP1 for Setting Deletion Flag
2. PPARCHP1 for Setting Deletion Indicator (Once set cannot be revoked- so care should be taken in selection of orders)
3. PPARCHA1 for archiving the production order with Deletion Indicator active. Basis should set the database/storage space for archiving/storing the records.
4. PPARCHD1 for Deleting the records from SAP database.
Regards,
Prasobh

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

Change of planning plant in the production Order

Dear Sapians
Please suggest me how we can change the planning plant in the production order once it is saved and confirmed before taking goods receipt.
Thanks
GVRR

Hi Prasanna,
1. Order is with material
2. This order is created independently
3. yes there are dependent requirements
Scenario is we have created Production orders with X plant. Later after confirmation and before GRN planning plant is changed as per the business decission. Now client wants to receive the goods in new planning plant.
I want to know, How can business area and functional area help us to receive the goods in changed planning plant scenario. can we maintain the plant values in this fields.
Regards
GVRR

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

Prevent entering result recording after the production order closed.

Similar Messages

Maybe you are looking for