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.

Similar Messages

  • SAP Standard Jobs are getting canceled

    Hi Basis Gurus,
    In our Quality BW 3.5 system the SAP Standard jobs are getting canceled.
    The jobs are as follows
    SAP_APPLICATION_STAT_COLLECTOR
    SAP_CCMS_CPH_HRCOLL
    SAP_CCMS_MONI_BATCH_DP
    SAP_COLLECTOR_FOR_JOBSTATISTIC
    SAP_COLLECTOR_FOR_NONE_R3_STAT
    SAP_COLLECTOR_FOR_PERFMONITOR
    SAPCONNECT ALL SEND
    SAP_REORG_ABAPDUMPS
    SAP_REORG_SPOOL
    SAP_RSICFDLT
    In SM37 when i click on the job log for the above mentioned jobs the system is promting a message saying as "Error reading job log"
    Please let me know how can troubleshoot it and resolve this issue.
    Our is qulaity BW 3.5 system
    Solaris OS
    Oracle Database
    Please help me.
    Regards,
    Anil.

    Hi ,
    For log display reason, try the note suggested. Jobs cancel reason may be due to that the user who schedule that job are locked or not exist on that client. Or other reason will be clear only after log display.
    Ankit

  • Job is getting cancelled in CPS

    Hi,
    We have implemented CPS on SOLMAN, and  when we were submitting a job for one of the SAP system and we are using Job chain method for submiting the job.
    Job is getting cancelled with the below error,please find the below error and log.
    Failed to create the job in the SAP system
    BAPI exception while calling BAPI_XBP_JOB_ADD_ABAP_STEP: E XM 034 Internal problem (function BAPI_XBP_JOB_ADD_ABAP_STEP) [BAPI_XBP_JOB_ADD_ABAP_STEP, , , ]
         at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.checkBapiReturnCode(ClientConnectionImpl.java:818)
         at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.call(ClientConnectionImpl.java:605)
         at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection$4.doPerform(AbstractRfcConnection.java:289)
         at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall.perform(RemoteFunctionCall.java:130)
         at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.perform(AbstractRfcConnection.java:445)
         at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.execute(AbstractRfcConnection.java:282)
         at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.SapFunctionModuleWrapper.execute(SapFunctionModuleWrapper.java:194)
         at com.redwood.scheduler.connector.sap.rfc.jco.AbstractSapFunctionModule.execute(AbstractSapFunctionModule.java:107)
         at com.redwood.scheduler.connector.sap.rfc.command.impl.AbapRunPrintCommand.doAddSteps(AbapRunPrintCommand.java:353)
         at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpJobRunCommand.execute(AbstractXbpJobRunCommand.java:177)
         at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpCommand.doExecute(AbstractXbpCommand.java:123)
         at com.redwood.scheduler.connector.sap.rfc.command.AbstractCommand.execute(AbstractCommand.java:56)
         at com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:107)
         at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:59)
         at java.lang.Thread.run(Thread.java:770)

    This message is most of the times thrown when the parameters you specify for the job to run are inconsistent. Possibly a variant name that does not exist or is missing, maybe a printer/sap user name/application server name that does not exist in the target system.

  • Job is getting cancelled

    Hi Friends !
    We have job name RSIMPCUST scheduled by the USER ID ABC. Now this ABC ID no longer exists. Hence job is getting cancelled. In the SM37, I did tried "Repeat Schedule" but thatz also getting cancelled. How I can schedule this job on my ID? Please advise.
    With Regards
    Rekha

    Hi Rekha,
    In order to be able to use the job with your Id please make setting according to this docuement ::
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b6b739-47a6-2e10-9abf-bdac1124dde1?QuickLink=index&overridelayout=true
    Regards,
    Arpit

  • Job E2E_HK_CONTROLLER getting canceled daily after EHP1 upgrade

    Hi, All,
    We upgraded solman system to EHP1.Since then; this job is getting canceled daily with following error:
    Job Log:
    Job started
    Step 001 started (program E2E_HK_CONTROLLER, variant , user ID SMD_RFC)
    Internal session terminated with a runtime error (see ST22)
    Job cancelled
    ST22 Dump log shows time out dump
    Current patch level is 04
    Kindly suggest how can this be solved

    Hi,
    Details are:
    Runtime Errors         TIME_OUT
    Date and Time          07.01.2010 01:30:54
    Short text
         Time limit exceeded.
    What happened?
         The program "SAPLRRSI" has exceeded the maximum permitted runtime without
         interruption and has therefore been 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
        After a specific time, the program is terminated to make the work area
        available to other users who may be waiting.
        This is to prevent a work area being blocked unnecessarily long by, for
        example:
        - Endless loops (DO, WHILE, ...),
        - Database accesses with a large result set
        - Database accesses without a suitable index (full table scan)
        The maximum runtime of a program is limited by the system profile
        parameter "rdisp/max_wprun_time". The current setting is 3600 seconds. If this
    Roll.... 16192
    EM...... 594970672
    Heap.... 0
    Page.... 16384
    MM Used. 585663104
    MM Free. 9274032
    r and Transaction
    Client.............. 100
    User................ "SMD_RFC"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "4B446D5B2E061DFFE10000003630905C"
    Program............. "SAPLRRSI"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "PS1"
    Database Release.... 701
    Kernel Release...... 701
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchron and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "

  • Job SLCA_LCK_SYNCHOWNERS getting cancelled

    Hi Guyz,
    We had job "SLCA_LCK_SYNCHOWNERS " getting cancelled everyday. Im not understanding what this job is doing. When i search in SAP Market Place this talks more as a job in MaxDB or some Live cache related. Could anybody tell me wht this job is doing  , is it necessary in our BI system, our DB is  Oracle 10g and OS in HP-UX.
    Thank you

    If this is not a LiveCache system, then you can just remove the job. This is scheduled by default in the SAP Standard Jobs area if you click the 'Default scheduling' button.
    Hope that helps.
    J. Haynes

  • Job SWWDHEX getting cancelled - OBJECTS_OBJREF_NOT_ASSIGNED

    Hi Guys,
    Here is the scenario:
    We modified WF 90000081 in dev box. In production, the workflow has been triggered and is awaiting response from agent.
    WF 90000081 has been moved to production, the workitems created by the WF in production is still awaiting response from the agent.
    Now, the job SWWDHEX runs after the WF is in production. The job is cancelled due to OBJECTS_OBJREF_NOT_ASSIGNED.
    In ST22, here is the details:
    Error analysis
    An exception occurred that is explained in detail below. The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not caught in procedure "IF_SWF_WFM_COMPONENT~RAISE_EXCEPTION" "(METHOD)", nor was it propagated by a RAISING clause.
    Question: How are we going to get away with it? Is there any SAP note which can help with this? I have looked note 1422978, it seems good and could solve the issue, but when I check on the method where the fix will be implemented, I checked in the Events called in ST22, the method is not being called by the job.
    Please advise.
    Thank you!

    Hello,
    Check if WF-BATCH is okay, ie password not changed and password not expired and it still has its roles.
    regards
    Rick Bakker
    Hanabi Technology

  • Job SWWDHEX getting cancelled - Report RSWWDHEX giving dump

    Hi Everyone,
    All instances of the Job SWWDHEX are being shown as cancelled in the background job log (SM37). On checking the job log, I found that the report RSWWDHEX is causing dump in the system. The job log shows:
    Job started
    Step 001 started (program RSWWDHEX, variant &0000000000001, user ID WF-BATCH)
    ABAP/4 processor: OBJECTS_OBJREF_NOT_ASSIGNED
    Job cancelled
    On checking ST22 for the runtime error-
    Error analysis
    An exception occurred that is explained in detail below. The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not caught in procedure "IF_SWF_WFM_COMPONENT~RAISE_EXCEPTION" "(METHOD)", nor was it propagated by a RAISING clause.
    The dump started happening yesterday onwards. We can't figure out what happened that started this. I tried to find some relevant notes & solutions, but was unable to find anything useful.
    Any suggestions or ideas would be very appreciated. Thanks.

    Hello,
    Check if WF-BATCH is okay, ie password not changed and password not expired and it still has its roles.
    regards
    Rick Bakker
    Hanabi Technology

  • RDDEXCEL job is getting cancelled

    Dear All,
    While transporting the request, the request ending with error code -12 , when i checked the log its showing RDDEXCEL JOB is cancelled , This is happening for every request .
    Thanks in advance .
    Thanks
    S SURESH
    <subject_modified>
    Do NOT use UPPERCASE on the subject
    Read the "Rules of Engagament"
    Edited by: Juan Reyes on Mar 25, 2010 9:43 AM

    Hi,
    Please check the below links which could help in resolving your issue.
    EXECUTION OF REPORTS AFTER PUT finsished with returncode 12 in spam
    Xpra_execution phase error execution of report return code 12
    Re: Upgrade NW640 to NW 700 - XPRAS_UPG - dump CALL_FUNCTION_PARM_MISSING
    Regards,
    Sharath

  • 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

  • Report program when run in background job getting cancelled immediately

    Hi
    When i run a program in foreground i am able to see the output. But when run in background not able to run the job successfully. The job is getting cancelled immediately.
    I am using the below function module for output display. Should i need to pass any parameters in the below function module so that i can run the program in background  successfully.
      CALL METHOD DETAIL_GRID->SET_TABLE_FOR_FIRST_DISPLAY     
          EXPORTING                                            
            IS_LAYOUT         = IS_LAYOUT                    
            I_SAVE            = 'A'                        
            IS_VARIANT        = GS_VARIANT                   
          CHANGING                                           
            IT_FIELDCATALOG   = IT_FIELDCATALOG               
            IT_OUTTAB         = BLOCKED_STOCK_TAB_ALV[].     
    Please suggest.
    Thanks and regards
    Rajani Yeluri

    Hi Rajani.
      ALV require the DRYPOR(screen) for display but incase you run in back ground which have to write to spool but in spool we can only write in format of LIST REPORT not inter-active report like ALV. That why
    system cancelled your process immediately.
    Hope it helps.
    Sayan.

  • LANDSCAPE FETCH job gets cancelled

    Hello Guru's,
    The  LANDSCAPE FETCH job gets cancelled on solution manager system due to the below mentioned error and in order to fix it
    we have already applied the SAP note 1335225 but, the issue still persists.
    Right now, we have come across the SAP note 1108071 which says the job will get cancelled "if you made adaptive computing
    settings in SMSY and the SLD is not accessible".
    can any one help me with how to check the adaptive computing settings in the header data of the system.
    Also, the SLD check from system via tcode:sldcheck is sucessfull and we could access the SLD via browser. Please find the
    details below.
    Properties of RFC destination SAPSLDAPI
    RFC host:
    %%RFCSERVER%%
    program id:      SAPSLDAPI_MP0
    gateway host:
    gateway service:
    Testing the RFC connection to the SLD java client...
    RFC ping was successful
    SLD server access settings:
    host name:   ashb01wa06pr.global.aes.com
    port number: 59000
    user       : SLDAPIUSER
    Use transaction SLDAPICUST if you wish to maintain the SLD server access d
    Launching the SLD GUI in a separate browser window...
    => Verify in the browser GUI that the SLD is in a healthy running state!
    Calling function LCR_LIST_BUSINESS_SYSTEMS
    Retrieving data from the SLD server...
    Function call returned exception code     3
    => Check whether the SLD is running!
    Immediate reponse is highly appreciated
    Best Regards,
    S.Viswanathan

    Hello,
    Could you include the Landscape_fetch error you mentioned in your message?
    I think the issue is still your SLD.  At the bottom of SLDCHECK it tries to retreive business systems in SLD. 
    If it is successfull you will see something like:
    Calling function LCR_LIST_BUSINESS_SYSTEMS
    Retrieving data from the SLD server...
    Function call terminated sucessfully
    List of business systems maintained in the SLD:
       yoursystem1
       yoursystem2
       yoursystem3
      (more...)
    Your SLD check shows that it cannot retrieve systems from the SLD:
    Calling function LCR_LIST_BUSINESS_SYSTEMS
    Retrieving data from the SLD server...
    Function call returned exception code 3
    => Check whether the SLD is running!
    Please make sure that you have configured your SLD according to the post-installSLD setup and configuration guide.  If you still have problems, follow this toubleshooting process...
    http://help.sap.com/saphelp_nw70/helpdata/EN/78/20244134a56532e10000000a1550b0/frameset.htm
    Best Regards.
    Edited by: Phil May on Sep 2, 2009 10:31 AM

  • RDDGENOL job getting cancelled with huge number of ABAP dumps

    Hi,
    In our Production system, we had applied Kernel upto patch level 263 and while
    applying SPAM 30 for release 640 it failed. We tried applying Basis patch 15 still
    it did not went through.
    Since then we are getting around 1500-2500 dumps daily. The job RDDGENOLis getting cancelled and the dumps RAISE_EXCEPTION and SYNTAX_ERROR is displayed in ST22. Today, there were around 2500 dumps in the system.
    When I now run the Database <-> ABAP Dictionary consistency check in
    DB02, I see number of errors for missing objects in the database. There
    are around of dozens of Primary Indexes, secondary Indexes, Tables,
    Views listed in the result:
    Objects Missing in database No.
    =========================== ===
    Primary indexes 6
    Secondary indexes 14
    Tables 37
    Views 26
    When I try to create each of them using SE16 or using SQL utility on OS
    level, it gives an SQL system error. We are also getting thousands of
    dumps each day (attached alongwith this message). Also I see the CPF327E error
    in the OS Level Joblog.
    Also we cannot transport any requests. There is some problem with or
    due to the conversions. Is it a problem with Kernel, ABAP dictionary or
    database.
    Following is the extract of the dumps due to DDIC in 000:
    ============================================================
    Runtime Error          SYNTAX_ERROR
    Date and Time         
    ShrtText
    Syntax error in program "CL_WB_CROSSREFERENCE==========CP ".
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLSEWB" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    In program "CL_WB_CROSSREFERENCE==========CP ", the following syntax error
    occurred
    in the Include "CL_WB_CROSSREFERENCE==========CM00D " in line 8:
    |    "The type "KEYWORD_TAB" is unknown." 
    ============================================================
    ============================================================
    Runtime Error          RAISE_EXCEPTION
    Date and Time         
    ShrtText
    Exception condition "DESTINATION_NOT_OPEN" raised.
    What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    A RAISE statement in the program "SAPLCRFC" raised the exception
    condition "DESTINATION_NOT_OPEN".
    Since the exception was not intercepted by a superior program
    in the hierarchy, processing was terminated.
    Short description of exception condition:
    Specified destination is not open.
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    How to correct the error
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "RAISE_EXCEPTION" C
    "SAPLCRFC" or "LCRFCU20"
    "RFC_CONNECTION_CLOSE"
    or
    "SAPLCRFC" "DESTINATION_NOT_OPEN"
    or
    "RADBAT01 " "DESTINATION_NOT_OPEN"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    System environment
    SAP Release.............. "640"
    Application server....... "TXTPDSAP"
    Network address.......... "172.16.0.140"
    Operating system......... "OS400"
    Release.................. "5.3"
    Hardware type............ "0065000655EC"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 35
    Short dump setting....... "full"
    Database server.......... "TXTPDSAP"
    Database type............ "DB400"
    Database name............ "TXT"
    Database owner........... "R3TXTDATA"
    Character set............ "en_US.ISO8859-1"
    SAP kernel............... "640"
    Created on............... "Dec 11 2008 23:06:45"
    Created in............... "AIX 1 5 00538A4A4C00 (IBM iSeries with OS400)"
    Database version......... "DB4_52"
    Patch level.............. "263"
    Patch text............... " "
    Supported environment....
    Database................. "V5R2, V5R3, V5R4, V6R1"
    SAP database version..... "640"
    Operating system......... "OS400 2 5, OS400 3 5, OS400 4 5, OS400 1 6"
    Memory usage.............
    Roll..................... 696832
    EM....................... 16759712
    Heap..................... 0
    Page..................... 32768
    MM Used.................. 1383120
    MM Free.................. 3483600
    SAP Release.............. "640"
    User and Transaction
    Client.............. 000
    User................ "DDIC"
    Language key........ "E"
    Transaction......... " "
    Program............. "SAPLCRFC"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    The termination occurred in the ABAP program "SAPLCRFC" in
    "RFC_CONNECTION_CLOSE".
    The main program was "RADBAT01 ".
    The termination occurred in line 22 of the source code of the (Include)
    program "LCRFCU20"
    of the source code of program "LCRFCU20" (when calling the editor 220).
    The program "SAPLCRFC" was started as a background job.
    Job name........ "RDDGEN0L"
    Job initiator... "DDIC"
    |    Job number...... 00032101    
    ============================================================
    Kindly let me know the immediate fix. Thanks!
    Regards,
    Nick

    Hi Nick,
    I would say, you are having a slight missperception of this forum ... it should not replace your basis ressources in your company.
    What you are doing is pretty complex (and the mixtrure of SPAM Update AND Basis SP seems to be wrong to me) and therefore, it will not be possible, to help you, just based on such a short dump.
    Sorry,
    Volker Gueldenpfennig, consolut international ag
    http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

  • Background Job cancelling with error Data does not match the job definition

    Dear Team,
    Background Job is getting cancelled when I run a Job on periodically but the same Job is executing perfectly when I run it manually(repeat scheduling) .
    Let me describe the problem clearly.
    We have a program which picks up files from an FTP server and posts the documents into SAP. We are scheduling this program as a background Job daily. This Job is running perfectly if the files contain no data. But if the file contains data the JOb is getting cancelled with the following messages.
    And also the same Job is getting executed perfectly when repeat scheduling is done ( even for files with data).
    Time     Message text                                                                       Message class Message no. Message type
    03:46:08 Job PREPAID_OCT_APPS2_11: Data does not match the job definition; job terminated        BD           078          E
    03:46:08 Job cancelled after system exception ERROR_MESSAGE                                      00           564          A
    Please help me in resolving this issue.
    Thanks in advance,
    Sai.

    hi,
    If you have any GUI function modules used in the program of job
    you cannot run it in background mode.

  • Reg:SAP_REORG_UPDATERECORDS job getting cancelled

    Hi Experts,
    I have a standard background job,SAP_REORG_UPDATERECORDS getting cancelled regularly in one of our production boxes.
    It runs only for a few seconds and then gets cancelled.
    The job log is.....
    "Job started
    Step 001 started (program RSM13002, variant SAP&001, user ID <XXXXXX>)
    Reorganization of update date not allowed in batch
    Job cancelled"
    I have searched for notes,but could not able to get the right solution
    kindly,help me resolve the issue
    Thnaks in advance
    Rgds-
    Venu

    Hello Venu,
    This job is no more needed as per recommenation from SAP
    Please go through the following notes:16083 and 67014 it shows that job is no more needed.This is the note of SAP about this job:
    "The standard job SAP_REORG_UPDATERECORDS that was contained in some delivered versions must no longer be executed (see Note 67014). In its new version, the underlying ABAP Program RSM13002 is programmed so that it terminates when running in a job (that is, in the background). Therefore, the job SAP_REORG_UPDATERECORDS always terminates in this case. In any case, the job SAP_REORG_UPDATERECORDS should be deleted from the pool of standard jobs, if it is still there: sm36 -> 'Standard jobs' -> 'Delete standard jobs'. In addition, released jobs that may exist and contain report RSM13002 should be deleted. You can find and delete these jobs using sm37."
    Rohit

Maybe you are looking for