How to lock targetserver execution in job scheduling

Hi,
I've a SAP System with a central instance and two application servers.
I would set authorizations so that users when they schedule their jobs (example in SM37), the field target server is locked and set to a particular application server.
Any idea ?
Thanks
Maurizio Manera

Hi,
Giving an overview of the tables involved in batch processing. The jobs details are stored in the system on the following tables.
TBTCO      - the overall state and information of a background job
TBTCS      - the view of the jobs that the time based job scheduler has
TBTCP      - the steps a background job consists of.
BTCEVTJOB - the view of the jobs that the event based scheduler has
BTCCTL     - Controls what BTC schedules runs in system
Fields include:
===============
JOBNAME, JOBCOUNT: unique identifiers(i.e. key fields)
SDLDATE, SDLTIME: scheduled date & time of when job is created
SDLSTRTDT, SDLSTRTIM: scheduled start date & time
These are the two fields EXECSERVER & REAXSERVER you should be concerned
EXECSERVER: executing server; filled if you specify a target server
REAXSERVER: filled at run-time; gets same server as EXECSERVER if target.
Regards,
Snow

Similar Messages

How to get the status of Job scheduled in Background.

Hi,
I wanted to know the status of job scheduled in Background.
I am using below FM.
BP_JOB_STATUS_GET
but what value will it reutrn after completion of the job.
That the status is complete.

Use the Table
TBTCO
to know the status
or else call the FUNCTION
BP_JOB_SELECT

How to Cancel a ACTIVE background Job scheduled in SM37.

Hi Friends,
I have scheduled a Background job. The job is ACTIVE now. How can I cancel this job?
Regards,
Viji

There is a last ditch method for jobs that don't get canceled for some reason or the other
Go to SM50 - first try canceling the job from there
If that doesn't work, note down the Process ID (PID) of the job
Take direct OS access to your system (You would need your Basis person for this) and terminate the job
If the server is Windows based, you can end it using the task manager and end that process id

How does this info on background job schedule mean?

Hi,
I have a flat file load which will take hours to load. I therefore schedule it as a background load with a job name. Within 5 mins the scheduled job shows as FINISHED in SM37. I checked in Monitor and there is no information on my load.
How can I see the current status of my flat file load?
Thanks

Hi
I verified the Monitor date and it is correct Today.
No, it is not a process chain.
The file is located on a server and therefore, I set it up as Application Server instead of Workstation in the Infopackage.
Are you suggesting that when in SM37 the status is FINISHED, it meant the flat file load completed? It could not be, because it could not have finished that fast. It is a huge file that is why I got an error previously and the system recommended that it be loaded as a background file.
Thanks

What is the spool, what is its role in background job scheduling

Hi,
I want to know what is meant by Spool request and spool number generated.
Tell about transaction SP01.
How it is linked to Background job scheduling.
thanks.
sam.

