Periodic Job Scheduling

Hi All,
I have scheduled two jobs periodically with same variant. The two jobs runs every day at same time. But two jobs are cancelling automatically. In job log the reason is Program is already active in background.
But in non periodic jobs, i mean i have two more jobs scheduled at same time with same variant. Those two jobs are not periodic jobs. In this case two jobs have been completed.
What would be the reason for cacel?
Thanks
Lakki

Hello Lakki,
look below this may help full for u..
use different Infopackages for different date selections, or else take example and proceed like below mentioned.
i think u will get idea.
Go to SM37 and enter your job name. In the checkboxes below, check 'Released' only and uncheck all others. In the date range give a future date in the 'To' date.
Once you get the list(there should only be one that is in released status), select that and delete(trash can in the application toolbar). That will remove it from future schedules.
Regards,
Lakshman.Annamaneni.

Similar Messages

Problem in periodic job scheduling in LBWE

hi,
i have activated the Material movements datasource 2LIS_03_BF. Filled up the set up table.
now when i try to schedula a job in jobcontrol, under the tab *immediate* the immediate start check box is checked and disabled. the periodic job check boxat the bottom is unchecked and disabled.
the periodic values button which has to be near the check button is not present.
i even tried for other datasources, the periodic job is disabled in all and periodic values button is not found.
could anyone suggest me on this issue.

Hi,
Did you initialize delta for 2LIS_03_BF from BI? If not, first initialize the delta and try to schedule V3 job from LBWE.
By default *Immediate start * check box will be in disable mode. If you want to run it immediately just click on Save button.
If you want to schedule it for future date and time then click on Date/time button then enter schedule start date and time and click on Save button.For more details about scheduling options please look at following link.
http://help.sap.com/saphelp_nw04/helpdata/EN/c4/3a7fae505211d189550000e829fbbd/frameset.htm
hope it works...
regards,
Raju
Edited by: VaraPrasadraju Potturi on Aug 3, 2009 8:54 AM
Edited by: VaraPrasadraju Potturi on Aug 3, 2009 9:02 AM

Restrict Periodic jobs scheduling from SM36 or any other t-code

HI,
We would like to restrict users from scheduling periodic background jobs. Immediate jobs will be fine.
And also one more concerns is that user should not be able to directly execute any report or transaction in background periodically.
In short immediate jobs will be fine but users should not be able to set periodic jobs by any T-code.
Thanks,
Chandresh Pranami

If you search for "btcoptions" you will find a comprehensive discussion about this, and a development suggestion in the wiki.
I attempted the same and ended up recreating the UI from scratch and scheduling the report + variant from a parameter transaction they are authorized for, but the user can navigate in many transactions showing this option.
A compensating control when retiring users and central batch administration with monitoring is easier.
Cheers,
Julius

Semi-Periodic Job Scheduling

Greetings,
Is anyone aware of a less complicated way to schedule a daily job that must skip the first six days of the month without setting up a Factory Calendar specific for the job? The factory calendar is the way I'm leaning to get this working but if there is an easier way, I'm all ears.
It has been suggested that I could set up a second step ABAP program which would schedule the job for the next day except if it is in the first six days of the month, but that seems to be counterintuitive to keeping it simple for maintainability of the job.
If there is no simpler way then the factory calendar, is there a more simple way to populate said calendar outside of using a CATT script?
Thanks in advance,
Conrad Thonger

Hi Conrad,
May be you can try writting a small wrapper in UNIX to raise a sapevent. Trigger the even only when it is required. This event can then in turn trigger the job.
Ofcourse not a good way as there is a dependency on UNIX and some times it becomes difficult to troubleshoot. We do have such situations in our company.
The other alternative is...... there is another UNIX daemon which runs on UNIX by default every UNIX system will have this daemon. You can simlply trigger this daemon at you specifc date and time.I dont remember the daemon name. But i am sure there is one.
Cheers
VJ

Job Scheduling in Solution Manager - Error creating Periodic Job

