Oracle eBusiness Suite Technical Reference

Release 11i - Copyright (c) 2001 - 2005 Oracle

This Technical Reference Manual (TRM) in any form, software or printed matter, contains proprietary information of Oracle ; it is provided under an Oracle agreement containing restrictions on use and disclosure and is also protected by copyright, patent, and other intellectual property law. Restrictions applicable to this TRM include, but are not limited to: (a) exercising either the same degree of care to safeguard the confidentiality of this TRM as you exercise to safeguard the confidentiality of your own most important Confidential Information or a reasonable degree of care, whichever is greater; (b) maintaining agreements with your employees and agents that protect the Confidential Information of third parties such as Oracle and instructing such employees and agents of these requirements for this TRM; (c) restricting disclosure of this TRM to those of your employees who have a 'need to know' consistent with the purposes for which this TRM was disclosed to you; (d) maintaining this TRM at all times on your premises; (e) not removing or destroying any proprietary or confidential legends or markings placed upon this TRM in whatever form, software or printed matter; and (f) not reproducing or transmitting this TRM in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle. You should not use this TRM in any form, software or printed matter, to create software that performs the same or similar functions as any Oracle products.

The information in this TRM is subject to change without notice. If you find any problems in the TRM in any form, software or printed matter, please report them to us in writing. Oracle does not warrant that this TRM is error free. This TRM is provided to customer 'as is' with no warranty of any kind. This TRM does not constitute Documentation as that term is defined in Oracle's agreements. Reverse engineering of the Programs (software and documentation) associated with this TRM are prohibited. The Programs associated with this TRM are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee's responsibility to take all appropriate fail safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs. Program Documentation is licensed for use solely to support the deployment of the Programs and not for any other any other purpose. Restricted Rights Legend

This TRM and the Programs associated with this TRM delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, this TRM and the Programs associated with this TRM delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the restrictions in FAR 52.227-14, Rights in Data General, including Alternate III (June 1987). Oracle, 500 Oracle Parkway, Redwood City, CA 94065.

Oracle is a registered trademark. AIM Advantage™, Big Business. Small Business. All Business.™, CDM Advantage™, .comference™, ConText®, Des40®, Easy*Query™, Easy*SQL®, Education Objects™, EMM Advantage™, Enabling the Information Age®, ExpertDetectSM, Express®, FastForwardSM, GEMMS®, Gist™, Hyper*SQL™, instantOracle™, "Internet Business Intelligence - Insight for Everyone"™, iSQL*Plus™, JInitiator™, NLS*Workbench®, Object Marketplace™, ODP Pulse™, ODP Techwire™, OLA™, On Oracle™, Oracle®, Oracle Book®, Oracle Bookbatch®, Oracle BookBuilder®, OracleBRONZE®, Oracle Business OnLine®, OracleDevConnectSM, Oracle® Discoverer™, Oracle® Expert™, Oracle Financials®, OracleGOLDSM, OracleIncidentSM, OracleJSP™, OracleLifeCycleSM, Oracle Media Objects®, OracleMERCURYSM, OracleMetaLinkSM, OraclemetalsSM, OracleMobile™, Oracle Names®, Oracle NetSolutions®, Oracle® One™, Oracle Open Gateways®, Oracle OpenWorld®, OraclePLATINUMSM, Oracle Power Objects®, Oracle Press®, Oracle Procedural Gateway®, Oracle Quality®, Oracle Secure Network Services®, OracleSILVERSM, Oracle® SQL/Services™, Oracle® SQL*TutorSM, OracleSTERLINGSM, Oracle Store®, Oracle Transparent Gateway®, OracleWare®, Oracle8i™, Oracle9i™, PC Express®, Personal Express®, PJM Advantage™, PL/SQL™, Pro*Ada®, Pro*C™, Pro*C/C++™, Pro*COBOL®, Pro*FORTRAN®, Pro*Pascal®, Pro*PL/1®, Pro*REXX®, Profit™, ProREXX™, Report Card™, Secure Access 2.0™, Secure Network Services®, Security Without Compromise™, SellingPoint®, SQL*Plus®, Tutor™ are trademarks or registered trademarks of Oracle. Other names may be trademarks of their respective owners. The absence of a product or service name, slogan, or logo from this list does not constitute a waiver of Oracle's trademark or other intellectual property rights concerning that name, slogan, or logo.

eTRM - QA Tables and Views

TABLE - QA.QA_ACTIONS

TABLE - QA.QA_ACTION_LOG

TABLE - QA.QA_AHL_MR_DUMMY

TABLE - QA.QA_BIS_RESULTS

TABLE - QA.QA_BIS_UPDATE_HISTORY

TABLE - QA.QA_BUG1339720_METHOD

TABLE - QA.QA_BUG1339720_TEMP

TABLE - QA.QA_CAR_TYPES

TABLE - QA.QA_CHARS

TABLE - QA.QA_CHART_CONSTANTS

TABLE - QA.QA_CHART_CONTROL

TABLE - QA.QA_CHART_DATA

TABLE - QA.QA_CHART_GENERIC

TABLE - QA.QA_CHART_HEADERS

TABLE - QA.QA_CHAR_ACTIONS

TABLE - QA.QA_CHAR_ACTION_OUTPUTS

TABLE - QA.QA_CHAR_ACTION_TRIGGERS

