Job msg 608: job set to cancelled manually

hi all,
there is dtp from dso to cube(full load) which has failed with job log : job set to cancelled manually and the msg 608.
i couldnt find any locks, short dump etc.This is background job and there is no info. in sm21.
when i try to debug (from dtp monitor screen) the data is fine.there was a kernel update .
what can be the reason and how to fix it?
will the bg job info be seen in sm21?(as i dont see any info abt the background job in sm21)
Edited by: jumboash on Nov 24, 2009 6:48 AM

Hi,
check in Transaction SM36 and let me know the details
Regards,
Marasa.

Similar Messages

Job SWWDHEX by WF-BATCH getting cancelled

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.

Hi.
Please check the note # 987978
1321773 - RSWWDHEX: Runtime error GETWA_NOT_ASSIGNED
Regards
Gangadhar
Edited by: gangadhar hm on Sep 9, 2009 2:49 PM

Each target assigned to a job must have a setting and destination.

Simple. Basic Question.
Trying to use Compressor to change the codec on my flip cam to make it more compatible with FCP X.
I have dragged a source and destination into the batch. But it keeps giving me the error "Each target assigned to a job must have a setting and destination." I saw others had this same issue and the solution I saw was to set a destination for the video AND audio. How do you assign for BOTH? I thought it was just a drag and drop method into batch ...

You didn't say what your settings were. But tif it's not one of the DVD presets, you shouldn't ordinarily be faced with separate audio and video streams with the majority of presets. Here's an example of a batch with one source file, multiple targets and multiple destinations. Only the DVD Preset has separate audio and video…and those do require that destinations be specified. If the destination is not specified, it defaults to Source.
Good luck.
Russ

Script to find Jobs in a Request Set having incompatibilities

All,
Could anyone please share - Script to find Jobs in a Request Set having incompatibilities.
Working on R12.1.1
DB:11.1.0.7
Thanks for your time and help!
Regards,

Could anyone please share - Script to find Jobs in a Request Set having incompatibilities.Please see this thread -- Re: incompatibilities table
Thanks,
Hussein

Delete messages with "Cancelled Manually" state (MSGSTATE is 21)?

Hello,
I want to delete messages from master table SXMSPMAST which are in "Cancelled Manually" state i.e. the value of field MSGSTATE is 21.
I have tried running reports "RSXMB_ARCHIVE_MESSAGES" and "RSXMB_DELETE_ARCHIVED_MESSAGES" but with no success. the vlaue of the field ITFACTION is ARCH.
Can anyone guide me how do i delete these messages?
thanks,
Yash

Hi Yash,
in productive sysems the messages with status 21 can not be deleted by the regular deletion report, it has to be archived first and then will be deleted by the archive job itself. so you have to configure archiving.
for non productive systems you can set the parameter ARCHIVE->PERSIST_ARCH_MANUAL_CHANGES to delete the manually changed messages, afterwards it will be deleted by the regular deletion job.
please check the SAP note 872388.
manually cancelled or manually changed messages (status 019 and 021) have to be archived. Therefore you always have to configure archiving to handle manually edited messages. Should you decide (for non-productive systems only) that you would like to delete these manually cancelled messages, please refer to Note 820149
Thanks,
Francis

Problems creating background job for program (job open, submit and close)

