Background job Z_SC_STATUS_CHECK_1 is getting cancelled in EBP system

Hi,
We are facing following error with the batch job Z_SC_STATUS_CHECK_1-" Error INSERT in BBP_DOCUMENT_TAB" with the erroe message "Job cancelled after system exception ERROR_MESSAGE?".
We are using an SRM 3.0 version.
Can you please provide any inputs on the same.
Regards,
Rohit

SInce this is a Z function, you should explain something more likewise what it does etc.....
Did you analysed the dump in ST22.

Similar Messages

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

  • Job DIM_OBSERVER is getting canceled with with a runtime error UNCAUGHT_EXCEPTION

    Dear Experts,
    Job DIM_OBSERVER is getting canceled with with a runtime error UNCAUGHT_EXCEPTION. Below are the details of runtime error.
    Category          
    ABAP Programming Error
    Runtime Errors    
    UNCAUGHT_EXCEPTION
    Except.           
    CX_UJA_ADMIN_ERROR
    ABAP Program      
    CL_UJA_MD_QUERY_OPT===========CP
    Application Component  EPM-BPC-NW-ADM
    Date and Time     
    02.08.2014 23:35:46
    I am unable to find related note and solution for the same. any help would be much appreciated.
    Thanks,
    Akbar.

    Hi Akbar,
    I believe this issue is coming up in BPC.
    But could you please provide some more detailed information like when exactly(after performing which step) is this error occurring?
    BR
    Prabhith

  • The job SAP_REORG_JOBSTATISTIC_000 somtimes gets cancelled and sometime not

    The job SAP_REORG_JOBSTATISTIC_000 getting cancelled sometime and sometimes it gets finished ,
    cancelled error log :
    Report RSBTCPRIDEL is already running
    Can any onle help on this.
    Manish

    Manish,
    The job SAP_REORG_JOBSTATISTIC_000 getting cancelled sometime and sometimes it gets finished
    cancelled error log :
    Report RSBTCPRIDEL is already running
    It seems this job is running from client 000  & also from some other client. Can you check in other client at which time it runs?
    Check Note 999951 for more information on RSBTCPRIDEL
    Hopw it helps
    Thanks
    Sushil

  • Background Job Monitoring not getting activated

    Hi Gurus,
    I have been trying to use the batch job monitoring with ccms.
    I have a problem in activating the "Background Job Monitoring" in few systems.
    I followed the steps in SAP Note 553953 but no use.
    In RZ21 i am not able to see the Background Job Monitoring under "Background" MTE .
    The same is wokring in Dev but in QA and Prod its not .
    Please suggest the solution and cause of the problem.
    Dev

    Hi,
    in SAP Solution Manager there are actually tools to support you in implementing the Job Scheduling Management (JSM) standard and these tools cover the request, documentation, schedulign and monitoring of a job.
    http://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000087418&_SCENARIO=01100035870000000202&_OBJECT=002007974700000007302009E
    Visit the following FAQs to find out more about JSM
    http://wiki.sdn.sap.com/wiki/display/SM/FAQJobScheduling+Management
    http://wiki.sdn.sap.com/wiki/display/SM/FAQBusinessProcess+Monitoring
    Kind regards,
    Martin
    http://service.sap.com/jsm
    http://service.sap.com/bpm

  • After reports running in background job need to get automatically open in excel sheet

    Dear All,
    I have a requirement which is new to me ,
    Once the user runs the report in background  system is displaying the output in HTML format .... But the Users needs to open in Excel sheet .
    kindly  do the needful
    Regards
    Srikanth BG

    Hi Srikanth,
    Excel processing in background is currently not possible using standard ways. There exist a really good external library that allows you to handle Excel files, and even create them in background. So you could create a final, ready to use Excel file from your background run that can then be opened.
    You might have a look at the library here: http://wiki.scn.sap.com/wiki/display/ABAP/abap2xlsx
    Maybe it helps and suits your needs.
    Cheers,
    Marc

  • System exception while deleting the file from app server in background job

    Hi All,
    I have a issue while the deleting the file from application server.
    I am using the statement DELETE DATASET in my program to delete the file from app server.
    I am able to delete the file from the app server when i run the program from app server.
    When i run the same report from background job i am getting the message called System exception.
    Is there any secuirity which i need to get the issue.
    Thank You,
    Taragini

    Hi All,
    I get all the authorization sto delete the file from application serever.
    Thing is i am able to run the program sucessfully in foreground but not in the background .
    It i snot giving any short dump also just JOB is cancelled with the exception 'Job cancelled after system exception ERROR_MESSAGE'.
    Can anybody please give me suggestion
    Thanks,
    Taragini

  • Background Job " RDDVERSI" getting terminated

    Hi gurus,
    When we check in SM37, We are seeing a background job that is getting terminated. In the job log it says DATASET_NOT_OPEN, Job cancelled. It is trying to run "RDDVERSI" program.
    It is creating a Dump in ST22 and when we check the Dump in ST22, it says "The file "/usr/sap/trans/tmp/D01V985854.P01" has not been opened".
    I checked the log in the trans directory and it gives me following error. Path of the Log "usr/sap/trans/log/D01V985854.P01".
    1AEPU320 See job log"RDDVERSI""07435800""P01"
    1 ETP184 CREATE VERSIONS BEFORE IMPORT
    1 ETP110 end date and time   : "20070912074448"
    1 ETP111 exit code           : "12"
    1 ETP199 ######################################
    1 ETP199X######################################
    1 ETP184 CREATE VERSIONS BEFORE IMPORT
    1 ETP101 transport order     : "D01K985854"
    1 ETP102 system              : "P01"
    1 ETP108 tp path             : "tp"
    1 ETP109 version and release : "340.16.24" "640"
    1 ETP198
    1AETR012XProgram terminated (job: "RDDVERSI", no.: "07460000")
    1AEPU320 See job log"RDDVERSI""07460000""P01"
    1 ETP184 CREATE VERSIONS BEFORE IMPORT
    1 ETP110 end date and time   : "20070912074651"
    1 ETP111 exit code           : "12"
    1 ETP199 ######################################
    I think when it is trying to import a transport request, it is trying to create a version of it  and it is not able to create that.
    Can anybody help me in solving this problem?
    Any Help is appreciated
    Regards,
    Swaroop.

    Can you run this program in the foreground with a user that has the same permissions. If you get an authorization error again, check with transaction se53 on which objects you are missing authorization.
    For these objects you can create an additional authorization profile...
    Kind regards,
    Mark

  • How to trigger a mail when a job gets cancelled

    Hi experts,
                     I have a requirement to trigger a mail to the user when a job fails or gets cancelled.I need to add this part in the program for which the job is running.
    Kindly help,any sample code will be very helpful.
    thanks in advance,
    regards,
    Ashwin

    check this thread out. Hope this might help you
    how can i insure that job finished and good  and send mail to the user  ?
    Regards,
    Santosh

  • The Job SAPRUPGM gets cancelled

    Hi Experts!!!
    We have recently updated tp and r3trans.When ever we are applying the support packages they are imported successfully
    but we have found that the job  SAPRUPGM is getting cancelled,Once it runs and the other time its cancelled.The folowing is the
    Step 002 started (program ENH_SAPRUPGM, variant , user ID DDIC)
    Step 003 started (program ENH_CREATE_ENHCROSS, variant , user ID DDIC
    ABAP/4 processor: DBIF_RSQL_SQL_ERROR
    Job cancelled
    This is the job log.
    The same job was run successfully just 20 min before this cancelled job.
    Regards,
    Vamshi.

    Hi Ruchit,
    We are on  SPAM26 and every time when we defined queue it was asking whether we want to add the request to the import queue or not then this time we have selected no.The job was not cancelled this time. I think i should apply the note which you have provided.
    Regards,
    Vamshi.

  • Query regarding Background Jobs

    I have 3 Application servers + Central instance.
    After a background job has been completed/cancelled, how do I determine on which App Server it was executed?
    Also, Waht does the big Button 'Application Server' display. I am guessing list of all available servers, right?
    Thanks in advance.

    Hello Gautam,
    You can  follow the approach suggested by Santosh. However this approach can be used for only one job at a time. If you want to do it simultanoeusly for several jobs then you can follow the below process:
    1. In SM37 give the selection criterion for the desired  job output and execute.
    2. Now you will have a complete list of the desired jobs.
    3. In the application menu bar you will fiind an icon for Define output fields(normally this icon is reserved for variants). Click on the icon. If you are  not able to find the icon you can also use CTEL+F7.You will get a popup.
    4. In this pop up there will be 2 columns. On the left hand side will be the fields which are already being shown in SM37. On right side you will find the hidden fields like: Progress, Executing server etc.
    5. Select executing server and click the single arrow icon (in the middle) pointing towards left side. Press COPY button and now see the result.
    Regards.
    Ruchit.

  • SAP_COLLECTOR_FOR_PERFMONITOR getting cancelled

    Dear All,
    The job SAP_COLLECTOR_FOR_PERFMONITOR is getting cancelled daily at 7.00 AM. It is scheduled to run hourly. All other times it finishes succesfully. But only 1 time at 7 it gets cancelled. The job log is :-
    Date       Time     Message text                                                Message class Message no. Message type                                                                               
    15.11.2007 07:00:17 Job started                                                      00           516          S       
    15.11.2007 07:00:17 Step 001 started (program RSCOLL00, variant , user ID DDIC)      00           550          S       
    15.11.2007 07:00:38 ABAP/4 processor: CONNE_IMPORT_WRONG_COMP_TYPE                   00           671          A       
    15.11.2007 07:00:38 Job cancelled                                                    00           518          A                                                                               
    the Dump is pasted below:-
                                                                                    ShrtText                                                                               
    Error when attempting to IMPORT object "HIST2".                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "RSORAT4M" had to be terminated because one of the                 
        statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                                                               
    When attempting to import data, it was discovered that the data                             
        type of the stored data was not the same as that specified in the                           
        program.                                                                               
    Error analysis                                                                     
        An exception occurred. This exception is dealt with in more detail below       
        . The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR', 
         was neither                                                                   
        caught nor passed along using a RAISING clause, in the procedure               
         "AKT_DAY_HIST2" "(FORM)"                                                      
    Since the caller of the procedure could not have expected this exception       
         to occur, the running program was terminated.                                 
        The reason for the exception is:                                               
        When importing the object "HIST2", the component no. 8 in the                  
        dataset has a different type from the corresponding component                  
        of the target object in the program "RSORAT4M".                                                                               
    The data type is "I" in the dataset, but "P" in the program.                   
    How to correct the error                                                               
        Try to find out why the type of the object is different.                           
        There are several possible reasons:                                                
    --- In the ABAP Dictionary, the type of the imported                               
    field has changed. Make sure that the type of the imported                     
    field matches the length of the Dictionary field.                              
    |   If the data could not be restored from another source, this data               
        |   must be read with the "old" structure, then converted and exported             
        |   back with the new structure, so that future IMPORTs always work                
        |   with the new structure.                                                        
        |                                                                               
    --- A new program version is active, and it no longer matches the                  
            dataset. Try to solve the error by generating the program "RSORAT4M" again     
            as follows:                                                                    
            In the SAP System, choose the transaction SE38. Enter the program              
            name "RSORAT4M". Then choose the "Activate" function.                                                                               
    ===
    It is saying
    The data type is "I" in the dataset, but "P" in the program.                              
    But it runs 23 times correctly except 1 time.
    Can Anyone help me in this please
    Thanks
    Tajinder

    Hi,
    Can u please suggest me what will be the monikey here. below is the dump for that
    154   DATA: FLAG VALUE ' '.                                                       
    155   LOOP AT HIST2.                                                              
    156     IF HIST2-DATE = DATE. DELETE  HIST2. FLAG = '*'. ENDIF.                   
    157   ENDLOOP.                                                                    
    158   IF FLAG NE SPACE. SUBTRACT 1 FROM LOGBUCH-ANZDAYS. ENDIF.                   
    159 ENDFORM.                                                                      
    160                                                                               
    161 FORM AKT_DAY_HIST2.                    " Aktualisiere Tage-Historie           
    162   PERFORM PREPARE_MONIKEY USING 36.    " Lese Historie                        
    >>>>   IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.                             
    164   IF SY-SUBRC <> 0.                                                           
    165     REFRESH HIST2. CLEAR HIST2.                                               
    166     PERFORM LOGBUCH_INIT USING 1.                                             
    167     PERFORM TRANSFORM_ALL_HISTORIES.   " Strukturaenderung fuer Dynami        
    168     PERFORM PREPARE_MONIKEY USING 36.    " Lese Historie                      
    169     IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.                           
    170   ENDIF.                                                                      
    171   READ TABLE HIST2 INDEX 1.                                                   
    172   IF SY-SUBRC <> 0.                                                           
    173     REFRESH HIST2. CLEAR HIST2.                                               
    174     PERFORM LOGBUCH_INIT USING 1.                                             
    175   ENDIF.                                                                      
    176   PERFORM DELETE_AKT_DAY_HIST2.        " Delete aktuellen Tag                 
    177   LOOP AT HIST2_DAY.                   " Füge neue Analyse an                 
    178     MOVE-CORRESPONDING HIST2_DAY TO HIST2.                                    
    179     APPEND HIST2.                                                             
    180   ENDLOOP.                                                                    
    181   ADD 1 TO LOGBUCH-ANZDAYS.                                                   
    182   MOVE DATE TO LOGBUCH-LASTDAY.                                               
    Thanks
    tajinder

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

  • Error while opening the file in Background job in Virsa.

    We are using Virsa 5.2
    I click on the result tab to view the job results.(informer->Background job) I am getting this message.
    Mar 3, 2008 1:49:15 PM com.virsa.cc.comp.GenericRAReportView wdDoModifyView
    WARNING: .\virsa\bgJobSpool\16.i (The system cannot find the file specified)java.io.FileNotFoundException: .\virsa\bgJobSpool\16.i (The system cannot find the file specified)
    Can you please let me know?
    Nothing has been changed including my user profile.
    From,
    PT.

    Hi,
    Here are number of notes that I have listed out to sort some issues on SAP GRC 5.2 .
    There is a note for background daemon issue as well
    Installation
    Note 1009509 - VIRSANH 5.2 Support Packages for BASIS 700
    Note 1022187 - Compliance Calibrator 5.2 Support Pack
    Post Installation
    Note 1022187 - Compliance Calibrator 5.2 Support Pack
    Note 1008500 - VIRSA 4.0 Support Packages for Basis 700
    Note 1060673 - Configuration of SAP Adapter in CC 5.2
    Note 709140 - Recommended JDK and VM Settings for the WebAS630/640/7.0
    Note 1044173 - Recomended Netweaver Setting for Access Control 5.x
    Note 1044174 - Recommendation for CC 5.x running on Oracle 10G Database
    Note 1121978 - Recommended settings to improve peformance in CC 5x analysis
    Note 978536 - Language Configuration for Virsa Compliance Calibrator 5.2
    Issues
    Note 1008500 - VIRSA 4.0 Support Packages for Basis 700
    Note 999785 - CC Background Daemon will not Start
    Note 987386 - Graphics Rendering Issue in SAP Compliance Calibrator
    Note 1009267 - System ID is not available in drop down menu-CC5.1
    Note 1052455 - Error-No relevant language message available in database
    Note 1062037 - java.lang.NullPointerException error in Adapter activation
    Note 1088378 - CC 5.2 - Undeployment of ccappcomp from SDM fails
    Thanks,
    Uday

  • Hi.Background Job

    Hi Guru's,
    I having problem while uploading pricing conditions data.i want to upload more than 10000 thousand records.
    in selection screen,we are provinding file path (Presentation server) and using  fm "gui_upload" updating the content into internal table and updating pricing document using fm "RV_CONDITION_COPY".
    My question is.
    while upadting more than 10000 round records im getting time out dump error so im trying to execute this program using background job but im getting error like "Cannot perform frontend function in batch input mode".
    Anybody help me on this issue.
    Regards
    P.Senthil Kumar

    Hi,
    Its not possible to use GUI_UPLOAD in background mode as the SAP system is completely independent and wont allow any GUI based operations. You can try transfering the file to application server and then try running the report as a background job.
    Regards,
    Vik

Maybe you are looking for