TABLE - QA.QA_CHAR_INDEXES

TABLE - QA.QA_CHAR_VALUE_LOOKUPS

TABLE - QA.QA_CONTROL_LIMITS

TABLE - QA.QA_CRITERIA

TABLE - QA.QA_CRITERIA_HEADERS

TABLE - QA.QA_CSI_ITEM_INSTANCES_DUMMY

TABLE - QA.QA_DEVICE_DATA_VALUES

TABLE - QA.QA_DEVICE_INFO

TABLE - QA.QA_GRANTED_PRIVILEGES

TABLE - QA.QA_INTERFACE_ERRORS

TABLE - QA.QA_IN_LISTS

TABLE - QA.QA_MQA_LOT_SERIAL_TEMP

TABLE - QA.QA_PC_CRITERIA

TABLE - QA.QA_PC_ELEMENT_RELATIONSHIP

TABLE - QA.QA_PC_PLAN_RELATIONSHIP

TABLE - QA.QA_PC_RESULTS_RELATIONSHIP

TABLE - QA.QA_PLANS

TABLE - QA.QA_PLAN_CHARS

TABLE - QA.QA_PLAN_CHAR_ACTIONS

TABLE - QA.QA_PLAN_CHAR_ACTION_OUTPUTS

TABLE - QA.QA_PLAN_CHAR_ACTION_TRIGGERS

TABLE - QA.QA_PLAN_CHAR_VALUE_LOOKUPS

TABLE - QA.QA_PLAN_COLLECTION_TRIGGERS

TABLE - QA.QA_PLAN_TRANSACTIONS

TABLE - QA.QA_RESULTS

TABLE - QA.QA_RESULTS_INTERFACE

TABLE - QA.QA_RESULTS_UPDATE_HISTORY

TABLE - QA.QA_SAMPLING_ASSOCIATION

TABLE - QA.QA_SAMPLING_CUSTOM_RULES

TABLE - QA.QA_SAMPLING_INSP_LEVEL

TABLE - QA.QA_SAMPLING_PLANS

TABLE - QA.QA_SAMPLING_STD_RULES

TABLE - QA.QA_SEQ_AUDIT_HISTORY

TABLE - QA.QA_SKIPLOT_ASSOCIATION

TABLE - QA.QA_SKIPLOT_LOG

TABLE - QA.QA_SKIPLOT_LOT_PLANS

TABLE - QA.QA_SKIPLOT_PLAN_STATES

TABLE - QA.QA_SKIPLOT_PROCESSES

TABLE - QA.QA_SKIPLOT_PROCESS_PLANS

TABLE - QA.QA_SKIPLOT_PROCESS_PLAN_RULES

TABLE - QA.QA_SKIPLOT_RCV_RESULTS

TABLE - QA.QA_SKIPLOT_STATE_HISTORY

TABLE - QA.QA_SL_SP_RCV_CRITERIA

TABLE - QA.QA_SPECS

TABLE - QA.QA_SPEC_CHARS

TABLE - QA.QA_TXN_COLLECTION_TRIGGERS

VIEW - APPS.QABV_COLELMACTN

VIEW - APPS.QABV_COLELMACTT

VIEW - APPS.QABV_COLLECTION_ELEMENTS

VIEW - APPS.QABV_COLLECTION_PLANS

VIEW - APPS.QABV_COLLECTION_PLAN_ELEMENTS

VIEW - APPS.QABV_COLPLNELAC

VIEW - APPS.QABV_COLPLNTXN

VIEW - APPS.QABV_COLPLNTXNT

VIEW - APPS.QABV_PLNELMACTT

VIEW - APPS.QABV_QUALITY_ACTION_TYPES

VIEW - APPS.QABV_QUALITY_SPECIFICATIONS

VIEW - APPS.QABV_QUALSPCELM

VIEW - APPS.QAFV_COLELMACTN

VIEW - APPS.QAFV_COLELMACTT

VIEW - APPS.QAFV_COLLECTION_ELEMENTS

VIEW - APPS.QAFV_COLLECTION_PLANS

VIEW - APPS.QAFV_COLLECTION_PLAN_ELEMENTS

VIEW - APPS.QAFV_COLPLNELAC

VIEW - APPS.QAFV_COLPLNTXN

VIEW - APPS.QAFV_COLPLNTXNT

VIEW - APPS.QAFV_PLNELMACTT

VIEW - APPS.QAFV_QUALITY_ACTION_TYPES

VIEW - APPS.QAFV_QUALITY_SPECIFICATIONS

VIEW - APPS.QAFV_QUALSPCELM

VIEW - APPS.QA_ACTION_LOG_V

VIEW - APPS.QA_BIS_RESULTS_V

VIEW - APPS.QA_CHARS_V

VIEW - APPS.QA_CHAR_ACTIONS_V

VIEW - APPS.QA_CHAR_ACTION_OUTPUTS_V

VIEW - APPS.QA_CHAR_ACTION_TRIGGERS_V

VIEW - APPS.QA_CHAR_VALUE_LOOKUPS_V

VIEW - APPS.QA_CRITERIA_HEADERS_V

VIEW - APPS.QA_CRITERIA_V

VIEW - APPS.QA_CRITERIA_V1

VIEW - APPS.QA_CUSTOMERS_LOV_V

