• The four key steps in Quality Management are: Define, Identify, Analyze, and

Correct. The Define and Identify tasks together constitute Quality Inspection
Management, while the Analyze and Correct tasks together constitute Quality
Issues and Actions Management.
• Quality Issue and Action Management is a part of Product Management
Cloud that integrates with other Oracle Fusion applications to help you
achieve closed loop quality.
• You can assign privileges ONLY to roles and not to the user directly.
• With the role of a quality engineer, you can create, manage, and review 1)
inspection characteristics, 2) levels, 3) plans, and 4) quality inspections.
• Other roles like the production operator, warehouse operator, and receiving
agent enable you to do different types of inspections.
• With the role of a quality analyst, you can create, manage, and review
quality actions and issues and also navigate to the items and change orders in
Product Development.
• To give View Only access to users, you can create a new SCM job role, and
either add the 'Quality Inspection Review' shipped duty role.
• All users can access problem reports or corrective actions, until you restrict
access.
Quality Inspection:
• Item based inspection characteristics- mapped to item attributes.
• Non-item based inspection characteristics - that aren't mapped to item attribute
values. These non-item inspection characteristics can be of type: Number,
Character, or Date.
• You can use the non-item based inspection characteristics for both item and
resource related inspections.
• An inspection level determines the relative amount and frequency of
inspection.
• Skip lot is applicable only for the Receiving inspections.
• Except for the Receiving plan type and the Work in Process plan type, all
other plan types only allow 100 percent inspection level.
• If sampling is employed, three types of sampling can be done: ANSI, Fixed
Count, %age.
• With percentage-based sampling and fixed count sampling, the entire
inspection quantity will be rejected if even one of the representative samples
fails the inspection.
• With AQL sampling, the entire inspection quantity will be rejected if the
number of representative samples that fail inspection is greater than or equal
to the rejection quantity as set forth in the Acceptable Quality Limit tables.

Inspection Plans:
• RIRAWIP-Acronym to remember five types of inspection plans: Receiving,
Inventory, Resource, Assets, Work in Progress.
• If you are creating the inspection plan for an item catalog, then select the
catalog associated with one of these functional areas: Inventory, Purchasing,
Planning, or Quality Inspection Management.
• For receiving and work in process in-line inspections, when there are
applicable plans defined against more than one functional area, the priority
sequence of selection will be: 1) Receiving: Quality Inspection Management,
Purchasing, Inventory, and then Planning. 2)Work In Process: Quality
Inspection Management, Planning, Inventory, and then Purchasing.
• Means in receiving inspection, first purchasing will be inspected, and in wip
inspection, first planning will be inspected.
• Plan statuses: New, On hold, Obsolete, Approved.
• By default, all plans have 100 percent inspection level. This means that all
units must be inspected, all the time. The only exception is for the Receiving
and Work in Process plans, as they allow user-defined inspection levels.
• User-defined inspection levels can include: Sampling and Skip lots.
• You can mark a plan as optional when you want to do ad hoc inspection.
However, if you want to do inline inspections, you must not make a plan
optional.
• You can only copy a plan between the same inspection type. For example, you
can copy a plan from an inventory plan to another inventory plan, but not to a
work in process plan
• We can Specify inspection criterion for Receiving, Inventory, Asset and
Work in Process inspection plans – means what we want to be inspected.
• You don't separately specify inspection criteria for Resource Inspection
plans, as no additional criteria is required other than the information entered
in the plan details.
• Inspection plan criteria is optional for an Asset inspection plan.
• At any point of time, you can only use one version of a plan to do inspections
• When you create a new version, you specify a start date. If you have not
specified an end date for the previous plan version, the previous version
becomes obsolete a day before the new version's start date. From the new
version's start date, you can start using it for new inspections.
• For the Resource inspection plan, you can only add non-item inspection
characteristics.
• Use inspection action rules to either guide the users or automatically trigger
an action based on the inspection results.
• While creating or modifying an inspection plan, use the inspection
characteristics listed in the Specifications tab to create action rules.
• Steps to create inspection action rules:
Inspection plan>Inspection Characteristics>Manage Action Rules>Create
Action Rule>Attributes>Select the characteristic for the IF condition>Select
one or more actions to trigger for the Then or Else part of the condition.
• Six actions can be triggered using action rules: 1)Create Maintenance work
order 2) Create quality issue 3) Display message 4) Raise an event 5) Change
material status 6)Send a notification
• WIP supports both ad hoc and inline inspections.
• Resource, Inventory and asset support only ad-hoc inspections.
• Receiving supports only inline inspections.
• Ad hoc inspections are also called as standalone inspections
• With standalone inspections, you can collect inspection results without a
parent transaction.
• Adhoc inspections can be created from Maintenance landing page, Quality
Management landing page, or Work Execution landing page.
• For Adhoc inspections, It is not mandatory to select a plan. You can proceed
even without selecting a plan.
• You must have a matching inspection plan to do inline inspections.
• Skip lot is applicable only for the Receiving inspections.
• Entering the lot number is optional for a work in process inspection and
mandatory for an inventory inspection.
• Even if a line is marked for skip lot inspection, you can override the skip
quantity inspection setting during inspection and choose to inspect all
samples.
• For receiving inspections, when sampling is enabled, during the inline
inspection, if one or more samples fail the inspection, and the entire lot is
rejected, you can choose to inspect all units. Then the inspection ceases to be
 a sampling inspection. You can then inspect all units, reject or accept each