Hi,
Refer this link.
https://www.sdn.sap.com/irj/sdn/inf?rid=/library/uuid/7a5f4061-0a01-0010-c9bc-a4e4cb100438
About SP01.
Printing does not work in SAP. There is a printer definition for your local printer, but it does not work. Presuming that you use the program SAPLPD on your computer.
Boot your computer and start only the SAPLogon and the SAPLpd program.
Delete all of your old print jobs in the SAP system (Transaction SP01).Generate only one new print job.
Check that there is enough resource in your computer. Check the free memory (Win 3.1x) and the free disk space (The lists are temporarily saved on your disk).
Open the SAPLPD and read the print log in the window. The printer definition must correspond with the parameters shown here.
Check that the standard printer is on the same lpt (Win 3.1: Control panel, Printer) as defined for the printer (usually lpt1).
In Transaction SP01 read the protocol of your print job. Do not generate new print jobs! Wait till the SAP system changes the status of the print job.
If you can not find the print job in SP01 anymore, then the print job was successfully printed out. If it didn't come out on your printer and the SAPLpd didn't indicate an incoming print job, then the connection was realised with another PC. Then SAP printer definition you used, does not correspond with your computer.
Scheduling Background Jobs:
1.        Background jobs are scheduled by Basis administrators using transaction SM36.
2.        To run a report in a background, a job needs to be created with a step using the report name
and a variant for selection parameters. It is recommended to create a separate variant for each
scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.
company codes).
3.        While defining the step, the spool parameters needs to be specified
(Step-> Print Specifications->Properties) to secure the output of the report and help authorized users
to find the spool request. The following parameters needs to be maintained:
a.        Time of printing: set to u201CSend to SAP spooler Only for nowu201D
b.        Name u2013 abbreviated name to identify the job output
c.        Title u2013 free form description for the report output
d.        Authorization u2013 a value defined by Security in user profiles to allow those users to access
this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching
authorization value in their profiles will be able to see the output.
e.        Department u2013 set to appropriate department/functional area name. This field can be used in
a search later.
f.        Retention period u2013 set to u201CDo not deleteu201D if the report output needs to be retained for more
than 8 days. Once the archiving/document repository solution is in place the spool requests could
be automatically moved to the archive/repository. Storage Mode parameter on the same screen
could be used to immediately send the output to archive instead of creating a spool request.
Configuring user access:
1.        To access a report output created by a background job, a user must have at
least access to SP01 (Spool requests) transaction without restriction on the user
name (however by itself it will not let the user to see all spool requests). To have
that access the user must have S_ADMI_FCD authorization object in the profile with
SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).
2.        To access a particular jobu2019s output in the spool, the user must have
S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used
in the Print Specifications of the job (see p. 3.d above).
3.        Levels of access to the spool (display, print once, reprint, download, etc) are
controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least
BASE access (display).
On-line reports:
1.        Exactly the same configuration can be maintained for any output produced
from R/3. If a user clicks u201CParametersu201D button on a SAP Printer selection dialog, it
allows to specify all the parameters as described in p. 3 of
u201CScheduling background jobsu201D section. Thus any output created by an online report
can be saved and accessed by any user authorized to access that spool request
(access restriction provided by the Authorization field of the spool request
attributes, see p. 3.d of u201CScheduling background jobsu201D section).
Access to reportu2019s output:
1.        A user that had proper access (see Configuring user access above) can
retrieve a job/report output through transaction SP01.
2.        The selection screen can be configured by clicking u201CFurther selection
criteriau2026u201D button (e.g. to bring u201CSpool request name (suffix 2)u201D field or hide other
fields).
3.        The following fields can be used to search for a specific output (Note that
Created By must be blank when searching for scheduled jobu2019s outputs)
a.        Spool request name (suffix 2) u2013 corresponds to a spool name in p. 3.b in
u201CScheduling background jobsu201D section above).
b.        Date created u2013 to find an output of a job that ran within a certain date range.
c.        Title u2013 corresponds to spool Title in p. 3.c in u201CScheduling background jobsu201D
section above).
d.        Department - corresponds to spool Department in p. 3.e in u201CScheduling
background jobsu201D section above).
4.        Upon entering selection criteria, the user clicks the Execute button   to
retrieve the list of matching spool requests.
5.        From the spool list the user can use several function such as view the
content of a spool request, print the spool request, view attributed of the spool
request, etc. (some functions may need special authorization, see p.3 in
Configuring user access)
a.        Click the Print button   to print the spool request with the default attributes
(usually defined with the job definition). It will print it on a printer that was
specified when a job was created.
b.        Click the u201CPrint with changed attributedu201D button   to print the spool request
with the different attributes (e.g. changing the printer name).
c.        Click the u201CDisplay contentsu201D button   to preview the spool request contents. A
Print    and Download   functions are available from the preview mode.
Exporting the Contents of a Spool Request
Use
You want to export the contents of a spool request as a text file to the SAP GUI working directory or to a directory of your choice. The content of the spool request is downloaded as plain text without, for example, graphics, images, or specific fonts.
The following procedures are irrelevant for the PDF-based form printing integrated as of SAP Web Application Server 6.40, since the print data can be opened and stored as a PDF. See also Displaying and Printing PDF-Based Forms.
Procedure
Exporting to the SAP GUI Working Directory:
Choose Spool Request ® Forward® Export as Text.
The entire text is stored in your SAP GUI working directory in ASCII format.
A file of this type is named using the following pattern:
.txt
Example: ABC0000004327.txt
You require appropriate authorization for this function.
Exporting to a Directory of Your Choice:
With this method of exporting a spool request, the content of the spool request is first displayed and you then download the screen list as a text file to the directory of your choice.
       1.      Select the spool request to be exported and choose Display Contents.
       2.      In the case of SAPScript/Smart Forms documents, activate list display by choosing Goto.
       3.      Choose System ® List ® Save ® Local File.
       4.      Choose one of the available formats and confirm your choice.
       5.      Choose a directory and save the spool request.
