Manually kick off scheduled jobs

Hi all, now and again I have a situation where the database that the BIP reports are run against is not availalbe in the morning when the BIP jobs are scheduled to run. When the database comes online mid-morning, I've been manually running all jobs that were scheduled to run earlier that morning.
Is there a way to manually kick off the scheduled jobs? The scheduled job already contains the report output name, format, destination etc. and having to go back to the original reports and manually run takes a lot of time. Any ideas?

Hi Joe,
I have done migration Discoverer Admin EUL Layer into OBIEE repository using below methodology.
Navigate to the <installdrive>\OracleBI\server\Bin directory. There are two important files in this directory: the migration assistant executable file named MigrateEUL.exe and a properties configuration file named MigrationConfig.properties.
Could you please help me how to migrate discoverer plus workbooks and worksheets into OBIEE Answers?
go through below link, It will show navigation steps for migrating of EUL from Discoverer to OBIEE.But i need migration of workbooks and worksheets from Discoverer into OBIEE Answers.
http://www.oracle.com/technology/obe/obe_bi/discoverer/discoverer_1012/discomigration/migrate_disco_biee.htm
This is very great full help to me …
Advance thanks for your suggestions.
Regards
Duraga Prasad.

Similar Messages

Kicking off Background Job from Another SAP system

Hi,
Does anybody know how to kick off a background job from a separate SAP system??
i.e I have a job on our CRM system that is dependant on a Job finishing from our ECC6 system first.
Does anyone know how to do this? I know I might be able to use events, is there anything else I should be making use of??
Many Thanks

Hi Daniel,
Guess there is one more solution. In system A write a report (let us name it X) that would trigger a job in system B through an RFC call.
Now in System A create a job with 2 steps. First step would be normal one, the second one for report X. Only when step 1 is over would step 2 start. So indirectly end of the existing Job A would trigger the required Job B.
Regards.
Ruchit.

Manually kick off a single pre-packaged ETL?

Hi everyone,
Hopefully this is an easy question to answer. I want to run certain ETLs manually via the Workflow Manager. But when I do so, they fail with the 'can't find parameter file' error.
Is there a way I can easily just kick off one of these ETLs for testing purposes?
Thanks!
-Joe

Hi Joe,
I have done migration Discoverer Admin EUL Layer into OBIEE repository using below methodology.
Navigate to the <installdrive>\OracleBI\server\Bin directory. There are two important files in this directory: the migration assistant executable file named MigrateEUL.exe and a properties configuration file named MigrationConfig.properties.
Could you please help me how to migrate discoverer plus workbooks and worksheets into OBIEE Answers?
go through below link, It will show navigation steps for migrating of EUL from Discoverer to OBIEE.But i need migration of workbooks and worksheets from Discoverer into OBIEE Answers.
http://www.oracle.com/technology/obe/obe_bi/discoverer/discoverer_1012/discomigration/migrate_disco_biee.htm
This is very great full help to me …
Advance thanks for your suggestions.
Regards
Duraga Prasad.

Background processes on SAP BW Production stall - kicked off via UC4

All,
We have the following issue; there 6 background processes available on the BW server. The UC4 (external) scheduler kicked off 3 jobs that in turn was kicking off 3 process chains which were trying to kick off 10 background processes. The result was that 6 background processes were kicked off, seemed to be active (in sm37), but actually stalled (they were not doing anything), it was like they ended up in a deadlock. Normally one would expect the processes to run according to the mechanism that when there are no background processes available, to wait. My guess is that because they were initiated by an external scheduler and demanded more than the total available background processes that mechanism did not work. Has anyone encountered this problem before? And knows why it happens?
Regards, Meindert

Hi Meindert,
If I recall correctly I remember having seen this before as well, and then the root cause actually was the way the process chains work. There was (is?) some dependency on free batch processes in the initialization phase of the process chain which lead to hanging processes if you started a few process chains at the same time and there are not enough free batch processes available.
I believe this is internal to SAP so probably not caused by scheduling the chains externally, however your external scheduler could maybe take the number of free batch processes into account. I do not know your external scheduler well enough to explain it for that product, I do know how I would handle it with CPS: I'd use queueing to make sure that there are enough free batch processes available, or I would let it monitor the number of free batch processes on the system and if that would become too low, I'd temporarily hold new process chains that needed to start. The chosen option would depend on the priorities of the processes involved, to make sure that the processes with the highest priorities can always start and always have batch processes available.
Regards,
Anton.