VIEW - APPS.QA_DEVICE_DATA_VALUES_V

VIEW - APPS.QA_ERES_INTEGRATION_PLANS_V

VIEW - APPS.QA_ERES_PC_RESULTS_REL_V

VIEW - APPS.QA_ERES_PLANS_V

VIEW - APPS.QA_ERES_PLAN_CHAR_ACTIONS_V

VIEW - APPS.QA_ERES_RCV_TRANS_INTERFACE_V

VIEW - APPS.QA_ERES_SPECS_V

VIEW - APPS.QA_ERES_WSH_DELIVERABLES_V

VIEW - APPS.QA_ERES_WSH_NEW_DELIVERIES_V

VIEW - APPS.QA_GLOBAL_RESULTS_V

VIEW - APPS.QA_GRANTED_PRIVILEGES_V

VIEW - APPS.QA_GROUP_V

VIEW - APPS.QA_HZ_PARTY_RELATIONSHIPS_V

VIEW - APPS.QA_IN_LISTS_V

VIEW - APPS.QA_LOOKUPS

VIEW - APPS.QA_MQA_COLLECTION_TRIGGERS_V

VIEW - APPS.QA_PC_CRITERIA_COLUMNS_V

VIEW - APPS.QA_PC_PLAN_COLUMNS_V

VIEW - APPS.QA_PC_RESULTS_RELATIONSHIP_V

VIEW - APPS.QA_PC_RESULT_COLUMNS_V

VIEW - APPS.QA_PLANS_V

VIEW - APPS.QA_PLANS_VAL_V

VIEW - APPS.QA_PLAN_CHARS_V

VIEW - APPS.QA_PLAN_CHAR_ACTIONS_V

VIEW - APPS.QA_PLAN_CHAR_ACTION_OUTPUTS_V

VIEW - APPS.QA_PLAN_CHAR_ACTION_TRIGGERS_V

VIEW - APPS.QA_PLAN_COLLECTION_TRIGGERS_V

VIEW - APPS.QA_PLAN_TRANSACTIONS_V

VIEW - APPS.QA_PO_NUMBERS_LOV_V

VIEW - APPS.QA_RESULTS_FULL_V

VIEW - APPS.QA_RESULTS_QWB_V

VIEW - APPS.QA_RESULTS_V

VIEW - APPS.QA_RESULTS_VAL_V

VIEW - APPS.QA_SALES_ORDERS_LOV_V

VIEW - APPS.QA_SAMPLING_PLANS_V

VIEW - APPS.QA_SAMPLING_RCV_CRITERIA_V

VIEW - APPS.QA_SAMPLING_RCV_CRITERIA_VAL_V

VIEW - APPS.QA_SEQ_AUDIT_HISTORY_V

VIEW - APPS.QA_SKIPLOT_PLAN_STATE_V

VIEW - APPS.QA_SKIPLOT_PROCESSES_V

VIEW - APPS.QA_SKIPLOT_PROCESS_PLANS_V

VIEW - APPS.QA_SKIPLOT_RCV_CRITERIA_V

VIEW - APPS.QA_SKIPLOT_RCV_CRITERIA_VAL_V

VIEW - APPS.QA_SKIPLOT_RCV_RESULTS_V

VIEW - APPS.QA_SKIPLOT_STATE_HISTORY_V

VIEW - APPS.QA_SL_CRITERIA_ASSOCIATION_V

VIEW - APPS.QA_SL_SP_RCV_CRITERIA_ALL_V

VIEW - APPS.QA_SL_SP_RCV_CRITERIA_V

VIEW - APPS.QA_SPECS_V

VIEW - APPS.QA_SPECS_VAL_V

VIEW - APPS.QA_SPEC_CHARS_V

VIEW - APPS.QA_SPEC_CHARS_VAL_V

VIEW - APPS.QA_SPEC_ORGS_V

VIEW - APPS.QA_SPEC_ORG_ASSIGNMENTS_V

VIEW - APPS.QA_SP_CRITERIA_ASSOCIATION_V

VIEW - APPS.QA_TXN_COLLECTION_TRIGGERS_V

VIEW - APPS.QA_USER_GROUP_V

Table: QA_ACTIONS

Primary Key: QA_ACTIONS_PK

1. ACTION_ID

Foreign Keys to this table:

Comments

QA_ACTIONS stores the master list of actions available in Oracle Quality. Each row of the table defines one action and provides its description. Actions may be enabled or disabled as indicated by the flag ENABLED_FLAG and may be visible to the user or run in the background. All enabled actions in this table are available to users during collection element and collection plan definitions and are triggered during results entry. All information in the table is pre-seeded and should not be changed.

Indexes

Columns

[top of page]

QA.QA_ACTIONS does not reference any database object

QA.QA_ACTIONS is referenced by following:

QA

VIEW - QA_ACTIONS#

[top of page]

Table: QA_ACTION_LOG

Primary Key: QA_ACTION_LOG_PK

1. LOG_ID

Foreign Keys from this table:

Comments

QA_ACTION_LOG contains traceability information for the Post an Entry to Quality Action Log action. Traceability information includes textual information, dates, the trigger (action rule), and the entry that activated the trigger. Entries in this table are also created when an action being processed
in concurrent mode fails.

Indexes

Columns