By default, only the first 10 pages of a spool request are saved in a file. You can increase the number of pages to be saved by choosing Goto ® Display Requests ® Settings and making the desired entries in the Display Area group box.

Job Scheduling -- About SM36

Hi,
       can any tell me ..how to run the bdc thru job scheduling ( SM36 ). In my BDC I have Used GUI_UPLOAD function.So I want to Upload the data thru scheduling.
Thx & Regards,
Sunder.

report zmiro
       no standard page heading line-size 255.
include bdcrecx1.
selection-screen begin of block blk3 with frame title text-019.
parameters : pa_fname type localfile.
selection-screen end of block blk3.
data : lv_fname type string.
data: begin of record occurs 2,
        bldat_003(010),
        xblnr_004(016),
        ebeln_008(010),
        zfbdt_021(010),
        xmwst_030(001),
        mwskz_031(002),
        wrbtr_050(016),
      end of record.
at selection-screen on value-request for pa_fname.
call function 'F4_FILENAME'
    exporting
      program_name = syst-cprog
      dynpro_number = syst-dynnr
      field_name    = 'PA_FNAME'
    importing
      file_name     = pa_fname.
start-of-selection.
lv_fname = pa_fname.
perform open_group.
call function 'GUI_UPLOAD'
exporting
    filename                      = lv_fname
    filetype                      = 'ASC'
    has_field_separator           = 'X'
tables
    data_tab                      = record
loop at record.
if sy-subrc <> 0. exit. endif.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'INVFO-BLDAT'
                              record-bldat_003.
perform bdc_field       using 'INVFO-XBLNR'
                              record-xblnr_004.
perform bdc_field       using 'BDC_CURSOR'
                              'RM08M-EBELN'.
perform bdc_field       using 'RM08M-EBELN'
                              record-ebeln_008.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=HEADER_PAY'.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=HEADER_TOTAL'.
perform bdc_field       using 'BDC_CURSOR'
                              'INVFO-ZFBDT'.
perform bdc_field       using 'INVFO-ZFBDT'
                              record-zfbdt_021.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=DUMMY'.
perform bdc_field       using 'INVFO-XMWST'
                              record-xmwst_030.
perform bdc_field       using 'INVFO-MWSKZ'
                              record-mwskz_031.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=DUMMY'.
perform bdc_field       using 'BDC_CURSOR'
                              'INVFO-MWSKZ'.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'BDC_CURSOR'
                              'INVFO-WRBTR'.
perform bdc_field       using 'INVFO-WRBTR'
                              record-wrbtr_050.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=PB'.
perform bdc_dynpro      using 'SAPLMR1M' '6250'.
perform bdc_field       using 'BDC_CURSOR'
                              'RM08R-SUMME_SOLL'.
perform bdc_field       using 'BDC_OKCODE'
                              '=BU'.
perform bdc_transaction using 'MIRO'.
endloop.
perform close_group.
Hi the above is my program ..thru this program i want to upload thru scheduling how can i do ..kindly modify and give me the procedure for sm36...i dont any thing..about this..
thx& Regards,
sunder

How to deactivate Filter and Job in Job scheduling?

Hi,
My scenario is:
XI will poll the file from 3rd party system and wil send to R/3 via IDOC adapter.
On every sunday , R/3 will be down for 3-4 hrs for maintenance purpose.
I need to create job scheduling in such a way that XI sould collect all the message coming on sunday during that period
of time and after endtime has reached , it should process those message and should send the message to R/3 system.
I have created Sender/Receiver ID ..also create Filter and a JOBID.
while creating Job ID i specified the following
1: Start Date    = 18.08.2009
2:Start Time     = 11.00.00
3:End Date      = 18.08.2009
4:End Time      = 15.00.00
5:Period          = 7
6:Period Unit   = D (Days)
Job should be scheduled at 11.00.00 and end at 15.00.00 ,filter and Job both should deactivate and after 15.00.00 it should process those messages.
But the problem is it doesnt deactivate the filter.
I tried using SXMS_JOB_DEACTIVATE and SXMS_START_JOB_AT_ONCE
Both deacitvtes the JOB but not filter.
Can any body tell me , how to go with it.
Also if I have to write a report, what all things are required.
regards,
Mayank

Hi Volker,
Down time for R/3 is more ..so i am not sure whether XI will trying till that time or not.
And XI is not able to than all the incoming messages in XI during that period of time will be Red Flag.
can we write a report in XI such a way that .. all the queued messages should be processed ..thorugh Job scheduling.

