Job Cancelled Problem

Hi Masters,
In SM37 I seen that 3 jobs were cancelled.
Pls see below:
======
Job started
Step 001 started (program RSSTAT1, variant &0000000002410, user name ALEREMOTE)
Log:Programm RSSTAT1; Request REQU_3ZAF2Q2IY0EE5RZCTYPE2FCAT; Status ; Action Start
Deleting/reconstructing indexes for InfoCube ZSRVPUR01 is not permitted
Deleting/reconstructing indexes for InfoCube ZSRVPUR01 is not permitted
Log:Programm RSSTAT1; Request REQU_3ZAF2Q2IY0EE5RZCTYPE2FCAT; Status @08@; Action Callback
Report RSSTAT1 completed with errors
Job cancelled after system exception ERROR_MESSAGE
How to investigate cancelled jobs under ALEREMOTE? How can i know this cancelled Job's request is assigned for what task.?
How to rerun a cancelled job? Pls tell steps.
Please suggest me.
Thanks,
BW26.

Hi,
it looks like you have an authority problem with aleremote. But anyway, did you check the syslog (sm21) or the dump overview (st22)? Are there any problems logged for the run time of the job?
regards
Siggi
PS: Have look here it might be of some help for you! /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Message was edited by: Siegfried Szameitat

