Background landscape fetch getting cancelled in solman

Dear All,
I m getting Abap dump in Solution Manager .One of my Background process is getting cancelled Job 'Landscape Fetch' .
I m pasting the dump here.
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
xception              CX_SY_REF_IS_INITIAL
ate and Time          07.06.2010 13:00:37
Short text
Access via 'NULL' object reference not possible.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSMSY_ACTUALIZE_DATA" had to be terminated because
     it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
    administrator.
  The exception must either be prevented, caught within proedure
"SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
    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 that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
     caught in
    procedure "SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", nor was it propagated by a
     RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: "ACCESSOR").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
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:
    "OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
    "SAPLSMSY_ACTUALIZE_DATA" or "LSMSY_ACTUALIZE_DATAU14"
    "SMSYAD_GET_DATA_FROM_LCR"
    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
The exception must either be prevented, caught within proedure
"SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
I refer the following note number and implimented that 1042815.But its not working.
I refer this follwing thread Re: Solution Manager 4.0  Re-Configuration
Kindly suggest me how to resolve this.
Regards
Ashok

Hello Ashok singh
I think that this note below will help you to solve this issue. There's a PDF attached in this note that will help you to check this issue step by step. I believe that this issue is being caused by a problem with SLD.
  Number              768452
  Short text          Troubleshooting SLDCHECK - Releases 640, 70X