[top of page]

QA.QA_ACTION_LOG does not reference any database object

QA.QA_ACTION_LOG is referenced by following:

QA

VIEW - QA_ACTION_LOG#

[top of page]

Table: QA_AHL_MR_DUMMY

Comments

A dummy table to mirror ahl_mr_headers_b. Oracle Internal use only - reserved for future use.

Columns

[top of page]

QA.QA_AHL_MR_DUMMY does not reference any database object

QA.QA_AHL_MR_DUMMY is referenced by following:

QA

VIEW - QA_AHL_MR_DUMMY#

[top of page]

Table: QA_BIS_RESULTS

Primary Key: QA_BIS_RESULTS_PK

1. OCCURRENCE

Comments

QA_BIS_RESULTS is used in Business Intelligence Reports (BIS) to enhance performance. This table is periodically populated by the QLTBISB concurrent program to mirror data in QA_RESULTS.

Indexes

Columns

[top of page]

QA.QA_BIS_RESULTS does not reference any database object

QA.QA_BIS_RESULTS is referenced by following:

QA

VIEW - QA_BIS_RESULTS#

[top of page]

Table: QA_BIS_UPDATE_HISTORY

Comments

QA_BIS_UPDATE_HISTORY stores the last refresh date and time for the BIS Summary Table. It also acts as a log for records deleted from QA_RESULTS, which are then deleted from QA_BIS_RESULTS during the next Incremental Rebuild.

Columns

[top of page]

QA.QA_BIS_UPDATE_HISTORY does not reference any database object

QA.QA_BIS_UPDATE_HISTORY is referenced by following:

QA

VIEW - QA_BIS_UPDATE_HISTORY#

[top of page]

Table: QA_BUG1339720_METHOD

Comments

Used as a temporary resource in Bug 1339720

Columns

[top of page]

QA.QA_BUG1339720_METHOD does not reference any database object

QA.QA_BUG1339720_METHOD is referenced by following:

QA

VIEW - QA_BUG1339720_METHOD#

[top of page]

Table: QA_BUG1339720_TEMP

Comments

Used as a temporary resource in Bug 1339720

Columns

[top of page]

QA.QA_BUG1339720_TEMP does not reference any database object

QA.QA_BUG1339720_TEMP is referenced by following:

QA

VIEW - QA_BUG1339720_TEMP#

[top of page]

Table: QA_CAR_TYPES

Primary Key: QA_CAR_TYPES_PK

1. CAR_TYPE_ID

Foreign Keys to this table:

Comments

QA_CAR_TYPES supports functionality being planned for a future
release.

Indexes

Columns

[top of page]

QA.QA_CAR_TYPES does not reference any database object

QA.QA_CAR_TYPES is referenced by following:

QA

VIEW - QA_CAR_TYPES#

[top of page]

Table: QA_CHARS

Primary Key: QA_CHARS_PK

1. CHAR_ID

Primary Key: QA_CHARS_UK1

1. NAME

Foreign Keys to this table:

Comments

QA_CHARS contains information about collection elements also known as Quality Characteristics. Some collection elements are seeded when Oracle Quality is installed, however, you can define new collection elements, which are also stored in this table. Collection elements may be enabled or disabled. You can only use enabled collection elements for the purpose of defining collection plans.
QA_CHARS can store the following types of information: display information, such as prompts and hints, which are shown during results entry; data, such as the datatype and default value of the collection element; validation information such as SQL validation strings; and specifications, such as upper and lower limits. QA_CHARS also stores information about the collection element type and context.
Collection element context is determined by the value of the CHAR_CONTEXT_FLAG, which indicates whether or not a collection element is a standard Quality Characteristic, has any dependency to any other collection element, or is referenced from any other elements in another Oracle Applications table. Depending on the value of CHAR_CONTEXT_FLAG, some other fields in this table may represent unifying context information for the collection element. For example, the collection element in CHAR_ID depends on the collection element represented by DEPENDENT_CHAR_ID. If a collection element is referenced, information from fields such as FK_TABLENAME or PK_ID denote the relationship between QA_CHARS and the foreign table.
QA_CHARS.HARDCODED_COLUMN stores the name of the corresponding column in the QA_RESULTS table in which the values for this collection element are stored. For example, if QA_CHARS.HARDCODED_COLUMN has a value, there will be a corresponding column in the QA_RESULTS table that will store the collection element's result value. If QA_CHARS.HARDCODED_COLUMN has a null value, then one of the generic CHARACTERx columns is used to store the collection element's value.

Indexes

Columns

[top of page]

QA.QA_CHARS does not reference any database object

QA.QA_CHARS is referenced by following:

QA

VIEW - QA_CHARS#

[top of page]

Table: QA_CHART_CONSTANTS

Primary Key: QA_CHART_CONSTANTS_PK

1. SUBGROUP_SIZE

Comments

QA_CHART_CONSTANTS contains tabular information used in the
calculation of control limits. This information is seeded when Oracle
Quality is installed and cannot be changed.

Columns

[top of page]

QA.QA_CHART_CONSTANTS does not reference any database object

QA.QA_CHART_CONSTANTS is referenced by following:

QA

VIEW - QA_CHART_CONSTANTS#

[top of page]

Table: QA_CHART_CONTROL

Comments

Special charting table for control chart type.

