Profile Options (Oracle Quality Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Profile Options

Oracle Quality profile options control how data is accessed and processed and how Oracle Quality integrates with other Oracle and non-Oracle products. The following table list all the profile options for Oracle Quality, the level at which they can be updated, whether they are required, and their default values, if any:

Key

You can update the profile option.

QA:Action Processing Mode

Determines the processing mode of actions that are invoked as quality results are collected or updated.

The Display a message to the operator, Reject the input message, and the Assign a Value action are processed immediately regardless of how this profile option is set. See: Action Processing.

Alert actions are processed concurrently in the background regardless of how this profile option is set. See: Action Processing and Alert Actions.

Available options are as follows:

Concurrent processing When you save quality results, the system spawns a concurrent process and returns control immediately to you, allowing you to continue working.

On-line processing The system processes your actions while you wait, and control is returned once action processing is completed.

If a concurrent process fails, a failure message appears in the concurrent manager log file and in the Quality Action Log. See: Viewing and Deleting Action Log Entries.

QA:Blind Results Entry

Indicates whether, as quality results are collected, the specification limits and UOMs associated with collection plan elements or specification elements are displayed.

Available values are listed below:

Blind Entry On The operator does not see the specification limits and UOMs when collecting quality results. Actions associated with results are, however, processed regardless.

Blind Entry Off The operator sees the specification limits and UOMs when collecting quality results.

QA:Default Collection Plan

Indicates which collection plan to use as a default when entering, updating, and viewing quality results. This default is also used when viewing lot and serial quality results and when finding and viewing action log entries. The default collection plan is not used during transactional data collection.

QA:Default Specification Target

Indicates whether to use specification element target values as collection plan element default values when you collect quality results.

If you do not select a specification when entering quality results, or if no specification element target values are defined, target values from collection elements are defaulted instead.

If you have explicitly defined collection plan element default values, these values are used regardless of how this profile option is set. See: Default Value Assignment Rules.

Available values are listed below:

Yes Defaults target values from specification elements.

No Does not default target values from specification elements.

QA:PO Inspection

Determines whether inspection results and quantities accepted/rejected are entered in Oracle Purchasing or Oracle Quality.

Available options are as follows:

Quality Quality If this option is set, when you choose the Inspect button from the Oracle Purchasing Receiving Transactions window, Oracle Quality's Enter Quality Results window appears. See: Entering Quality Results Directly.

Oracle Purchasing If this option is set, when you choose the Inspect button from the Oracle Purchasing Receiving Transaction window, Oracle Purchasing's Inspection Details window appears. See: Inspecting Received Items

QA:Quality Category Set

Indicates which item category set to use as the default in Oracle Quality. Item category sets are defined in Oracle Inventory. See: Overview of Item Categories and Defining Category Sets.

The item category set specified here is used as the default when defining item category specifications. You must therefore set this profile option before defining item category specifications.

If you are entering quality results for an item using a collection plan that is associated with a specification, but no specification for that item can be found, then the system uses the Quality Category Set to find a specification that is defined with the item's category. See: Finding Specifications While Entering Results Directly and Finding Specifications During Transactional Data Collection.

Attention: You can only view specifications associated with the Quality Category Set specified by this profile option. Changing this profile option prevents you from viewing specifications entered under a previously entered category set.

QA:Statistics Engine

Determines which statistics engine to use when creating charts, viewing descriptive statistics, and exporting the data used to create these charts and views.

Oracle Quality Charts and descriptive statistics views are create in Oracle Quality. The results used to created these charts and views can be exported to an ASCII file.

Statit Charts and descriptive statistic views are created using the Statit statistical analysis package. The results used to create these charts and views can be exported directly to Statit.

Warning: If you choose to use the Statit engine, you must set the QA:Statistics Engine Path profile option.

See: Integrating Oracle Quality and Statit.

QA:Statistics Engine Path

Indicates where the Statit software is installed. This path is also used when Statit data is saved and files are exported.

Example: c:\statit

Concurrent processing	When you save quality results, the system spawns a concurrent process and returns control immediately to you, allowing you to continue working.
On-line processing	The system processes your actions while you wait, and control is returned once action processing is completed.

Blind Entry On	The operator does not see the specification limits and UOMs when collecting quality results. Actions associated with results are, however, processed regardless.
Blind Entry Off	The operator sees the specification limits and UOMs when collecting quality results.

Yes	Defaults target values from specification elements.
No	Does not default target values from specification elements.

Quality Quality	If this option is set, when you choose the Inspect button from the Oracle Purchasing Receiving Transactions window, Oracle Quality's Enter Quality Results window appears. See: Entering Quality Results Directly.
Oracle Purchasing	If this option is set, when you choose the Inspect button from the Oracle Purchasing Receiving Transaction window, Oracle Purchasing's Inspection Details window appears. See: Inspecting Received Items

Oracle Quality	Charts and descriptive statistics views are create in Oracle Quality. The results used to created these charts and views can be exported to an ASCII file.
Statit	Charts and descriptive statistic views are created using the Statit statistical analysis package. The results used to create these charts and views can be exported directly to Statit.