oracle quality setup document

8/3/2019 Oracle Quality Setup Document

1/15


2/15

Oracle Quality Created by: Aarti Gautam

Contents

Collection Elements ........................................................................................................ 3Reference ........................................................................................................................ 4Variable ........................................................................................................................... 5Attribute .......................................................................................................................... 6Specifications .................................................................................................................. 7Collection Plans .............................................................................................................. 9Actions and Notifications ............................................................................................. 12


3/15


Collection Elements

Collection elements are the basic building blocks of collection plans, which are the data structures that are

used to collect Quality results. Before you can collect Quality data, you must first create a collection plan.

You begin by creating collection elements, which define the characteristics of the product or process that

you want to monitor, record, and analyze.

Collection elements are categorized by type so that they can be sorted and grouped in database searches and

on reports. You assign collection element types to collection elements when you define them.


4/15


Reference

The Reference Information collection element type groups collection elements that reference common

objects defined in other Oracle Applications, such as Oracle Flow Manufacturing, Inventory, Order

Management, Purchasing, and Work in Process. You can reference any data within an Oracle Database.

From the Quality menu, NAV > Setup > Collection Elements.

When the Screen appears, query for Customer. This will bring up the Customer Reference Collection

Element, as shown below.

This is a seeded element and you should not modify it. You can create another as long as the name is

different. The Select statement is used to define the valid values for the data a user would select from.

Make sure the data type and reporting length match the data you are referencing. You cannot change the

data type once the element is saved page.


5/15


VariableIf you need collection elements based on specification tolerance ranges, you would use a variable collection

element type. The setup is the same except you would press the Spec Limits button at the bottom of the

form. The screen below will display.

Here you can establish the acceptable ranges of your specification. You will note the Bell curve

arrangement of the data. You can use these ranges to define actions taken when data is input outside of the

range.


6/15


Attribute

If you need collection elements based on a customized list of values, you would use an attribute collection

element type. The setup is the same except you would press the Values button at the bottom of the form.

The screen below will display. Here you can create your values you wish the user to select from.

While it is recommended you use the above elements types as described, you are not required to by the

application code. You can use create reference elements that use spec limits and so on. You can also

develop you own element types to categorize them.


7/15


Specifications

Specifications define the requirements to which the product must conform. You can define specifications

for the key characteristics of the products that you produce or for the materials that you receive from

suppliers.

You can attach illustrative or explanatory files to specifications, such as text, images, word processing

documents, spreadsheets, video, and so on. Attachments can be used to document processing instructions as

well as inspection and disposition procedures.

From you Quality menu, NAV > Setup > Specifications. The form below will appear.

You can link the specification to an Item, Supplier or Customer. It can also apply to a single item, category

or category set. I most cases you will link it to a single item. If this is the case, you can make the

Specification Name the same as the item.


8/15


Using the collection elements you previously created, enter you range data. You can also copy from

existing specifications.


9/15


Collection PlansFrom your Quality menu, NAV > Setup > Collection Plans. The screen below will appear. Here you can

enter the collection plan information.

The plan type adds no functionality beyond the grouping of collection plans. You can use the Copyelements button to open a form to copy all the elements from another collection plan. To link the collection

to an existing specification, press the SPECIFICATIONS button. The form below will appear and you may

select from the list.


10/15


For each collection plan created, Oracle generates a table view of the plandata.To generate the table, press the VIEWS button. Oracle will show a form displaying the view table name

and the import table name. You can open these tables in any SQL editor. Press the CREATE button to

complete the process.

If you wish to link the collection plan to a transaction, press the TRANSACTION button. The form belowwill appear.

Since this module was developed for discrete applications, most of the transactions refer to those modules.

It does offer links to Purchasing, EAM and Service. If you need have a user access the collection plan from

a transaction not supported, you can use a custom ZOOM.

Checking the Mandatory box will not let the user save the transaction without entering a collection plan

record. Checking the Background box allows the collection plan to automatically collect data from the

transaction detail so the user does not have to reenter it. You must check the Enabled box if you wish to use

the transaction link.

In the Collection Triggers section of the form you can establish the conditions you wish to launch the

collection plan. I the above instance, the collection plan is triggered when a user is performing a

receiving transaction of a 319-I item. The user will not be able to complete the receipt without entering the

collection plan data. There are many triggers you can choose from. It image to the right show several.


11/15



12/15


Actions and Notifications

You can use actions to perform notifications to the user or to generate emails to others based on specific

conditions. Select an element on the Collection Plans screen press the ACTIONS button.

You should now see the screen below.

There are two actions specified. We are looking at the first. This action is invoked when the user inputs a

value outside of the upper and lower specification limits of this element. When this occurs, the user is

prompted with a dialog box containing the message shown. When we review the second action, we see the

action details change. When we review the second action, we see the action details change.


13/15


Press the ACTION DETAILS button.You can now see the Actions: Send Email screen.


14/15


Here you can enter the email address, subject, and Cc or Bc addresses. In the Text area, you can enter the

body of the text along with any Variables. Variables are a way to include data specific to the record. In

order to link the variables to your plan data, press the VARIABLES button.

From this form you can define the variables used in the body of the email. This will link them to the actual

values in the quality record.

You can also create collection elements as a place holder for information determined by data in other

elements. For instance, you may wish to display the item description next to the item number. You needcreate an element. In this case we created Aleris Item Description. We added it to our collection plan and

we can now add an action rule as seen in the form below.


15/15


oracle quality setup document

Documents