Hi all,
I am in the process of testing the Job Scheduling functionality using the Solution Manager. I have setup the criteria manager, ec. in the satellite system, and done the config in Solman as well.
I am able to successfully setup up a 'on-time' job.
it's only when I try to setup a periodic job, I end up getting following error
Any thoughts? Is there any piece of config that's missing? All the SICF services needed for this functionality are running fine.
Thanks for the help.
500 Internal Server Error
Error when processing your request
What has happened?
The URL https://fsspsm.target.com:/sap/bc/webdynpro/sap/wd_ags_ejr_job_req_gaf_app was not called due to an error.
Note
The following error text was processed in the system PSM : Message was not created
The error occurred on the application server fsspsmap01_PSM_00 and in the work process 1 .
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Function: BAPI_NOTIFICATION_CREATE of program SAPLDSWP_NOTIF
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: SUBMIT_REQ_CRM_DATA of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: SUBMIT of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: PROCESS_SCENARIO_PERIODIC of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: PROCESS_JOB_SCENARIO of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: IF_AGS_EJR_JSM_PROC_FPM_CTRL~AFTER_PROCESS_EVENT of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: IWCI_IF_FPM_APP_CONTROLLER~AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: CALL_UIBB_PROCESS_EVENT of program CL_FPM========================CP

Hello,
This is the basic Job Scheduling functionality and not the Redwood Job scheduling, correct?
Have you performed the IMG Activiteis in SPRO?
See the following Help link:
http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/c5/7edcbd58ce4e29bc1baf1c4761d71f/frameset.htm
Change a job
You can change the scheduling of a job as long as it has not been completed. Proceed as follows:
Make changes.
Note
When you change a periodic job, the system searches for the changeable successor and only changes this successor.
If there is more than one changeable job with the same name, the system does not change any of these jobs.
End of the note.
Save your entries.
To release the job in the target system, select Release.
You go to the transaction SM37 in the target system.
You just may want to ensure HTTP Services have been enabled. I realize you said the services workin SICF, but this needs to be verified as 500 Internal Server Error most often means the HTTP services are not activated.
Regards,
Paul

I want to revoke rights so users cannot schedule periodic jobs

We do encourage users to run reports in Background but we want to prevent them from scheduling periodic jobs.
We want to have more controll over periodic jobs as we observed that users schedule them and then forget about them.
Morover this has become our audit recommendation.
As far as I can see there is no standard way to do it.
Has anyone managed to achieve it?

Hi..
while searching for the answer i have seen following interesting point.chk whether this will help you..
A job is eligible to start when both of the following are true:
The start condition specified for the job is met.
The job has been released to run.
No job can be run until it has been released, even those scheduled to start immediately. To monitor and control what jobs are submitted to run in background processing, the system can be configured so an administrator can check jobs before releasing them to run.
The release requirement can also be turned off on a per-user basis. Trusted users can be given a special authorization (authorization object S_BTCH_JOB (Batch Processing: Operations on Batch Jobs), value RELE) which will automatically and immediately release any job scheduled by that user.
http://help.sap.com/saphelp_nw2004s/helpdata/en/20/2d513897110872e10000009b38f889/content.htm
thank you
<b><removed_by_moderator></b>

Background Job Scheduling

Hi,
I am scheduling a report to run in background.
In this report it is creating background jobs automatically for different company codes.
It submits the 1st background job and waits until it finishes.
Then 2nd job starts in background and continues with other jobs.
At end it finishes all the jobs and closes.
Now my problem is.
1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
2.       If possible how can we do that.
What I have written is
loop at companycode.
Create job name.
call fun 'Job_Open'.
submit xxxx user sy-uname via job job_name numer job_count
to sap-spool
spool parameters l_spool_parameter
without spool dynpro
with companycode
with ......
and return.
endloop.
Please help ASAP, urgent.

hi praveen,
Job Scheduling Explained
Definition
Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the jobs definition. There are several ways to schedule jobs:
From Transaction SM36 (Define Background Job)
With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
Through the background processing systems own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
Through an external interface.
Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
       1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
       2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
       3.      Set the jobs priority, or Job Class:
·         High priority:      Class A
·         Medium priority: Class B
·         Low priority: Class C
       4.      In the Target server field, indicate whether to use system load balancing.
·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
·         To use a particular application server to run the job, enter a specific target server.
       5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
       6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
       7.      Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
       8.      Save the fully defined job to submit it to the background processing system.
       9.      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.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
Specifying Job Start Conditions
Use
When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
Procedure
Choose the Start condition button at the top of the Define Background Job screen.
Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
Once youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
Managing Jobs from the Job Overview
Use
The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
Procedures
To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
To copy a single existing job, choose Job ® Copy.
To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
To repeat a single job, choose Job ® Repeat scheduling.
To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
To review information about a job, choose Job ® Job details. Details displayed can include:
current job status
periodicity, or the repetition interval
other jobs linked to the current job, either as previous or subsequent jobs
defined job steps
spool requests generated by the current job
To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
regards
karthik
reward me points if helpfull

Background job scheduling for report

Hi can any one explain me how to do background job scheduling for report periodically for every 15 min.

