Importing Oracle Applications Concurrent Programs

You import concurrent programs to schedule them from within Redwood Server directly. The process definition parameters have constraints to allow you to easily select the appropriate username and responsibility, for example.

The following process definitions can be used to import Oracle Applications concurrent programs:

System_OraApps_ConcurrentProgramImport - imports a specific concurrent program
System_OraApps_ConcurrentProgramMultipleImport - imports multiple concurrent programs

Renaming Imported Process Definitions

The imported process definitions are named after the application short name and the program to be run. In previous releases, you were not able to rename Oracle Applications process definitions in Redwood Server as the application/program combination were derived from the name of the process definition. You can identify these legacy process definitions by the contents of the Source field on the Definition tab of the process definition editor.

Process definitions that cannot be renamed have the following in the Source field:

SUBMIT

Process definitions that can be renamed have the following in the Source field:

SUBMIT
APPL_SHORT_NAME=<application_short_name>
APPL_PROG_NAME=<program_name>

For example, the No Response Action Processor ( ALPPNR ) program that belongs to application ALR would have the following source:

SUBMIT
APPL_SHORT_NAME=ALR
APPL_PROG_NAME=ALPPNR

Both syntaxes are allowed. You re-import concurrent programs that use the old syntax to update the process definitions to use the new syntax.

Calling Your PL/SQL in Oracle Applications Processes

You specify the _userExit parameter on the imported process definition to execute a Document of type PLSQL that carries the same partition/name as the process definition, the parameter accepts the following values:

Before - the PL/SQL is executed before the function/procedure is called.
PreCommit - the PL/SQL is executed immediately before commit is called.
After - the PL/SQL is executed after the function/procedure has been called and committed.

Procedure

Importing a Concurrent Program

Navigate to "Definitions > Processes".
Choose Submit from the context-menu of System_OraApps_ConcurrentProgramImport.
On the Parameters tab, select a system in Applications System name, select an application name in Application Short name, note that although the field refers to the short name, you select the user-friendly application name.
Select a concurrent program in the Concurrent Program name field.
The following steps are optional:
On the Generation Settings tab, set Overwrite Existing Process Definitions? to Y as you want to overwrite existing process definitions. Note that if you are re-importing.
Select a partition in the Partition field.
Select an application in the Application field.
Choose Save & Close.

Example

Importing No Response Action Processor from the Alert (ALR) application

Navigate to "Definitions > Processes".
Choose Submit from the context-menu of System_OraApps_ConcurrentProgramImport.
On the Parameters tab, select a system in Applications System name, select Alert in Application Short name.
Select No Response Action Processor in the Concurrent Program name field.
Choose Save & Close.
In the main window, Refresh the process definition overview and locate ALR_ALPPNR.

Product Documentation