Indexes

Columns

[top of page]

QA.QA_CHART_CONTROL does not reference any database object

QA.QA_CHART_CONTROL is referenced by following:

QA

VIEW - QA_CHART_CONTROL#

[top of page]

Table: QA_CHART_DATA

Comments

QA_CHART_DATA is used by Oracle Quality for the temporary storage of
charting calculation results.

Columns

[top of page]

QA.QA_CHART_DATA does not reference any database object

QA.QA_CHART_DATA is referenced by following:

QA

VIEW - QA_CHART_DATA#

[top of page]

Table: QA_CHART_GENERIC

Comments

Table to keep data points of a chart to be plotted.

Indexes

Columns

[top of page]

QA.QA_CHART_GENERIC does not reference any database object

QA.QA_CHART_GENERIC is referenced by following:

QA

VIEW - QA_CHART_GENERIC#

[top of page]

Table: QA_CHART_HEADERS

Comments

Table to keep an instance of a chart to be plotted.

Indexes

Columns

[top of page]

QA.QA_CHART_HEADERS does not reference any database object

QA.QA_CHART_HEADERS is referenced by following:

QA

VIEW - QA_CHART_HEADERS#

[top of page]

Table: QA_CHAR_ACTIONS

Primary Key: QA_CHAR_ACTIONS_PK

1. CHAR_ACTION_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

QA_CHAR_ACTIONS contains actions defined for collection elements. Each row of the table defines one action and its detail.

Indexes

Columns

[top of page]

QA.QA_CHAR_ACTIONS does not reference any database object

QA.QA_CHAR_ACTIONS is referenced by following:

QA

VIEW - QA_CHAR_ACTIONS#

[top of page]

Table: QA_CHAR_ACTION_OUTPUTS

Primary Key: QA_CHAR_ACTION_OUTPUTS_PK

1. CHAR_ACTION_ID
2. TOKEN_NAME

Foreign Keys from this table:

Comments

QA_CHAR_ACTION_OUTPUTS stores the mapping between collection elements and tokens used to define actions. Oracle Quality allows you to define actions based on the tokens for some of the actions. While executing the actions, these tokens are substituted with collection element values. Each row of this table stores information about a collection element, its associated action, and the token used in defining the action.

Indexes

Columns

[top of page]

QA.QA_CHAR_ACTION_OUTPUTS does not reference any database object

QA.QA_CHAR_ACTION_OUTPUTS is referenced by following:

QA

VIEW - QA_CHAR_ACTION_OUTPUTS#

[top of page]

Table: QA_CHAR_ACTION_TRIGGERS

Primary Key: QA_CHAR_ACTION_TRIGGERS_PK

1. CHAR_ACTION_TRIGGER_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

QA_CHAR_ACTION_TRIGGERS contains one row for each defined action trigger associated with a collection element. Action triggers are the rules that specify the conditions under which the action is activated during results entry. When the specified condition is met, the designated action is activated. You can define more than one trigger for a collection element. You assign each trigger a sequence number, which indicates the order in which the trigger is activated.
Each row in the table contains a collection element Identifier, a trigger sequence, and the operator used to define the trigger for the collection element. Operators are assigned numeric equivalents, which are displayed in the table. For example, the Less Than (<) operator is represented by the number six.
Based on the operator used, a row may contain a single value, or two values used to define a range of values from low (LOW_VALUE_OTHER) to high (HIGH_VALUE_OTHER). For example, if you use the operator Equals (=), which is represented by the number one, you enter a single value in the LOW_VALUE_OTHER field. When the user enters a collection element for this value, the action rule evaluates to TRUE. If you use the operator Between, which is represented by the number nine and indicates a range of values, you must enter a value for both LOW_VALUE_OTHER and HIGH_VALUE_OTHER. When the user enters a collection element value that falls within that range, the action rule is evaluated to TRUE. If the LOW_VALUE_LOOKUP or HIGH_VALUE_LOOKUP fields are populated, the collection element's specification limits determine whether or not the action is activated. If these fields are NULL, the actual values from LOW_VALUE_OTHER and HIGH_VALUE_OTHER determine whether or not the action is activated.

Indexes

Columns

[top of page]

QA.QA_CHAR_ACTION_TRIGGERS does not reference any database object

QA.QA_CHAR_ACTION_TRIGGERS is referenced by following:

QA

VIEW - QA_CHAR_ACTION_TRIGGERS#

[top of page]

Table: QA_CHAR_INDEXES

Primary Key: QA_CHAR_INDEXES_PK

1. CHAR_ID

Foreign Keys from this table:

Comments

Collection Element User-Defined Indexes. This table keeps track of information about user-defined indexes created on collection elements.

Indexes

Columns

[top of page]

QA.QA_CHAR_INDEXES does not reference any database object

QA.QA_CHAR_INDEXES is referenced by following:

QA

VIEW - QA_CHAR_INDEXES#

[top of page]

Table: QA_CHAR_VALUE_LOOKUPS

Primary Key: QA_CHAR_VALUE_LOOKUPS_PK

1. CHAR_ID
2. SHORT_CODE

Foreign Keys from this table:

Comments

QA_CHAR_VALUE_LOOKUPS contains the set of permissible values for
collection elements. Each row of the table contains one value for
a collection element. The collection element value entered by the user
is validated against this table. These values take precedence over
SQL_VALIDATION_STRING.

