eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

TABLE: QA.QA_PLAN_TRANSACTIONS

Object Details

Object Name:	QA_PLAN_TRANSACTIONS
Object Type:	TABLE
Owner:	QA
FND Design Data:	QA.QA_PLAN_TRANSACTIONS
Subobject Name:
Status:	VALID

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.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
QA_PLAN_TRANSACTIONS_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	PLAN_TRANSACTION_ID
QA_PLAN_TRANSACTIONS_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PLAN_ID
QA_PLAN_TRANSACTIONS_N2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	TRANSACTION_NUMBER

Columns

Name	Datatype	Mandatory	Comments
PLAN_TRANSACTION_ID	NUMBER	Yes	Plan Transaction identifier
LAST_UPDATE_DATE	DATE	Yes	Standard Who column
LAST_UPDATED_BY	NUMBER	Yes	Standard Who column
CREATION_DATE	DATE	Yes	Standard Who column
CREATED_BY	NUMBER	Yes	Standard Who column
LAST_UPDATE_LOGIN	NUMBER		Standard Who column
PLAN_ID	NUMBER	Yes	Collection plan Identifier
TRANSACTION_NUMBER	NUMBER	Yes	Parent transaction number. Each transaction has been assigned a unique number within Oracle Quality. For example, WIP MOVE TRANSACTION has been assigned number 1
MANDATORY_COLLECTION_FLAG	NUMBER		Flag to indicate if collection plan ID mandatory. A mandatory collection plan enforces Quality result collection before parent transaction can be committed
BACKGROUND_COLLECTION_FLAG	NUMBER		Flag to indicate if collection plan is background collection plan
ENABLED_FLAG	NUMBER		Flag to indicate if collection plan is enabled for the given transaction
EQR_LAYOUT_MODE	NUMBER		Layout mode in OA Framework Transaction Integration.

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT PLAN_TRANSACTION_ID
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_LOGIN
,      PLAN_ID
,      TRANSACTION_NUMBER
,      MANDATORY_COLLECTION_FLAG
,      BACKGROUND_COLLECTION_FLAG
,      ENABLED_FLAG
,      EQR_LAYOUT_MODE
FROM QA.QA_PLAN_TRANSACTIONS;

Dependencies

[top of page]

QA.QA_PLAN_TRANSACTIONS does not reference any database object

QA.QA_PLAN_TRANSACTIONS is referenced by following:

APPS: QA_PLAN_TRANSACTIONS