Examples - Using Specialization Rules (User, System Administrator, and Flexfields Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Examples - Using Specialization Rules

Following are examples of using specialization rules to define what requests a concurrent manager can read. When multiple rules are used to specialize a manager, the words OR and AND appear between each rule to clarify the relationship among multiple specialization rules.

Using Include and Exclude actions

Include	Program - Oracle Assets, No entry for Name field.
*Result*	The manager only reads requests to run concurrent programs for the application "Oracle Assets".

Include Program - Oracle Assets, No entry for Name field.

OR

Include Program - Oracle Payables, No entry for Name field.

Net Result The manager only reads requests to run concurrent programs for the application "Oracle Assets", or for the application "Oracle Payables".

The use of multiple Include actions expands the manager's ability to read requests beyond that of a single Program (single Include action).

Exclude Oracle ID - APPS2

Result The manager reads requests to run concurrent programs that connect to any Oracle ID, except those programs that connect to Oracle ID "APPS2".

Exclude Oracle ID - APPS2

AND

Exclude Program - Oracle Payables, No entry for Name field.

Net Result The manager reads requests to run concurrent programs that connect to any Oracle ID, except programs that connect to Oracle ID "APPS2", and programs for the application "Oracle Payables".

Simplify your work

Multiple rules may not always be necessary, or the number or complexity of rules can be simplified. Consider the example below.

Include Program - Oracle Sales and Marketing, No entry for Name field.

OR

Include Request Type - Sales Forecasts

Net Result The manager only reads requests to run concurrent programs for the application "Oracle Sales and Marketing", or programs whose request type is "Sales Forecasts".

In this example, both rules are not necessary when programs belonging to the request type "Sales Forecasts" all connect to the Oracle ID "OSM". There is no need for the second Type Include rule.

Exclude rules override Include rules

Include

Program - Oracle Payables, No entry for Name field.

AND

Exclude Program - Oracle Payables Invoice Aging Report

Net Result The manager reads all requests for concurrent programs for the application "Oracle Payables", but does not read requests to run the Oracle Payables program "Invoice Aging Report".

Include Program - Signon Audit Forms

AND

Exclude Request Type - Signon Audit Reports

Net Result If the System Administrator program Signon Audit Forms belongs to the Request Type "Signon Audit Reports", the manager will not read requests to run the program, even though it has been specifically identified by an Include rule. The Exclude rule overrides the Include rule.

Specializing to only run a Program against specific Oracle IDs

In the following example, a manager can be specialized to only run a program against a specific Oracle ID. This is useful when there are multiple installations of an Oracle Application.

Include Program - Oracle Payables Invoice Aging Report

AND

Exclude Oracle ID - APPS2

Net Result The manager only reads requests to run the Oracle Payables program "Invoice Aging Report" when the program does not connect to the Oracle ID "APPS2". The Exclude action overrides the Include action.

However, when the Invoice Aging Report runs against another Oracle ID, for example, "APPS", then this manager will read requests to run the program. This is useful when working with multiple installations of an application and data groups.

Distinguishing a Program from a Request Type

You can specialize a manager to read requests to run all the programs belonging to a Request Type, except for individual programs you wish to identify.

Include Request Type - Oracle General Ledger Reports

AND

Exclude Program - Oracle General Ledger Account Analysis

Net Result If the Account Analysis program belongs to the request type Oracle General Ledger "Reports", then this manager will run every program in the request type Oracle General Ledger Reports, except the program Account Analysis.

Preventing specific programs from running

You can use an Exclude action more than once. For example, suppose your manager reads all requests to run concurrent programs for a particular application, but you want to prevent your manager from running two specific programs. You can:

Include Program - Oracle General Ledger, No entry for Name field.

AND

Exclude Program - Oracle General Ledger Consolidation Audit

AND

Exclude Program - Oracle General Ledger Consolidation Rules

Net Result The manager reads requests for any concurrent programs for the application "Oracle General Ledger", except for the programs "Consolidation Audit" and "Consolidation Rules".

Specializing to run only specific programs at certain times

Using multiple Include rules, you can specialize a manager to run only specific programs. Then, when you define the manager's work shift, you can control when the manager reads requests to run the specific programs.

Include Program - Oracle Payables Invoice Aging Report

OR

Include Program - Oracle Purchasing Receipt Accruals

Net Result The manager only reads requests to run the Oracle Payables Invoice Aging Report, or the Oracle Purchasing Receipt Accruals program.

Suggestion: If you only wanted these two reports run during the night you can define the manager's work shift to run from 2:00am-6:00am (02:00-06:00).

Suggestion: When you first submit the requests to run the programs, you can define a resubmission interval, for example, 1 month, to resubmit the programs to run every month.

Specializing according to application User

You can specialize managers to only read requests from specific users.

Include User - Markus Kalkin

Net Result The manager only reads requests submitted by the application user "Markus Kalkin".

Include User - Markus Kalkin

OR

Include Program - Oracle Inventory Process Demand Interface

OR

Include Program - Oracle Inventory Summarize Demand Histories

Net Result The manager reads both requests submitted by user Markus Kalkin and requests to run the Oracle Inventory programs "Process Demand Interface" and "Summarize Demand Histories".

Suggestion: If you want specific programs submitted by a specific user to "jump ahead" of other requests waiting to be run, you can define and specialize a manager as in the example above, and set the user profile option Concurrent:Priority for the user to a high priority (Concurrent:Priority sets the priority of requests submitted by the user).

Define a manager and give it a descriptive name.

Specialize the manager as in the example above.

Set the user profile option Concurrent:Priority for user Markus to 10.

Include	Program - Oracle Payables, No entry for Name field.
*Net Result*	The manager only reads requests to run concurrent programs for the application "Oracle Assets", or for the application "Oracle Payables".
	The use of multiple Include actions expands the manager's ability to read requests beyond that of a single Program (single Include action).
Exclude	Oracle ID - APPS2
*Result*	The manager reads requests to run concurrent programs that connect to any Oracle ID, except those programs that connect to Oracle ID "APPS2".
Exclude	Oracle ID - APPS2

Include	Request Type - Sales Forecasts
*Net Result*	The manager only reads requests to run concurrent programs for the application "Oracle Sales and Marketing", or programs whose request type is "Sales Forecasts".
	In this example, both rules are not necessary when programs belonging to the request type "Sales Forecasts" all connect to the Oracle ID "OSM". There is no need for the second Type Include rule.

Exclude	Program - Oracle Payables Invoice Aging Report
*Net Result*	The manager reads all requests for concurrent programs for the application "Oracle Payables", but does not read requests to run the Oracle Payables program "Invoice Aging Report".

Exclude	Request Type - Signon Audit Reports
*Net Result*	If the System Administrator program Signon Audit Forms belongs to the Request Type "Signon Audit Reports", the manager will not read requests to run the program, even though it has been specifically identified by an Include rule. The Exclude rule overrides the Include rule.

Exclude	Program - Oracle General Ledger Account Analysis
*Net Result*	If the Account Analysis program belongs to the request type Oracle General Ledger "Reports", then this manager will run every program in the request type Oracle General Ledger Reports, except the program Account Analysis.

Exclude	Program - Oracle General Ledger Consolidation Rules
*Net Result*	The manager reads requests for any concurrent programs for the application "Oracle General Ledger", except for the programs "Consolidation Audit" and "Consolidation Rules".

Include	Program - Oracle Purchasing Receipt Accruals
*Net Result*	The manager only reads requests to run the Oracle Payables Invoice Aging Report, or the Oracle Purchasing Receipt Accruals program.

Include	User - Markus Kalkin
*Net Result*	The manager only reads requests submitted by the application user "Markus Kalkin".

Include	Program - Oracle Inventory Summarize Demand Histories
*Net Result*	The manager reads both requests submitted by user Markus Kalkin and requests to run the Oracle Inventory programs "Process Demand Interface" and "Summarize Demand Histories".