Concurrent Programs
A concurrent program is an instance of an execution file, along with parameter definitions and incompatibilities. Concurrent programs use concurrent program executables to locate the correct execution file. Several concurrent programs may use the same execution file to perform their specific tasks, each having different parameter defaults and incompatibilities.Concurrent Program Executable
A concurrent program executable links an execution file or and the method used to execute it with a defined concurrent program. Under Concurrent Processing, an execution method may be a program written in a standard language, a reporting tool, or an operating system language.An execution method can be a PL/SQL Stored Procedure, an Oracle Tool such as Oracle Reports or SQL*Plus, a spawned process, or an operating system host language.
Concurrent Program Execution File
A concurrent program execution file is an operating system file or database stored procedure which contains your application logic and can be executed by either invoking it directly on the command line or by invoking a program which acts upon it. For example, you run a Pro*C program by invoking it on the command line. You run a SQL script by running SQL*Plus and passing the name of the SQL script without the .sql extension.Steps to Create a Concurrent Pro
1. Executable :
The first step in creating a concurrent program in oracle applications is to create the concurrent program executable. To do this, navigate to Application Developer responsibility after you login to Oracle Applications. To login, you can take the help of the ‘Topic11 - Oracle Applications Login Document’.
To open the Executable form follow the below mentioned navigation path.
Application Developer à Concurrent à Executable.
Figure 1. Executable Form Navigation
You will see the form as shown in figure 2 below.
Figure 2. Executable Form
Field Description
i) Executable - Enter executable name here. Enter any user friendly name.
ii) Short Name - Enter short name for your executable. This is used for mapping the executable with the concurrent program. Usually executable name are of 8 characters.
iii) Application - Give the application to which the executable belongs to. E.g. you want some program to run from oracle payables then account payables should be entered as application name.
iv) Description - Give the brief description of the executable in this field.
v) Execution Method - Here you need to choose the appropriate execution method for your executable. Following are the possible execution methods which are commonly used in oracle applications.
iii) Application - Give the application to which the executable belongs to. E.g. you want some program to run from oracle payables then account payables should be entered as application name.
iv) Description - Give the brief description of the executable in this field.
v) Execution Method - Here you need to choose the appropriate execution method for your executable. Following are the possible execution methods which are commonly used in oracle applications.
- Oracle Reports – used for the RDF reports
- Host – used for shell scripts, basically the language of the host operating system
- PL/SQL Stored procedure – used to run the stored procedure through oracle applications
- SQL*Loader – used to run the sql loader programs
- SQL*Plus - used to run the anonymous PL/SQL blocks. It will get executed in the same fashion as you are running on SQL Plus.
- Java Stored Procedure – The execution file is a Java stored procedure.
- Java Concurrent Program – Used for program written in Java.
- Spawned – used for c or pro*c Program. Mainly used by standard oracle interfaces.
- Perl Concurrent Program – used for programs written in CGI Perl.
- Request Set Stage Function – PL/SQL stored function that can be used to calculate the completion statuses of request set stages.
- Immediate – execution file is a program written to run as subroutine of the concurrent manager. Oracle doesn’t recommend use of this executable type.
- Multi-Language function – execution file is an MLS function that supports running concurrent program in multiple languages.
vi) Executable File name – This should contain the name of the executable file. In case of PL/SQL Stored procedure or Java Stored Procedure it should be the fully defined name of the stored procedure.
vii) Subroutine Name – This field is only used when executable type is spawned or immediate.
viii) Execution File Path -
ix) The Stage Function Parameters button opens a window that allows you to enter parameters for the Request Set Stage Function. This button is only enabled when you select Request Set Stage Function as your Execution Method.
No comments:
Post a Comment