Hi gurus,
im trying to start a background job using the FM BP_START_DATE_EDITOR to show the start date to the job or if it's imediate. this FM it's working fine, after call it im opening a job, submiting it and call the job close FM and the job close FM creates me the job.
The problem it's when i go to the sm37 to see the job status the job has been canceled, and the job log says that i have to give a start date to the job.
What i dont understand it's either the job is imediate or i choose a date to start the job always gives me this error...
Below goes my code,
any ideas will be rewarded
CLEAR: stdt_modify_type, stdt_output.
CALL FUNCTION 'BP_START_DATE_EDITOR'
       EXPORTING
            stdt_dialog                    = 'Y'
            stdt_input                     = stdt_input
            stdt_opcode                    = 14
       IMPORTING
            stdt_modify_type               = stdt_modify_type
            stdt_output                    = stdt_output
       EXCEPTIONS
            fcal_id_not_defined            = 1
            incomplete_last_startdate      = 2
            incomplete_startdate           = 3
            invalid_dialog_type            = 4
            invalid_eventid                = 5
            invalid_opcode                 = 6
            invalid_opmode_name            = 7
            invalid_periodbehaviour        = 8
            invalid_predecessor_jobname    = 9
            last_startdate_in_the_past     = 10
            no_period_data_given           = 11
            no_startdate_given             = 12
            period_and_predjob_no_way      = 13
            period_too_small_for_limit     = 14
            predecessor_jobname_not_unique = 15
            startdate_interval_too_large   = 16
            startdate_in_the_past          = 17
            startdate_is_a_holiday         = 18
            startdate_out_of_fcal_range    = 19
            stdt_before_holiday_in_past    = 20
            unknown_fcal_error_occured     = 21
            no_workday_nr_given            = 22
            invalid_workday_countdir       = 23
            invalid_workday_nr             = 24
            notbefore_stdt_missing         = 25
            workday_starttime_missing      = 26
            no_eventid_given               = 27
            OTHERS                         = 28.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    MOVE 'X' TO gv_flag.
ENDIF.
DATA jobname LIKE tbtcjob-jobname.
DATA jobcount LIKE tbtcjob-jobcount.
DATA job_release LIKE btch0000-char1.
DATA job_imediate TYPE c.
CLEAR: jobname, jobcount, job_release.
CONCATENATE 'MAPAEXEC' sy-uname sy-datum
               INTO jobname SEPARATED BY space.
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            jobname          = jobname
       IMPORTING
            jobcount         = jobcount
       EXCEPTIONS
            cant_create_job = 1
            invalid_job_data = 2
            jobname_missing = 3
            OTHERS           = 4.
IF sy-subrc <> 0.
    MESSAGE i003(zmapas).
    EXIT.
ENDIF.
SUBMIT z_mapa_execucao_orcamental
         VIA JOB jobname NUMBER jobcount
         WITH ano EQ ano
         WITH so_perio IN so_perio
         WITH so_date IN so_date
         WITH so_org EQ so_org
         WITH so_num IN so_num
         AND RETURN.
IF stdt_output-startdttyp EQ 'I'.
    CLEAR job_imediate.
    job_imediate = 'X'.
ENDIF.
CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
            calendar_id                 = stdt_output-calendarid
            event_id                    = stdt_output-eventid
            event_param                 = stdt_output-eventparm
            event_periodic              = stdt_output-periodic "?
            jobcount                    = jobcount
            jobname                     = jobname
            laststrtdt                  = stdt_output-laststrtdt
            laststrttm                  = stdt_output-laststrttm
            prddays                     = stdt_output-prddays "??
            prdhours                    = stdt_output-prdhours "?
            prdmins                     = stdt_output-prdmins "??
            prdmonths                   = stdt_output-prdmonths
            prdweeks                    = stdt_output-prdweeks "?
            predjob_checkstat           = stdt_output-checkstat
            pred_jobcount               = stdt_output-predjobcnt
            pred_jobname                = stdt_output-predjob
            sdlstrtdt                   = stdt_output-sdlstrtdt
            sdlstrttm                   = stdt_output-sdlstrttm
            strtimmed                   = job_imediate
            targetsystem                = stdt_output-instname
            start_on_workday_not_before = stdt_output-notbefore
            start_on_workday_nr         = stdt_output-wdayno
            workday_count_direction     = stdt_output-wdaycdir
       IMPORTING
            job_was_released            = job_release
       EXCEPTIONS
            cant_start_immediate        = 1
            invalid_startdate           = 2
            jobname_missing             = 3
            job_close_failed            = 4
            job_nosteps                 = 5
            job_notex                   = 6
            lock_failed                 = 7
            OTHERS                      = 8.
IF sy-subrc <> 0.
    MESSAGE i003(zmapas).
    EXIT.
