Introduction

Before we start with the topic let us try to understand what we mean by Job Set.

But prior to that we should understand by the terms Job and Set here.

In context of this article the terms are defined as:

Job

While I have referred to this as a job this actually denotes the ESS Job Definition. In simple terms a Scheduled Job in Oracle Fusion Application (this was referred to as a Concurrent Program Request in Oracle E-Business Suite).Typically a ESS Job (In Fusion Applications) or Concurrent Program Request (In Oracle E-Business Suite) is a packaged program which performs a specified task like updating, deleting, inserting, archiving, synchronizing, merging, copying, import, export… etc. on Application Data.

Set

When we try to run more than one Job (explained above) either in parallel execution mode (where-in more than one job run at the same time) or in serial execution mode (one job completes and triggers the other one) we refer to such set-up as a Job-Set.

While some may argue here that in essence a Job-Set is then basically individual jobs clubbed together ( they might run at same time or one after another) then why or how do they help users, they can very well execute them in isolation. The answer is yes they can but imagine there are multiple jobs which needs to be clubbed together and it becomes hard to remember the sequence too. Job-Set comes to the rescue.

So that goes about what a Job-Set is and why we need one. And now let’s try to create a sample job-set to understand the same better.

For this example we would create a Job-Set of Execution Type Serial Mode (i.e. Second Job would start post completion of first job)

Now since, we are concentrating on creating a Job-Set in this article we would not create individual jobs but leverage the already existing ones.

Perquisite

Existence of at least two Jobs in the Application

For this example we will use

1. PersonBIAnalysisESSJob

2. PersonHireCountReport

Both of the above are Custom ESS Jobs (BIPJobType) and we will have them executed in serial mode one after another in this example. So without further delay we will get started into creating a Custom Job Set.

For easier understanding we will categorize the article in various steps as below:

Step1: Creating Job-Set

For this, we will presume the logged in user has the requisite Roles (Application Implementation Consultant in particular apart from the Employee Role) and next we need to navigate to the “Setup and Maintenance”

Next, click on the Navigator Icon and click on ’Setup and Maintenance’

On the Task List search for ‘Manage Custom Enterprise Scheduler for HCM Core Processes’

Click on the ‘Go to Task’

Two things of primary notice here:

1. We are able to see the individual jobs based on which we are going to create our set

2. We should be able to locate the Manage Job Sets tab.

Once you click on the ‘Manage Job Sets’ click on the Create button

Next, we need to populate the following details in the JobSet Section:

We would now need to populate the JobSet Steps with the below details:

JobType: Serial

Similarly, the following details need to be filled in for step20:

When we click on OK the below screen will appear:

Some key-points to note from above screen:

1. The ESS Jobs are now represented in a diagram clearly depicting that if Step10 errors out or-ends up in a warning    then the process will stop

2. Application Defined Properties gets auto-populated with two attributes as below:

1. srsFlag: A string type attribute auto-populated with the value of ‘Y’ because both the ESS Jobs can be submitted from the ESS Job Screen. This value however maybe explicitly changed to ‘N’ where in the Job-Set would not be visible for submission. For this example we would keep the default value.

2. ExT_PortletContainerWebModule: Another string type attribute which describes the basic portlet settings( default settings required on the UI during invocation from the screen) and it has the initial value of ‘hcmCore’ thereby confirming that keep the settings as required for a seeded Job (which belongs to HCM Core Setup, remember “Manage Custom Enterprise Scheduler Jobs for HCM Core Processes’ on the Task-list we chose in the beginning)

Next, we need to populate the system properties and the details to be used are:

Click on Ok and this will take you to the main screen.

If we collapse all the collapsible sections to get a complete view the definition would be similar to below snap-shot:

With this, we have completed the step of defining the Job-Set.

Next, we should move to Step2 where we would try to run the newly created Job-Set

Step2: Run the Custom Job-Set

For this, we would need to navigate to the Scheduled Processes Screen from the Navigator

A new screen would open up and you need to select the values: Schedule New Process> Type: Job Set> Name: Sample Job Set

Once you click on the ‘OK’ button a new popup window will appear

Yes!! You guessed it right once we review and find that the Job-Set displays the jobs we are interested in next we would click on the ‘Submit’ button and this will take us to the next screen

Good!!!!

The Job-set has completed and the status says succeeded.

Next, we should click on the ‘Status’ section to verify the results:

So the first Job of the Job-Set gave desired results

Now, let’s have a look at the second job:

And same with the second one, thereby confirming that we have successfully created a Custom Job-Set and have established that the same works fine.

Now the above is just a Prototype demonstrating the capabilities on the application and we may extend the same logic to add multiple Jobs and create a complex job set (either parallel or serial) depending on specific requirements.

Hopefully, this article was able to help you all in some way or other and may-be you all would be able to use this in real world scenarios.

Good Bye and Good Luck and last but not the least ‘Keep Smiling’ . ☺

Ashish Harbhajanka

Add comment