Similar Messages

  • Job cancelled after system exception ERROR_MESSAGE in DB13

    Hello All,
    When i opened the t-code DB13 i saw that this job "Mark tables requiring statistics update" is cancelled.
    JOB LOG:
    12.02.2011  22:00:16  Job started
    12.02.2011  22:00:16  Step 001 started (program RSDBAJOB, variant &0000000000085, user ID 80000415)
    12.02.2011  22:00:18  Job finished
    12.02.2011  22:00:18  Job started
    12.02.2011  22:00:18  Step 001 started (program RSADAUP2, variant &0000000000081, user ID 80000415)
    12.02.2011  22:01:26  Error when performing the action
    12.02.2011  22:01:26  Job cancelled after system exception ERROR_MESSAGE
    When check for the BGD Job in SM37 for this job i found the same error in the job log with the status cancelled.
    Job log overview for job:    DBA!PREPUPDSTAT_____@220000/6007 / 22001700
    12.02.2011 22:00:18 Job started
    12.02.2011 22:00:18 Step 001 started (program RSADAUP2, variant &0000000000081, user ID 80000415)
    12.02.2011 22:01:26 Error when performing the action
    12.02.2011 22:01:26 Job cancelled after system exception ERROR_MESSAGE
    I couldn't find any logs in SM21 of that time also no dumps in ST22.
    Possible reason for this error:
    I have scheduled the job Check database structure (only tables) at some other time and deleted the earlier job which was scheduled during the bussiness hours which caused performance problem.
    So to avoid performance issue i scheduled this job in the mid night by cancelling the old job which was scheduled during the bussiness hours.
    And from the next day i could see this error in DB13.
    Rest all the backups are running fine but the only job getting cancelled is for "Mark tables requiring statistics update"
    Could anyone tell me what should i do to get rid of this error?
    Can i schedule this "Mark tables requiring statistics update" again by deleting the old one?
    Thanks.
    Regards.
    Mudassir Imtiaz

    Hello Adrian,
    Thanks for your response.
    Every alternate day we used to have performance issue at 19:00hrs.
    Then when i checked what is causing this problem, i discovered that there was a backup "Check Database Structure (tables only)" scheduled at this time and it was mentioned that this backup may cause performance issue.
    Then i changed "Check Database Structure (tables only)" the time of this backup to 03:00hrs.
    The next day when i checked DB13 i found that one of the backups failed.
    i.e. "Mark Tables Requiring Statistics Update"
    Then i checked the log which i posted earlier with the error: "Job cancelled after system exception ERROR_MESSAGE"
    I posted this error here and then i tried to delete the jobs scheduled i.e. "Mark Tables Requiring Statistics Update" and then re-schedule it at the same time and interval.
    And then it started working fine.
    So i just got curious to know the cause of the failure of that job.
    Thanks.
    Regards,
    Mudassir.Imtiaz
    P.S There is one more thing which i would like to say which is not related to the above issue, and m sorry to discuss this in this thread.
    I found a few Bottlenecks in ST04 with Medium and High priority.
    Medium: Selects and fetches selectivity 0.53%: 122569 selects and fetches, 413376906 rows read, 2194738 rows qualified.
    High: 108771 primary key range accesses, selectivity 0.19%: 402696322 rows read, 763935 rows qualified.
    There are a lot these.
    I would really appreciate if you tell me what is the cause for these Bottlenecks and how to resolve.
    Thanks a lot.

  • Background job cancelled , where as working fine in foreground

    Hi,
    In selection screen , I have a to provide a file name and execute the program.
    When I execute in foreground its working fine, but where are when I execute in background with variant it shows invalid file name and job cancelled in long text.
    Please suggest me what would be the problem and possible solution.
    Thanks,
    Ameer

    Hi Ameer,
    Add the following condition for running the prgram in Background.
    *****To upload file*********
    IF sy-batch = 'X'.  "-----> If backgroung execution option is selected.
    OPEN DATASET p_filename FOR INPUT IN TEXT MODE ENCODING DEFAULT.
    WHILE sy-subrc = 0.
          READ DATASET p_filename INTO wa_struc.
          APPEND wa_struc TO itab_struc.
    ENDWHILE.
    CLOSE DATASET p_filename .
    ENDIF.
    *****To download file*********
    IF sy-batch = 'X'.
       OPEN DATASET p_filename1 IN TEXT MODE FOR OUTPUT ENCODING DEFAULT.
       IF sy-subrc = 0.
        LOOP AT itab_struc INTO wa_struc.
          TRANSFER wa_struc TO p_filename1.
        ENDLOOP.
        CLOSE DATASET p_filename1.
      ENDIF.
    ENDIF.
    Hope this addresses your issue.
    Regards,
    Arnab

  • SAP_COLLECTOR_FOR_PERFMONITOR background job cancelled in SM37

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

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

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

  • Background job canceled in  Solution Manager system

    Dear all expert ,
    Two background jobs canceled in solution manager  system before some time.
    details-
    Background jobs :
                        1 -  LANDSCAPE FETCH
        Program name : RSGET_SMSY
    Job log : Job started
    Step 001 started (program RSGET_SMSY, variant ,
    The SLD server connection is inactive
    Job cancelled after system exception ERROR_MESSAGE
                       2 - SEND_SYSTEM_RELATIONSHIP_TO_SUP
        Program name : AI_SC_SEND_SYSTEM_RELATIONSHIP
    Job log :  
                       Job started
    Step 001 started (program AI_SC_SEND_SYSTEM_RELATIONSHIP, variant ,
    SOL determined as monitoring Solution Manager system
    SAP customer number unknown for installation number 0020606335
    Job cancelled after system exception ERROR_MESSAGE
    please help me , what should i do ?
    I am waiting for your positive response.
    Regards
    Shubh

    hi,
    You can try following ....
    For the job SEND_SYSTEM_RELATIONSHIP_TO_SUP
    Program : AI_SC_SEND_SYSTEM_RELATIONSHIP
    1. Up to Support Package 09:
    a) Start transaction SMSY.
    b) Choose Shft+F5.
    c) Select the system named in the message.
    d) Choose F6.
    e) Select the "System Data in SAP Support Portal" tab.
    f) Using the input help, fill the system number field with the correct system.
    g) Save the data.
    2. Up to and including Support Package 08:
    a) Start transaction SOLMAN_CONNECT.
    b) Select the system in question in the ID field and choose the filter pushbutton.
    c) Select the system and select "Create configuration".
    d) Fill the system number field using the input help with the correct system.
    e) For example, select the "BW GUI Connection" service type.
    f) Carry out all of the subsequent steps of the Configuration Assistant until you see the "Finish" pushbutton.
    This establishes a unique relationship between your system in the Solution Manager and the system number in the SAP Support Portal. Problems no longer occur with this system when the SEND_SYSTEM_RELATIONSHIP_TO_SUPP job is next run. However, the problem may still exist for other systems (in these cases, you should follow the same steps).
    Hope this will help to solve your issue..
    Regards
    Bhuban
    RKFL

  • Back ground job cancelling

    Hello Everyone,
    Our scheduled background job cancel each time in job log log it gives this error message:
    ""ABAP/4 processor: TSV_TNEW_BLOCKS_NO_ROLL_MEMORY"".
    This is a ABAP Memory Message.
    I went into ST22 and saw the error message. System is not able to allocate memory to the data selected from the table( No roll storage space of length 3178504 available for internal storage.). Probably i need increase the roll memory of our server, i think this will done by basis people.or  Alternatly i can process the data by small packets like 1000 records every time.
    So i can i know how can i process the data by small packets like 1000 records every time.
    Need your help.
    Thanks,
    Lasya.

    Hi
    If you can divide the data into two internal tables and later collect into the one internal table, this could solve yuor problem.
    Also you need to make sure that enough memory is available in the system. Check DB6cockpit for that.
    Also there are a lot of correction notes available with SAP for the error"TSV_TNEW_BLOCKS_NO_ROLL_MEMORY"
    Check what the job exactly does, and search for the relevant notes, as there are different notes for different application areas...
    if its a loading job(Infopackage) you can reduce the data packet size of the IP, but that might hamper the loading performance.
    Hope this helps
    Regards
    Shilpa

  • All my B/G job canceling due to dump: TSV_TNEW_PAGE_ALLOC_FAILED

    Hi SAP Gurus,
    Production system SAP R/3 Enterprice. 4.7
    OS:AIX 5.3
    DB:DB2
    memory Parameters are already set properly, there was no issues from past 3 years, We din't change any parameter recently.
    All my Pay run B/G job canceling due to dump: TSV_TNEW_PAGE_ALLOC_FAILED
    B/G job log
    ================
    11/26/2007     03:01:22     Job started
    11/26/2007     03:01:22     Step 001 started (program RBDSER01, variant YBD40_01, user ID BC-BATCH)
    11/26/2007     03:01:22     0 master IDocs set up for message type CHRMAS
    11/26/2007     03:01:22     0 communication IDoc(s) generated for message type CHRMAS
    11/26/2007     03:01:23     0 master IDocs set up for message type CLSMAS
    11/26/2007     03:01:23     0 communication IDoc(s) generated for message type CLSMAS
    11/26/2007     03:01:23     0 master IDocs set up for message type CLFMAS
    11/26/2007     03:01:23     0 communication IDoc(s) generated for message type CLFMAS
    11/26/2007     03:05:53     ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
    11/26/2007     03:05:54     Job cancelled
    Please let me know ASAP,
    Thanks & Regards,
    Kishore.
    null

    Hi,
    If you did'nt change anything in the system, you'd better open a SAP support call urgently as it is a production problem...
    >>>Production system SAP R/3 Enter<b>price</b>. 4.7
    Nice and well choosen typo !  
    Regards,
    Olivier

  • Custom Background Job Cancelling

    Hi Folks,
    I'm working on a custom development and I'm experiencing some trouble - I would greatly appreciate any help / effort from anyone in providing me with some ideas as to what the cause may be.
    Basically my development is made up of two parts - Part 1) A custom RFC used to trigger a custom program in the background - here i'm using job_open / submit program / job_close. This works fine and a job is successfully created to run the custom program
    Part 2) - The custom program, running in the background job tries to create a background job  to trigger standard program (f.05) with a variant. Again using job_open / submit program / job_close. However on this occassion when the second background job starts it cancels immediately -  stating "Make an entry in all required fields". . However the variant is fine and all the parameters for the standard program are filled. I can even trigger this program and variant seperately and it works.
    Are there conflicts in creating a background job from a background job ? I'm confused as to why this is not working and i would appreciate any help or ideas anyone could give me on this.
    Thanks alot for your time.
    Regards
    DK
    Overview
    RFC -> Create Background Job # 1 -> Background Job # 1 created successfully - Custom program running in Background Job # 1 tries to run standard program in backgroun - Background Job # 2 created successfully but immediately cancels - Job log message - "Make an entry in all required fields". Job cancelled after system exception ERROR_MESSAGE.

    Hi Guys,
    Thanks for your answers. The job log does say "Make an entry in all required fields" - but all the required fields are specified under the variant. I can even run this program with the same variant with no problems. I'm wondering what would affect the submit to program to prevent it passing the variant correctly - here is my submit
        SUBMIT sapf100 VIA JOB l_jobnam NUMBER l_jobcnt
        USING SELECTION-SET l_vari
        AND RETURN.
    l_vari = Variant Name
    l_jobname = job name
    l_jobcnt  = job count
    here is the message from the job log. your help is appreciated - thanks
    10.09.2009 14:22:18 Job started                                                             
    10.09.2009 14:22:18 Step 001 started (program SAPF100, variant &0000000000018, user ID XXXX)
    10.09.2009 14:22:18 Make an entry in all required fields                                    
    10.09.2009 14:22:18 Job cancelled after system exception ERROR_MESSAGE

  • RSCRM_BAPI job cancel

    Hi guys!! I'm trying to execute RSCRM_BAPI (table mode) and I'm trying to execute it in background but the job cancel and no data is loaded to the specified table. When I execute the query in dialog mode, everything is ok and data is retrieved to the screen. When I go to the batch monitor the status is red, but in the details no information appears. Can you help me? Someone had this problem before? I'm using SAP_BW 7 with level 15.
    Thank you very much for your help.

    Hello Sergio,
    Please look at this forum
    Need to run a BW query in the background
    Thanks
    Chandran

  • Backgroung job cancelled with the error-Homogenous Lock

    Hi All,
    We have a custom report ( customer update )which is scheduled to run in the background. In the production system, the job gets cancelled and when we check the log We have the following messages:
    20.10.2010 07:14:17 Job started                                                                               
    20.10.2010 07:14:17 Customer 10372118 has been updated                                                               /DS1/A         411          S
    20.10.2010 07:14:17 Object requested is currently locked by user XXXX                                                MC           601          E
    20.10.2010 07:14:17 Job cancelled after system exception ERROR_MESSAGE     
    Because of the message"Object requested is currently locked by user xxxx( Homogenous lock ), the job gets cancelled.
    Enqeue and deqeue have been taken care correctly.
    This problem is reported recently...before that it was working fine.
    Have checked SM12, there is no lock. While debugging this error is not reported.
    Now please let me know how to know the cause of the error.
    Edited by: swarupa.mayflower on Oct 20, 2010 10:45 AM

    Hi Immanuel,
    I tried opening the customer which I am trying to update in the change mode and then tried debugging the job then it gives me an error message at the bottom of the screen, in this case when I go check there is a lock in SM12.
    But my problem is I get this message in the job log and not at the bottom of the screen because of this message(error) the job gets cancelled. Also there is no lock in SM12 in this case and while debugging also I am not getting this message anywhere....
    This type of lock is called homogenous lock....but I donno how to trace this error .....

  • BWREMOTE background job canceled in sap r/3 system

    Hi my friends,
    Thanks for your help ahead.
    Today I checked the background job in SAP R/3 created by BWREMOTE via SM37. It showed me some jobs had been canceled.
    I displayed its log, the detail message is:
    ==========================================
    Step 001 started (program SBIE0001, variant &0000000083494, user name BWREMOTE)
    DATASOURCE = ZQM_NOT_SHFGRP
    Call up of customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 1,593 records
    Result of customer enhancement: 1,593 records
    Call up of customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 1,593 records
    ABAP/4 processor: SAPSQL_INVALID_FIELDNAME
    Job cancelled
    ==========================================
    Then I displayed the "Long Text" of the job log. It is
    One of the field names in the SELECT clause was not recognized.
    Error analysis
    The SELECT clause was specified in an internal table at runtime.
    It contains the field name "TPR00", but this does not occur in any of
    the database tables listed in the FROM clause.
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "SAPLXRSA " in
    "EXIT_SAPLRSAP_001".
    The main program was "SBIE0001 ".
    Source code extract
    008840 concatenate 'TPR'
    008850 day_temp+6(2)
    008860 ' = '
    008870 ' ''' zshift '''' into
    008880 cond .
    008890 append cond to itab .
    008900 select schkz into i_not_shfgrp-zzschkz from t552a
    008910 where zeity = '2'
    008920 and mofid = 'CN'
    008930 and mosid = '28'
    008940 and ( schkz = 'SFTA' or
    008950 schkz = 'SFTB' or
    008960 schkz = 'SFTC' or
    008970 schkz = 'SFTD' )
    008980 and kjahr = day_temp+0(4)
    008990 and monat = day_temp+4(2)
    > and (itab) .
    009010 endselect.
    I guess that there is not a field named TPR00 in table t552a.
    Next, I opened the 'project management of sap enhancement' via CMOD, entering the project name and chosing 'Display'.
    Then Double click the Components 'EXIT_SAPLRSAP_001', we can see the function module 'EXIT_SAPLRSAP_001'. In the source codes, there is an include program, it is 'INCLUDE ZXRSAU01.'.
    Then, I double clicked the Include program and find the position program terminated. The source codes are:
    ZQM_NOT_SHFGRP *
    when 'ZQM_NOT_SHFGRP'.
    loop at c_t_data into i_not_shfgrp .
    l_tabix = sy-tabix .
    clear :mbatch ,zshift,cond ,zfield, zcharg, day_temp .
    refresh itab.
    if i_not_shfgrp-ausvn is initial.
    else.
    aa = '080000'.
    bb = '160000'.
    cc = '235959'.
    day_temp = i_not_shfgrp-ausvn.
    if i_not_shfgrp-auztv ge aa and
    i_not_shfgrp-auztv lt bb .
    zshift = 'MSHF' .
    elseif i_not_shfgrp-auztv ge bb and
    i_not_shfgrp-auztv le cc .
    zshift = 'LSHF'.
    else .
    zshift = 'NSHF'.
    day_temp = i_not_shfgrp-ausvn - 1.
    endif.
    concatenate 'TPR'
    day_temp+6(2)
    ' = '
    ' ''' zshift '''' into
    cond .
    append cond to itab .
    select schkz into i_not_shfgrp-zzschkz from t552a
    where zeity = '2'
    and mofid = 'CN'
    and mosid = '28'
    and ( schkz = 'SFTA' or
    schkz = 'SFTB' or
    schkz = 'SFTC' or
    schkz = 'SFTD' )
    and kjahr = day_temp+0(4)
    and monat = day_temp+4(2)
    and (itab) .
    endselect.
    endif.
    I found that we got a TPR00 during concatenation. In other words, day_temp+6(2) = 00. But I think it is impossible. I can not explain this.
    Any ideas, my friends. Many thanks.

    select schkz into i_not_shfgrp-zzschkz from t552a
    where zeity = '2'
    and mofid = 'CN'
    and mosid = '28'
    and ( schkz = 'SFTA' or
    schkz = 'SFTB' or
    schkz = 'SFTC' or
    schkz = 'SFTD' )
    and kjahr = day_temp+0(4)
    and monat = day_temp+4(2)
    <b>and (itab) .</b>  => doesn't make sense?!
    endselect.
    endif.
    it seems something got deleted between 'and' and '(itab)'... so, you'll have to recheck the requirements for your select to fill the 'and' statement further.
    so, it should look like
    and monat = day_temp+4(2)
    and <b><some kind of condition that needs to be fulfilled></b>.
    endselect.
    <b><some logic to fill a line in your internal table></b>.
    append cond to itab.
    endif.
    obviously <some kind of condition that needs to be fulfilled> needs to be replaced by a real condition
    and <some logic to fill a line in your internal table> needs to be replaced by some kind of formula
    I assume something like (otherwise it would be really weird to select that field):
    cond = i_not_shfgrp-zzschkz.
    or a formula using the i_not_shfgrp-zzschkz field.
    It would also be a lot better to replace your select ... endselect by a select single as you'll be selecting 1 record only anyways.
    Message was edited by:
            RafB

  • Job cancelled While loading data from DSO to CUBE using DTP

    Hi All,
      while i am loading data frm DSO to CUBE the job load is getting cancelled.
    in the job overview i got the following messages
        SYST: Date 00/01/0000 not expected.
       Job cancelled after system exception ERROR_MESSAGE
    wt can be the reason for this error as i have successfully loaded data into 2 layers of DSO before loading the data into the CUBE

    hi,
    Are u loading the flat file to DSO?
    then check the data in the PSA in the date field and replace with the correct date.
    i think u r using write optimised DSO which is similar to PSA it will take all the data from PSA to DSO.
    so clear the data in PSA and then load to DSO and then to CUBE.
    If u dont need a date field in CUBE then remove the mapping in transformation in cube and activate and make DTP activate and trigger it it will work.

  • Job cancelled after system exception ERROR_MESSAGE

    Hello all
    I am facing the following issue.
    A custom report is schedulled and run as backround job. The report should create a txt file on server.
    The report works fine in foreground, but as backround job ends up cancelled all the time.
    The job log:
    Job log overview for job:    VI5 / 13072800
    Date       Time     Message text                                                                     Message class Message no. Message type
    27.03.2009 13:09:28 Job started                                                                           00           516          S
    27.03.2009 13:09:28 Step 001 started (program ZESSRIN110R, variant PR1_0000381, user ID METAPARTNER)      00           550          S
    27.03.2009 13:09:28 File creation ERROR:                                                                  00           001          E
    27.03.2009 13:09:28 Job cancelled after system exception ERROR_MESSAGE                                    00           564          A
    There is no info in SM21 regarding the error.
    Can anybody help with this?
    Thanx in advance.
    imi
    Edited by: Imrich Vegh on Mar 27, 2009 2:27 PM

    btw the part of my code  looks like this:
    server path check
        IF p_srv IS NOT INITIAL.
          OPEN DATASET gv_server FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
          IF sy-subrc EQ 0.     --- I keep receiving 8 here in BACKGROUND JOB
            WRITE : / text-077,  gv_server.
          ELSE.
            MESSAGE text-069 TYPE 'E'.
          ENDIF.

  • Job Cancelled with an error "Data does not match the job def: Job terminat"

    Dear Friends,
    The following job is with respect to an inbound interface that transfers data into SAP.
    The file mist.txt is picked from the /FI/in directory of the application server and is moved to the /FI/work directory of application server for processing. Once the program ends up without any error, the file is moved to /FI/archive directory.
    The below are the steps listed in job log, no spool is generated for this job and it ended up with an error "Data does not match the job definition; job terminated".Please see below for more info.
    1.Job   Started                                                                               
    2.Step 001 started (program Y_SAP_FI_POST, variant MIST, user ID K364646)                           
    3.File mist.txt copied from /data/sap/ARD/interface/FI/in/ to /data/sap/ARD/interface/FI/work/.
    4.File mist.txt deleted from /data/sap/ARD/interface/FI/in/.                                   
    5.File mist.txt read from /data/sap/ARD/interface/FI/work/.                                    
    6.PD-DKLY-Y_SAP_FI_POST: This job was started periodically or directly from SM36/SM37 (Message Class: BD, Message Number : 076)  
    7.Job PD-DKLY-Y_SAP_FI_POST: Data does not match the job definition; job terminated (Message Class : BD, Message No. 078)    
    8.Job cancelled after system exception
    ERROR_MESSAGE                                                
    Could you please analyse and come up about under what circumstance the above error is reported.
    As well I heard that because of the customization issues in T.Code BMV0, the above error has raised. 
    Also please note that we can define as well schedule jobs from the above transaction and the corresponding data is stored in the table TBICU
    My Trials
    1. Tested uplaoding an empty file
    2. Tested uploading with wrong data
    3. Tested uploading with improper data that has false file structue
    But failed to simulate the above scenario.
    Clarification Required
    Assume that I have defined a job using BMV0. Is that mandatory to use the same job in SM37/SM36 for scheduling?
    Is the above question valid?
    Edited by: dharmendra gali on Jan 28, 2008 6:06 AM

    Dear Friends,
    _Urgent : Please work on this ASAP _
    The following job is with respect to an inbound interface that transfers data into SAP.
    The file mist.txt is picked from the /FI/in directory of the application server and is moved to the /FI/work directory of application server for processing. Once the program ends up without any error, the file is moved to /FI/archive directory.
    The below are the steps listed in job log, no spool is generated for this job and it ended up with an error "Data does not match the job definition; job terminated".Please see below for more info.
    1.Job Started
    2.Step 001 started (program Y_SAP_FI_POST, variant MIST, user ID K364646)
    3.File mist.txt copied from /data/sap/ARD/interface/FI/in/ to /data/sap/ARD/interface/FI/work/.
    4.File mist.txt deleted from /data/sap/ARD/interface/FI/in/.
    5.File mist.txt read from /data/sap/ARD/interface/FI/work/.
    6.PD-DKLY-Y_SAP_FI_POST: This job was started periodically or directly from SM36/SM37 (Message Class: BD, Message Number : 076)
    7.Job PD-DKLY-Y_SAP_FI_POST: Data does not match the job definition; job terminated (Message Class : BD, Message No. 078)
    8.Job cancelled after system exception
    ERROR_MESSAGE
    Could you please analyse and come up about under what circumstance the above error is reported.
    As well I heard that because of the customization issues in T.Code BMV0, the above error has raised.
    Also please note that we can define as well schedule jobs from the above transaction and the corresponding data is stored in the table TBICU
    My Trials
    1. Tested uplaoding an empty file
    2. Tested uploading with wrong data
    3. Tested uploading with improper data that has false file structue
    But failed to simulate the above scenario.
    Clarification Required
    Assume that I have defined a job using BMV0. Is that mandatory to use the same job in SM37/SM36 for scheduling?
    Is the above question valid?

Maybe you are looking for