NWA Job scheduler, how to change parameters?

Dear guys,
moving to AEX (java-only) the ABAP Stack is gone.
Regarding job scheduling there is no more transaction sm37, but Job scheduler within NWA to be used for scheduling jobs.
I configured a job for the predefined job definition AlertConsumerJob to get emails in case of alerts.
Doing this the questions arises how to change parameters once a job is scheduled e.g. add additional email receiver.
So far is seems you have to stop the configured job and define a NEW one from scratch by providing all job parameters. It seems not possible to adjust a job.
This is not very comfortable?
Is there an workaround / solution for this?
Best regards
Jochen

Hello Gaurav
thanks for your reply.
It's a pity, but shows that there is still some room of improvement regarding AEX functionality (java only)
Best regards
Jochen

When & how to use default settings option in job scheduling with BO 4.1

Hi,
With BO 4.1 we got new features and one of them is "Default Settings" option in the job scheduling. While scheduling a report in CMC we are getting below attached screen. I want to know when and how to use this option? while scheduling job on queries.
Please guide me to, thanks in advance.
Regards,
Mithun Pati.

Hi Mithun,
Below thread may give you clear idea.
The Purpose of the default settings is to have customized default settings for the enterprise. These settings would apply to any user who has access to Info view and wants to schedule a report. For example you can setup default values for "From" section of email so any scheduled reports use those settings. Similarly another setting we have defaulted is the number of retires involved and the seconds for each retry. Business Objects will not send out a failure emails unless the last retry has failed. The default settings should only be modified by an admin.
Purpose of Default Settings when scheduling a WebI report?

How to do the job scheduling in BDC Call transaction

Hi Experts,
I've a Query like how to do the job scheduling in BDC Call transaction
If anybody knows the answer please send me the reply.
Thanks.
Regards,
Rekha

Hi ,
any progarm can be scheduled, wether it may be BDC or report thru SM36 Tcode.
But do rememeber that if ur BDC is using GUI_UPLOAD function module, then it wont work , coz the function Gui_upload or GUI_DOWNLOAd wont work in back ground.
If u r going to use OPEN_DATASET , READ dataset ....then it can be scheduled. i.e BDC can work if ur program retrievesz the data from Application server.
Rvert back if any issues,
Reward with poinst if helpful.
Regards,
Naveen

How should i execute file transfer via batch job scheduling

Hi guys,
    i want to call unix transfer script via batch job scheduling. Executing the system commands witin ABAP is as below:
         DATA: BEGIN OF ITAB occurs 0,
                     LINE(200),
                    END OF ITAB.
        UNIXCOMM = '/usr/sap/trans/data/*******'
        CALL 'SYSTEM' ID 'COMMAND' FIELD UNIXCOMM
                ID 'TAB'     FIELD itab-sys.
Now i plan to assign application server ('Exec Target') to it and let it implement in the background.
Should i do it via batch job?
Any info is appreciated very much.

Instead of using
CALL 'SYSTEM' u can use FM..
SXPG_COMMAND_EXECUTE .. in which u have to pass a command name which u can create or get from SM49...
In CALL 'SYSTEM' .. u can not catch exceptions.. but in FM given above u can check
SY-SUBRC, STATUS and EXITCODE for successful command execution..
for successful command execution..
sy-subrc = 0
STATUS = 'O' " Capital O
exitcode = 0
For batch scheduling, you can use this FM in a report with one parameter for additional parameter which u need to pass to this FM and create a JOB for that report and schedule it..
I've used it and find it useful even for batch scheduling..
Reward if useful
Regards
Prax

How to see DBMS_OUTPUT error when pl/sql proc runs in the EM job scheduler?

I have a pl/sql package that uses DBMS_OUTPUT to handle exceptions. When I run the package in sql*plus:
set serveroutput on;
begin
mypkg.myproc;
end;
and there is an exception, I see the output from my DBMS_OUTPUT.PUT_LINE.
However, when I use the job scheduler in Enterprise Manager... if there is an error, I do not see the output from my exception handling code (i.e., the output from DBMS_OUTPUT.PUT_LINE).

Using DBMS_OUTPUT to handle exceptions is generally not considered good form. At a minimum, you would want to log the exception to a table (or a file). If you are catching an exception that you cannot handle, you would really want to let that propagate back up to the caller so that Oracle knows that the job failed and can take appropriate action (i.e. retrying, not running dependent jobs, notifying a DBA, etc).
Justin