ELSE.
    MESSAGE i004(zmapas) WITH jobname.
ENDIF.
Thanks in advance,
Best Regards
João Martins

Hello João.
In debug mode, check the value of variables you passed to parameters sdlstrtdt and sdlstrttm.
As aditional info, I usually achieve your goal without FM BP_START_DATE_EDITOR.
Check this code:
CALL FUNCTION 'JOB_OPEN'
      EXPORTING
           jobname          = w_jobname
      IMPORTING
           jobcount         = w_jobcount
      EXCEPTIONS
           cant_create_job = 1
           invalid_job_data = 2
           jobname_missing = 3
           OTHERS           = 4.
CHECK sy-subrc = 0.
CLEAR seltab_wa.
MOVE: t_jobs-param TO seltab_wa-selname,
t_processar-line+34 TO seltab_wa-low.
APPEND seltab_wa TO seltab.
seltab_wa-selname = 'P_LOJA'.
seltab_wa-low = t_processar-ficheiro+7(4).
APPEND seltab_wa TO seltab.
*** Submete o programa para o JOB
SUBMIT (t_jobs-repid)
WITH SELECTION-TABLE seltab
USER sy-uname
   VIA JOB w_jobname NUMBER w_jobcount
   AND RETURN.
*** Encerra o JOB
l_hora = sy-uzeit.
ADD 60 TO l_hora.
CALL FUNCTION 'JOB_CLOSE'
   EXPORTING
      jobcount           = w_jobcount
      jobname           = w_jobname
      sdlstrtdt            = sy-datum
      sdlstrttm           = l_hora
      targetserver       = w_servidor
   IMPORTING
      job_was_released     = l_liberado
   EXCEPTIONS
      cant_start_immediate = 1
      invalid_startdate    = 2
      jobname_missing      = 3
      job_close_failed     = 4
      job_nosteps          = 5
      job_notex            = 6
      lock_failed          = 7
      OTHERS               = 8.
Regards.
Valter Oliveira.

Unable to schedule a job from the Jobs Library

Hi,
I have created and stored a job in the Job Library, however when I try and submit it to run with a schedule and against specified targets Grid just seems to hang, and eventually it comes back with "Application server is not responding". I have set it up as a sql script and used a PL/SQL block, I have tested the script outside of Grid and it works fine. I have tried using prefered credentials and override credentials, but this makes no difference.
I am running OEM 10g Release 3 on Red Hat Enterprise Linux AS release 4 (Nahant Update 4)
Anybody had anything similar?

Thanks for the reply. Tested connectivity to both databases from Grid all looks good. Attempted to set up a job individually for each db and it hung on both, again I tried using default credentials and override credentials.

JSM - Creating Job Documentation from Job Request itself

Hi all,
I am still exploring JSM, and I know its possible to create Job Request (Job Req) from Job Documentation (Job Doc).
But is it possible to create the reverse (Job Doc from Job Req) ?
This will be great, if the user is creating Job Req from "Detailed" version (compared to "Basic"), which has similar entries and tabs, as Job Doc.
I did read somewhere that its possible, but I never find any documentation or SCN/blogs on this.
Thanks in advance
Regards
Shahul

This was answers below, in the comment area by Volker.
How to configure SAP's standard Job Request form - Part 2
Hi Shahul,
the user triggers the Job Doc creation from within the Incident or Change Request in the JSM assignment block, but then the data from teh Job Request is automatically taken over for the Job Document.
So starting the creation and pushing the save button is manual work, but the filling out the Job Doc is done automatically.
Kind Regards
Volker
Regards
Shahul

Restart a process or message in SXMB_MONI with status "Cancelled Manually"

SDN Crew,
This is query regarding the BPM process.
I have cancelled a process in MONI manually, Now i want to restart the process...
If i try to restart the process, it throws an error "only messages with error could be restarted and messages already processed or cancelled could not be resatarted".
How to solve the issue?
and also i want to restart the process because though i set the Poll interval in the Send Comm Channel as 60 sec, it processed only one message and that to in error(which i cancelled manually) no furthur processing is done i mean if u check for processed messages only one message is shown but it has to show similar error messages for every 60 sec?
i am new to BPM so could someone tell lme if i am doin gsomewhere wrong?

