Problem in deadline monitoring of batches

Dear experts,
Deadline monitoring of batches (transaction QA07) is not working. I tried running this but it did not post stock of a batch whou2019s expiry date was in next 2 days in blocked stock. I had specified the material no, plant, initial run in days (the one that is underu201D batch status change when expiration date is reachedu201D) and also flagged the checkbox for u201CBlock batchu201D. All other fields were left empty. Also QM module is not active. The message was u201CNo entries foundu201D , I confirmed the batch details with u201CMSC2Nu201D , it was in next 2 days and the same is reflected in report u201CMB5Mu201D too.
Please let me know whether QM is required to be active for execution of QA07 or there is some other problem.
thanks in advance

Ok... I'm still confused. Why can't you run the standard deadline mointoring program?
I believe you still need to activate the 09 inspection type but this can be done in mass using QA08.  Since your not using inspection intervals, don't maintain the inspection interval field in the QM view.
No config needs to be done, the standard as delivered config in QM should work.
Run the deadline mointoring program (QA07?) but only fill in data in the bottom half for blocking expired batches.
Set the program up to to run nightly with whatever 'window' you desire, i..e block those that expire in 1 day, or 5 days, or ten days.
If you are using batch status management, then the batches will be restricted.  If you are not, they will be moved to blocked stock.
Craig

