Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 6

Background Job Scheduling for IP30

(RISTRA20)
https://blogs.sap.com/2014/02/09/background-job-scheduling-for-ip30-ristra20/

Introduction

As soon as I’m done with my step-by-step reply to a discussion on the subject matter recently, I
realized that this long reply comprising of several Screen-captures possesses the characteristics of a
Document. So I thought of converting it into a Document, so that members will be benefited from this
frequently asked query.

Topic dealt here is for IP30 (program RSITRA20), but this method is valid for other programs too for
background scheduling.

Here we see, how to do:


Step1. Create IP30 Variant.

– Run IP30,

– Give your Plan (here it is ABC123 ) in the Maintenance Plan field (Do not forget this step)

– Click Save Button and in the resulting screen give the Variant name,

– Optional:- Tick Only for Background Processing and Save again.

So we have just created a Variant named TEST for IP30.


Note:

This variant will not be available for changes in IP30 Tcode, because ‘Only for Background
Processing‘ has been ticked.

For changes of this Variant, you need to Run SE38, give RISTRA20 in Program field, select Variants
radio button, and then click on Display,

Click F4 help in Variant field and click Change.

Step2. Create Background Job – Run Tcode SM36

Give Job Name and click Start Condition (See Picture)

A pop-up is displayed.

Follow the steps 1 to 7 given in Picture .

(Here it is assumed that you want the RISTRA20 program to run at midnights of everyday)
Click SAVE again

You will be given a pop-up.

Enter ABAP Program Name (Here it is RISTRA20) and the Variant (we know it is TEST), and SAVE.

(Steps 1,2,3 in the above picture)

You will be here:


Do not do anything, Click Back arrow and

SAVE

All Done

Now to see the schedule –

Run SM37 and Execute. (Give Current Date as FROM date and Date after 2 days as TO Date)

Execute to see a screen like this, where your Job is seen scheduled to be run at Midnight of Every
Day. (According to the settings in picture 3 above)

During Scheduling, the Status changes from Released to Active and after Scheduling it turns
to Finished.

Hope members will be benefited by this post.

Thank you

Jogeswara Rao K

This document was generated from the discussion: Job Scheduling and activate for Maintenance
Plans and modified to be a Document for general relevance.
Question:

During Scheduling, the Status changes from Released to Active and after Scheduling it turns
to Finished.
Can you explain what other status mean Ex: Scheduled, Ready etc.

Answer:
In SM37 screen, a list of jobs background scheduled by you are seen. At the time you are viewing
this (SM37) screen, if the system is performing the schedule (IP30 is running at that time on that
particular variant), then you will see the Status as Active . Once this Scheduling run is completed
the Status changes to Finished with Green highlighted. After Finishing the job another line of the
same job will be seen with Released status. See the picture below. (Here Active Status is not
there.)

Question:

It was a wonderful document from you on background job scheduling.

I want to know on e add-on feature on it. Suppose, I want to set few/one status automatically on MO
automatically based on some predefined conditions like order completion date (means order should
be CLSD/TECO once the order completion date is achieved.) . This prerequisite field can be a user
field also.

Once the above is achieved , a mail should be triggered from system notifying all the stakeholders
about the closure of MO.

Answer:

our query is good, But this should be discussed separately due to the reasons:

1. It has no close relation to the Scheduling function

2, It is purely technical.

Means, once you’ve achieved your requirement (using ABAP objects), they will be applicable and
automatically triggered for the Order called by Schedules.

Now coming to the point how to go about is:

1.Setting Automatic System Status upon reaching the date (perhaps you mean the Basic Start Date)
, I do not think this can be managed by user exits. I feel that BAPIs are there to meet this
requirement.

2. Triggering Mail is also possible and very frequently discussed in ABAP space.

Now there are 2 steps for you

You need to involve ABAPer closely for this task. and


1. Search the Forum through Google or otherwise for these two requirements separately with proper
search strings.

2. After getting some ideas, if your issue is still needs inputs, please post your query in two separate
discussions (both in ABAP space), using clear expressions.

(In case if you are interested to try in this EAM space first, you may)

You might also like