Indexes

Columns

[top of page]

QA.QA_CHAR_VALUE_LOOKUPS does not reference any database object

QA.QA_CHAR_VALUE_LOOKUPS is referenced by following:

QA

VIEW - QA_CHAR_VALUE_LOOKUPS#

[top of page]

Table: QA_CONTROL_LIMITS

Primary Key: QA_CONTROL_LIMITS_PK

1. CONTROL_LIMIT_ID

Foreign Keys from this table:

Comments

QA_CONTROL_LIMITS contains control chart limit information that will
be associated with a control chart for the specified collection element.

Indexes

Columns

[top of page]

QA.QA_CONTROL_LIMITS does not reference any database object

QA.QA_CONTROL_LIMITS is referenced by following:

QA

VIEW - QA_CONTROL_LIMITS#

[top of page]

Table: QA_CRITERIA

Primary Key: QA_CRITERIA_PK

1. CRITERIA_SEQUENCE

Foreign Keys from this table:

Comments

QA_CRITERIA is used to store "show results where" information to
retrieve specific values from collected results. QA_CRITERIA is used
by Oracle Quality's charts, Dynamic Reportwriter, and descriptive
statistics functionality.

Indexes

Columns

[top of page]

QA.QA_CRITERIA does not reference any database object

QA.QA_CRITERIA is referenced by following:

QA

VIEW - QA_CRITERIA#

[top of page]

Table: QA_CRITERIA_HEADERS

Primary Key: QA_CRITERIA_HEADERS_PK

1. CRITERIA_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

QA_CRITERIA_HEADERS is used to store use- defined charts, descriptive
statistics, and settings for the Dynamic Reportwriter. It has a
master-detail relationship with QA_CRITERIA.

Indexes

Columns

[top of page]

QA.QA_CRITERIA_HEADERS does not reference any database object

QA.QA_CRITERIA_HEADERS is referenced by following:

QA

VIEW - QA_CRITERIA_HEADERS#

[top of page]

Table: QA_CSI_ITEM_INSTANCES_DUMMY

Comments

Dummy table that mirrors a subset of csi_item_instances. This table is used to resolving splicing issue when QA needs to reference csi_item_instances table. There will be a synonym qa_csi_item_instances that points to this dummy table initially. Then, CSI installation will repoint the synonym to point to csi_item_instances.. Oracle Internal use only - reserved for future use

Columns

[top of page]

QA.QA_CSI_ITEM_INSTANCES_DUMMY does not reference any database object

QA.QA_CSI_ITEM_INSTANCES_DUMMY is referenced by following:

QA

VIEW - QA_CSI_ITEM_INSTANCES_DUMMY#

[top of page]

Table: QA_DEVICE_DATA_VALUES

Comments

QA_DEVICE_DATA_VALUES stores the data received from different devices.

Columns

[top of page]

QA.QA_DEVICE_DATA_VALUES does not reference any database object

QA.QA_DEVICE_DATA_VALUES is referenced by following:

QA

VIEW - QA_DEVICE_DATA_VALUES#

[top of page]

Table: QA_DEVICE_INFO

Primary Key: QA_DEVICE_INFO_U1

1. DEVICE_ID

Primary Key: QA_DEVICE_INFO_U2

1. DEVICE_NAME
2. SENSOR_ALIAS

Comments

QA_DEVICE_INFO stores the setup information for devices. Each device is uniquely identified by the Device Name and Sensor Alias combination.

Columns

[top of page]

QA.QA_DEVICE_INFO does not reference any database object

QA.QA_DEVICE_INFO is referenced by following:

QA

VIEW - QA_DEVICE_INFO#

[top of page]

Table: QA_GRANTED_PRIVILEGES

Primary Key: QA_GRANTED_PRIVILEGES_PK1

1. QA_GRANT_ID

Foreign Keys from this table:

Comments

Granted privileges for data security project

Indexes

Columns

[top of page]

QA.QA_GRANTED_PRIVILEGES does not reference any database object

QA.QA_GRANTED_PRIVILEGES is referenced by following:

QA

VIEW - QA_GRANTED_PRIVILEGES#

[top of page]

Table: QA_INTERFACE_ERRORS

Comments

QA_INTERFACE_ERRORS contains log information recorded by Oracle Quality's collection import concurrent manager. As the Collection Import Worker processes rows in QA_RESULTS_INTERFACE, it records problem information in QA_INTERFACE_ERRORS.

Indexes

Columns

[top of page]

QA.QA_INTERFACE_ERRORS does not reference any database object

QA.QA_INTERFACE_ERRORS is referenced by following:

QA

VIEW - QA_INTERFACE_ERRORS#

[top of page]

Table: QA_IN_LISTS

Primary Key: QA_IN_LISTS_PK

1. LIST_ELEM_ID

Comments

QA_IN_LISTS contains the list of values associated with an In or Not In
operator.

Indexes

Columns

[top of page]

QA.QA_IN_LISTS does not reference any database object

QA.QA_IN_LISTS is referenced by following:

QA

VIEW - QA_IN_LISTS#

[top of page]

Table: QA_MQA_LOT_SERIAL_TEMP

Comments

Temporary table used in mobile application. Specifically, the lot/serial numbers
from the parent transaction are stored in this table for LOV selection query.

