Background job hanging reasons

background job hanging reasons

Could you provide little more detail of the issue you encountering.
One of the reason could be 100% utilization of the CPU, all your background process might being used in parallel.
Check the load in the transaction st03n
To prevent this you may want to use load balancing on various application servers using the transaction smlg.
You may also want to define a flow of the the jobs, like job B should start after job A has completed.
Let us know more details of the environment to allow us to help you better
Thanks & Regards
Abhinav

Similar Messages

  • Background Job hangs!

    Hello Friends,
    I am encountering a problem with background jobs which has driven me crazy.
    The background job hangs and when I try to debug it using the JDBG command the results are surprising.
    When the program control reaches a particular PERFROM statement, then no matter what command I give (F5, F6 or if I double click on any of the variables) it hangs. When I press F5, it should atleast go in to the corresponding FORM, and hang during some processing or it should go into an infinite loop but this is not the case. The system hangs even when I press F5 on the PERFORM. The FORM routine exists in the program, so that possibility is ruled out.
    Actually the job processes records of a custom table, this problem starts with a particular record and if I skip the processing of this record then it happens with almost all the records after this one. Also, this does not happen every time the job is run, but whenever it does, it starts with a particular record.
    When the system hangs then even if I try to stop the transaction by right clicking on the task bar then it has no effect, the only way to close the session is by using the 'Windows task manager'.
    I tried transaction SM50, but there were no changes on that screen for this particular session indicating that it has hanged.
    Please let me know if you require any more information.
    Thanks and Regards,
    Haseeb.

    Hi,
    Debug it in Sm66.
    kishore.

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

  • Background job getting CANCELLED

    hello,
    i have  a background job scheduled for a report program.it is getting cancelled and giving the following error:
    "TABLE_ILLEGAL_STATEMENT"
    You attempted to change, delete or create a line in the       
    internal table "???", but no valid cursor exists              
    for the table.                                                
    Possible reasons:                                             
    1. The relevent ABAP/4 statement does not include the addition
       "...INDEX...", although the statement is not               
       inside a "LOOP...ENDLOOP" loop processing this table.      
    2. The relevent ABAP/4 statement was called from within a     
       "LOOP...ENDLOOP" loop after a DELETE "???".                                                                               
    what could be the reason?

    it is also giving following error message:
    Caution: Program has changed
    Caution: At time of termination,  Active source code no longer available  and after above two statements its giving sign "?" before every statement in below manner:
    024300 ?     lit_ekpo_dummy1[] = it_ekpo[].                     
    024310 ?     DELETE lit_ekpo_dummy1 WHERE ebeln NE tab1-ebeln.  
    024320 ?     DESCRIBE TABLE lit_ekpo_dummy1 LINES count01.      
    024330 ?                                                        
    024340 ?     REFRESH lit_ematn_dummy[].                         
    024350 ?     lit_ematn_dummy[] = lit_ematn[].

  • Failed to Run OLE Excel program in background JOB (SM36)

    Please help.
    I have write a program to use OLE to create a Excel file.
    The program can run successful in front end workstation. However, when I run the program in background job by SM36.
    The statement "CREATE OBJECT EXCEL 'EXCEL.APPLICATION'" return with error "SY-SUBRC = 2".
    How can I solve it ?
    Can OLE Excel be run on background job ?
    Thanks so much,
    Mark

    Hi Mark:
    Your need is a very common one. I also was asked to generate an Excel in Background.
    It is not possible to work with OLE in background mode.
    The reason is: In background mode there is no presentation server. OLE is executed in presentation server.
    Below I paste the code I wrote to solve my problem.
    This class sends a mail with an excel attached. The Excel content will be the internal table you pass to the class. But the Excel is not binary, it is a plain text file, separated by tabulators. Anyway, when you open it with Excel, the columns are properly shown.
    Sorry. Comments are in spanish, I don't have time to translate it.
    I kindly ask to everybody which want to use it to keep my name in the code.
    * Autor: Jordi Escoda, 30/10/2008.
    * Descripción: Esta clase genera un correo electrónico destinado a
    *  una persona, adjuntando el contenido de una tabla interna como
    *  Excel (campos separados por tabuladores).
    *  La virtud de esta clase es su sencillez de utilización. Para lanzar
    *  el mail con el excel adjunto basta con declarar la tabla interna,
    *  llenarla, colocar el asunto del mensaje, el destinatario, el nombre
    *  del excel adjunto, y pasar la tabla interna.
    * Ejemplo de utilización:
    *  DATA: lc_mail TYPE REF TO cl_mail_builder_xls_attach.
    *  DATA: lt_anla TYPE STANDARD TABLE OF anla.
    *    SELECT * INTO TABLE lt_anla  FROM anla.
    *    CREATE OBJECT lc_mail.
    *    CALL METHOD lc_mail->set_subject( 'Excel adjunto' ).
    *    CALL METHOD lc_mail->set_recipient( 'XXX@XXXDOTCOM' ).
    *    CALL METHOD lc_mail->set_attach_filename( 'ANLA' ).
    *    APPEND 'Cuerpo del mensaje' TO  lt_body.
    *    APPEND 'Saludos cordiales' TO  lt_body.
    *    CALL METHOD lc_mail->set_bodytext( lt_body ).
    *    CALL METHOD lc_mail->set_attach_table( lt_anla ).
    *    CALL METHOD lc_mail->send( ).
    *       CLASS cl_mail_builder_xls_attach DEFINITION
    CLASS cl_mail_builder_xls_attach DEFINITION.
      PUBLIC SECTION.
        METHODS: set_subject
                               IMPORTING im_subject TYPE so_obj_des,
                 set_bodytext
                               IMPORTING im_body TYPE bcsy_text,
                 set_recipient
                               IMPORTING im_recipient TYPE ad_smtpadr,
                 set_attach_table
                               IMPORTING im_table TYPE ANY TABLE,
                 set_attach_filename
                               IMPORTING im_attach_name TYPE sood-objdes,
                 send.
      PRIVATE SECTION.
        CONSTANTS:
          c_tab  TYPE c VALUE cl_bcs_convert=>gc_tab,
          c_crlf TYPE c VALUE cl_bcs_convert=>gc_crlf,
          c_singlequote TYPE c VALUE '.
        DATA: l_recipient_addr TYPE ad_smtpadr.
        DATA: send_request   TYPE REF TO cl_bcs,
              document       TYPE REF TO cl_document_bcs,
              recipient      TYPE REF TO if_recipient_bcs,
              bcs_exception  TYPE REF TO cx_bcs.
        DATA: binary_content TYPE solix_tab,
              size           TYPE so_obj_len.
        DATA: l_string TYPE string,
              l_body_text TYPE bcsy_text,
              l_subject TYPE so_obj_des,
              l_attach_name TYPE sood-objdes.
        METHODS: create_binary_content,
                 get_dataelement_medium_text
                        IMPORTING im_table_name TYPE tabname
                                  im_field_name TYPE fieldname
                        EXPORTING ex_medium_text TYPE scrtext_m.
    ENDCLASS.                    "cl_mail_builder_xls_attach DEFINITION
    *       CLASS cl_mail_builder_xls_attach IMPLEMENTATION
    CLASS cl_mail_builder_xls_attach IMPLEMENTATION.
      METHOD set_bodytext.
        l_body_text[] = im_body[].
      ENDMETHOD.                    "add_bodytext
      METHOD set_subject.
        l_subject = im_subject.
      ENDMETHOD.                    "add_subject
      METHOD set_attach_filename.
        l_attach_name = im_attach_name.
      ENDMETHOD.                    "add_subject
      METHOD set_recipient.
        l_recipient_addr = im_recipient.
      ENDMETHOD.                    "add_subject
      METHOD set_attach_table.
    *   Rellena en un string el contenido de la tabla interna recibida
        DATA: ref_to_struct  TYPE REF TO cl_abap_structdescr.
        DATA: my_like TYPE fieldname,
              nombretabla TYPE tabname,
              nombrecampo TYPE fieldname,
              texto_mediano TYPE scrtext_m.
        DATA: l_idx TYPE i,
              l_valorcampo(16) TYPE c,
              l_long TYPE i.
        FIELD-SYMBOLS: <fs_linea> TYPE ANY,
                       <fs_campo> TYPE ANY.
        FIELD-SYMBOLS: <comp_descr> TYPE abap_compdescr.
        CHECK NOT im_table[] IS INITIAL.
    *   Línea con los nombres de las columnas.
        CLEAR l_string.
        LOOP AT im_table ASSIGNING <fs_linea>.
    *     Toma los atributos del componente
          ref_to_struct  =
                     cl_abap_structdescr=>describe_by_data( <fs_linea> ).
          LOOP AT ref_to_struct->components ASSIGNING <comp_descr>.
            ASSIGN COMPONENT <comp_descr>-name
                                OF STRUCTURE <fs_linea> TO <fs_campo>.
    *       Obtenemos el origen de donde proviene (like). Ej:BKPF-BUDAT
            DESCRIBE FIELD <fs_campo> HELP-ID my_like.
            SPLIT my_like AT '-' INTO nombretabla nombrecampo.
            CALL METHOD get_dataelement_medium_text
              EXPORTING
                im_table_name  = nombretabla
                im_field_name  = nombrecampo
              IMPORTING
                ex_medium_text = texto_mediano.
            IF texto_mediano IS INITIAL.
              CONCATENATE l_string <comp_descr>-name INTO l_string.
            ELSE.
              CONCATENATE l_string texto_mediano INTO l_string.
            ENDIF.
            AT LAST.
              CONCATENATE l_string c_crlf INTO l_string.
              EXIT.
            ENDAT.
            CONCATENATE l_string c_tab INTO l_string.
          ENDLOOP.
          EXIT.
        ENDLOOP.
    *   Contenido de la tabla
        LOOP AT im_table ASSIGNING <fs_linea>.
    *     Toma los atributos del componente
          ref_to_struct  =
                     cl_abap_structdescr=>describe_by_data( <fs_linea> ).
          LOOP AT ref_to_struct->components ASSIGNING <comp_descr>.
    *       Asignamos el componente ue tratamos, para obtener
    *       el valor del mismo
            ASSIGN COMPONENT <comp_descr>-name OF STRUCTURE <fs_linea>
                                            TO <fs_campo>.
            CASE <comp_descr>-type_kind.
              WHEN 'P'. "Packed Number
    *           Convierte a caracter
                WRITE <fs_campo> TO l_valorcampo.
                CONCATENATE l_string l_valorcampo INTO l_string.
              WHEN OTHERS.
                l_long = STRLEN( <fs_campo> ).
                IF l_long > 11 AND <fs_campo> CO ' 0123456789'.
    *             El Excel muestra un número tal como 190000000006
    *             en formato 1,9E+11.
    *             Para eviarlo, los números de más de 11 dígitos los
    *             concatenamos con comillas simples.
                  CONCATENATE l_string c_singlequote
                              <fs_campo> c_singlequote INTO l_string.
                ELSE.
                  CONCATENATE l_string <fs_campo> INTO l_string.
                ENDIF.
            ENDCASE.
            AT LAST.
    *         Añade CRLF
              CONCATENATE l_string c_crlf INTO l_string.
              EXIT.
            ENDAT.
    *       Añade tabulador
            CONCATENATE l_string c_tab INTO l_string.
          ENDLOOP.
        ENDLOOP.
        create_binary_content( ).
      ENDMETHOD.                    "set_attach_table
      METHOD create_binary_content.
        DATA: l_size TYPE so_obj_len.
    *   convert the text string into UTF-16LE binary data including
    *   byte-order-mark. Mircosoft Excel prefers these settings
    *   all this is done by new class cl_bcs_convert (see note 1151257)
        TRY.
            cl_bcs_convert=>string_to_solix(
              EXPORTING
                iv_string   = l_string
                iv_codepage = '4103'  "suitable for MS Excel, leave empty
                iv_add_bom  = 'X'     "for other doc types
              IMPORTING
                et_solix  = binary_content
                ev_size   = size ).
          CATCH cx_bcs.
            MESSAGE e445(so).
        ENDTRY.
      ENDMETHOD.                    "create_binary_content
      METHOD send.
        DATA: l_sent_to_all TYPE os_boolean.
        TRY.
    *       create persistent send request
            send_request = cl_bcs=>create_persistent( ).
    *       create and set document with attachment
    *       create document object
            document = cl_document_bcs=>create_document(
              i_type    = 'RAW'
              i_text    = l_body_text
              i_subject = l_subject ).
    *       add the spread sheet as attachment to document object
            document->add_attachment(
              i_attachment_type    = 'xls'
              i_attachment_subject = l_attach_name
              i_attachment_size    = size
              i_att_content_hex    = binary_content ).
    *       add document object to send request
            send_request->set_document( document ).
    *       add recipient (e-mail address)
            recipient =
               cl_cam_address_bcs=>create_internet_address(
                                          l_recipient_addr ).
    *       add recipient object to send request
            send_request->add_recipient( recipient ).
    *       send document
            l_sent_to_all = send_request->send(
                                 i_with_error_screen = 'X' ).
            COMMIT WORK.
            IF l_sent_to_all IS INITIAL.
              MESSAGE i500(sbcoms) WITH l_recipient_addr.
            ELSE.
              MESSAGE s022(so).
            ENDIF.
          CATCH cx_bcs INTO bcs_exception.
            MESSAGE i865(so) WITH bcs_exception->error_type.
        ENDTRY.
      ENDMETHOD.                    "lcl_mail_xls_attachment
      METHOD get_dataelement_medium_text.
        DATA: lt_fld_info TYPE STANDARD TABLE OF dfies,
          wa_fld_info TYPE dfies.
    *   Busca en el diccionario los datos del campo
        CALL FUNCTION 'DDIF_FIELDINFO_GET'
          EXPORTING
            tabname        = im_table_name
            fieldname      = im_field_name
            langu          = sy-langu
          TABLES
            dfies_tab      = lt_fld_info
          EXCEPTIONS
            not_found      = 1
            internal_error = 2
            OTHERS         = 3.
        CLEAR ex_medium_text.
        IF sy-subrc = 0.
          READ TABLE lt_fld_info INDEX 1 INTO wa_fld_info.
    *     Si lo ha podido tomar del diccionario...
          IF NOT wa_fld_info-scrtext_m IS INITIAL.
    *       Toma el nombre del nombre de campo del diccionario
            ex_medium_text = wa_fld_info-scrtext_m.
          ENDIF.
        ENDIF.
      ENDMETHOD.                    "get_dataelement_medium_text
    ENDCLASS.                    "cl_mail_builder_xls_attach IMPLEMENTATION

  • Background Job RSPPFPROCESS Taking too long to execute.

    Hi Gurus,
    I'm working with SAP CRM 2007 - Interaction Centre
    We have configured first response date and to do by date in item category.
    If agent fails to response within the first response date or if agent fails to complete
    to close the ticket within the to do by date,An action is configured to trigger and an
    escalation email(Smart Form) is sent to agent`s manager inbox.
    We have scheduled background job for the program RSPPFPROCESS with variant in background
    to trigger this actions( It is scheduled 4 times in a day ).
    Previously this job used to take 6 hours to complete execution.
    But now its taking 12 hours to complete the execution and there is no change in the
    variant.
    Can anyone please advice me reason for this behavior.
    Kind Regards,
    Vinod

    Hi Manfred,
    We are experiencing similar performance issue when running the RSPPFPROCESS  Job. We opened a OSS message for quite some time but didn't get any useful help from SAP.
    Can you please provide more information regarding your ZRSPPFPROCESS program on identifying the crtical performance steps to resolve the performance issue? We are also thinking of archiving  the record in table PPFTTRIGG , we have over 73+ millions records in the table but there is no archiving object for PPF actions. We would like to focus on reducing the number of entries in the table PPFTTRIGG hopefully to improve the performance. Any thoughts on it?
    Thanks in advance for your kind help!
    Best Regards,
    Madeline

  • ATP as background job?

    Hi everyone,
    ATP is being a real struggle for us and we are  for a required balance of not missing out on deadlines and improving the service levels if possible within the constraints. For a product not in stock it or available at a later date, the MAD comes in perfectly on the basis of the RLT or in house production time set up. It gives it's correct dates and are communicated - the system proposes the MAD, loading date etc on the basis of which the shipping personnel run the VL10C.
    However, if, in a day or two (before the proposed delivery creation date), for any reason, we re-schedule a batch earlier or get returns for non quality reasons, the dates remain as they were (which of course, is the way it should be considering they were promised that way) but now, we are in a position to ship the goods out earlier. However, the shippers won't see it in VL10C as they would run it for their usual parameters.
    How can we get around this? Assuming a big range of products and hundreds of orders a day, it isn't feasible to do a CO06 individually. Is there any way to re-run the ATP in the background or something and it's report gives us the changes the system made, the new proposed dates etc?
    Or any other suggestions to handle these situations?
    Appreciate any help or guidance for any more research or answers...
    Many thanks.

    Hi,
    You can write a BDC program to open that order with the transaction VA02 and click the avaialbility check button once again. Based on that the availability check program will fire once again. You can run this BDC program as a background job!!!!!!!
    If it helps give me points na!!!!!!!!!!!!!!
    Chandra

  • Different result when running as background job

    Hi,
    We got a program which has a selection screen with a couple of select-options.
    When we start this programm with a specified variant, it proceeds to a result screen. If we click back now (to the selection-screen) and run the programm with the exactly same settings again, one select-option is getting ignored and therefore we get incorrect results.
    This happens only, if you go back from the result screen and  excecute it again from the selection screen or if we start it as a background job.
    If you exit the programm completely and restart it, the results are correct again.
    It makes no sense to post any code snippets here, since the program is very complex. I just can't imagine any reason, why the select-option is sometimes getting ignored.
    Does anyone have an idea?
    Thanks in advance.
    Regards,
    Tobi

    oh well it DOES explain it.
    just think of following select:
    Select *
    from   vbap
    into    ls_vbap
    where vbeln not in lr_vbeln.
    if lr_vbeln is not cleard you will run into problems maybe.
    anyway, may it be that somewhere in coding you are manually modifying your select option?
    It´s just an internal table of type range, so have a look there.

  • Page-break in alv background job for alv output variant not coming correctl

    Hi,
    I have created an ALV grid report. When i run the report in background i get the output with correct page-break on FIELD1. Now when i run the report in background with an "ALV output variant" (its the ALV variant that controls the fields display in the output; this is not the program variant), i do not get the page-break on FIELD1.  I have already build the sort criteria and using:
    gs_sort-group = '* '.     "New-Page
    Please let me know what could be reason for not getting the page-break in background when i am using the alv output variant and how do i correct this problem.
    Regards,
    Rakesh

    Hello Everyone,
    I have solved the problem. While running the program in background, we get the page-breaks when we use the below part of code in the sort catalogue with the condition that the program variant should not use any ALV layout variant.
    gs_sort-group = '* '.     "New-Page
    If you are using the ALV layout variant in the program variant then we can check the ROWPOS, COLPOS, and NO_OUT for that ALV layout variant and pass them along in the fieldcatalog table. You should be careful with not to pass the layout variant in the DISVARIANT. You can notice that i have cleared it and simply passing the program name into that.
    *C-- Process separately for jobs running in Background. Actually
    *C-- sortcat-group solves the problem only in Foreground. In background
    *C-- when ALV layout variant is not selected then it works otherwise it
    *C-- fails. So for background jobs we are reading the fieldcat and then
    *C-- passing the same in the display FM.
      IF sy-batch = 'X'.
        CALL FUNCTION 'REUSE_ALV_VARIANT_SELECT'
          EXPORTING
           i_dialog                  = ' '
           i_user_specific           = ' '
           i_default                 = ' '
    *   I_TABNAME_HEADER          =
    *   I_TABNAME_ITEM            =
            it_default_fieldcat       = gt_fieldcat
            i_layout                  = gs_layout
    *   I_BYPASSING_BUFFER        =
    *   I_BUFFER_ACTIVE           =
         IMPORTING
    *   E_EXIT                    =
           et_fieldcat               = lt_fieldcat
    *     et_sort                   = gt_sort[]
    *   ET_FILTER                 =
    *     es_layout                 = gs_layout
         CHANGING
           cs_variant                = gs_disvariant
         EXCEPTIONS
           wrong_input               = 1
           fc_not_complete           = 2
           not_found                 = 3
           program_error             = 4
           OTHERS                    = 5
        IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
        CLEAR gs_fieldcat.
        LOOP AT gt_fieldcat INTO gs_fieldcat.
    *C-- Transfer all position changes to gt_fieldcat from lt_fieldcat
          CLEAR ls_fieldcat.
          READ TABLE lt_fieldcat
                INTO ls_fieldcat
                WITH KEY fieldname = gs_fieldcat-fieldname.
          IF sy-subrc = 0.
            gs_fieldcat-row_pos = ls_fieldcat-row_pos.
            gs_fieldcat-col_pos = ls_fieldcat-col_pos.
            gs_fieldcat-no_out = ls_fieldcat-no_out.
            MODIFY gt_fieldcat FROM gs_fieldcat INDEX sy-tabix.
            CLEAR gs_fieldcat.
          ENDIF.
        ENDLOOP.
    *C-- Clear the disvariant for the background job as it contains the ALV
    *C-- layout varinat
        CLEAR gs_disvariant.
        gs_disvariant-report = 'ZGPPMP0001'.
    Then pass gt_fieldcat to 'REUSE_ALV_GRID_DISPLAY'.
    The reason i'm doing it this way is that when we pass the layout variant name, the contents in gt_fieldcat were getting modified.
    One more thing i'd like to point out is that that, i tried to delete the fields with no_out = 'x'. Now when i ran the program in background with all the fields in sort catalog (suppose there are 2 fields field1 and field2) also in fieldcatalog it ran fine. In the next run in background i removed one of the fields in sort catalog from the fieldcatalog (delete the fields with no_out = 'x') and i got dump. Basically i had hidden field1 and so the code which was deleting fields with no_out = 'x' deleted this field from gt_fieldcat. So basically we should not delete fields with no_out = 'x'.
    I was getting ABAP runtime errors    MESSAGE_TYPE_X in the following part of the standard code.
    000310     LOOP AT CT_SORT INTO LS_SORT.
    000320
    000330       READ TABLE IT_FIELDCAT ASSIGNING <LS_FIELDCAT>
    000340            WITH KEY FIELDNAME = LS_SORT-FIELDNAME BINARY SEARCH.
    000350       IF SY-SUBRC NE 0.
         >         MESSAGE X000(0K).
    000370       ENDIF.
    000380
    000390       LS_SORT-SELTEXT = <LS_FIELDCAT>-SELTEXT.
    i have just mentioned this part because when i checked the forum many people were getting such errors "MESSAGE_TYPE_X". This could also be one of the reasons.

  • DYNPRO_SEND_IN_BACKGROUND when submitting a background job, when creating a

    Hi.
    We create sales orders via EDI.   When certain sales orders are created, we execute user exists on the Sales Order save.  During the User Exit, we submit/create (job_open_adk function, the submit command, and the job_close_adk function) a background job. 
    The background, is created and executed successfully, but we get 2
    short dumps everytime.
    The short dump is:
    DYNPRO_SEND_IN_BACKGROUND
    The description is:
    Screen output without connection to user.
    The short dump is for the user WF-BATCH.
    I've used DEBUG and the shortdump occurs on the submit command.
    submit zsd
    to sap-spool
    destination 'null'
    immediately ''
    keep in spool 'X'
    without spool dynpro
    and return
    user l_user via job tbtcjob-jobname
    number tbtcjob-jobcount
    with p_vbeln = l_order
    with p_ebeln = l_po
    with p_uname = l_user.
    Nothing should be displayed on the screen.
    I used 'without spool dynpro' to prevent the 'Print Screen List' window
    from appearing.
    I've put this code into a TEST program. I ran the test program
    myself. (under my ID) The program run perfectly. No
    shortdump.
    Similar code is used in other programs and it works perfectly - no shortdumps.
    The short dump occurs when we use ALE/EDI to create a sales order.
    The short dump has the ID WF-BATCH on it.
    I'm guessing the problem is with the WF-BATCH ID. Are printer setting
    missing on a Work Flow ID?
    Any ideas why the 'without spool dynpro' parameter doesn't work for the
    WF-BATCH ID?
    I've tried searching OSS and I looked at the on-line help/documentation
    on Submit. I saw a recommentation to use the
    fuction 'GET_PRINT_PARAMETERS' to set all of the print parameters. I
    tried this, but still got the short dumps.
    Any suggestion on how I can run the Submit command and not get a short dump?
    thanks,
    Michelle

    Hi,
    Try this notes:
    0100915 RSBDCREO: System hangs or parameters not effective
    0377038 HR-CA-ALE: DYNPRO_SEND_IN_BACKGROUND for HR doc. d
    0105165 Dump "DYNPRO_SEND_IN_BACKGROUND" in prog.SAPMSSY0
    0169303 Warning messages displayed for settlement mass pro
    0428489 VL10: Dump 'DYNPRO_SEND_IN_BACKGROUND' with backgr
    [[http://forums.sdn.sap.com/thread.jspa?threadID=14875|http://forums.sdn.sap.com/thread.jspa?threadID=14875]]
    Regards
    HM

  • 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 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 BI_ODSA_ASD is getting cancelled, set privilege at db level

    Hi,
    Background job BI_ODSA_ASD is getting cancelled,
    i have increased the tablespace, still no luck,
    last time i faced the same problem at that time , i gave some permission at oracle level which worked fine, i dont not remember now,
    it was something like GRANT PRIVILEGE SAPSYS SAPCON...... (not sure)
    if anyone knows please let me know.
    Regards,
    SM

    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_SDB_ORA_PROGRAM_ERROR
    Date and Time          20.09.2007 15:46:44
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_SDB_ORA_PROGRAM_ERROR' was raised, but it was not caught
    anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_SDB_ORA_UPDATE_STATS=======CP' has to be
    terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
    caught and
    therefore caused a runtime error.
    The reason for the exception is:
    &#1600;bernehmen
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SQL_EXCEPTION", which was raised in the program
    "CL_SQL_STATEMENT==============CP",
    specifically in line 31 of the (include) program
    "CL_SQL_STATEMENT==============CM002".
    The cause of the exception was:
    ORA-20000: Insufficient privileges
    ORA-06512: at "SYS.DBMS_STATS", line
    2150
    ORA-06512: at "SYS.DBMS_STATS", line 14112
    ORA-06512: at line 1
    How to correct the error
    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:
    "UNCAUGHT_EXCEPTION" "CX_SDB_ORA_PROGRAM_ERROR"
    "CL_SDB_ORA_UPDATE_STATS=======CP" or "CL_SDB_ORA_UPDATE_STATS=======CM00I"
    "UPDATE_STATS"
    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
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.

  • 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

  • Background job finishes but error Error While Updating Material into Standard SAP5678

    Dear
    we run background job which finishes successfully but when we sqw logs it shows
    Error While Updating Material into Standard SAP5678
    Kindly share the reasons
    Regards

    This is an ERP Upgrade space and you should consider raising threads in the right space for prompt replies. Next time consider using SAP NetWeaver Administrator space for issues like these. Also you should consider closing your previous thread with the correct answer for future reference.
    What I see is a custom job. You should check what the job does and also the trace file of the work process and the consult with the application team or the developer for more information. Unfortunately with that screenshot there is nothing much we can advice you.
    Regards
    RB

Maybe you are looking for