hi,
its posible,
take a look of this blog
/people/michal.krawczyk2/blog/2005/11/09/xi-restarting-successfully-processed-messages
Thanks
Rodrigo
ps:reward points if useful

SAP Scheduler. Multiple jobs for one job definition issue.

Hi.
I am facing one problem concerning scheduling jobs. I've created a job definition and deployed it on server. In onJob(...) method system queries to DB for a single result, when this result matches some conditions job is finished, otherwise it waits for a minute and then queries again. Then I tried to create several tasks for this job definition and set similar execution time for all tasks to check their simultaneous behavior. I was surprised to find out that only one job status is 'RUNNING' and for others status is 'STARTING'. But I expected to see all my jobs in status 'RUNNING'. At first I thought the problem was in MDB pool stuff(e.g. InitialSize of beans or something like that), supposing that there is only one working bean and huge queue of messages. But nothing changed after setting different values for pool params.
So, can anyone help me to make at least 2 simultaneous working jobs for one job definition, if it possible, off cause. Or may be I am wrong somewhere. (By the way, I used Threads in MDB for waiting).
Thanks in advance.

May be I described my problem rather messy. The main question is it possible to create several jobs for one job definition and see them running at the same time (simultaneously)?
Thanks.

DBMS_JOB.RUN: cannot run a job from a job

I'm trying to set up a job to automatically run every October 1st. The "submit" part of this job is pretty simple, but I am getting some errors on the "run" part:
declare
job_nbr binary_integer;
BEGIN
dbms_job.submit(job => job_nbr,
          what => 'RESET_ORDER_NBR_SEQ;',
          next_date => to_date('10/1/2008', 'mm/dd/yyyy'),
          interval => 'add_months(sysdate,12)');
dbms_job.run(job_nbr);
COMMIT;
END;
When I run this script, I get the following error: "ORA-32317: cannot run a job from a job". I know this is due to the dbms_job.run because I don't get the error when I comment this line out. Also, even when I moved the dbms_job.run into its own script (and even hard-coded the job_nbr, so the dbms_job.run was the only line in the script), it still gave me the same error. This is working in SQL Developer when but not in Application Express. It seems to be something specific to the "run", since "submit" and "remove" work fine. Has anyone had any problems like this?

MBETTIS,
Rather than including dbms_job.run in your PL/SQL block, why don't you just schedule the job to run via next_date?
Also, the interval will be computed after the job successfully executes. So if your job takes 5 minutes to run, the value of SYSDATE in your interval may "slide" after each execution. Consider using some form of TRUNC against the SYSDATE in your interval if you want to achieve a consistent execution time.
Joel

Report Job Server - Maximum Jobs Allowed

BOE XI.2
We would like to increase our simultaneous report jobs per Report Job Server. We currently have 4 CPUs and the Deployment and Configuration Guide says the 'Supported Load' is 5 reports per CPU so we should only run 20 reports simultaneously. Our CPU usage is very low and we'd like to increase the Maximum Jobs Allowed on the Job Servers, but I don't know what the consequences would be to our servers. Has anyone gone above the 'Supported Load' numbers for simultaneous report jobs per Report Job Server? How high could I go without having problems?

Hi Eileen
There is no definite answer on this. The Maximum Jobs Allowed setting depends very much on your environment. If you have reports that run quickly you could increase it. Also, do you have a high concurrency of jobs? The fact that the CPU time is low means either that your Job Server (CR, DeskI) or Web Intelligence Report Server (WebI) is waiting for results from the database OR that there are simply no reports or not even 1 report per Job Server to process at this time. If you run 1 report and you see 25% CPU usage in the task manager on a quad core machine, means that the Job Server uses up the resources on one core fully.
Regards
Roland

Broken jobs and failed jobs