unit separately. This saves the entire lot from getting rejected.
• When you create an inspection, the inspection number is automatically
generated as a concatenation of the inspection results
• Inspection number for : 1) Inventory inspection is the concatenation of item
number and subinventory 2)Receiving inspection is the concatenation of
receipt number and item number 3) Work in process inspection is the
concatenation of work order number and item number 4) Resource
inspection is the resource name.
• Quality Management Cloud cannot be used as a standalone solution without
the Oracle SCM Cloud.
• Remember to first enable Auditing of Issues and Actions to see any audit log
entries in the History side tab to see auditing of quality issues and actions.

Quality Issues and Actions:

• Save as - you can use it to create a quality action from a quality issue, copying
over all attachments and affected objects.
• You can create and relate a new quality action from a quality issue. This copies
affected objects, attachments, and some attributes to the new quality
action.
• You can't edit the quality event when it's in a read-only state like Approval or
Closed.
• Workflow in QIM is minimum: Draft, open, closed.
• 8D workflow is a type of quality action workflow.
• Workflow tasks are withdrawn automatically if they're not used in 180 days or
more.
• Providing a comment while terminating and restarting the workflow is
required.
• You can assign a specific organization to a quality action or issue during its
creation or later with the Organization attribute on the quality action or issue.
• Relationship rules or Dependency rules are used to move an object
automatically in its workflow, when the related object moves to its specific
status.
• Relationship rules can close a quality issue upon the closure of its related
quality action. It can also close a quality action upon implementation of a
related change order.
• The creator and the assignee can always access the quality issues or actions.
• The ability to update an issue or action in each status is controlled by the Allow
Updates setting for that status in the workflow template. If updates aren’t
allowed for that status, we can’t update issue.
Security:
• Use the Security side tab on issues and actions to add users and roles who can
view and search for issues or actions.
• Two types of security are functional security and data security.
 • Functional security defines the functions you can perform and the pages and
objects you can access.
• Data security defines access to specific data (records) and is applied in
addition to functional security. For example, even though you can create and
manage quality issues (functional security) as a user you may not see the
quality issue "ISSUE46", because the data record isn't visible for your user role
(data security).
• Quality objects creation can only be allowed or prevented through functional
security.
• You can't delete inspection nonconformances, but you can perform most
editing operations.
• You can't edit quality issues and actions if they're in certain states, such as
waiting for approval, or after approval and closure
• Four standard status types are: Open, Interim approval, approval, completed.
Problem Reports:
• A problem report is a generic quality incident or problem reported from a
customer's perspective.
• Problem reports can be created from QIM, PIM and PD.
• You can add or remove approvers in the interim approval and approval status.
You can add or remove participants of type reviewers when the change is in
draft, open, approval, and interim approval, scheduled, or completed statuses.
•