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:

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:

Copy 
SUBMIT

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

Copy 
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:

Copy 
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

  1. Navigate to Definitions > Processes.
  2. Choose Submit from the context menu of System_OraApps_ConcurrentProgramImport.
  3. 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.
  4. Select a concurrent program in the Concurrent Program name field.
  5. The following steps are optional:
  6. 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.
  7. Select a Partition in the Partition field.
  8. Select an Application in the Application field.
  9. Click Save & Close.

Example

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

  1. Navigate to Definitions > Processes.
  2. Choose Submit from the context menu of System_OraApps_ConcurrentProgramImport.
  3. On the Parameters tab, select a system in Applications System name, select Alert in Application Short name.
  4. Select No Response Action Processor in the Concurrent Program name field.
  5. Click Save & Close.
  6. In the main window, Refresh the Process Definition overview and locate ALR_ALPPNR.

Speeding Up Parameter List Building

When you are preparing to submit a concurrent program, and you are supplying values in the Parameters screen, you may notice a delay after you select a field while RunMyJobs queries Oracle EBS for a list of valid parameter values. The length of this delay depends on the size and complexity of the table being queried. If the time required to fetch valid parameter values for a particular parameter is very long, you can configure the Process Definition to wait until a certain number of characters is entered in the field before querying the database.

For example, assume a parameter named OraApps_UserNametakes a few seconds to pull up a full list of valid user names because there are many users. To speed this up, you can configure the OraApps_UserName parameter to wait until you have entered three characters before querying the Oracle database. This results in a shorter list of valid values, so the list populates much more quickly.

To configure a field in this way, add the following to the end of the Source field in the Process Definition's Definition tab:

Copy 
[MinimumParameterLength]
FieldName=x

You can configure multiple parameters this way. For example:

Copy 
[MinimumParameterLength]
OraApps_SystemName=3O
OraApps_ResponsibilityName=3

See Also