Similar Messages

  • Creat 'recurring inspection' in Deadline monitoring of Batches

    Hi guys,
    Conditions:
    (1) Today is '11.24.2011''.
    (2) MSC3N
    - 'Shelf Life Exp. Date' is '11.30.2011' and 'Next Inspection' is '12.10.2011'.
    (3) QA07
    - 'Initial run in days' is '30' and Check radiobutton at 'To insp.stock at lot creation' in the 'Additional goods movement at time of recurring inspection' box.
    'Initial run in days' is '00' and Check 'Block batch' in the 'Batch status change when expiration date is reached' box.
    i think, in order for the 'Shelf Life Exp. Date' to arrive first, no recurring inspection lot created??
    But, when i am running QA07, the system automatically creates 'recurring inspection'.
    The inspection lot not to make automatically, it will be able to setting??

    Dear,
    The function for recurring inspections allows you to monitor the quality of batches contained in the warehouse stock.
    For this purpose, an inspection date is calculated (in addition to the expiration date) when a batch is received in a goods receipt shipment
    To be able to determine the inspection date, you must enter an inspection interval when you maintain the QM data in the material master record. The inspection interval defines the time period that must expire before the next recurring inspection must be carried out.
    A program that is run periodically (batch job) monitors the batch materials in the warehouse and causes one of the following activities to be carried out when the inspection date is reached or exceeded:
    Inspection lot creation
    Inspection lot creation and batch posting to inspection stock
    Inspection lot creation and changing status of batch to "not released"
    If the expiration date is reached or exceeded for a batch, the batch is blocked. This changes the batch status to "not released" or causes the batch quantity to be posted to blocked stock, if the batch status management function is not active. In this case, an inspection lot is not created.
    When you make a usage decision to accept an inspection lot, the batch quantity is posted to unrestricted-use stock or the batch status is changed to "released," depending on the option you selected.
    The system calculates the next inspection date for the batch and stores it in the batch record.
    Please go through:
    http://help.sap.com/bp_bblibrary/600/Documentation/P18_BB_ConfigGuide_EN_DE.doc
    http://help.sap.com/saphelp_45b/helpdata/en/2d/350e0c448c11d189420000e829fbbd/frameset.htm
    Regards,
    Ram

  • Problem in Deadline monitoring

    Hi i am using deadlien monitoringin my workflow, I need certain trasaction to be called if that has come from  Dealine moniroting, is there any way i can come to know that this has come from deadline moniroting?

    Hello Munish,
    For a transaction to be called when a step has missed the deadline monitoring, you can use the modeled deadline monitoring and then insert a step type, execute a method in which the required transaction is called.
    Hope this will help.
    Regards,
    Sam

  • Deadline monitoring of batches

    Dear Experts,
              In retest inspection even if we have mentioned total shelf life 60 months & retest period a 360 days, system is automatically updating in the batch master any irrelevent shelf life expiry date & retest date.
    Previously this was working fine but since from some days this is happening. And this is happening for any material in random & not for all materials.
          Can anybody suggest any note which is to be applied to the system to correct this problem.
    Thanks & regards
    Milind

    Thanks Radhak MK,
           But there is no any differance in the master data maintained for the faulty material & normal materials. And it is not material specific. But  the same material one batch have correct results & the other batch have faulty results. Is there anything else.
    Regards
    Milind

  • Problem in Deadline monitoring-Requested Start

    Hi All,
    We have custom PR workflow in whcih in the case of rejection we are creating the event for the same workflow using SAP_WAPI_CREATE_EVENT.
    for this create event step we have an activity where in Requested start is activated on "Work item creation" for 3 minutes.
    As a result we are getting 2 workitems genearated for the same PR and same event.
    Examaple: Create event step started at say 10.00.00
    we have one workitem created st 10.00.00 and another
    workitem at 10.06.00.
    In SWWA we have given 5 Minutes.
    I jus wanted to know how this Requested start is expected to behave? And how can i solve this issue?
    if i remove the requested start, does it work properly?

    Raj..
    You are right..but i dont see any harm in using API FM inside the workflow...
    And this has been perfectly working in prod environment for several years..
    In sandbox..they have create some new release groups and for which we are facing issue...
    Between i have a doubt in Background program of deadline :
    In sandbox we hre having like this :
    Name           RSWWDHEX
    Variant        &0000000000001
    Language       EN
    And in job log am getting like this " '2' entries have been edited"
    But in prod we are having like this
    Name           RSWWDHEX
    Variant        &0000000000000
    And in job log am getting like this " '1' entries have been edited"
    So i doubt abt this settings...Can you please check in your Prod environment ane let me know the correct settings.
    Language       EN
    Edited by: Swaminathan PJ on Dec 31, 2009 12:19 PM

  • RQAAAS10 - Deadline monitoring of batches

    Hi, 
    RQAAAS10 program is scheduled in background for weekly.
    The first job run correctly 27.09.2011
    After that all weekly scheduled jobs are cancelled.
    Why ?
    Thanks.

    check SM21
    also
    check very interesting thread
    SAP  Back ground Jobs getting cancel automatically

  • Deadline monitoring batch jobs

    Hi batch jobs for deadline monitoring are getting hanged for few times. Sometimes it works fine.
    I am not getting why it is getting hang out for few times.
    If anybody faced this problem, pls share the possibilities.
    regards,
    Kedar

    Hi,
    Please check parameters of deadline monitoring especially parameter "Interval for call objects".If its very long in future then possible reason is system is trying to generate calls for this long period and it may that job is not completed with time parameters set by basis administrator.And this may resulting into termination of job.
    So try to limit this parameter and also no of maintenace plan if you have a very huge list.Also check with basis person if any such jobs terminated due to very long time they are running
    regds,
    atul

  • Why we use tcode qa07 deadline monitoring batches

    Dear Sir,
    i m new in qm module,can u tell what is deadline monitoring baches,what exactly the use of this tcode-QA07
    There is initial run days enter what the use of  that days.its for transfer there quality stock to unrestricted befor retest date or what.
    pl guide me

    hi
    this is for recurring inspection lot  inspecion type 09
    for ex : if your company is food grade industry having shelf life for every product. for ex one product having 1 month shelf life.
    so if the batch's shelf life exceeded then system would automatically transfer that particulor batch into blocked stock and create inspection lot for that particulor batch. so this setting we have to define in QA07 and that we have schedule this variant so that this should be done back ground in QA05.
    Regards
    Pravin

  • Error in Schedule Background Job for Deadline Monitoring of swu3

    While Auto Customization swu3 i am getting error message 'Output device "" not known' in 'Schedule Background Job for Deadline Monitoring'
    Please advice what could be cause of it

    the earlier problem of background job was solved by changing the  output device assigned to user wf-batch .
    regarding the transport request :
    when i was trying to execute the step : "Schedule bakgrd for missed deadlines " MANUEL it was giving me an option of SAVE AND SCHEDULE . which was creating the transport request . but when i executed it automatically it worked fine without asking a request to me ... i don't know why )-: ... probablly we can specify a different interval then the standard of three minutes and which will be transported (it's just a guess) . i have  executed it  automatically ...
    well thanks all for u r help

  • Possible loop deadline monitoring for a period of time?

    Hi All,
    Here is our scenario.. We have a task sent to the managers inbox with deadline monitoring on it.  If the manager does not action this task, we set this task to obsolete and then we want to send a reminder email every day until the manager performs the required action.
    So the problem.. originally this email was to be a task but the loop would not work with the task as it's waiting on action from the user.  We changed this task to an email and it looped as expected however the only way I could think to put a wait for a period of time before another email is sent is by actually counting down the time in a method.
    However, the problem with this is that wf-batch is locking the worklfow so it can never complete, even if the event to complete the workflow is triggered.  wf-batch has it locked so the workflow can never complete, so it loops infinitely.
    So my question.. is it possible to repeatedly send notifications to a manager at specifically defined time intervals without locking the workflow?
    Below is how the workflow currently looks:
    Any guidance on this would be most gratefully received!
    Thanks in advance,
    Liz.

    Hi Liz
    in your wait step, do not count down the time.
    Instead keep the method as a dummy method with no code.
    In the wait step, use the deadline monitoring - Requested Start - set it to current date + 1 day
    The step will start 1 day after 'today' , execute nothing in Dummy method and then go on to the mail step
    I am sure that the deadline monitoring job is running because "Latest End" of the first task is executed in your system. So the same job will take care of Requested Start of the wait step.
    regards,
    Modak

  • Premiere Pro CS4 - Problem with the monitor program.

    Hi. I'm not able solving problems with the monitor using PremiereProCS4. When I drag a photo (also only one photo) in the timeline and play it in the monitor program, vision in the monitor program doesn't run:black monitor or a little part of the photo appear... sometimes distort colours. Asus P5QPRO, Intel 9550 and Sparkle Nvidia GeForce 9800 GTX+ 1024 DDR3; last gpu driver and directX are installed. Different configuration of stratch disks were tested. Where am I wrong?

    Dear Bill,
    thanks for your answer and your article. I tried with your NTSC 4:3 720x480 PAR 0.9 and, "magically", no more problem!!! I used the script pocedure in Photoshop CS4 to resize my images. Now, before starting my workflow and hoping not to overuse your patience, I would like to indicate you my equipment and my target: I use a Canon Eos 7D (generally for still images, 90% are vertical, and just some videos) and I use Premiere Pro CS4 to burn a dvd (normal, 4.7 Gb or double side, more than 8 Gb) with a 16.9 lcd tv (I'm Italian); my camera save as .jpg and .raw (but why use heavy .raw files if I've to redute to 720x480?!??).
    So, according to your "everyone wants the highest quality that they can obtain when doing theri videos..." and "your video project may vary, so you will need to plug in the dimensions for YOUR video project in that case", I've a question: which is the best for me?
    And then:
    1 - Premiere Pro CS4 havn't a batch or a script procedure for still image like PS (only for videos)!?!
    2 - Premiere does'nt allow you to import images like 4.181 Kb (a too large dimension file error appears)!
    3 - In the timeline of Premiere, after you dragged images, you can select them and right click to perform "resize to frame size": it seems to run good without problem, but what appen to the photo? Which is it's pixel?
    4 - In the general preferences of Premiere you can to optimize rendering for "memory" or not: which is the best for you?
    5 - I attached file with a screen of something strange in Premiere: dragging an image (the first of the project) in the timeline, the timeline appears distort (you can see the part in the yellow square): then, when I render the project and play in the monitor program, it becames normal.
    Thanks!

  • Multiple levels escalation for deadline monitoring

    Hi all,
    We have a business requirement to perform multiple levels escalation in one of the workflow steps. If the approver does not approve the work item(WI) after one day,  a mail notification will be sent to the approver.  A second mail will be sent again if approver still doesn't approve WI after 48 hours.  Then the third/fourth mail will be sent to approver and approver's boss if approver still doesn't approve WI after 72 / 96 hours.  The fifth mail will be sent to approver's boss's boss if WI is not approved still after 5 days.
    I know how to do simple and modeled deadline monitoring in workflow builder. But I don't know whether our business requirement can be achieved in workflow builder( and this is a step in dynamic parallel processing).  Other option I have is to create an ABAP report to go through the table stores workflow run time data and make this report run several times a day in the batch to send mail notification reminder.
    Did anybody have a similar business requirement like ours? What's the best way to handle it - build it in workflow builder or write an ABAP report?
    Thank you in advance,
    Merta

    Hi Merta,
    We had a similar requirement and this is how I achieved it:
    1.  Pleace your approval task into a loop (while not approved) and create a container element as the approval flag.  This allows you to get out of the loop when the item has been correctly actioned.  Also create a DL element to hold your calculated deadline value;
    2.  Create a method and task to determine the next escalation point based on how many loop passes the instance has had, ie:
         Pass 1 - DL = sy-datum + 1 day;
         Pass 2 - DL = DL1 + 1 day, and so on.
    3.  Create a method to determine who should get what.  Link this to a condition so you know whether to send a mail or escalate the entire workitem.  Create the notification as a send mail within the condition;
    4.  Change the Deadline parameters in your step to "Refer.date/tim" = Expression and bind the DL element;
    5.  Set the processing obsolete property to ensure the workitem is killed when a new pass (and therefore and new deadline/agent etc) is started.
    See the following:
    This one handles the loop/obsolete concept.
    http://help.sap.com/saphelp_47x200/helpdata/en/c5/e4b97e453d11d189430000e829fbbd/frameset.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/bc/ecdd5ad24e11d2b494006094b9ea0d/frameset.htm
    Regards
    Gareth

  • Deadline monitoring/Escalation - Purchase Requisition Workflow WS20000077

    Dear Friends,
    I have read some stuff on SDN but still couldnt figure out the soultion.
    Its a common problem. We have set a release strategy in Purchase Requisition and are using std workflow WS20000077.
    Now the requirement is that if an approver doesnt approve in 2 days time then the PR will automatically go to the next approver for release.
    I have set the deadline monitoring using the workflow wizard for model deadline monitoring. With this, The work item gets deleted from the approvers inbox. Next in the obsolete path I have set a process control which specifies the worklow step as the step in which deadline monitoring was specified.
    When I check in SWI1, the work item is set as obsolete but it doesnt go to the next approver for approval.
    Your replies will be highly apprecialted.
    Thanks & Regards,
    Fawaz

    Hi
    For your Requirment :
    "the requirement is that if an approver doesnt approve in 2 days time then the PR will automatically go to the next approver for release."
    Please follow the below steps.in copy of  WS20000077.
    1.For taskTS20000159:Overall release of requisition , go to
    Latest END tab:  put ACtion as :Modeled ,  Refer.date/time:Workitem creation , below time : choses: DAY,  and on left add 2.
    Outcome :Deadline Montoring.
    2.Then come to OUTcomes tab of the same task:  see  there are 3 lines 1.Step executed, 2.Latest end:Deadline Montoring, 3.Processing obsolete:Processing obsolete ,, all are ACTIVE or not , if not, Activate .then  all should be Green.
    4.next in the OUtcome :Deadline Montoring , use a process control step. to Set missed workitem to obsolete,  in Function: chose : set Work item   to Obsolute. and Workflow Step : chose then step no for the above task(TS20000159:Overall release of requisition).
    5.In "Processing obsolete" path, again call the same task TS20000159. in different activity . and see to the agent assignment.
    I think this will slove your problem.
    How it works:
    1st the PR is send in a WI to the perticular agent by the 1st activity . if the agent do not execute for 2 days. then that WI will set to obsolute . and process flow to" Processing obsolete" path, then agian PR is send to the next agent using the same task but activity created in  step 5.
    thanks
    Kakoli.

  • Modeled Deadline monitoring is not working

    In workflow i have used modeled Deadline monitoring  for the task, in modeled branch i put a send mail step
    in that branch that is working fine.  once the deadline is reached that workitem is not disappearing from users inbox and modeled branch is working fine , what could be the problem  please suggest me.

    Hi,
    Refer below link  and fix it
    [Link1|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/303617cf-73dd-2a10-c993-cc6303585176] [Link2|https://wiki.sdn.sap.com/wiki/x/EwEqB] [Link3|https://wiki.sdn.sap.com/wiki/x/fQDDAw].
    Regards,
    Surjith

  • Deadline monitoring is not working

    HI,
    i had requirement to change the text displayed in the decision step type. I copied that task using pftc and changed the description and i replaced the new task number with old one. the deadline monitoring is not working for the new task .
    Please anybody have idea about why deadline is not working for the new task ?
    advance thanks
    regards
    paveee

    Hi Praveen,
    Deadline is failing only for this workflow? Or is it failing completely in the whole system. Just create a small dummy WF with a standard decision step (or some acitvity) with deadline monitoring activated and see if it fails there also.
    <b>If deadline monitoring is failing in all workflows</b>
    Can you just check whether the scheduled report RSWWDHEX are executing properly. You can check it in SM37 for user WF-BATCH. Also check in ST22 if there are any dumps for report RSWWDHEX (for user WF-BATCH).
    <b>If deadline monitoring is not failing in other workflows</b>
    In your activity where you have put your cutom task goto the "Outcomes" tab an check if the outcome for your deadline monitoring is "Active" (This may not change but just have a check)
    Also can you let us know what are the steps that you are using in your modelled outcome? Just suspecting if the first step in your modelled outcome is going to error (which is not displayed in log).
    Thanks,
    Prasath N

Maybe you are looking for