Indexes

Columns

[top of page]

QA.QA_MQA_LOT_SERIAL_TEMP does not reference any database object

QA.QA_MQA_LOT_SERIAL_TEMP is referenced by following:

QA

VIEW - QA_MQA_LOT_SERIAL_TEMP#

[top of page]

Table: QA_PC_CRITERIA

Primary Key: QA_PC_CRITERIA_PK1

1. CRITERIA_ID

Foreign Keys from this table:

Comments

This table stores criteria for the child plans to be applicable

Indexes

Columns

[top of page]

QA.QA_PC_CRITERIA does not reference any database object

QA.QA_PC_CRITERIA is referenced by following:

QA

VIEW - QA_PC_CRITERIA#

[top of page]

Table: QA_PC_ELEMENT_RELATIONSHIP

Primary Key: QA_PC_ELEMENT_RELATIONSHIP_PK1

1. ELEMENT_RELATIONSHIP_ID

Foreign Keys from this table:

Comments

This table stores the relationships between parent and child plan elements

Indexes

Columns

[top of page]

QA.QA_PC_ELEMENT_RELATIONSHIP does not reference any database object

QA.QA_PC_ELEMENT_RELATIONSHIP is referenced by following:

QA

VIEW - QA_PC_ELEMENT_RELATIONSHIP#

[top of page]

Table: QA_PC_PLAN_RELATIONSHIP

Primary Key: QA_PC_PLAN_RELATIONSHIP_PK1

1. PLAN_RELATIONSHIP_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

This table stores the parent plan id and the child plan id, along with the relation type and a flag to indicate if the child plan is mandatory

Indexes

Columns

[top of page]

QA.QA_PC_PLAN_RELATIONSHIP does not reference any database object

QA.QA_PC_PLAN_RELATIONSHIP is referenced by following:

QA

VIEW - QA_PC_PLAN_RELATIONSHIP#

[top of page]

Table: QA_PC_RESULTS_RELATIONSHIP

Foreign Keys from this table:

Comments

This table stores the relationship between two parent and child result rows.

Indexes

Columns

[top of page]

QA.QA_PC_RESULTS_RELATIONSHIP does not reference any database object

QA.QA_PC_RESULTS_RELATIONSHIP is referenced by following:

QA

VIEW - QA_PC_RESULTS_RELATIONSHIP#

[top of page]

Table: QA_PLANS

Primary Key: QA_PLANS_PK

1. PLAN_ID

Foreign Keys to this table:

Comments

QA_PLANS stores collection plan definitions. Collection plans consist of collection elements grouped for the purposes of data collection. Each row of the table represents one collection plan and contains the collection plan name, the inventory organization in which the plan is defined, the plan type, the plan view name, and the import view name. The plan view and import view are also referred to as dynamic views. These are created through the Collection Plan window.
The plan view has the format Q__V where corresponds to the name of the collection plan that this view is based on. The dynamic
plan view, which publishes the results collected for a plan, can also
be used for additional reporting purposes. The import view can be used to ease collection import.
The QA_PLANS table has a master-detail relationship with the QA_PLAN_CHARS and the QA_PLAN_TRANSACTIONS tables.

Indexes

Columns

[top of page]

QA.QA_PLANS does not reference any database object

QA.QA_PLANS is referenced by following:

QA

VIEW - QA_PLANS#

[top of page]

Table: QA_PLAN_CHARS

Primary Key: QA_PLAN_CHARS_PK

1. PLAN_ID
2. CHAR_ID

Foreign Keys from this table:

Comments

QA_PLAN_CHARS stores information about a collection plan and the collection elements assigned to that collection plan. Each row of the table represents one collection element and its attributes for the plan. Collection element attributes include the collection element prompt that is displayed, the default value for the collection element, and the column name in QA_RESULTS to which this collection element is mapped. This table also stores information regarding whether or not a collection plan is enabled, mandatory, or hidden.
When a collection plan is defined, a link is maintained to QA_CHARS
for each of the collection elements available in the plan. Some additional
information is also derived from QA_CHARS and populated in this table.

Indexes

Columns

[top of page]

QA.QA_PLAN_CHARS does not reference any database object

QA.QA_PLAN_CHARS is referenced by following:

QA

VIEW - QA_PLAN_CHARS#

[top of page]

Table: QA_PLAN_CHAR_ACTIONS

Primary Key: QA_PLAN_CHAR_ACTIONS_PK

1. PLAN_CHAR_ACTION_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

QA_PLAN_CHAR_ACTIONS contains defined actions for collection plan
elements. Each row of the table represents one action assigned to a collection element in a collection plan.

Indexes

Columns

[top of page]

QA.QA_PLAN_CHAR_ACTIONS does not reference any database object

QA.QA_PLAN_CHAR_ACTIONS is referenced by following:

QA

VIEW - QA_PLAN_CHAR_ACTIONS#

[top of page]

Table: QA_PLAN_CHAR_ACTION_OUTPUTS

Primary Key: QA_PLAN_CHAR_ACTION_OUTPUTS_PK

1. PLAN_CHAR_ACTION_ID
2. TOKEN_NAME

Foreign Keys from this table:

Comments