Hi Rajesh thanks for your brief explanation.
but I am new to abap so I can't understand exactly will you please make it clear for the below program
REPORT zklj.
data: begin of itab occurs 0,
      partner type but000-partner,
      type     type but000-type,
      BU_SORT1 type but000-BU_SORT1,
      end of itab.
select partner type from but000 into table itab.
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
BIN_FILESIZE                    =
    FILENAME                        = 'd:\al1\ahaj.xls'
    FILETYPE                        = 'DAT'
APPEND                          = ' '
WRITE_FIELD_SEPARATOR           = ' '
HEADER                          = '00'
TRUNC_TRAILING_BLANKS           = ' '
WRITE_LF                        = 'X'
COL_SELECT                      = ' '
COL_SELECT_MASK                 = ' '
DAT_MODE                        = ' '
CONFIRM_OVERWRITE               = ' '
NO_AUTH_CHECK                   = ' '
CODEPAGE                        = '400'
IGNORE_CERR                     = ABAP_TRUE
REPLACEMENT                     = '#'
WRITE_BOM                       = ' '
TRUNC_TRAILING_BLANKS_EOL       = 'X'
WK1_N_FORMAT                    = ' '
WK1_N_SIZE                      = ' '
WK1_T_FORMAT                    = ' '
WK1_T_SIZE                      = ' '
WRITE_LF_AFTER_LAST_LINE        = ABAP_TRUE
SHOW_TRANSFER_STATUS            = ABAP_TRUE
IMPORTING
FILELENGTH                      =
TABLES
    DATA_TAB                        = itab.

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.

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.

Back ground job scheduling(urgent)

Hi all,
can anybody will help me ,regarding the step by step procedure to schedule the background job.
i have to do back ground job scheduling for one program so that in that specified time my report will execute?
plz suggest.
ur idea will be highly appreaciated.
Regards
pabitra

HI
Please follow the below steps to schedule a background job.
First - create a Report-Variant for your print programm using the SE38.
Then...
1.) Call the transaction SM36
Enter a Job Name / You may set a job class other
than 'C' (See online Help on that field).
2.) Push the STEP Button
3.) Push the ABAP Program button
Enter der programm name an the variant name
save that window
4.) Push "BACK"
5.) Push "Start Condition"
6.) Push Date/Time
Enter Date + Time for the first start
Mark "Periodic Job" !!
7.) Push "Period Values"
Set the period you want the job to be started
Save everything
For more info please refer to this link:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a7ed1505211d189550000e829fbbd/content.htm">Background Processing</a>
Kind Regards
Eswar

IR jobs scheduled error

hi,
i have 13 jobs scheduled on workspace. the task is to import bqy document. when the scheduled run, i check the folder and i only see 10 bqy imported, not 13. when i see the job output, it says unknown error. no problems appear when i try to run the jobs one by one.
below is the error :
Job: 'FlashReportCharts_1' executed by user 'admin'
At 07/14/09 04:58 PM UTC+7 (server time)
Using Interactive Reporting Job Service 11.1.1.1.0.797.
Connecting to AI as 'sa' at 07/14/09 04:58 PM.
Sending SQL to server:
SELECT AL1.curr_month, AL1.curr_year FROM dbo.current_period AL1
1 rows retrieved at 07/14/09 04:58 PM.
Connecting to aijkt-hypdb as 'admin' at 07/14/09 04:58 PM.
Sending SQL to server:
<HYBRIDANALYSISOFF {SSFORMAT} {ROWREPEAT} {INDENTGEN -2} {SUPBRACKET} {SUPCOMMA} <QUOTEMBRNAMES {DECIMALS 0} <SUPSHARE {OUTALTNAMES} <OUTALTSELECT "Default" <PAGE ("Site" ,"Scale" ) "Site" "Input Value" {OUTALTNAMES} <OUTALTSELECT "Default" <ROW("Period") "Gen2,Period" "Gen3,Period" "Gen4,Period" <SYM {OUTALTNAMES} <OUTALTSELECT "Default" <COL("Year","Scenario","Measure") {SUPCOMMA} {TABDELIMIT} &CurrYear "Actual" "Budget" "Forecast" "Overburdened Removal" "Coal Sales" "Coal Barged" "Coal Produced" "Strip Ratio" "Coal Mined" "Coal Stock" "FOB Sales Price" !
Connecting to aijkt-hypdb as 'admin' at 07/14/09 04:58 PM.
Sending SQL to server:
<HYBRIDANALYSISOFF {SSFORMAT} {ROWREPEAT} {INDENTGEN -2} {SUPBRACKET} {SUPCOMMA} <QUOTEMBRNAMES {DECIMALS 0} <SUPSHARE {OUTALTNAMES} <OUTALTSELECT "Default" <PAGE ("Site" ,"Scale" ) "Site" "Input Value" {OUTALTNAMES} <OUTALTSELECT "Default" <ROW("Scenario","Period") "Actual" "Year Total" <SYM {OUTALTNAMES} <OUTALTSELECT "Default" <COL("Year","Measure") {SUPCOMMA} {TABDELIMIT} &PrevYear "Overburdened Removal" "Coal Sales" "Coal Barged" "Coal Produced" "Strip Ratio" "Coal Mined" "Coal Stock" "FOB Sales Price" !
61 rows retrieved at 07/14/09 04:58 PM.
Saving 'C:\Hyperion\products\biplus\data\cache\IRJobCache\4211a25c451326567edb40f6121ece4edd179d0\0a06011600002604-0000-25ec-00000009\0000012278b2fb70-0000-16b0-0a060116\FlashReportCharts_1-20090714.bqy' (compresseed) at 07/14/09 04:58 PM.
Save failed with unknown error.
Job for document FlashReportCharts_1.bqy completed at 07/14/09 04:58 PM UTC+7 (server time) on @HOST:aijkt-hypapp.arutmin.net with errors.
Edited by: r.senoputro on Jul 23, 2009 11:14 PM

