MRP background job - on hold - ARFC

hi
Off late, the MRP background job scheduled weekly is taking a very long time. more than 4 hours and when i check the status in SM50, it shows the job shows status  ON HOLD and reason as ARFC.
In SM66 , i can see the job is STOPPED.  
But after a long interval it gets running and the job gets completed after several hours.
Can anyone please help me on this. 
Thanks and Regards
Joe

Hi Joe,
Since this job is a weekly job. It's might be the case that the job is processing lot of data. Can you check the job logs in the SM37, exactly what is the error message you are getting.
The probable solution can be restricting the selection to finish the job in very less time.
Rgds,
Ashish

Similar Messages

  • Background job - on hold

    Hi
    Can I put a background job 'on hold' ? how ? A particular job is utilizing more work processes.
    Thanks
    Rajesh.

    Hi,
    If the job is running, you can not really "pauze" it...if you have access you could "debug" its like pushing the  pauze...
    A job normally only takes 1  process, but it could be using dialogs also ...  So i really need to know a bit more about the problem before I can give more advice.;
    Rgds
    Nico

  • MRP background job generating Plnd Ord instead of Pur Req

    Hi Gurus,
    There is a variant created for background job of MRP, which is running once in a day. In this varaint, I have control parameters set in such a way in that , it should create purchase requisition ( Purchase requisitions in opening period = 3 ) . But its creating planned order only.
    When I am running in foreground, it is generating Pur Req as expected but not generating Pur Req when running in background.
    Please help me creating purchase requisitions instead of planned order.
    Regards,
    Om
    Edited by: Om.P.Singh on Nov 24, 2011 5:12 PM

    Dear Om.P.Singh,
    As per your settings (Setting value 3  for Create Purchase Req paremeter) it will create only planned orders for the externally
    procured items.
    If you have set the value as 1 then it creates only purchase req's for all the externally procured materials.
    If you have set the value as 2,then it creates PR in the opening period(mentioned in the scheduling margin key) and planned
    orders for the remaining period.
    This parameter setting works only for the externally procured items.
    Check and revert back.
    Regards
    Mangalraj.S

  • Background job is in on hold

    Dear sir,
    i am facing problem in background job.
    we have scheduled MRP run in background.
    Background job is in "on Hold " and status "ARFC". The job is running in "Active" mode for 11 hours.
    please give me the  suggestions with your  experience
    regards
    Ramesh

    Hi,
    Refer this
    Background work process On-hold
    Regards,
    Ravi

  • Background job delay due to  'ARFC' jobs running continously

    Dear all,
               As we are facing problem that,there is job starting with the 'ARFC'(example: ARFC:AC1F0C0D386B463CA88E8D10)  which runs with all the users in the system.Thus the other background jobs even the sys monitoring jobs also goes for the delay for the longer time.This is happening from past 10 days.I m  unable to trace what has got change in the system due to which ,I m facing this issue.I had checked in the job logs also, in which i didnt got any help.In that it is only mentioned owner of the job.Pls check this at the high priority as it is affecting my normal background jobs.
    Thanks in advance.
    Regards,
    Akif

    Hi akif,
    jobs which are stuck at ARFC mode needs to trigger other event controlled jobs. since they are updating the Database, unless those jobs trigger this job cannot run forward so try to find what kind of jobs from the user who scheduled the job and then take the action if the jobs are related to support packages and releasing of change request then try to schedule RDD* jobs under user DDIC in 000 client
    this is not due to instance consistency
    regards,
    kanthi

  • How to terminate background job for MRP

    Hi dudes,
    how to terminate background job set earlier and i want start again with fresh scheduling. as user discontinued using the MRP process.
    thanks inadvance for quick response.
    Robert.

    Robert,
    Just though of sharing the alternate way to do this work, instead of DELETE use CHANGE option.
    1. Execute transaction SM37 for the program "RMMRP000" and Job name what you have specified with job status "Scheduled" check box activated. Job Overivew screen appears
    2. Now select the job in the Job Overivew screen and use Menu bar: Job--->Change or Ctrl+F11. Change Job Screen appears
    3. In the change Job screen Hit the function button Start Condition (Green Flag). Start time screen appears.
    4. In the Start time screen define your Job schedule and save the time parameters and save change job screen. Now your job is scheduled with new parameters what you have entered.
    Regards,
    Prasobh

  • Error in MRP Run- Background Job.

    Hi PP Gurus,
    I defined scope of planning for two plants and defined counter too. And set background job through Transaction code MDBT taking 24Hrs as Schedule selection parameter.
    When I'm accessing MDBT after 24Hrs system is throwing following messages in Scheduling log:
    1. Please check the destination for Parallel MRP (message no. MD251)
    Diagnosis of Message:
    No destination have been entered in Customizing or none of the destinations (application server) entered are active. In Customizing for MRP, you define the logical destinations (servers) to be used for parallel processing.
    2. Job cancelled after system exception ERROR_MESSAGE (Message no. 00564)
    Though I tried to enter to Customization through Message no. 1 but system is not allowing for it.
    What could be the problem. No help is available through any OSS note also.
    Please suggest the required solution in terms of Configuration or any other changes?
    Thanks & Regards,
    Abu Arbab

    Hi,
    Two more queries:
    1. If I don't want to go for Parallel Processing MRP, I don't have to select 'Parallel Processing' in Transaction code MDBT variant. But when I'm trying to change it system is not allowing me. It's not allowing me to go further without selection of it. What could be the reason behind it? Either Customization problem or any other?
    2. If set 'Parallel Processing destination' through Customization, system is giving only Development server as available destination and also Customization Request is getting generated. But the request is going to be transported to Production server. Since Parallel Processing destination was selected 'Development server' earlier and now MRP will run on 'Production server', it has to be changed to 'Production server'. But as already mentioned Customization Request will be getting generated and further it is freeze for Customization. How could get rid of these issues?
    Please come back with prompt comments.
    Thanks & Regards,
    Abu Arbab

  • Background Job Processing Spool Retention period

    Hi ,
    In my program i am calling another ABAP program and sumitting the same as a background job(using Job_Submit,Close etc.)
    In this case i can view the Spool generated by the called program(using sm37).
    But this spool exists for a very less period in the system.Is it possible to specify a retention period,as 90 days in my case.?
    Pls Help !!!
    Answers will be rewarded.
    Regards,
    Rohan

    hi Roahn,
    You must set print parameters before the printing process starts.
    When printing lists after creating them, the system uses the print format specified in the print parameters to split the completed list and fit it onto the print pages, truncating it if necessary.
    When printing lists while creating them, the system uses the print format to actually format the list in the program.
    Print parameters are set either interactively by the user or from within the program.
    For each print process, the spool system needs a complete and consistent set of print parameters. In ABAP, the structure PRI_PARAMS (ABAP Dictionary) represent a set of print parameters.
    When passing the print parameters interactively, the system displays a dialog box after starting the report, on which the user has to enter the most important print parameters.
    It's shown below which input field of the Print List Output dialog window conform to which PRI_PARAMS component.
    Input field----
    Retention period
    Component-------PEXPI
    Meaning----
    Number of days for which the system holds the spool request before deleting it. (Default value: 8).

  • MDVP only working as background job

    Hello,
    I was working on the ATP check when i discovered the only way to actually perform this check correctly was to execute it as a background job. When executing online, the stock is just not committed (even with full confirmation logic set on in the MRP group).
    It only works fine from the planned order.
    Isn't it possible to run MDVP online ??
    Any enlightements on this topic appreciated.
    Olivier

    Hi,
    You can run the availability check in background with program RLD05000. You have to create variant and schedule this program in batch from SM36 transaction, Out out you can check in spool.
    If helps rewards your points.
    Regards
    TAJUDDIN

  • Background job executed as SAP*, need advice to change owner.

    Hi all,
    I'm facing an issue where my SAP background job currently has 2 job "SAP_CCMS_CPH_REORG" and "SAP_CCMS_CPH_HRCOLL" under the ownership of sap. I would like to move them away from SAP ID.
    I have tried to recreate the job using sm36 (and using my ID with sap_all profile) in testing environment, but it not seem to work.
    Highly appreciates any advices and/or pointers with regards to the above mention question.
    Thank you.

    Hi all,
    Thank you for the reply but I have forgotten to add a few updates.
    The issue is that I can change owner from SAP* to my ID with sap_all profile.
    But, after execution,
    Job with sap* owner ended successfully, with spool status marked as completed.
    whereas
    Job with my ID as owner ended successfully, but spool status marked as "waiting"
    error mesage:
    Description          Value
    Status:              Frontend unavailable
    Last event:
    Message:             Request on hold
    Date:                19.02.2009
    Time:                11:57:28
    Job status:          On hold
    Error class:         Delayed
    Area:                Data transfer
    Printout:            Not printed
    Apologies for the inconveniences caused.

  • Background job issue

    The background job - SAP_COLLECTOR_FOR_NONE_R3_STAT is taking too long to complete.
    It is stuck with -
    Reason - RFC  
    Status - On-hold
    Double clicking on the work process I see this -
    Waiting f.
    Gateway A92SV093XI034
    Report / Spool action
    CL_SLD_ACCESSOR===============CP
    On the SAP system of server A92SV093XI034, rdisp/max_gateways = 500 and the SLD is running fine.
    So, could you please tell me the cause of the work process being stuck?

    Jobs been running for last 2 days, so no errors.
    I cancelled the jobs now.
    Also, I checked the SAPSLDAPI RFC and it is not connecting to the SLD.
    So, mostly a problem with SLD connection.
    I checked everything as per the Link -
    http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm
    Just can't figure out what's wrong

  • MDVP only working as a background job

    Hello,
    I was working on the ATP check when i discovered the only way to actually perform this check correctly was to execute it as a background job. When executing online, the stock is just not committed (even with full confirmation logic set on in the MRP group).
    It only works fine from the planned order.
    Isn't it possible to run MDVP online ??
    Any enlightements on this topic appreciated.
    Olivier

    Hi,
    You can run the availability check in background with program RLD05000. You have to create variant and schedule this program in batch from SM36 transaction, Out out you can check in spool.
    If helps rewards your points.
    Regards
    TAJUDDIN

  • BackGround Job's Spool Request is having "Waiting" "Frontend unavailable"

    Hello Friends,
    I am facing one problem related to Spool Request, which is generated through Scheduled Background Jobs (scheduled by funcional people).
    The Background Job is having status "completed" when analyzing it. But, its associated Spool Request is showing "waiting" Status, with "Frontend unavailable" as Status Text.
    Here is the brief status of that Spool Request.
    28448     1      300 USER1 00:00 LP01 X_65_80      Frontend unavailable
    in Detail:
    Description          Value
    Status:              Frontend unavailable
    Last event:
    Message:             Request on hold
    Date:                01.07.2009
    Time:                00:00:27
    Job status:          On hold
    Error class:         Delayed
    Area:                Data transfer
    Printout:            Not printed
    The Setting of LP01 O/Device is as followed:
    Output Device        LP01
    Device Type        SWIN SWIN  : Windows printing via SAPlpd
    Device Class      Standard Printer
    Host Spool Access Method       F F: Printing on Front End Computer
    Host printer                     __DEFAULT
    Moreover, the SAP User USER1 is allocated LP01 as Output Device with "Output Immediately" & "Delete After Output" checked status.
    Some Background Jobs are showing the same status for this LP01.
    I have a doubt on allocated O/P Device LP01.
    Any Clue for this issue ?
    Regards,
    Bhavik G. Shroff

    Hello Markus,
    Here , in our Landscape , there is not Print Server. All are taking prints through, Networked Printer and their local connected Printers.
    Can i configure "send to SAP Spooler for now" instead of "Print Immediately "in the Print Specification of those Background Jobs ?
    Moreover, Some Background jobs are sending E-Mails with the processed Reports as an Attachments. They are showing sometime unexpected behavior, in sending emails,  although there is no relation is with this Printing related issue.
    When i am looking into "Overview of Send Orders" of SCOT, some Background Jobs are showing success for sending emails, and some are not showing success, even though All the recipients are same for the scheduled Background Jobs which are running on same time.
    Regards,
    Bhavik G. Shroff

  • MRP Batch job RMMRP000 not woking but MD01 works

    Hi Gurus,
    We have a batch job running nightly for program RMMRP000 (MRP) in the morning when we check it, it does not propose any requirment. But when we run MD01 in the morning. It proposes requirments for materials. Why is this happening? I was told to check if the material is in the planning file and it is.
    What Am i missing.
    Thanks,
    Jograd

    Hi,
    That's okay, I think your background job running is no problem, because there are 64 materials planned. You should double check the other parts' planning file entry, whether they should be taken into account the MRP run? Normally there are the following prerequisitions:
    Material master data changed, e.g. some fields in MRP1, 2, 3 and 4 views;
    BoM or Routing changed;
    The requirements of parts with Higher Low-Level code changed, e.g. sales order, sales scheduling agreement;
    Production plan changed.
    And so on, all data is relevant to MRP. Check your production plan, it's daily plan or weekly plan!
    Regards
    Tao

  • Userexit or BADI for program *RMMRP000* for background job

    Hi,
    We are scheduling background job for MRP through SM36 using program  RMMRP000 or Through Transaction MDBT (MDBT is calling program RMMRP000) which creates PR (through background job).
    I want to default one field in PR (PO Price field in valuation tab in PR default to gross) using any userexit or BADI.
    Can any body suggest me userexit or BADI for program RMMRP000 for background job
    Regards.

    Hi,
    1. The below are the List of  Userexit for this MDBT t.CODE.
    2. But i dont see any one helping to resolve your issue.
    3. May be you should lookg at the Userexit for me21n or relevant Purhcase requisition creation transaction.
    reg
    dsk

Maybe you are looking for