hi all..
please tell me difference between broken jobs and failed jobs
thanks

Please refer documentation .
Failed Jobs
If a job has the status of FAILED in the job table, it was scheduled to run once but the execution has failed. If the job was specified as restartable, all retries have failed.
If a job fails in the middle of execution, only the last transaction of that job is rolled back. If your job executes multiple transactions, you need to be careful about setting restartable to TRUE. You can query failed jobs by querying the SCHEDULERJOB_RUN_DETAILS views.
Broken Jobs
A broken job is one that has exceeded a certain number of failures. This number is set in max_failures, and can be altered. In the case of a broken job, the entire job is broken, and it will not be run until it has been fixed. For debugging and testing, you can use the RUN_JOB procedure.
You can query broken jobs by querying the SCHEDULERJOBS and SCHEDULERJOB_LOG views.
Regards
Renjith Madhavan

Difference between batch job and Background Job

Hi Forum,
Can anyone distinguish between batch job and background job for me please ?
SK

Hi,
Batch Job:
A batch job is a process that runs in the background, often deferred and unattended, to process data in groups (batch) rather than by individual transactions (e.g. a monthly phone bill rather than a bill for each individual phone call). A batch job executes a sequence of programs and technical instructions that are stored in a command file. Progress and error messages are output to a log file allowing users to determine, at any time, if the batch job completed successfully or identify the cause of the problem. Because batch jobs run in the background they are less visible to the end user.
In a business-computing context, batch job scheduling implies the automatic execution of background tasks (batch jobs) at pre-determined points in time (e.g. every day at 8pm, midday on Wednesday).
3 types of batch job scheduling can be distinguished: native, basic and advanced batch job scheduling.
Most operating systems and some business solutions software come equipped with native batch job scheduling tools that provide a limited service (e.g. Windows Scheduled Tasks, UNIX crontab, SAP CCMS) locally to each installation. However, business processes may span multiple platforms, applications, countries and companies. Their complexity may require much more functional power as provided by basic batch job scheduling including national and regional variations in the working calendar, sequence variations according to the day of the month, triggering of jobs by the successful completion of preceding jobs, elimination of gaps and reduced batch windows. Major benefits of basic batch job scheduling are enhanced productivity, operations reliability and cost-reduction. For e-business applications that require real-time processing, the distance between interactive individual processing and batch processing tends to decrease. Advanced batch job scheduling can handle these advanced requirements: event-driven scheduling for a real-time synchronization with interactive processing, just-in-time scheduling to run operations as soon as possible, cross-platform and cross application services for the entire IT landscape, real-time overall monitoring to track background operations for all applications on all servers.
The standard benefits of batch job scheduling are drastically amplified when job schedulers can handle the end-to-end automation and monitoring requirements for all background operations.
To schedule a back ground job follow the below steps:
1. Use Transaction SM36.
2. Assign a job name.
3. Set the jobs priority, or Job Class:
High --- Class A
Medium --- Class B
Low ---Class C
4. Here you can specify,when the job is to start by choosing Start Condition. If you want the job to repeat, or be periodic, check the box at the bottom.
Else click on the immediate and save this.
5. Now,define the jobs steps by choosing Step.
Here you need to give the ABAP program that has been used and the name of the variant thats being used.
6. Save the fully defined job to submit it to the background processing system.(You need to click save button on the main screen i.e SM36)
7. When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
8. Release the job so that it can run.
The job, even those scheduled for immediate processing, can not run without first being released.So,do remember to release.
Hope this helps you.
Regards,
Rakesh

How do you add a video on i-pod after you set it to manual

How do you add a video on i-pod after you set it to manual and not erase a ton of stuff in the process?
Thanks

after choosing the manually manage your songs you will not be able to add videos by clicking "update". all you going to do.. after converting videos compatible to ipod video, click your ipod on the left portion of the i tunes it will immediately show your songs from your ipod then drag the selected video from its folder to your i tunes just like adding songs to your ipod

Job msg 608: job set to cancelled manually

Similar Messages

Maybe you are looking for