Frequency of CC background Jobs

Hi,
I am just wondering what is standard practice with regard to the frequency of which background jobs are scheduled in the production CC
1) Upload static text
2) Upload authorization objects
3) Refresh Informer Reports
Also there is a backend sync for mitigation and rules- I have tried to run these but the destination system field does not contain any values. I have searched for information on what these background jobs but cannot find any doucmentation.
If anybody has advice on CC background jobs I would be grateful.
Thanks,

We are running CC 5.1 and after the initial setup we only run three background jobs on the weekends. We do a user, role and profile incremential analysis. We also do a weekly batch risk analysis and then we do a weekly management report to populate the graphs in the mamagement report section.
Dave

Similar Messages

  • 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 job’s 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 system’s 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 job’s 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 job’s 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 you’ve 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 not deleted

    Hi Experts,
    i want delete the   "SM:SELFDIAGNOSIS" background job on solution manager system .
    and i have deleted,  go to next date and then delete the released job but after one day again its showing in released.
    so how i can delete it properly .
    Regards
    jai kr.

    Shiv,
    First check the frequency of this job from SM37
    Go to  SM37 -> give your job name ->and select all the options like
    delete  the entries in start date and end date fileds. then execute.
    If you find  job in Released state  ,simply go to  menu Job -> click on release to schedule.
    Now this job will in Schedule and won't run untill you release it.
    Deleting the jobs is not good idea ,simply you can suspend it.
    Regards,
    Srinivas Chapa.

  • Background job 'SPOOL_OBJECTS' ?

    We have a background job in our SRM 5.0 (Extended Classic Scenario) which runs the program SPOOL_OBJECTS.  This job is sometimes run by RFCUSER, and sometimes by user WF-BATCH.
    We've been live on SRM since 02/2007. We are trying to document all background jobs, and this one has slipped thru the cracks. 
    Can anyone shed some light on what this job is or what it does ?
    Thanks
    Sue
    Edited by: Susan Keohan on Feb 5, 2008 11:24 AM

    Hi Susan,
    I guess it is the one from the configuration point "Set Control Parameters".
    Here are an extract of the configuration help.
    Set Control Parameters
    You only perform this step if you create Materials Management documents in the backend system.
    You specify:
    Information about the spooler
    Information about the update frequency
    Documents in the backend system are updated asychronously. You can only further process the requirement coverage request in the Enterprise Buyer system after the update has been made.
    The system checks at set intervals whether the backend documents have been created. If so, the system updates the requirement coverage request. Then the requirement coverage request can be further processed. If not, the system checks after the next interval whether the documents have been posted.
    Example
    You specify:
    That the spooler should try to contact the backend system at ten-minute intervals
    You enter the lead time in seconds
    The system calculates the time until the next attempt as follows:
    Time interval = lead time entered * square of the number of previous attempts
    The backend user names that the system should use to start the retries
    That the spooler should try to contact the backend system a maximum of ten times
    Key Description Value
    SPOOL_JOB_USER User name MEIER
    SPOOL_LEAD_INTERVAL Lead time 600
    SPOOL_MAX_RETRY Number of tries 10
    For the update interval, you define:
    That the system should check at 60 second intervals whether the backend documents have been posted
    The backend user name that the system should use to start the retries
    Key Description Value
    CLEANER_INTERVAL Interval 60
    CLEANER_JOB_USER User name SMITH
    Kind regards,
    Yann

  • How to schedule a background job in realtime

    Hi,
    Can you tell me how to schedule a background job in realtime.
    give some example scenerios in scheduling the background jobs in realtime.
    Thanks.
    sam.

    And also.....
    There are two ways for you to handle,
    one manually setting up the job through SM36 which is better and convinient,
    secondly through program using FM's JOB_OPEN, SUBMIT, JOB_CLOSE.
    Find below steps in doing both:
    Procedure 1:
    1. Goto Trans -> SM36
    2. Define a job with the program and variant if any
    3. Click on start condition in application tool bar
    4. In the pop-up window, click on Date/Time
    5. Below you can see a check box "Periodic Job"
    6. Next click on Period Values
    7. Select "Other Period"
    8. Now give '15' for Minutes
    9. Save the job
    Procedure 2 via Program:
    Below is a sample code for the same. Note the ZTEMP2 is the program i am scheduling with 15mins frequency.
    DATA: P_JOBCNT LIKE TBTCJOB-JOBCOUNT,
    L_RELEASE(1) TYPE c.
    CALL FUNCTION 'JOB_OPEN'
    EXPORTING
    JOBNAME = 'ZTEMP2'
    IMPORTING
    JOBCOUNT = P_JOBCNT
    EXCEPTIONS
    CANT_CREATE_JOB = 1
    INVALID_JOB_DATA = 2
    JOBNAME_MISSING = 3
    OTHERS = 4.
    IF SY-SUBRC 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    SUBMIT ZTEMP2 VIA JOB 'ZTEMP2' NUMBER P_JOBCNT
    TO SAP-SPOOL WITHOUT SPOOL DYNPRO
    WITH DESTINATION = 'HPMISPRT'
    WITH IMMEDIATELY = SPACE
    WITH KEEP_IN_SPOOL = 'X' AND RETURN.
    CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
    JOBCOUNT = P_JOBCNT
    JOBNAME = 'ZTEMP2'
    STRTIMMED = 'X'
    PRDMINS = 15
    IMPORTING
    JOB_WAS_RELEASED = L_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
    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.
    Hope the above helps you.
    ***********reward points,if found useful

  • How to create a Background Job?

    Hi All,
    A ABAP List report is taking too long to run. It takes nearly 5 mints sometimes it is halted by a timeout. I would like to run this report as a background job. What's the transaction I should use & could U give me the steps. Also is it possible to schedule the Job to run on 1st of every month.
    Thanks,
    Kishan

    1.programatically ( job_open , job_close)
    2.thorugh sm36 ( defining a job & scheduling)
    doing something programmatically certainly has an advantage of automation... there may be cases wherein depending on certain conditions u need to run different programs in the background.. so this can be incorporated in the program itself using if/else or other condition commands..
    there may be numerous other differences too.
    SM36 option is more of static one and programmitaclly is more on the fly scheduling a job.
    Using SM36, it not a one time thing. If you want program to run at a specific frequency, say every 24 hrs, that also can be done.
    1)data: sdate type sy-datum,
    stime type sy-uzeit,
    l_valid,
    ls_params like pri_params,
    l_jobcount like tbtcjob-jobcount,
    l_jobname like tbtcjob-jobname.
    start-of-selection.
    Get Print Parameters
    call function 'GET_PRINT_PARAMETERS'
    exporting
    no_dialog = 'X'
    importing
    valid = l_valid
    out_parameters = ls_params.
    Open Job
    l_jobname = 'ZRICH_0005'.
    call function 'JOB_OPEN'
    exporting
    jobname = l_jobname
    importing
    jobcount = l_jobcount.
    Submit report to job
    submit zrich_0005
    via job l_jobname
    number l_jobcount
    to sap-spool without spool dynpro
    spool parameters ls_params
    and return.
    Kick job off 30 seconds from now.
    sdate = sy-datum.
    stime = sy-uzeit + 30.
    Schedule and close job.
    call function 'JOB_CLOSE'
    exporting
    jobcount = l_jobcount
    jobname = l_jobname
    sdlstrtdt = sdate
    2)Use transaction SM36.
    http://help.sap.com/saphelp_bw30b/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm
    sdlstrttm = stime
    strtimmed = 'X'
    Please use T/code SM36> enter your Job name Starts with Z or Y Ex: ZTEST> STEP>ABAP Program> Define your Report /Variant--> Save.
    Start condition--> Press Date and Time > Enter your start date and time> Save
    Then Use SM37--To execute ur job
    Lanka

  • Periodic Scheduling of sequencial background job

    I schedule monthly & weekly planning jobs. These jobs are scheduled one after another in a sequence. frequency of running these jobs is fix hence I want to schedule it on periodic basis. It possible for me to schedule single background job periodically but I don't know how to schedule sequncial backgorund jobs on periodic basis.
    Regards,
    Chetan

    Dear Siva,
    Thanks for your reply.
    for execution of single job periodically I am following the same procedure mentioned by you.
    I scheduled background jobs one after another by clicking on start condition & in pop-up select "After job". this way I schedule 7 to 8 jobs one after another.
    So in first scheduled job you will find 7 to 8 successor jobs.
    Now if I try to make it periodic, then only first job becomes periodic & successor jobs doesn't get released periodically.
    I want to make entire chain of jobs to be scheduled peiodic.
    Regards,
    Chetan

  • How to get BI background jobs to utilize parallel processing

    Each step in our BI process chains creates exactly 1 active batch job (SM37) with in turn utilizes only 1 background process (SM50).
    How do we get the active BI batch job to use more than 1 background process similar to parallel processing (RZ20) in an ERP system?

    Hi there,
    Have you checked the number of background and parallel processes. Take a look in SAP Note 621400 - Number of required BTC processes for process chains. This may be helpful ...                                                                               
    Minimum (with this setting, the chain runs more or less serially):        
    Number of parallel SubChains at the widest part of the chains + 1.        
    Recommended:                                                              
    Number of parallel processes at the widest part of the chain + 1.         
    Optimal:                                                                  
    Number of parallel processes at the widest part of the chain + number of  
    parallel SubChains at the widest part + 1.                               
    The optimal settings just avoids a delay if several SubChains are         
    started in parallel at the same time. In case of such a Process Chain     
    implementation and using the recommended number of background processes   
    there can be a short delay at the start of each SubChain (depends on the  
    frequency of the background scheduler, in general ~1 minute only).                                                                               
    Attention: Note that a higher degree of parallel processing and           
    therefore more batch processes only make sense if the system has          
    sufficient hardware capacity.                                                                               
    I hope this helps or it may lead you to further checks to make .
    Cheers,
    Karen

  • Background job cancelled

    Hi Experts
           I have defined and scheduled a background job using variant, but when i try to execute the job, but it is cancelled and gives the job log as follows.
    Job started                                                                                00 516 S 
    Step 001 started (program ZCUT1, variant ZONE, user ID SAP01)  00 550  S 
    ABAP/4 processor: OBJECTS_OBJREF_NOT_ASSIGNED           00  671  A 
    Job cancelled                                                                            00  518  A 
    What could be the reason, pls help me solve it out.
    Thanks in advance.
    Regards
    Rajaram

    HI,
    refer this once.
    There are two ways for you to handle,
    one manually setting up the job through SM36 which is better and convinient,
    secondly through program using FM's JOB_OPEN, SUBMIT, JOB_CLOSE.
    Find below steps in doing both:
    Procedure 1:
    1. Goto Trans -> SM36
    2. Define a job with the program and variant if any
    3. Click on start condition in application tool bar
    4. In the pop-up window, click on Date/Time
    5. Below you can see a check box "Periodic Job"
    6. Next click on Period Values
    7. Select "Other Period"
    8. Now give '15' for Minutes
    9. Save the job
    In SM37 u can check the status of the jobs that u have assigned to background...
    Here u mention the job name or the report name to check the status of the job...
    After mentioning the job name or program name u just execute it.. ( without any name also u can execute then it gives u all the jobs set by your user name..
    the status colud be released,active,finished etc..
    Procedure 2 via Program:
    Below is a sample code for the same. Note the ZTEMP2 is the program i am scheduling with 15mins frequency.
    DATA: P_JOBCNT LIKE TBTCJOB-JOBCOUNT,
    L_RELEASE(1) TYPE c.
    CALL FUNCTION 'JOB_OPEN'
    EXPORTING
    JOBNAME = 'ZTEMP2'
    IMPORTING
    JOBCOUNT = P_JOBCNT
    EXCEPTIONS
    CANT_CREATE_JOB = 1
    INVALID_JOB_DATA = 2
    JOBNAME_MISSING = 3
    OTHERS = 4.
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    SUBMIT ZTEMP2 VIA JOB 'ZTEMP2' NUMBER P_JOBCNT
    TO SAP-SPOOL WITHOUT SPOOL DYNPRO
    WITH DESTINATION = 'HPMISPRT'
    WITH IMMEDIATELY = SPACE
    WITH KEEP_IN_SPOOL = 'X' AND RETURN.
    CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
    JOBCOUNT = P_JOBCNT
    JOBNAME = 'ZTEMP2'
    STRTIMMED = 'X'
    PRDMINS = 15
    IMPORTING
    JOB_WAS_RELEASED = L_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
    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.

  • Notification upon Background Job Cancellation

    Hi All,
    We would like to send a notification to responsible person upon CANCELLATION of background job for various reasons.
    What would be the best way to do it?
    I tried to various events of business objects BPJOB/BPJOB_SMAN, with no sucess.
    Will appreciate any guidance in this regard.
    Thanks in Advance.
    Regards,
    Lakshmi Narayana

    HI ,
    You create one Z- Report and Write the following logic in it :-
    1. Give a Job Name as selection selection parameter on the selection screen.
    2. Select all those records from the Table TBTCO where JOBNAME = selection screen job name and SDLSTRTDT - sy-datum and STATUS = 'A'.
       This will return you with all those jobs which were scheduled and canceled on current date. Status 'A' Means Canceled jobs.
    3. Now you use FM 'EFG_GEN_SEND_EMAIL' to send a notification to the required user as per your requirement.
    4. Now Enter all the JOb name which you want to monitor and save one varient for it
    5. Now go to SM36 and Schedule this Z-Report with the created variant and the frequency you want.
    This will Satisfy your requirement.
    Please check and Revert.
    Regards,
    Nikhil Joshi

  • Setting up Background job

    Hello Guys,
    I gone thru the forum and tried to set up the background job for an requirement but could not able to proceed further as I was not sure how to move on..
    Requirement
    We would like setup to call our PM's automatically when they are due or at least 3 days before.This would save time to plan well in advance.
    In this case where should I mention the 3 day period ? I just started getting into SM36 and clikc the start condition and set the time to run and then flagged the periodic job and clicked the periodic values as daily and save it. Then I hit steps button and maintain ristra20 as prog name and keep the variant as blank and save it .(Is variant is neccessary ?) Then I get into sm37 where I could see some * on job name .I dont know how to proceed from here and wht would be the job name and other steps Also I tested job wizard and not sure what is the purpose of this ?
    Could anyone walk me through for the above mentioned requirement
    Mahee

    Mahee,
      Creating the work order ahead of the actual due date is actually accomplished by the "call Horizon" parameter on the Maintenance Plan. A 100% Value on this field indicates that the Call object be created on the date its due. Please enter a appropriate value here based on the plan to get the order created 3 days ahead.
    You actually schedule the PM in background using IP30 transaction.First create and save a variant for the plan that you would liek to schedule.Then call up the variant In here enter the plan details and then choose Program > execute in background.Enter a valid SAP printer and then choose "DATE AND TIME" push button to enter the start date and time of the job.After this, Choose the "Periodic job" check box and then choose "period values" at the bottom of the screen to indicate the frequency at which you would like to run the program and then choose the "SAVE" button.
    This should complete teh job creation for you.
    Regards
    Narasimhan

  • Difference between Batch jobs and background jobs...

    hi APO Gurus ....
    This may sound a very silly question. What is  the exact difference between a batch run and executing a background job ?

    If i understand correctly  your question is  executing a program (for example) in background and running in a batch jobs.  You can execute a program in background while you are online, go to menu program->execute in background and enter print parameter, schedule parameter. System creates and starts job dynamically. You can check in SM37.  Batchjob is you create job using   SM36 (with program and Variant) define run frequency. System automatically run job in specified frequency.  I my experience, technically both are same, system behaves exactly same. One dynamically creates job other one runs on predefined freq.
    Thanks,
    Niranjan

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

  • Scheduling one background job inside another

    Hi All,
    Is it possible to Scheduling one background job inside another.? i.e In my Z program I am calling job_open, job_submit, job_close and to execute one standard report in background. And after that I am executing my Z program itself  from SE38 as Program->Execute->Background->Execute Immediately. Is this logically correct? I am asking this because I am not getting the desired result
    Thanks & Regards,
    Neethu.

    HI,
    Check the job steps in SM36.
    First schedule the Standard job and in the job steps schedule the z report.
    Schedule job in chain

  • Background Job pass value

    Hi, I am calling a Background job in my program. I am using JOB_OPEN, JOB_SUBMIT and JOB_CLOSE FM to start a job. My need is to pass a value to the job program(job program doesnt have any selection screen values). Is their any way without creating variants each time to pass value to it.
    Please advice.....

    Hello,
    You can first use  JOB_OPEN which returns job number. Then build ranges or parameters to use SUBMIT to call the program.
    Eg: SUBMIT RM06BB20 AND RETURN
          WITH S_EKGRP IN R_EKGRP
          WITH S_EKORG IN R_EKORG
          WITH S_FLIEF IN R_FLIEF
          WITH S_KONNR IN R_KONNR
          USER sy-uname VIA JOB w_jobname
          NUMBER w_job_number.
    Now use JOB_CLOSE.
    Thanks,
    Venu

Maybe you are looking for