Background Job not running

Hi All,
A background job has been scheduled to run every minute.It was working fine but a few days back it did not get scheduled for 2 hours . Any suggestions as to why this might have happened.
TIA.
Vartika

Hi Manik,
The job started working fine after 2 hours. It was only for 2 hrs that it did not work. How to check if the userid was locked or not during that period.
Thanks
Vartika

Similar Messages

  • Background job not run properly

    Hi,
    When an infopackage is triggred through process chain in BI a background job will be exeuted at R/3 to fetch data from R/3.
    But the bakground job did not execute properly hat is it did not fetch any data but ot finished.
    But when the infopackage is executed manually the background job fetches the data from R/3.
    Why the job is not fetching data when triggered through process chain.
    Please help me to sole this issue.
    Regards,
    Indhu

    Hi Induja,
    In your case, you will have to debug the background job that is activated through BI. Check if proper data is coming from BI.
    You can only debug a background job if it is created under your user id. Thus, to debug the job you first have to own it and then debug by selecting it and either typing 'JDBG' in the command field or through menus available on the top.
    Job overview transaction code - SM37.
    Hopefully the issue is in Development/Test/Quality system and not in Production.
    Hope that helps!.
    Regards,
    Saba

  • Convert Spool to PDF and mail for the jobs not run in background.

    Dear All,
    I need to convert the spool job into pdf and mail as attachment for job not run in background.
    I am printing the bills  using the program  SD70AV3A to print the bills in a batch using the SUBMIT.
    But i am not using the spool options since its going to into waiting state in spool...and i need to change the printer properties to G
    to get the printer to print the reports as these jobs run in backgroud....but this solution is not acceptable solution.
    SUBMIT SD70AV3A
             WITH RG_KSCHL-LOW = 'ZRR'
             WITH RG_NACHA-LOW = '1'
             WITH PM_VERMO = '2'
             WITH PM_NSORT = '1'
             WITH RG_VBELN IN range.
    *        TO SAP-SPOOL
    *        SPOOL PARAMETERS print_parameters
    *        WITHOUT SPOOL DYNPRO
    *        VIA JOB name NUMBER number
    *        AND RETURN.
    so how do i get the spool number from the above after the job is submitted....and then convert into pdf and mail
    please suggest some solution. I have searched on net but most the solutions are say to run the job as background job...
    i have also looked into the program RSTXPDFT4 but it asks for the spool id ....how can i get spool id for the job that has been completed.
    please suggest some solution.
    Thanks
    Bhargava.

    Hi,
    Spool to PDF : FM 'CONVERT_ABAPSOOLJOB_2_PDF'
    Table TSP01 to get spool number
    You ,may need to convert OTF to PDF: FM CONVERT_OTF
    and the to binary : FM 'SMCS_XSTRING_TO_BINARY'
    To send mail use class: cl_document _bcs.
    Regards,
    Maria João Rocha

  • Background job not automatically poopulating Dependant Demand

    Hi Users,
    We've recently set up a POS & PA using the DP-BOM selection and characteristics, manually created PPM's and generated CVC's using the BOMS. All of this is set up fine in our SCM 7.0.
    The background job has created the forecasts for the ouptput products but NOT the input product.
    Now if I call up the parent material, and then choose to show the input products the dependant demand is generated. If I now return to the material with the dependant demand, it now shows the demand from the parent.
    Or, if the forecast is genereated interactively, then the dependant demand is poopulated.
    Is there an automated method to populate the dependant demand when using background jobs? I would like to think that we don't have to query every sales BOM parent in DP and drill into the input products to load the dependant demand?
    Please let me know if there is an easier way to do this as part of the background processing.
    Thanks
    Edited by: Paul_111 on Mar 31, 2011 4:20 PM

    Hi Andand,
    Thanks for your reply and sorry if my post is confusing.
    As far as the PPM with imputs A & B, output C - I have this relationship working and calcuclating demand in DP no problems.
    If I now add a new PPM combination inpput X, Y and output Z. Create the BOM CVC and TSO so its all set to go. Add to selection profiles and background jobs.
    Now, if I run the background job to create the forecast and this runs successfully. Now I check my products.
    Z has the forecast generated, X & Z have no dependant demand showing.
    The only way I've found that pushes the demand to X & Z is:
    - open product Z in demand planning and then choose the option to show input products from the header
    OR - from demand planning, select the univariate forecast to run interactively.
    My issue:
    The background job (if run alone) does not push the forecast on Z to X & Y.
    And if I show the input products or create forecast (as bove) the dependat demand is shown on X & Y.
    This is going to be a slow process if we have to do this everytime we run the backgound job.
    What am I missing when running the background job?

  • Background Job Still Running - Data Can Be Displayed Only Msg Populated in Maintain Versions (OKEQ) Screen

    Hi,
    I try to create 2013 FY in "Setting for Each FY" in OKEQ - Maintain Versions unfortunately I have created Null FY, try to delete Null FY on the time it will ask Job schedule, I have cancelled the job & reopen Maintain Versions (OKEQ) screen on the time system populated the msg "Background Job still running - Data can be displayed only"
    In Settings for Each FY screen there is no New Entries button, all FY are blocked status, changes was not allowed.
    How can I resolve it.
    Waiting for your valuable suggestions.
    Regards,
    Nageswar.

    Dear Rajneesh Saxena
    Thanks for your prompt reply.
    Yes you are correct, on the time of deletion it will ask Background Job Process, for immediate deletion must & should select "NO".
    While "Settings for Each FY" screen populates message "Background Job Still Running - Data Can Be Displayed Only" open  screen in display mode enter the command "=KILL" in command bar press enter, then you will allow to changes get New Entries button also.
    Problem is solved
    Regards,
    Nageswar.

  • Background job is running for long tome in source system (ECC)

    Hi All,
    Background job is running for long tome in source system (ECC) while extracting data to PSA.
    I checked in ECC system SM66,SM50 the job is still running
    in SM37 the job is Active
    There are only maximum 7000 records the extractor is 2LIS_02_ITM but it is taking 11 to 13 hours to load to PSA daily
    I had checked enhancements every thing is correct.
    Please help me on this how can I solve this issue.
    Regards
    Supraja K

    Hi sudhi,
    The difference between Call customer enhancement...  and  Result of customer enhancement:... is very less we can say this as a second.
    The difference is between LUWs confirmed and 1 LUWs -
       and Call customer enhancement -
    Please find the job log details below, and give me the solution to ressolve this
    01:06:43 ***01:06:43 * ztta/roll_extension........... 2000000000                              *                 R8           050
                     R8           048
    01:06:43 1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA     RSQU          036
    06:56:31 Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 5.208 records                  R3           407
    06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
    06:56:31 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 5.208 records                      R3           407
    06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
    06:56:31 PSA=1 USING SMQS SCHEDULER / IF [tRFC=ON] STARTING qRFC ELSE STARTING SAPI                 R3           299
    06:56:31 Synchronous send of data package 1 (0 parallel tasks)                                      R3           410
    06:56:32 tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =                           R3           038
    06:56:32 tRFC: Start = 00.00.0000 00:00:00, End = 00.00.0000 00:00:00                               R3           039
    06:56:32 Synchronized transmission of info IDoc 3 (0 parallel tasks)                                R3           414
    06:56:32 IDOC: Info IDoc 3, IDoc No. 1549822, Duration 00:00:00                                     R3           088
    06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
    06:56:32 Altogether, 0 records were filtered out through selection conditions                      RSQU          037
    06:56:32 Synchronized transmission of info IDoc 4 (0 parallel tasks)                                R3           414
    06:56:32 IDOC: Info IDoc 4, IDoc No. 1549823, Duration 00:00:00                                     R3           088
    06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
    06:56:32 Job finished                                                                               00           517
    Regards
    Supraja

  • Background job not updating data for some steps of program

    We have created a custom program and submitting the standard program RPRCCC_READ_KR1025
    which is used for conversion of AMEX credit card files.
    Since this program can update data for 1 company id at a time,we have created a background job
    for that program with 10 steps and 10 variants of data related to 10 different company codes.
    when this job is executed it is not updating data for all the 10 files , sometimes it updates 5,7,etc...
    If we execute the other files which didnt update in job manually they are getting updated.
    All the files executed with that program can be seen in PRTA transaction.
    Regards,
    Gautham.
    Edit: Solved.
    Since the standard program updates the database every time with commit work
    there should be some time until the next database update,so we can use wait command
    after the submit statement which will do the trick.
    Edited by: Gautham Vangaveti on Aug 5, 2010 7:20 PM

    Hi,
    I mean B(Sub Assembly)
    Item Rollup Flag
    A No
    --B                       Yes
    ---B1 No
    ---B2 No
    ---B3 No
    --C                      Yes
    In this case when we run cost rollup by giving item A, Oracle will consider below structure.
    A
    --C
    Regards,
    Sarvottam.

  • Background job not showing full output of Report

    Dear Experts
    we have created zpgm for stad report and try to take output as mail to particular user for future analysis bcaz stad gives only 2 days report only we need keep report for months together so when we run job in foreground it shows proper output but when same thing when we run from background it shows only some part of report in mail (we are unable to get full output through background job )
    we send mail through spool receipts we have created folder and maintain user for getting mails through so15 distribution list
    we need some input to come out of this major issue
    if there is any other workaround let me know
    Regards

    Hello,
    If a job is defined by transaction SM36, the print format parameters will only be taken into account, if they are saved as user specific print parameters of the batch user. If no user specific print format
    is defined,  the ALV standard logic will be processed adjusting the print format to the actual line size of the report.
    For example, the list line size is about 132 characters, the widest available format of the chosen printer will be selected X_65_132.
    The problem would be solved by defining a device type which is no format assigned to print, or by defining user specific print format parameters for the batch user, who creates the jobs in SM36 (see
    SAP note 1179399, item 6).
    Regards,
    David

  • Background job not deleted

    Hi Experts,
    i want delete the   "SM:SELFDIAGNOSIS" background job on solution manager system .
    and i have deleted,  go to next date and then delete the released job but after one day again its showing in released.
    so how i can delete it properly .
    Regards
    jai kr.

    Shiv,
    First check the frequency of this job from SM37
    Go to  SM37 -> give your job name ->and select all the options like
    delete  the entries in start date and end date fileds. then execute.
    If you find  job in Released state  ,simply go to  menu Job -> click on release to schedule.
    Now this job will in Schedule and won't run untill you release it.
    Deleting the jobs is not good idea ,simply you can suspend it.
    Regards,
    Srinivas Chapa.

  • Background job not yet been Finished

    Hi,
    I have set a Background job today at 10:15 to start run at today 11:30 AM.
    it is a periodic daily process at 11:30 am.
    But when i checked the status of this job, its still in the status Released.
    i know that, this job will not take more then 20 mins
    what could be reason?
    Regards,
    Swetha

    Hello Sweta,
    As the job is in 'released' status so you can say that it has not started running, it will come to 'active' status as soon as it starts running, so you should not fear to cancel the job scheduled.
    Answer to why in 'released' status for such a long time may be due to some network speed problem or due to some other jobs alreay running in the system which would be occupying all the work processes which are available in the system. If possible try to find the job which has taken more that 65 thousand seconds, kill that job and then refresh after 5-10 mins to see the status of your job.
    Hope it helps.
    Thanks,
    Jayant

  • Background Job not Printing TOs immediately

    Hello experts,
    I am having an issue with printing Transfer Orders created by background job, the output requests are sent to the output controller with status '-' . It works when I manually create the TOs or if I run the RLAUTA10 program with my userID in SE38 .
    I have set the background job user default print parameters in SU3 to print immediately.
    Also in the Job step, I have set up the print parameters  to 'print immediately'
    I have assigned printer for sorce storage type & set the indicator to use the source sto type in OMLV, The printer seems to be determined correctly, I've checked the Spool request name & printer in the spool controller, only issue seems to be the print not being triggered immediately.
    Not sure, if there is some other setting that I have to make to be able to print the TOs created by the background job immediately.
    Any help would be appreciated.
    Thanks
    Kris T

    whether the printer which you assigned is configured in SAP (network printer)? or LOCL?
    printing may not happen if LOCL(background job)
    Thanks

  • Background job not invoking in CC.

    hi,
    I am facing a problem in running background job in CC. Actually its invoking a wrong url and when i am checking in application deployed url is different.
    We are at CC SP9.
    Url invoked is "is http://hostname:51700/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=/usr/sap/FAP/DVEBMGS17/j2ee/cluster/server1/.&threadId=4&daemonType=WS
    As per deployment
    Url should be "http://chmsxp41.eame.syngenta.org:51700/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart"
    Please suggest.
    Thanks & Regards,
    Pravin

    Please check SAP Note 999785.
    Somewhere between SP04 and SP06 the URL changed, and you need to re-configure that on database level (change "virsa/ccappcomp" to "sap.com/grc~ccappcomp").
    Frank.

  • Infopackage loads 0 record in process chain as BG job not running correctly

    Hi Experts,
    I have scheduled a daily process chain for Purchasing.
    The infopackage in the process chain loads 0 records from R/3 and shows green status but data is available in R/3. Its a FULL update.
    But when I load the data manually the infopackage fetchs the record form R/3.
    When I checked the background job in R/3 that loaded 0 records, the job gets finished abruptly without fetchig any data.
    Please find the job log below:
    Job started
    Step 001 started (program SBIE0001, variant &0000000210024, user ID RFCUSR)
    DATASOURCE = ZPUR_S600
             Current Values for Selected Profile Parameters               *
    abap/heap_area_nondia......... 0                                       *
    abap/heap_area_total.......... 0                                       *
    abap/heaplimit................ 40894464                                *
    zcsa/installed_languages...... ED                                      *
    zcsa/system_language.......... E                                       *
    ztta/max_memreq_MB............ 2047                                    *
    ztta/roll_area................ 3000320                                 *
    ztta/roll_extension........... 2000683008                              *
    Job finished
    But the background job for the request when I run the infopackage manually calls a function BW_BTE_CALL_BW204010_E (BTE) and fetches the record from R/3.
    Please find the job log that fetches the record when run manually.
    Job started
    Step 001 started (program SBIE0001, variant &0000000210036, user ID RFCUSR)
    DATASOURCE = ZPUR_S600
             Current Values for Selected Profile Parameters               *
    abap/heap_area_nondia......... 0                                       *
    abap/heap_area_total.......... 41230008320                             *
    abap/heaplimit................ 40000000                                *
    zcsa/installed_languages...... DE                                      *
    zcsa/system_language.......... E                                       *
    ztta/max_memreq_MB............ 2047                                    *
    ztta/roll_area................ 3000000                                 *
    ztta/roll_extension........... 2000000000                              *
    Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 26,596 records
    Result of customer enhancement: 26,596 records
    Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 26,596 records
    Result of customer enhancement: 26,596 records
    Asynchronous send of data package 000001 in task 0002 (1 parallel tasks)
    Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 26,596 records
    Result of customer enhancement: 26,596 records
    Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 26,596 records
    Result of customer enhancement: 26,596 records
    Asynchronous send of data package 000002 in task 0004 (1 parallel tasks)
    Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 1,062 records
    Result of customer enhancement: 1,062 records
    Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 1,062 records
    Result of customer enhancement: 1,062 records
    Asynchronous send of data package 000003 in task 0006 (1 parallel tasks)
    tRFC: Data Package = 000001, TID = , Duration = 000001, ARFCSTATE =
    tRFC: Start = 20110217 054648, End = 20110217 054649
    tRFC: Data Package = 000003, TID = , Duration = 000000, ARFCSTATE =
    tRFC: Start = 20110217 054652, End = 20110217 054652
    tRFC: Data Package = 000002, TID = , Duration = 000001, ARFCSTATE =
    tRFC: Start = 20110217 054651, End = 20110217 054652
    Job finished
    Kindly help me on this issue as why the job run through process chain is not fetchibg any records.
    Regards,
    Indhuja

    Hi Prasanth,
    If the background jobs are not availbale when IP is triggered then the BG job will ot be executed and the IDOCs will get struck.
    Once we push the IDOc only the BG job will be executed until then the PC will wait with yellow status.
    Hence this is not the issue with the non availability of BG WP.
    Also for last one week this issue was happening but today the job executed successfully through the Process chain itself.
    Then it shows this is not the issue with PC also.
    The job is executed using RFCUSR.
    Please suggest what would be the possible cause for this issue.
    Regards,
    Indhuja
    Edited by: Induja Rajkamal on Feb 23, 2011 11:48 AM

  • Schedule jobs not running

    the user execute the abap job and execute in background, but it is not running. He execute many times, but still sit in schedule state, do you know why? there is no error in SM21, will it be authority issues? how to check? thanks

    It looks like it is an authorization issue. Ask them to do that again and immediately in another session, run SU54. This will show all the authorization checks that the user went through and tells you if it failed.
    Alternatively, they can just go to SM37 and try to release it. If it comes back with a message, you will know.
    Srinivas

  • Standard background job is running after deleting a user also

    Hi Gurus,
    in my production system environment i observed below thing.
    1)Default standard background jobs were scheduled by earlier basis admin after some days he left and his id also deleted but still some jobs are running with his id and finishing also, how is it possible without having his ID in system?
    2) what is the standard procedure to schedule default standard bg jobs in SAP? either from sap* or DDIC or basis admin?
    one more question regarding Audit logs:
    1)can we activate audit log for selective ids and selective period?
    2)if we activate audit log is there any performance issues will come?
    Thanks in advance
    Venkat

    Hello Venkat,
    1)Default standard background jobs were scheduled by earlier basis admin after some days he left and his id also deleted but still some jobs are running with his id and finishing also, how is it possible without having his ID in system?
    - Please cross check whether multiple jobs are scheduled with that user in different time period. If that user is defined in step then only that job fails otherwise it runs without any issues.
    2) what is the standard procedure to schedule default standard bg jobs in SAP? either from sap* or DDIC or basis admin?
    - Please go through the note suggested by Juan. I recommend to schedule with DDIC or Basis Admin.
    Thanks,
    Siva Kumar

Maybe you are looking for