QA_PLAN_CHAR_ACTION_OUTPUTS stores the mapping between collection elements and tokens used in defining actions for a specific collection plan. Oracle Quality allows the user to define actions based on the tokens for some of the actions. These tokens are substituted with actual collection element values while executing the actions. Each row of this table stores information about a collection element, along with its associated action and the token name used to define the action in a specific plan.

Indexes

Columns

[top of page]

QA.QA_PLAN_CHAR_ACTION_OUTPUTS does not reference any database object

QA.QA_PLAN_CHAR_ACTION_OUTPUTS is referenced by following:

QA

VIEW - QA_PLAN_CHAR_ACTION_OUTPUTS#

[top of page]

Table: QA_PLAN_CHAR_ACTION_TRIGGERS

Primary Key: QA_PC_ACTION_TRIGGERS_PK

1. PLAN_CHAR_ACTION_TRIGGER_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

QA_CHAR_ACTION_TRIGGERS contains one row for each defined action trigger associated with a collection element. Action triggers are the rules that specify the conditions under which the action is activated during results entry. When the specified condition is met, the designated action is activated. You can define more than one trigger for a collection element. You assign each trigger a sequence number, which indicates the order in which the trigger is activated.
Each row in the table contains a collection element Identifier, a trigger sequence, and the operator used to define the trigger for the collection element. Operators are assigned numeric equivalents, which are displayed in the table. For example, the Less Than (<) operator is represented by the number six.
Based on the operator used, a row may contain a single value, or two values used to define a range of values from low (LOW_VALUE_OTHER) to high (HIGH_VALUE_OTHER). For example, if you use the operator Equals (=), which is represented by the number one, you enter a single value in the LOW_VALUE_OTHER field. When the user enters a collection element for this value, the action rule evaluates to TRUE. If you use the operator Between, which is represented by the number nine and indicates a range of values, you must specify a value for both LOW_VALUE_OTHER and HIGH_VALUE_OTHER. When the user enters a collection element value that falls within that range, the action rule is evaluated to TRUE. If the LOW_VALUE_LOOKUP or HIGH_VALUE_LOOKUP fields are populated, the collection element's specification limits determine whether or not the action is activated. If these fields are NULL, the actual values from LOW_VALUE_OTHER and HIGH_VALUE_OTHER determine whether or not the action is activated.

Indexes

Columns

[top of page]

QA.QA_PLAN_CHAR_ACTION_TRIGGERS does not reference any database object

QA.QA_PLAN_CHAR_ACTION_TRIGGERS is referenced by following:

QA

VIEW - QA_PLAN_CHAR_ACTION_TRIGGERS#

[top of page]

Table: QA_PLAN_CHAR_VALUE_LOOKUPS

Primary Key: QA_PC_VALUE_LOOKUPS_PK

1. PLAN_ID
2. CHAR_ID
3. SHORT_CODE

Foreign Keys from this table:

Comments

QA_PLAN_CHAR_VALUE_LOOKUPS contains the master set of values that are permissible for the collection elements of a given plan. You can define a master set of permissible values for a collection element, and then copy them to individual plans. Once values for a collection element are copied into a plan, only one of the values can then be entered for that collection element. The values are also used to display a List of Values (LOV) during data entry. They take precedence over the SQL validation string. Each row of the table contains one value for a collection element in the plan.

Indexes

Columns

[top of page]

QA.QA_PLAN_CHAR_VALUE_LOOKUPS does not reference any database object

QA.QA_PLAN_CHAR_VALUE_LOOKUPS is referenced by following:

QA

VIEW - QA_PLAN_CHAR_VALUE_LOOKUPS#

[top of page]

Table: QA_PLAN_COLLECTION_TRIGGERS

Primary Key: QA_PLAN_COLLECTION_TRIGGERS_PK

1. TXN_TRIGGER_ID

Foreign Keys from this table:

Comments

QA_PLAN_COLLECTION_TRIGGERS stores the collection triggers associated with a plan and transaction. These triggers evaluate whether or not a particular collection plan applies to the Quality Collection transaction, such as a WIP Move or PO Receiving Inspection transaction. Each row of this table represents one collection trigger and the conditions that determine whether or not the trigger applies for a certain plan and transaction.

Indexes

Columns

[top of page]

QA.QA_PLAN_COLLECTION_TRIGGERS does not reference any database object

QA.QA_PLAN_COLLECTION_TRIGGERS is referenced by following:

QA

VIEW - QA_PLAN_COLLECTION_TRIGGERS#

[top of page]

Table: QA_PLAN_TRANSACTIONS

Primary Key: QA_PLAN_TRANSACTIONS_PK

1. PLAN_TRANSACTION_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

QA_PLAN_TRANSACTIONS stores the transaction information defined for a specific collection plan. Oracle Quality allows the user to define a collection plan for specific transactions, as well as to enter quality results for these plans while executing parent transactions. For example, you can define collection plans specific to the WIP Move transaction. The user can then invoke this collection plan while performing the transaction. Each row of this table defines one transaction for a collection plan. A transaction is identified in Oracle Quality by assigning it a unique number called a transaction number. A plan can be associated with one or more transactions. This table stores information on whether or not collection plans for transactions are set to enabled, background, or mandatory, and whether or not they have a master-detail relationship with QA_PLAN_COLLECTION_TRIGGERS.

Indexes

Columns

[top of page]