Execute Now a scheduled Job

We have EM12C and among several other things we use it to schedule backups and other jobs on our several Oracle databases.
My question: Is there a way to manually execute a scheduled job, a sort of "execute job now" type of command
Regards
James

I opened an SR with Oracle and they confirmed that there is no option to "execute Now" a scheduled job on EM12C.
What can be done is to edit the job schedule to run in say next minute and then re-schedule it again to normal time.
James

Problem kicking off process chains using Tivoli Job Scheduling

In our pre-production BW system testing,when the process chains are being kicked off through Tivoli,they are not working.
We dont get issues when the chains are run directly in BW,without using Tivoli.
The jobs with 'after event' RSPROCESS setting that kick off next node on each node's completion,are not leaving out a 'copy' after a scheduled run.
So in the next run from Tivoli,the dependency job isnt there in scheduled status,which fails the chain.
We tried manually copying the dependency jobs on the nodes.Doing this,chain does kick off from Tivoli.But again jobs dont leave copies and next run from
Tivoli fails.We tried using 'periodic job' setting.This leaves copies of job.But then why is BW able to copy out and kick off jobs,while this isnt happening when kicked off through Tivoli.
A node in the process chain is BLUE when it has a scheduled job ready in sm37,but turns GREY(no scheduled job is there in sm37),once the Tivoli kicks off chains after the manual copy.
We suspect this either to be a authorization problem or an issue with how it works when kicked off through Tivoli.Process chain 'context' is somehow not created when it runs through Tivoli.
Anyone seen such an issue before?Suggestions are welcome..
cheers,
Vishvesh

Hi Manfred,
The chain does get kicked off from Tivoli.
But the job fails in Tivoli as..when it tries to hand over execution to the 1st local chain in the 'meta chain' the required job isnt there in scheduled status,with the 'after event' RSPROCESS dependency set on it.
cheers,
Vishvesh

DS run longer with scheduled job as compare to manual run

I have scheduled a job through Management Console (MC) to run everyday once at
certain time. After some time, maybe after 15 days of running, the execution
time has increased to double from 17 mins to 67 mins by one time jump. After
that, the job kept running and spent 67 mins to complete.
The nature of the job is to generate around 400 output flat files from a
source db2 table. Under efficient running time, 1 file took around 2 seconds to
generate. But now it became taking 8 seconds to generate one file. The data
volume and nature of the source table didn't change, so that was not the root
cause of increasing time.
I have done several investigations and the results as such:
1) I scheduled again this job at MC to run for testing, it would take 67 mins
to complete. However, if I manually run this job thorough MC, it would take
17 mins efficient time to run.
2) I replicated this job to a second job as a copy. Then I scheduled this
copied job at MC to run, it would take 67 mins to run. But if I manually run
this job through MC, it will take 17 mins to run.
3) I created another test repo and load this job in. I scheduled the job to
run at this new repo, it would take 67 mins to run. If I manually run the job
through MC, it only took 17 mins to run.
4) Finally, I manually executed the job through unix job scripts command,
which is one of the scheduled job entry in the cron file, such as
./DI__4c553b0d_6fe5_4083_8655_11cb0fe230f4_2_r_3_w_n_6_40.sh, the job also would take 17
mins to run to finish.
5) I have recreated the repo to make it clean and reload back the jobs and
recreated again the schedule. Yet it still took 67 mins to run scheduled job.
Therefore, the conclusion is why it takes longer time to run by scheduling
method as compare to manually running method?
Please provide me a way to troubleshoot this problem. Thank you.
OS : HPUX 11.31
DS : BusinessObjects Data Services 12.1.1.0
databasee : DB2 9.1

Yesterday we had done another test and indirectly made the problem to go
away. We changed the generated output flat file directory from current directory
of /fdminst/cmbc/fdm_d/bds/gl to /fdminst/cmbc/fdm_d/bds/config directory to
run, to see any difference would make. We changed the directory pointing
inside Substitution Parameter Configurations windows. Surprisingly, job had
started to run fast and completed in 15 minutes and not 67 minutes anymore.
Then we shifted back and pointed the output directory back to original
/fdminst/cmbc/fdm_d/bds/gl and the job has started to run fast ever since and all
completed in 15 minutes. Even we created ad hoc schedule to run and it was
still running fast.
We not sure why it was solved by shifting directory away and shifting back,
and whether this had to do with BODS problem or HP Unix system environment
problem. Nonetheless, the job is started to run normally and fast now as we
test.