Put the IR job logs in TRACE:32 mode which will give more information in the logs . Refer this document link to put in TRACE mode :http://docs.oracle.com/cd/E17236_01/epm.1112/epm_install_troubleshooting_1112200.pdf
Thanks,
KK

Auto TECO Orders for which finished date has been reached-Periodic Job

Dear PP GURUS N EXPERTS,
My company want to TECO all the production order automatically for which finished date has been reached or (Finish date is before current date).
On SDN, I have found that it can be carried our by scheduling the variant of PPIO_ENTRY or COHV. and it will be a periodic job.
I want to know that for this which parameters I have to select and where / how I mention that order finish date has been reached. Since it will be a periodic job.
Early response will be highly appreciated.
With thanks,
DSC

Dear DSC
You can use tranaction code CO44, define a variant for periodic job.
Important selection parameters :
Status selection profile : define which kind of production orders you want to set TECO indicator, for example with status CNF or DLV.
Basic finish date : define basic finish date, for example if you want to TECO the production orders whose basic finish date is less than or equal current date, when you create the variant, selection variable can be D ( D: Dynamic date calculation ), name of variable can be "current date"
Actions : please select the indicator "complete Technically".
You can have a try, please let me know the result.
Qiu

Changing job schedule time

Hi,
I have scheduled a job to execute at a specific time daily.
But now I want to change the execution time, job will execute daily.
How to do that ?
Regards,
Amit R.

hi,
Specifying Job Start Conditions
Use
When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
Procedure
Choose the Start condition button at the top of the Define Background Job screen.
Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
Once youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission.
i got this from link,
http://help.sap.com/saphelp_nw04/helpdata/en/c8/6a56389f64246fe10000009b38f889/frameset.htm
Regards,
Arunsri

REG : disable "periodic jobs" icon

While scheduling a job in background there is checkbox on the screen "periodic jobs",
its our client requirement that they want disable this check box for some particular users , so it will have to disable through authorization but I could not find any object
Or option to disable it can any one Help me !!
Hearty thanks in advance
sathies

Hi,
With auth objects check you wont be able to switch of or disable the periodic check option in SM36. Via auth objects you can only restrict the authorization to a particular txn or screens of a txn, not to screen values.
You will have to create a transaction variant for SM36 (this can be client-dependent or client-independent) in txn SHD0. The screen variant is automatically created when you create a txn variant. Please, find below the link to create a txn variant.
http://help.sap.com/saphelp_nw70/helpdata/en/67/232037ebf1cc09e10000009b38f889/frameset.htm
Once,you have finished creating a txn variant - you can then have a txn itself which then calls the original txn with the variant only. This is known as a VARIANT Transaction. You then go ahead and share this with the customer and lock down the SM36.Please find below how to do this.
http://help.sap.com/saphelp_nw70/helpdata/en/67/232037ebf1cc09e10000009b38f889/frameset.htm
Please note the restrictions as wel:
Only "normal" screens, dialog boxes, and subscreens can be included in the variant. The screens of the following functions may not be included:
- Help and possible entries help (F1, F4)
- List display (and selection screens)
- Confirmation dialog boxes
- Various system functions (status display, save list...)
Hope this helps.
- Regards, Dibya

Periodic Job Scheduling

Similar Messages

Maybe you are looking for