Skip to Content

Note: Prior to maintaining the settings for the process chains in the job commander transaction, check table TFK090A and find the job type (JTYPE) for the desired mass activities.  Analyze the determined job type to see if it used in multiple mass activities.  If so, for example A1 is used with both BILL and EMTB.  If this is true for any of the desired mass activities, the n you will need to implement logic in event 1906 so that the right mass activity can be determined.

Start:

Execute transaction FKJOXTR or follow menu path Utilities Industry -> Tools -> Administration of Mass Processing -> Background Processing Control

6-25-2013 10-33-20 AM.png

Right-click on the Container Sample and choose Create Job Container.

At the pop-up window, enter the details about one of the jobs to be scheduled.

6-25-2013 10-35-41 AM.png

The copy template data is necessary to enable the job processor to determine/copy the specifics of the mass activity, e.g. posting date or company code.   Here the template to be copied is defined for Jan 1, 2013 ID MASS.

Period data indicates the frequency and periodicity for the job.  You are also able to define how to handle non-workdays for any of the dates in the newly created job.

The type-specific settings indicate the job(s) that will be included in this container.  Only jobs of the same category can be included in one container.

After the first container is created, then create the next one.  In this example, I create the invoicing job to follow billing:

6-25-2013 10-44-20 AM.png

I have made similar settings as for the previous container, using the new job category A2 which refers to invoicing.

Having created two containers, I can create a chain to hold both of them.

Right-click on Process Chain Sample and choose Create Process chain template.

6-25-2013 10-48-09 AM.png

Click on Add to add containers to the chain.  Note: Only inactive containers will be shown here.  Do not activate your container.  It will be activated when you activate the chain.

6-25-2013 10-49-46 AM.png

Choose the billing job container to add it.

6-25-2013 10-52-43 AM.png

Repeat the process for the invoicing job container.

6-25-2013 10-53-22 AM.png

The details for the chain are saved.  Activate the chain.

6-25-2013 10-54-47 AM.png

6-25-2013 10-56-10 AM.png

After activation, generate the job containers.

6-25-2013 10-56-22 AM.png

Click on the Process Chain Overview button.

6-25-2013 11-05-29 AM.png

Double-click on the newly-defined process chain.

6-25-2013 11-06-06 AM.png

Choose the start date/time for the chain.

Look at the job log to find the scheduled chain.

6-25-2013 11-06-49 AM.png

After the job chain is executed, the SM37 log shows all of the executed processes.

6-27-2013 10-21-49 AM.png

6-27-2013 10-21-57 AM.png

Results: Here are the mass activities run and scheduled via the Job Commander settings.

6-27-2013 10-22-27 AM.png

The billing job which was scheduled and run via the job commander parameters:

6-27-2013 10-23-11 AM.png

The invoicing run which was scheduled and run via the parameters:


To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Manoj Ku. Joshi

    Hi  William ,

    Thanks for sharing such a descriptive & useful document.

    One question

    as of now in order to create automatic (periodic) batch job we are creating jobs using SM36 TCODE & putting steps using program –  “RFKK_MA_SCHEDULER”  (fpscheduler) . So my question is what are the advantages one will have if one will do the same activity by above method.

    or Which is the best way of scheduling automatic batch jobs, using “FKJOXTR” or by using “SM36 + FPSCHEDULER”

    (0) 

Leave a Reply