Auto-kick off MaxL script after Oracle GL data load?

Hi guys, this question will involve 2 different modules: Hyperion and Oracle GL.
My client has their accounting department updating Oracle GL on a daily basis. My end-user client would like to write a script to automatically kick off the existing MaxL script which is for our daily data load in Hyperion. Currently, the MaxL script is manually executed.
What's the best approach to build a connection for both modules to communicate with each other? Can we use a timer to trigger the run? If so, how?

#1 External scheduler.
I've worked on Appworx and it has build a chain dependent task. There are many other external schedulers like Tivoli,....
#2 As Daniel pointed out you can use Windows scheduler.
For every successful GL load add a file to a folder which is accessible for your Essbase task.
COPY Nul C:\Hyperion\Scripts\Trigger\GL_Load_Finished.txt
Create another bat file which is scheduled to run on every 5 or 10 mins (this should start just after your GL Load scheduled task)
This is an example i've for a triggered Essbase job.
IF EXIST %BASE_DIR%\Trigger\Full_Build_Started.txt (
Echo "Full Build started"
) else (
     IF EXIST %BASE_DIR%\Trigger\Custom_Build_Started.txt (
     Echo "Custom Build started"
     ) else (
          IF EXIST %BASE_DIR%\Trigger\Post_Build_Batch_Started.txt (
          Echo "Post Build started"
          ) else (
          IF EXIST %BASE_DIR%\Trigger\Start_Full_Build.txt (
          Echo "Trigger found starting batch"
          MOVE %BASE_DIR%\Trigger\Start_Batch.txt %BASE_DIR%\Trigger\Full_Build_Started.txt
          call %BASE_DIR%\Scripts\Batch_Files\Monthly_Build_All_Cubes.bat
          ) else (
               IF EXIST %BASE_DIR%\Trigger\Start_Custom_Build.txt (
               Echo "Trigger found starting Custom batch"
               MOVE %BASE_DIR%\Trigger\Start_Custom_Batch.txt %BASE_DIR%\Trigger\Custom_Build_Started.txt
               call %BASE_DIR%\Scripts\Batch_Files\Monthly_Build_All_Cubes_Custom.bat
               ) else (
                    IF EXIST %BASE_DIR%\Trigger\Start_Post_Build_Batch.txt (
                    Echo "Trigger found starting Post Build batch"
                    MOVE %BASE_DIR%\Trigger\Start_Post_Build_Batch.txt %BASE_DIR%\Trigger\Post_Build_Batch_Started.txt
                    call %BASE_DIR%\Scripts\Batch_Files\Monthly_Post_Build_All_Cubes.bat
)So this bat file if it finds Start_Full_Build.txt in the trigger location, it'll rename that to Full_Build_Started.txt and will call the Full Build (likewise for custom and post build)
Regards
Celvin
http://www.orahyplabs.com

Scheduled jobs fail to run after reboot

A couple of months back we moved our CF 8 server to a VM (VMWare). We have noticed that after the server (Windows OS) is rebooted, all scheduled jobs do not run. There are no errors in the logs. One oddity is that after the reboot in the scheduler log there are a series of entries for all jobs with the ThreadID of "main", after that there are no other entries. Normally when the job runs the ThreadID will be something like “Scheduler-1”. Here is where it gets really strange. Simply logging into the console will “trigger” the jobs and they will run. I do not have to manually initiate on of the jobs. This can be repeated over and over simply by rebooting the server. Manually stopping and starting the service does not trigger this issue nor will it “kick start” the jobs to run.

Update:
I opened up a case with Microsoft Support and resolved the issue. Apperantly this is a known issue and the bug will be addressed in CU6. Microsoft was able to give me a hotfix (QFE_MOMEsc_4724.msi) which I applied on all systems that have SCOM Console. I
am told that this issue occurs when SCOM 2007 R2 CU5 runs on SQL 2008 R2.
I hope it helps to others that run into same problem.
ZMR

Issue with scheduled jobs

Hello Team,
After creating a new protection group, the jobs were frozen and was never kicked off.
What could be the reason?
Regards,
Suman Rout

Hi,
Please see the below blog which may assist with troubleshooting scheduled jobs.
Blog:
http://blogs.technet.com/b/dpm/archive/2014/10/08/how-to-troubleshoot-scheduled-backup-job-failures-in-dpm-2012.aspx
Pervious fourm post:
https://social.technet.microsoft.com/Forums/en-US/ed65d3e0-c7d7-488b-ba34-4a2083522bae/dpm-2010-scheduled-jobs-disappear-rather-than-run?forum=dataprotectionmanager
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually
answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

Scheduled job keeps hanging after sveral days

MII experts,
We are using MII 12.0.8. I have several scheduled jobs. Those that run once every day never have any problem. However, I have one that runs every 10 minutes keeps hanging after running for 3-4 days. I have to stop and start to kick it off again if that happens. When it hangs, it appears it is still in running state but it never finish.
Have anyone seen this problem before?
Thanks.

We are running MII Version 12.1.5 Build(91) and have noticed jobs in the schedule that are running but are obviously not doing anything. These jobs are user to trnsfer files around our site via ftp.
MII gives no error or indication that the job has failed so we know nothing about these problems untill an end user complains about their file transfers not working. As we are a 24 by 7 site this involves calls to aur support people at all hours.
We have asked SAP for help but they require a Step by Step method to duplicate the error. As this is a very intermitant problem that we have not been able to reproduce on demand this request has been ignored by SAP.
We have many schedule jobs that run once per minute. Slowing them down more would have a bad impact on the usefullnes of the transfers.
If anyone gets an answer to this issue we would love to hear it.

SCEP 2012 clients kicking off random scans

We have an SCCM 2012 environment with SCEP 2012 recently deployed. We have a policy in place that does weekly full scans on Tuesdays at 12AM. The client machines are 64 bit Windows 7. We are seeing some random computers kicking off Full scans
at various points in the day. We thought that initially there were viruses on these machines and that was causing the scans, but according to the EP console, they do not have any type of virus or malware.
Any ideas?

Here is the way MS does such things. (Update works this way too) It is STUPID, of course, but then "SMART" is not a word that fits Microsoft very well. Just look at Windows 8 for an example or to the fact you can't even find a simple link to the
SCEP client for what ever happens to be the latest greatest version.
As for the auto scanning, it will occur REGARDLESS of the time set shortly after you start your PC if it was not able to do it at the appointed time. So if it is set for 12am, and if the system, for whatever reason was not on, it will kick off shorty after
it is booted, REGARDLESS of the current time. (It is supposed to wait until the system is idle, but MS uses lack of keyboard or mouse action to decide if a system is active instead of actually looking to see if its. For example watching a movie. MS would say
after five minutes, it is inactive, then run the scan, screen save, update, or whatever. Maybe you were just reading a long email, letter, or article online, doesn't matter MS will kick off the scheduled event. Of course this will cause problems for the movie
etc, but MS won't care. Bottom line is if the MS AV is doing its job, or anyone's Av for that matter, and was installed on a 100% clean PC, then one should NEVER need to do a blind system scan. Common sense really. Of course MS AV is not very good at preventing
the more destructive of the evils out there such as the Ransomewares and things like the ASK or the Google toolbar or the many fake "fix your PC" popups that are out there etc. etc.
Best just to keep it disabled.
Ralph

Troubled to get scheduler job to run?

Hi all friends:
I'm having trouble getting any scheduler jobs (here, troubled job name is CUSTMASTER_CHANGES_01) to actually run.
when
sql>select job_name,state,enabled,retry_count,failure_count,run_count,restartable,start_date,repeat_interval,job_class
from all_scheduler_jobs;
JOB_NAME STATE ENABL RETRY_COUNT FAILURE_COUNT RUN_COUNT RESTA START_DATE REPEAT_INTERVAL JOB_CLASS
CUSTMASTER_CHANGES_01 SCHEDULED TRUE 0 0 0 FALSE 14-JAN-08 09.46.14.6 FREQ=SECONDLY;I SCANNER_JO
72965 AM AMERICA/NEW NTERVAL=5 B_CLASS
_YORK
for job 'CUSTMASTER_CHANGES_01'
we can see RUN_COUNT 0 and restartable false.
I upped slave processes to 5. dbms_scheduler.run_job('CUSTMASTER_CHANGES_01') works, but it's still not executing on the schedule
when run as sysdba
SQL> exec dbms_scheduler.run_job('CUSTMASTER_CHANGES_01');
ERROR at line 1:
ORA-27475: "SYS.CUSTMASTER_CHANGES_01" must be a job
ORA-06512: at "SYS.DBMS_ISCHED", line 150
ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
ORA-06512: at line 1
to resolve that,
we found
When you create your job by using dbsm_scheduler, it has a parameter called ‘auto_drop’, is by default, =’true’, like, auto_drop => TRUE
see below;
dbms_scheduler.create_job(
job_name IN VARCHAR2,
job_type IN VARCHAR2,
job_action IN VARCHAR2,
number_of_arguments IN PLS_INTEGER DEFAULT 0,
start_date IN TIMESTAMP WITH TIME ZONE DEFAULT NULL,
repeat_interval IN VARCHAR2 DEFAULT NULL,
end_date IN TIMESTAMP WITH TIME ZONE DEFAULT NULL,
job_class IN VARCHAR2 DEFAULT 'DEFAULT_JOB_CLASS',
enabled IN BOOLEAN DEFAULT FALSE,
auto_drop IN BOOLEAN DEFAULT TRUE,
comments IN VARCHAR2 DEFAULT NULL);
The job you manually run once and then it drops itself when you test.
so I am specifiying auto_drop to be false, but it is showing it has true as the attribute.
DBMS_SCHEDULER.CREATE_JOB(
job_name => scanner.scanner_name,
job_type => 'PLSQL_BLOCK',
job_action => 'BEGIN IF EEG_SCAN.GET_RUNNING_JOBS_COUNT('
||''''||UPPER(scanner.scanner_name)||''''
||') < 2 THEN '||scanner.scanner_proc_name||'; END IF; END;',
repeat_interval => 'FREQ=SECONDLY;INTERVAL=5',
job_class => c_job_class_name,
auto_drop => FALSE,
enabled => true
scheduler job is still not working as expected.....?
Can you help me for this??
thanks a lot in advance.
Message was edited by:
jerrygreat
Message was edited by:
jerrygreat

Hi,
There are a few other limits you could check .
Make sure that you have not exceeded the maximum number of sessions or the maximum number of processes or the maximum number of scheduler jobs
select * from dba_scheduler_global_attribute;
and
select name,value from v$parameter where name like '%process%';
select name,value from v$parameter where name like '%session%';
Also check how many jobs are currently running
select count(*) from dba_scheduler_running_jobs;
select count(*) from dba_jobs_running ;
select count(*) from v$session ;
One of these limits may need to be increased.
The run_job succeeds because it runs in the current session by default, if you use use_current_session=>false, does it still work ?
Also auto_drop only drops the job when it has completed e.g. past its end_date or exceeded its max_runs.
Finally note that there is a dedicated forum for dbms_scheduler located here
Scheduler
Hope this helps,
Ravi.

Background Processing? how schedule job for "System Error" Message .

Hello everyone,
in sap help i have read.
http://help.sap.com/saphelp_nw04/helpdata/en/5a/f72040599a8f5ce10000000a155106/frameset.htm
PCK> Monitoring>Message Monitoring-->Background Processing
you can schedule jobs for various background processing:
●     Archiving of messages processed successfully
●     Deletion of messages that are not to be archived
●     Restarting of messages with errors
●     Rescheduling of lost messages
can anyone understand this docu?
give me some introduction, how can i define and schedule these jobs ?
thx in advance!!
best regards
Yaning

Background Processing
Prerequisites
You have started the message monitor on the initial screen of the PCK and are in Background Processing.
Features
Archiving
You require two archiving sessions to archive messages:
●     One session to write the messages to the archive
●     One session to delete the persisted messages that have been archived
To do this, you schedule an archiving job, which implicitly schedules the sessions to write to the archive and delete the archived messages.
You can define one or more rules for each archiving job; these rules contain conditions that a message must meet in order to be archived by the job. At least one of the defined rules must be met for archiving to take place.
All information that is displayed for a message in message monitoring is archived, in addition to the audit log for each message.
Deleting
A standard delete job is created automatically. It runs once a day. You can schedule additional delete jobs; however, you cannot define rules for them.
Restarting
Instead of restarting messages with errors manually with message monitoring, you can schedule a job to automatically restart these messages. This is possible for all messages for which the number of defined restart attempts has been exceeded (messages with the system error status).
You can define one or more rules for each job to restart messages; these rules contain conditions that a message must meet in order to be restarted by the job. At least one of the defined rules must be met for archiving to take place.
Rescheduling
A standard job to reschedule messages is created automatically. The job runs once a day and ensures that messages lost as a result of database failure, for example, are rescheduled. You can schedule additional rescheduling jobs; however, you cannot define rules for them.
Thx Aamir.
But I mean the messages with errors in Adapter Engine , not in Intergrations Engine.
the situation is like Naveen Pandrangi's WebLog
II. Errors in Adapter Engine [XI : How to Re-Process failed XI Messages Automatically|XI : How to Re-Process failed XI Messages Automatically]
I
Till now we have seen how to resubmit/restart message that failed in Integration Engine. One a message makes it from Integration Engine to Adapter Engine, the message is flagged as checked in Integration Engine. The status of the message in Adapter engine does not effect the processed state in Integration Engine. Now if this message was asynchronous, XI will by default try to restart the message 3 times at intervals of 5 minutes before the status of the message is changed from Waiting to System Error .
*how can i schedule a job to automatically restart these messages with errors?
best regards
Yaning
Edited by: Yaning Liu on Aug 18, 2008 1:43 PM

How to schedule job hourly on daily basis

Hi,
Experts.
I want to schedule a job between 9:00 AM to 9:00 PM daily on working days Monday to Friday IST.
It should run on hourly basis daily. Currently we are following the manual process for scheduling the jobs in SM36. We want to automate the process. Can SCMA help in this ?
How to achieve this, would like to have experts insights on the same.
Regards,
Edited by: Sharvari Joshi on Nov 23, 2010 7:36 PM

Write an ABAP report program. with the below code stub.
Further you can check the function group BTCH for more options.
Customize the function call job close.
Hope this helps in automating.
CALL FUNCTION 'JOB_OPEN'
    EXPORTING
      JOBNAME          = JOBNAME
      JOBCLASS         = 'C'
    IMPORTING
      JOBCOUNT         = JOBCOUNT
    EXCEPTIONS
      CANT_CREATE_JOB = 01
      INVALID_JOB_DATA = 02
      JOBNAME_MISSING = 03.
IF SY-SUBRC NE 0.
    exit."error processing
ENDIF.
SUBMIT (JOBNAME)
USER SY-UNAME
VIA JOB JOBNAME
NUMBER JOBCOUNT
AND RETURN.
IF SY-SUBRC = 0.
ELSEIF SY-SUBRC = 4.
    RAISE SCHEDULING_CANCELLED_BY_USER.
ELSEIF SY-SUBRC = 8.
    RAISE ERROR_DURING_SCHEDULING.
ELSEIF SY-SUBRC = 12.
    RAISE ERROR_IN_INTERNAL_NUMBER_ASSIG.
ENDIF.
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
*   AT_OPMODE                         = ' '
*   AT_OPMODE_PERIODIC                = ' '
*   CALENDAR_ID                       = ' '
*   EVENT_ID                          = ' '
*   EVENT_PARAM                       = ' '
*   EVENT_PERIODIC                    = ' '
    JOBCOUNT                          =
    JOBNAME                           =
*   LASTSTRTDT                        = NO_DATE
*   LASTSTRTTM                        = NO_TIME
*   PRDDAYS                           = 0
*   PRDHOURS                          = 0
*   PRDMINS                           = 0
*   PRDMONTHS                         = 0
*   PRDWEEKS                          = 0
*   PREDJOB_CHECKSTAT                 = ' '
*   PRED_JOBCOUNT                     = ' '
*   PRED_JOBNAME                      = ' '
*   SDLSTRTDT                         = NO_DATE
*   SDLSTRTTM                         = NO_TIME
*   STARTDATE_RESTRICTION             = BTC_PROCESS_ALWAYS
*   STRTIMMED                         = ' '
*   TARGETSYSTEM                      = ' '
*   START_ON_WORKDAY_NOT_BEFORE       = SY-DATUM
*   START_ON_WORKDAY_NR               = 0
*   WORKDAY_COUNT_DIRECTION           = 0
*   RECIPIENT_OBJ                     =
*   TARGETSERVER                      = ' '
*   DONT_RELEASE                      = ' '
*   TARGETGROUP                       = ' '
*   DIRECT_START                      =
* IMPORTING
*   JOB_WAS_RELEASED                  =
* CHANGING
*   RET                               =
* EXCEPTIONS
*   CANT_START_IMMEDIATE              = 1
*   INVALID_STARTDATE                 = 2
*   JOBNAME_MISSING                   = 3
*   JOB_CLOSE_FAILED                  = 4
*   JOB_NOSTEPS                       = 5
*   JOB_NOTEX                         = 6
*   LOCK_FAILED                       = 7
*   INVALID_TARGET                    = 8
*   OTHERS                            = 9
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Manually kick off scheduled jobs

Similar Messages

Maybe you are looking for