ERM background jobs "waiting"

Dear all,
Any jobs I create in ERM - apart from those I schedule manually with "immediate" start - remain in status "waiting" forever and do not get processed.
This applies to periodic updates of transaction/object/activity data etc, as well as to automatically scheduled jobs with type "immediate", such as "Role Approver Update" after I have changed the workflow - approval criteria.
Deactivating/Activating the jobs doesn't help, either.
Am I missing something? Jobs in other capabilities are working fine, so surely it is not a problem with the background daemon itself?
Thanks and regards
Patrick

Thanks for the hint to the note, Sunny.
The note describes the problem, however the resolution is a bit funny. It really justs says that this is by design - surely, however, jobs hovering in "waiting" status without ever being executed cannot be "by deign"?
I not sure if I understand the note correctly.
Regards
Patrick

Similar Messages

  • 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

  • ERM - Background Static Jobs

    Hi Experts,
    After doing the initial static background jobs, namely:
    - Org Value Sync
    - Transaction/Object/Field Sync (the 5 hour job)
    - Activity Sync
    are this jobs something which should be run periodically in ERM or is it a one-off thing?
    Thanks!

    Hi,
    These static jobs should be ran periodically to synchronize the org values, Tcodes, field values etc. Otherwise custom transaction codes or updates done in the backend system will not reflect in the ERM system. So one day while adding some custom transaction code to role in ERM you may not find the SU24 objects being pulled in !!
    Cheers !!
    Zaheer

  • Submit RSEOUT00 as background job

    Hi all,
    Here is my requirement.There is a Z program from which RSEOUT00 program has to be called , so that it will change the Idoc status to '03'. I tried using Submit RSEOUT00..and return and also tried JOB_open and then SUBMIT rseout00 WITH docnum EQ p_idocno  user sy-uname  via  job jobname number jobcount and return and then JOB_CLOSE .I checked SM37 also where i can see this job as finished..
    I tried COMMIT WORK statement and also WAIT statement .
    But still the idoc status wont change to '03' .
    Can anyone plase advise on how to correct this .
    Regards,
    Sudheer

    Hi,
    I have created background job for RSEOUT00 and written the below code. It worked.
    DATA: w_number           TYPE tbtcjob-jobcount,
               w_name              TYPE tbtcjob-jobname VALUE 'ZTEST_JOB'.
       CALL FUNCTION 'JOB_OPEN'
         EXPORTING
           jobname          = w_name
         IMPORTING
           jobcount         = w_number
         EXCEPTIONS
           cant_create_job  = 1
           invalid_job_data = 2
           jobname_missing  = 3
           OTHERS           = 4.
       IF sy-subrc = 0.
         SUBMIT rseout00  VIA JOB w_name NUMBER w_number AND RETURN.
         IF sy-subrc = 0.
           CALL FUNCTION 'JOB_CLOSE'
             EXPORTING
               jobcount             = w_number
               jobname              = w_name
               strtimmed            = 'X'
             EXCEPTIONS
               cant_start_immediate = 1
               invalid_startdate    = 2
               jobname_missing      = 3
               job_close_failed     = 4
               job_nosteps          = 5
               job_notex            = 6
               lock_failed          = 7
               OTHERS               = 8.
           IF sy-subrc <> 0.
           ENDIF.
         ENDIF.
       ENDIF.
    Thanks,
    Appanaboina

  • To Check whether Background Job ran or no

    How can we programatically check in a program whether a background job ran or not for a particular output type of invoice ?? Pls help me out

    Hi,
      This will probably work.
    report zkiran_0001 .
    data: xtbtco type   tbtco .
    parameters: p_job type tbtco-jobname.
    start-of-selection.
      clear xtbtco.
      select single  * from tbtco
              into xtbtco
                         where jobname = p_job
                           and status = 'R'.  " running
      if sy-subrc = 0.
        write:/ 'Job', p_job, ' is currently running'.
      endif.
    Statuses....
    Status of background job
    The following statuses are possible:
    <b>Scheduled:</b> Job defined, but not yet eligible to run even if the start condition has been fulfilled.
    <b>Released:</b> Job eligible to be started as soon as the start condition with which it was scheduled is fulfilled.
    <b>Ready:</b> Job waiting to start. The job has been released and the job's start condition has been fulfilled.
    <b>Active:</b> Job is currently running and can no longer be deleted or reset to scheduled.
    <b>Finished:</b> Job has been successfully completed. All job steps completed successfully.
    Note: the background processing system cannot always determine whether an external job step was successfully completed. In this case, the system assumes successful completion.
    <b>Terminated:</b> Job was ended abnormally either through user action or through an error in running a job step.
    Internal codes for these are as follows.
      btc_running       LIKE tbtco-status VALUE 'R',
      btc_ready         LIKE tbtco-status VALUE 'Y',
      btc_scheduled     LIKE tbtco-status VALUE 'P',
      btc_released      LIKE tbtco-status VALUE 'S',
      btc_aborted       LIKE tbtco-status VALUE 'A',
      btc_finished      LIKE tbtco-status VALUE 'F',
      btc_put_active    LIKE tbtco-status VALUE 'Z',
      btc_unknown_state LIKE tbtco-status VALUE 'X'.
    refer
    https://forums.sdn.sap.com/click.jspa?searchID=4369376&messageID=1681128
    Regards
    Message was edited by:
            Kiran Sure(skk)

  • Background Job processing

    After writing a report, I used this Function Module “LIST_TO_ASCI” to copy my report to an internal table (DOWNTAB) because I’ll use that internal table to download a text file on the server using dataset.
    Here is my code:
    FORM DL_REP_SERVER.
       DATA: ABAP_LIST LIKE ABAPLIST OCCURS 1,
            MV_FILE2 LIKE RLGRAP-FILENAME.
      DATA: BEGIN OF DOWNTAB OCCURS 1,
              LINE(150),
            END   OF DOWNTAB.
      CLEAR: MV_FILE2.
      MV_FILE2 = ‘J:/Downloads/Report.txt’.
      CALL FUNCTION 'LIST_TO_ASCI'
           EXPORTING
                LIST_INDEX         = SY-LSIND
           TABLES
                LISTASCI           = DOWNTAB
                LISTOBJECT         = ABAP_LIST
           EXCEPTIONS
                LIST_INDEX_INVALID = 1
                OTHERS             = 2. 
      OPEN DATASET MV_FILE2 FOR OUTPUT IN TEXT MODE.
      IF SY-SUBRC <> 0.
        IF SY-SUBRC = 8.
          MESSAGE E037 WITH 'File could not be opened'.
        ELSE.
          MESSAGE E037 WITH 'Error occurs in downloading the file'.
        ENDIF.
      ENDIF.
      LOOP AT DOWNTAB.
        TRANSFER DOWNTAB TO MV_FILE2.
      ENDLOOP.
      CLOSE DATASET MV_FILE2.
    ENDFORM.                    " DL_REP_SERVER
    My big problem is this, when I’m running my program ordinarily (not as background job), I’m getting all the pages downloaded correctly but when I run it as background job (using SM36), I’m only getting the last page of my report being downloaded. Definitely, I can’t debug it because it’s in background. I can’t figure out why. Hope that I stated my problem clearly. Any help would be greatly appreciated. Thanks.

    You can debug batch jobs by going to 'SM37', type in 'JDBG' in the
    command line ( no '/' ), put the cursor on the job and press enter - will
    take you to the job in debug mode.
    You can do this only after the job has finished execution. This will simulate the exact background scenario with the same selection screen values as used in the job also sy-batch will set to 'X'.
    So type in the transaction code 'JDBG' and place your cursor on the job after It has finished. It will take you to a SAP program in debug mode. Step through this program which is about 10 lines, after this your program will be executed in the debug mode.
    Steps
    1. Create variant called BACKGROUND for program to be debugged.
    2. Execute ZDEBUGBG (pgm code below) in background for immediate processing.
    3. Execute transaction SM50.
    4. Select process that runs ZDEBUGBG.
    5. Goto 'Program/Session' 'Program' 'Debugging'.
    A se80 debug session will open.
    6. Change variable W_EXIT to 'E'.
    7. Step thru (F6) until ZWBTEST comes up.
    1. Go to Transaction SM66 and find your work porocess.
    Select the line work process is on and click on the Debugging button.
    If this is a custom program, you can put a wait statement in the code to buy yourself sometime.
    2. Go to Transaction SM50. From the tool bar "Program/session"->Program->Debugging.
    goto SM37 and from Program menu(not sure.. try other menu's)
    -->Catchjob . it will goto the active job in debugging mode.

  • Background Job Scheduling

    Hi,
      I am scheduling a report to run in background.
    In this report it is creating background jobs automatically for different company codes.
    It submits the 1st background job and waits until it finishes.
    Then 2nd job starts in background and continues with other jobs.
    At end it finishes all the jobs and closes.
    Now my problem is.
    1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
    2.       If possible how can we do that.
    What I have written is
    loop at companycode.
    Create job name.
    call fun 'Job_Open'.
    submit xxxx user sy-uname via job job_name numer job_count
    to sap-spool
    spool parameters l_spool_parameter
    without spool dynpro
    with companycode
    with ......
    and return.
    endloop.
    Please help ASAP, urgent.

    hi praveen,
    Job Scheduling Explained
    Definition
    Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the job’s definition. There are several ways to schedule jobs:
    From Transaction SM36 (Define Background Job)
    With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
    Through the background processing system’s own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
    Through an external interface.
    Scheduling Background Jobs   
    Use
    You can define and schedule background jobs in two ways from the Job Overview:
    ·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
    ·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
    Procedure
           1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
           2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
           3.      Set the job’s priority, or “Job Class”:
    ·         High priority:      Class A
    ·         Medium priority: Class B
    ·         Low priority: Class C
           4.      In the Target server field, indicate whether to use system load balancing.
    ·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
    ·         To use a particular application server to run the job, enter a specific target server.
           5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
           6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
           7.      Define the job’s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
           8.      Save the fully defined job to submit it to the background processing system.
           9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
    Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
    Specifying Job Start Conditions
    Use
    When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
    Procedure
    Choose the Start condition button at the top of the Define Background Job screen.
    Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
    For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
    Once you’ve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
    No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
    Managing Jobs from the Job Overview
    Use
    The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
    Procedures
    To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
    To copy a single existing job, choose Job ® Copy.
    To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
    To repeat a single job, choose Job ® Repeat scheduling.
    To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
    You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
    To review information about a job, choose Job ® Job details. Details displayed can include:
    current job status
    periodicity, or the repetition interval
    other jobs linked to the current job, either as previous or subsequent jobs
    defined job steps
    spool requests generated by the current job
    To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
    To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
    To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
    To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
    To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
    To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
    regards
    karthik
    reward me points if helpfull

  • 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 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.

  • How to submit a Program in Background without wait ?

    hi experts,
        I have one requirement in which i want to call another executable program from one program by passing some parameters to the calling program from called program. <b>I dont want to wait till the executatio of the calling program gets over.</b>i just want to submit the program & <b>wants to continue with my calling program</b>.
    i am not bothered with the results of the called program.
         How to do this...
    if possible pl. send me the code. especially i am using some parameters & internal tables to be passed to the called program from calling program.
    Regards,
    Umesh

    Hi Umesh,
    You can schedule a job programatically .. Please find below the steps..
    This will schedule a background job (and this you can view in Sm37) and returns control to the calling program.
      DATA: jobnumber TYPE tbtcjob-jobcount,
                jobname   TYPE tbtcjob-jobname.
    Set the job name
    jobname = 'xxx'.
      CALL FUNCTION 'JOB_OPEN'
           EXPORTING
                jobname  = jobname
           IMPORTING
                jobcount = jobnumber
           EXCEPTIONS
                OTHERS   = 0.
      SUBMIT reportname USER sy-uname
                                    VIA JOB jobname
                                   NUMBER jobnumber
                                   WITH  param1 =   "fill the parms/sel fields with new values
                                   WITH  Param2=     "fill the parameters/sel fields
         AND RETURN.
       CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
                jobcount  = jobnumber
                jobname   =jobname
                strtimmed = 'X'
           EXCEPTIONS
               OTHERS    = 0.
    Thank You.
    Regards,
    Uma

  • SAP_COLLECTOR_FOR_PERFMONITOR background job cancelled in SM37

    Dear all ,
    One of the scheduled background job has been  cancelled .
    Kindly check the below loga and Background job details .
    Job name        SAP_COLLECTOR_FOR_PERFMONITOR
    Job class       C
    Status          Canceled
    (ABAP Program
    Name           RSCOLL00
    Variant
    Language       EN)
    Job Log :
    30.05.2010 06:20:32 Job started
    30.05.2010 06:20:32 Step 001 started (program RSCOLL00, variant , user ID DDIC)
    30.05.2010 06:20:37 Clean_Plan:Cleanup of DB13 Plannings
    30.05.2010 06:20:37 Clean_Plan:started by RSDBPREV                       on server PRDCIXI
    30.05.2010 06:20:38 Clean_Plan:Cleaning up jobs of system IRP
    30.05.2010 06:20:39 Clean_Plan:finished
    30.05.2010 06:20:43 ABAP/4 processor: DBIF_RTAB_SQL_ERROR
    30.05.2010 06:20:43 Job cancelled
    Kindly suggest

    Dear all ,
    Kindly check the ST22 error logs .
    Short text SQL error occurred in the database when accessing a table. What happened? The database system detected a deadlock and avoided it by rolling back your transaction. What can you do? If possible (and necessary), repeat the last database transaction in the hope that locking the object will not result in another deadlock. Note which actions and input led to the error. For further help in handling the problem, contact your SAP administrator . You can use the ABAP dump analysis transaction ST22 to view and manage termination messages, in particular for long term reference. Error analysis The database system recognized that your last operation on the database would have led to a deadlock. Therefore, your transaction was rolled back to avoid this. ORACLE always terminates any transaction that would result in deadlock. The other transactions involved in this potential deadlock are not affected by the termination. Last error logged in SAP kernel Component............ "SAP-Gateway" Place................ "SAP-Gateway on host PRDCIXI / sapgw01" Version.............. 2 Error code........... 679 Error text........... "program prodoradb.sapccmsr.99 not registered" Description.......... "TP prodoradb.sapccmsr.99 not registered" How to correct the error Database error text........: "ORA-00060: deadlock detected while waiting for resource" Internal call code.........: "[RTAB/UPD /MONI ]" Please check the entries in the system log (Transaction SM21). If the error occures in a non-modified SAP program, you may be able to find an interim solution in an SAP Note. If you have access to SAP Notes, carry out a search with the following keywords: "DBIF_RTAB_SQL_ERROR" " " "RSHOST3M" or "RSHOST3M" "PUT_LOGBOOK" If you cannot solve the problem yourself and want to send an error notification to SAP, include the following information: 1. The description of the current problem (short dump) To save the description, choose "System->List->Save->Local File (Unconverted)". 2. Corresponding system log Display the system log by calling transaction SM21. Restrict the time interval to 10 minutes before and five minutes after the short dump. Then choose "System->List->Save->Local File (Unconverted)". 3. If the problem occurs in a problem of your own or a modified SAP System call.......... " " Module............... "gwr3cpic.c" Line................. 1835 The error reported by the operating system is: Error number..... " " Error text....... " "
    for detail log.
    System environment
    SAP-Release 700
    Application server... "PRDCIXI"
    Network address...... "10.54.145.32"
    Operating system..... "AIX"
    Release.............. "5.3"
    Hardware type........ "000184CAD400"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 8
    Shortdump setting.... "full"
    Database server... "PRODORADB"
    Database type..... "ORACLE"
    Database name..... "IRP"
    Database user ID.. "SAPSR3"
    Terminal................. " "
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Mar 7 2010 21:00:49"
    create on........ "AIX 2 5 005DD9CD4C00"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 246
    Patch text.. " "
    Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
    SAP database version. 700
    Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
    Memory consumption
    Roll.... 1217248
    EM...... 0
    Heap.... 0
    Page.... 32768
    MM Used. 1050520
    MM Free. 146024
    and Transaction
    Client.............. 000
    User................ "DDIC"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "4BFF227871E00187E10080000A369120"
    In the source code you have the termination point in line 521
    of the (Include) program "RSHOST3M".
    The program "RSHOST3M" was started as a background job.
    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
    Job Initiator.. "DDIC"
    Job Number..... 02033500
    In the source code you have the termination point in line 521
    of the (Include) program "RSHOST3M".
    The program "RSHOST3M" was started as a background job.
    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
    Job Initiator.. "DDIC"
    Job Number..... 02033500
    Program............. "RSHOST3M"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    rmation on where terminated
    Termination occurred in the ABAP program "RSHOST3M" - in "PUT_LOGBOOK".
    The main program was "RSHOST3M ".

  • 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

  • Background Job Hanged but no work process assigned

    Hi,
    Background job has hanged When i see in SM37. But no work process assigned to this job. All work process are waiting status.
    What could be the reason. What is the resolution process.
    Thanks,
    Dayakar

    How did you come to a conclusion that the bg job is hangend.
    What is the status of the job. ? I guess  Job defined, but not yet eligible to run even if the start condition has been fulfilled so it should be in Scheduled status.

  • FM for Background Job Check

    Hi,
    is there a function module that will check the background job status and will wait for it to finish before returning to the calling program?
    I have developed a program that triggers a background job at runtime, but i also need to make sure the job is finished, successful or not, before the output of the program. i'm currently doing a query in a job table inside a do enddo loop, but i believe this is not efficient.
    Any ideas?
    thanks.
    tyken

    I am not having the sample Code with me right now...
    But i'll help you to build the logic...
    after Write report.
    Use the Function module I told u...
    then...
    write a select query on  table tbtcp with job info you will get from FM.
    What is your objective after getting the Background Job details..?

  • Scheduling of process chain with background job

    Hello All,
                  I have scheduled the process chains through background jobs. I have copied the meta chain and created seven background jobs that is from Monday till sunday. The problem is most frequently the job gets cancelled with the message
    Process CHAIN, variant PAA1_GS001 is not scheduled waiting for event RSPROCESS 44NRPDWZ7CQUJ92ATDTY6368H.
    This is the variant for the next process after the start process. I tried by giving merge active versions, but one day the background job runs fine , but the next day it gets cancelled.
    If anyone has faced this issue before kindly let me know.
    Regards,
    Karthik.

    Hi,
    It seems to be there may be in probelm in Varients, so create a separate Varient for each PC and then activate the PC and execute.
    Thanks
    Reddy

Maybe you are looking for