See how easy it is to set up Oracle E-Business concurrent programs to run in Automate Schedule. With just a few simple steps you can integrate with other job streams, in different applications, and on different servers; with the flexibility to schedule jobs to run dependently or independently of each other. File transfers can react to other existing job streams, and be part of any job flow. 


Today I'm going to show you how to setup Oracle E-Business Suite concurrent programs to run in Skybot. The first thing that we need to do is define your Oracle E-Business server to Skybot. So you'll select a name and a description; this is a valid Oracle user name and password. We need to tell Skybot the location of the environment setting file, and this file might have a different path and name depending on the platform that you're running E-Business Suite on. And then the application settings, so you can run different applications on different servers, so this would be the user, the responsibility name, and the responsibility short name for that user that you want to run these applications within E-Business Suite.

Creating a Job to Run Your Concurrent Programs

Once we have the server setup, then we can create a Skybot job to run your concurrent programs. So we'll go ahead and create a job. So the job that we're running is a concurrent program from Oracle, so this is my list of programs, and I've searched and found the one that I want to go ahead and run on Skybot. And this one's within my application object library, and it's a report that I'm going to run. So I'll go ahead and copy that program name, I'm going to use that as the Skybot name. I'll use it as the description just for speed, and then we select the agent to run it onîBravo is my Oracle serverîand I'm going to add this tag that I can use for sorting and filtering. Now we're going to give a schedule to this job, and I want this job to run every day. I'm going to have it run in the evening at 20:00, and that's pretty much it for the schedule. We only want this job to run on working days, so if it's a holiday we're not going to run that job.

We need to add an environment for this job to run in; the easiest one is to just run as the agent's user so this is an operating system user. And now we're going to add the command to run the concurrent request. So we select from a list of options that we have, and you'll be prompted to enter the system definition. I'm going to check this Wait, yes for any processes that are spawned from this original request, because if I use this in a reactive job stream, I want to make sure that all those child processes are completed before I get a completion code on this job. Enter a short name for the applicationîthere's our concurrent program name againîI can leave this blank. This is the name that you would see the job running when you watch it in Oracle, and so I'm just going to let it keep the Skybot job name and number. I could also add some parameters if I needed to, but I don't for this one, so I'll go ahead, and save it.

So now I've created my E-Business Suite job, I'm going to go ahead and save that, and now this job is going to run every day at 20:00.

Scheduling E-Business Suite Jobs Within a Job Stream

One of the other options that you have is to use those jobs in other job streams, so even though this jobs going to run every day, I might have it in a job stream like this one. So here we have a number of different applications, and these jobs are all dependent on one another. So in this first job I have an E-Business concurrent request that I'm going to run as part of this job. This job is going to run two steps. The first step is using our file transfer built-in function, and I'm going to pull a file down from one of my FTP servers and then when that's completed I'm going to go ahead and run this concurrent request. So you can have your jobs run individually, you can add them to other existing job streams, and now E-Business concurrent programs can be part of any job flow.


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: October 24, 2019