How to use CELLWRAPPER in 10g for scheduling the job in print server?

Hi Gurus,
I need to add CELLWRAPPER while printing a report to a delimited file from
10G report server using 10G print server job scheduler. In 6i Its working fine.
Below code I used in 10G.
V_Cellwrapper := '''"''';
Srw.Add_Parameter(v_Param_List, 'CELLWRAPPER' , V_Cellwrapper);
v_Job := Srw.Run_Report (v_Param_List);
But It is throwing error (ORA-20999). Please help.

Hi,
when I remember right, 20999 is in the range of user defined exceptions. So it's not an error message created by Oracle internally, it's created by a developer (might be in your case inside a trigger). So I would look in the database, when this exception is created. Is there no text with the error-message?
Regards
Rainer

How to see jobs scheduled, running etc...

I need to see a list of all jobs scheduled and running in my Oracle database?

view all running job
SELECT a.sid, c.serial#, a.job, a.failures, to_char(a.this_date, 'mm/dd/yyyy hh:mi pm') startdatetime, b.what
FROM dba_jobs_running a, dba_jobs b, v$session c
WHERE a.job = b.job AND a.sid = c.sid order by a.this_date
View all jobs
SELECT job, to_char(last_date, 'mm/dd/yyyy hh:mi pm') lastdate, to_char(next_date, 'mm/dd/yyyy hh:mi pm') nextdate, failures, broken, what
FROM dba_jobs
ORDER BY next_date

Error in Backup job scheduling in DB13

Hi All
Backup job scheduled in DB13 kicks error ,I am using Oracle as database and ERP6.0
database and application are on diffrent servers.Before it was working fine,I didn't changed any password
I can run backupjob sucessfully directly from BRtools on database server.Please provide any hint
Job started
Step 001 started (program RSDBAJOB, variant &0000000000060, user )
No application server found on database host - rsh/gateway will be used
Execute logical command BRBACKUP On host DLcSapOraG08
Parameters:-u / -jid INLOG20090120204230 -c force -t online -m incr -p initerd.sap -w use_dbv -a -c force -p in
iterd.sap -cds -w use_rmv
BR0051I BRBACKUP 7.00 (31)
BR0128I Option 'use_dbv' ignored for 'incr'
BR0055I Start of database backup: bdztcorv.ind 2009-01-20 20.42.31
BR0484I BRBACKUP log file: D:\oracle\ERD\sapbackup\bdztcorv.ind
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance ERD failed
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance ERD failed
BR0056I End of database backup: bdztcorv.ind 2009-01-20 20.42.32
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0291I BRARCHIVE will be started with options '-U -jid INLOG20090120204230 -d disk -c force -p initerd.sap -cds -w use_rmv'
BR0002I BRARCHIVE 7.00 (31)
BR0181E Option '-cds' not supported for 'disk'
BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
BR0301W SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310W Connect to database instance ERD failed
BR0007I End of offline redo log processing: adztcorw.log 2009-01-20 20.42.32
BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
BR0005I BRARCHIVE terminated with errors
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.33
BR0292I Execution of BRARCHIVE finished with return code 3
External program terminated with exit code 3
BRBACKUP returned error status E
Job finished

Hi,
not sure if the recommendations given will address this issue.
You are getting this error:
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
the log file indicates:
> No application server found on database host - rsh/gateway will be used
This indicated that the user that is connecting from the AS to the DB server is not properly configured to perform the DB tasks on it.
So, first question would be to know if you have configured a gateway on the DB server and how, or if you are using remote shell.
Second question, you can do backups on the DB server.
> I can run backupjob sucessfully directly from BRtools on database server
How did you run exactly the backup job (what is the exact command line, what is the exact OS user that executed it)?
What is the OS of the DB server?
I have reread your post, your OS is windows therefore you fall in the "typical" error in Windows.
You have executed your backup as <sid>ADM and it works. Unfortunatelly, in windows, SAP is exectuted by SAPSERVICE<sid>, and this is the user who should be connecting to your DB server, and this is the user who cannot execute the backup.
The fact that you can run the backup with <sid>ADM in Windows does not means that you have SAPService<sid> properly configured.
For the error (see before) I think your ops$ user for this user is not properly configured in the DB server. take a look at the note mentioned by KT and pay attention to the SAPSERVICE<sid> configuration
Edited by: Fidel Vales on Jan 24, 2009 12:45 AM

How to lock targetserver execution in job scheduling

Similar Messages

Maybe you are looking for