Similar Messages

  • Job getting cancelled in background scheduling

    Hi,
        I have written a report  in the SAP HR system and it is to be scheduled in background. This program transfers the PERNRs from HR system to CRM system as partners in BUT000.The report works perfectly fine if it is run in foreground. When I run it in background the job gets cancelled and I get the job log having a message that it could not ascertain code page and the system exception ERROR_MESSAGE is raised. If anybody has any clues regarding this problem please help me.
    Thanks & Regards,
    Rahul.

    Hi,
    I Guess you are using container controllers in the Report, and all container contols requires help from Sap Gui for execution. I guess that is the reason it is failing in background . Please check on that aspect as well.
    Hope this helps..

  • Report J_1IEWT_CERT getting cancelled, generating ABAP dump!

    A long running report J_1IEWT_CERT in background mode is getting cancelled after running for a while and generating the following dump :
    Error analysis
        When changing or deleting one or more lines of the internal table
        "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]" or when inserting in the table
         "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]", 0 was used as
        the line index. An index less than or equal to zero is not
        allowed.
        The error can occur when using the following options:
        1. "INDEX idx" for specifying the line number in the table
         "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]"
           where you want to change, insert or delete.
        2. "FROM idx" for specifying the start index when deleting a line
           area from or inserting a line area into the table
         "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
        3. "TO idx" for specifying the end index when deleting a line
           area from or inserting a line area into the table
         "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
        At the time of the termination, the table contained 17008 lines.
    How to correct the error
        If the error occurred in your own ABAP program or in an SAP
        program you modified, try to remove 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:
        "TABLE_INVALID_INDEX" " "
        "J_1IEWT_CERT" or "J_1IEWT_CERT_F01"
        "FILTER_DATA"
        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".
    Tried searching for some SAP Notes to fix the issue, no success as of now, Please help me out...

    Have you checked these notes ?
    363107 Short dump occurs during TDS certificate printing.
      803806  Error while genrating TDS certificate 03.01.2005
      1066049  J1INCERT - Error while generating TDS certificate
    Regards,
    Subhash

  • 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

  • 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

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

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

  • Job in background is getting cancelled

    Hi Abapers,
    I have created the program to display data. It works fine when I execute it from SE38.
    But when I execute the same program in background, It gets cancelled.
    Can any one give me the reason & what can we do for this?
    Thanks,
    Hemal Shah

    Hi Hemanl ,
      Since you are executing the program ins background i assume that it is not an interactive ALV , so i would suggest you not to use a container on the screen and use the default screen provided by sap.
    Here is the steps you need to folllow
    1. Delete the Screen you created to display the ALV.
    2. As the screen in deleted so no custom container is required , hence remove the code to create the custom container .
    3: When you create grid object give the parent i.e. the parameter I_PARENT the value
        CL_GUI_CONTAINER=>SCREEN0 ,
    Rest of the coding with the gird as the original one .
    Make these changes and execute your program and see,
    Regards
    Arun

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

  • Background Jobs getting Cancelled

    Hi SRM Gurus
    we are working on SRM  4.0  and follow a classic scenarios.
    We have schedulled following background jobs
    1 BBP_GET_STATUS_2
    2 CLEAN_REQREQ_UP
    3 SMWP_BATCH
    Which were running successfully however from yesterday this all jobs are showing status cancelled.
    Can any one throw some light as to why this jobs are getting cancelled or how to check the reaons for the cancelling of jobs.
    regards,
    Nimish Sheth

    Hi Nimish,
    for how long where they running ?
    They might be cancelled because of time out (ex: R/3 system not available temporary).
    Do you have traces in SM21 in the same time fence ?
    Rgds
    Christophe

  • Background Job get Cancelled when executing the report. Reason?

    Hi All,
    I have scheduled a Back ground Job and executed Immediately.
    when checking transacion SM37 the job get canceled.
    How to find out the problem for the Job Cancellation.
    Regards,
    Viji

    hi
    After scheduling back ground job ( give a time laps of 2 min )
    then go to sm37 ( at this moment , the job is not yet started) .
    select ur job in sm 37 and when job starts processing , type JDBG as the command and press enter.
    Now it will go to the debugging screen, where u will find system program . Now set a break point at the stements used in ur program from the debugging screen itself.( menu - breakpoint- breakpoint at - statement ) and press F8 .
    Now you can start debug ur code.
    Revrt back if any issues.
    Regards,
    Naveen

  • EMIGALL Distributed Import Job for BP is getting cancelled in background

    Hi,
    When I'm restarting Distributed import and it's getting cancelled after some time with system error as "internal lock table overflow".
    I checked SM12 (while job was running) it's  showing 14,000 - 15,000 locks on table BUT000, even though EMIGALL is not updating that table as it's rerun of the old job. (Old job been cancelled due to network issue.).
    Can anybody please help me to understand why it's happening?
    Thanks in advance,
    Sagar

    Hi Sagar,
    I think I can explain what happened in your system:
    During data migration the application encountered many errors and does not release the locks immediately. Remember: it is not the slave jobs that creates locks but the called application (through the service functio module). If the application enncounters an error (also when the business object cannot be locked due to a lock table overflow) it returns the error and the load program writes it to the error log. The saved error message is not always directly related to the lock table overflow situation. Often it is saying: object already locked by user xxx).
    The master jobs uses also locks to block the configuration of its profile against concurrent access (exclusive access). If a user blocks the profile temporarily during an update of the profile, the master job waits until the update operation finishes. This last usually only very few ms. If the master encounteres a 'lock table overflow' situation it cancels - as designed be the developer.
    The simple solution is that you should avoid a lock table overflow situation and/or that the lock table must not be too small.
    Sagar,  I might also be that you find also the error 'lock table overflow' in the system log. Please check.
    Kind regards,
    Fritz

  • 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

  • Job getting cancelled with Tbale_illegal_statement dump

    hello,
    Hi Experts,
    i have a background job scheduled for a standard transaction SARA .it is getting cancelled and giving the following error:
    "TABLE_ILLEGAL_STATEMENT"
    Information on where terminated
    The termination occurred in the ABAP program "SAPLCKMLLAARCH" in
    "CKMLLA_INIT_READ".
    The main program was "RKSARCDL ".
    The termination occurred in line 253 of the source code of the (Include)
    program "LCKMLLAARCHF01"
    of the source code of program "LCKMLLAARCHF01" (when calling the editor 2530).
    The program "SAPLCKMLLAARCH" was started as a background job.
    The line it is giving Dump Is >       INSERT handle_tab.
    I have tried to debug the transaction but the execution is not ata all going to the program
    SAPLCKMLLAARCH where it is giving dump.Propably because that program is running in Background.
    So please let me know how I can fix this issue..Please

    Hi Prashanth,
    Were you able to resolve the issue ? Because, i am also facing the same problem, when I am triggering the Delete step for CO_CCMAST archiving object.
    Regards,
    Shail.

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

Maybe you are looking for

  • How do i disable bullets and lists in pages?

    pages is beautiful, but i have never been able to use it as my primary word processor for one simple reason.  I make staggered outlines constantly, and it ALWAYS tries to auto format them.  I've decided to try to make Pages my only word processor, bu

  • Videos not showing up on ipad

    videos are not showing up on ipad after syncing

  • Events in LSMW

    hi,    i was asked aboutthe  events in LSMW, pls if any one know , pls let me know thanks, bye

  • DMEE - Output in the required format

    Hi I need an output in this format: ........1........2........3........4........5........6.... 101 DEUT0797B CoCd    0905271433A094101DEUTSCHE BANK          Company Name         <CR/LF> 5200Company Name Payment Type      1         CCD     090527   1D

  • Errors during validation

    I am trying to burn using iDVD 6 but keep getting an "error during validation" message. There are no warnings in the map menu, and the dvd plays perfectly in preview. No matter what I do, I keep getting this message. Help!