Using Combined Rules (User, System Administrator, and Flexfields Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Using Combined Rules

Using combined rules you can precisely specialize a manager.

A combined rule combines more than one action to generate a single rule. Each action is defined by one line within the rule. Combining the lines or individual actions defines the overall combined rule.

Suggestion: You can use a combined specialization rule as one of many rules to specialize a manager.

Using single Exclude and Include actions

A single Exclude action within a combined rule acts the same way as a single Exclude action that defines a specialization rule. Both instruct a manager to read all requests to run concurrent programs except those identified by the action.

Exclude Oracle ID - APPS

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

A single Include action within a combined rule acts the same way as a single Include action that defines a specialization rule. Both actions instruct a manager to read only the requests that satisfy the action.

Include Oracle ID - APPS2

Result The manager only reads requests to run concurrent programs that connect to Oracle ID "APPS2".

Using multiple Exclude actions

Using multiple Exclude actions as multiple lines within a combined rule is equivalent to using multiple Exclude actions as multiple specialization rules.

You can exclude more kinds of requests by adding more Exclude lines to your combined rule.

Exclude Program - Oracle Sales & Marketing, No entry for Name field.

AND

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

Net Result The manager reads all requests to run concurrent programs except requests for programs for the application "Oracle Sales & Marketing", and requests for programs for the application "Oracle Inventory".

Using multiple Include actions

Using multiple Include actions adds more requirements to a combined rule, and excludes more kinds of requests.

You cannot use two Include actions for the same action type. Each Include action is an exclusive statement for a particular type of action. For example, you cannot require a request to be for a program that connects to two different Oracle IDs.

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

AND

Include Program - Oracle Payables Confirm Receipt Batch

Net Result The manager only reads requests to run a single program, Confirm Receipt Batch, and only if that program is from the application "Oracle Payables".

Using Exclude and Include actions

You cannot use Exclude and Include actions for the same type of action. Each Include action is an exclusive statement for a particular type of action.

For example, it does not make sense to require a request to be for a program that connects to the Oracle ID "APPS" and disallow a request to connect to another Oracle ID.

Exclude overrides Include

When using multiple lines within a Combined Rule, the Exclude action always overrides a Include action.

Include Program - Oracle Payables Invoice Import

AND

Exclude Oracle ID - APPS2

Net Result The manager reads requests to run the Oracle Payables Invoice Import program, but will not run the program when it connects to the Oracle ID "APPS2". The Exclude action overrides the Include action.

Specializing a manager to run one program submitted by one user

You can define a combined rule that instructs a manager to only read requests to run a single program when submitted by a specific user.

Include User - Sheryl

AND

Include Program - Oracle Project Accounting Distribute Usage Costs

Net Result The manager only reads requests submitted by Sheryl to run the Distribute Usage Costs program.

Restricting the programs a manager will run for a specific user

You can define a combined rule that instructs a manager to ignore requests to run a certain programs when submitted by a specific user.

Include User - Sheryl

AND

Exclude Program - Oracle Project Accounting Expenditure Status

Net Result The manager only reads requests submitted by Sheryl, excluding requests to run the Oracle Project Accounting program Accounting Expenditure Status.

Specifying Oracle ID and excluding a program from a request type

Include Request Type - Oracle Project Accounting Expenditure Reports

AND

Include Oracle ID - APPS2

AND

Exclude Program - Oracle Project Accounting Expenditure Status

Net Result The manager only reads requests to run programs belonging to the Oracle Project Accounting request type "Reports", run against the Oracle ID "APPS2", excluding the program Expenditure Reports.

Exclude	Oracle ID - APPS
*Result*	The manager reads requests to run concurrent programs that connect to any Oracle ID, except those programs that connect to Oracle ID "APPS".

Include	Oracle ID - APPS2
*Result*	The manager only reads requests to run concurrent programs that connect to Oracle ID "APPS2".

Exclude	Program - Oracle Inventory, No entry for Name field.
*Net Result*	The manager reads all requests to run concurrent programs except requests for programs for the application "Oracle Sales & Marketing", and requests for programs for the application "Oracle Inventory".

Include	Program - Oracle Payables Confirm Receipt Batch
*Net Result*	The manager only reads requests to run a single program, Confirm Receipt Batch, and only if that program is from the application "Oracle Payables".

Include	Program - Oracle Project Accounting Distribute Usage Costs
*Net Result*	The manager only reads requests submitted by Sheryl to run the Distribute Usage Costs program.

Exclude	Program - Oracle Project Accounting Expenditure Status
*Net Result*	The manager only reads requests submitted by Sheryl, excluding requests to run the Oracle Project Accounting program Accounting Expenditure Status.