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: PON.PON_DISCUSSIONS

Object Details

Object Name:	PON_DISCUSSIONS
Object Type:	TABLE
Owner:	PON
FND Design Data:	PON.PON_DISCUSSIONS
Subobject Name:
Status:	VALID

The identity of the discussion owner and the data the discussion is associated with are kept here.
(for instance the auction number, and the owner of the auction).

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
PON_DISCUSSIONS_N2	NORMAL	UNIQUE	APPS_TS_TX_IDX	DISCUSSION_ID
PON_DISCUSSIONS_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PK1_VALUE ENTITY_NAME

Columns

Name	Datatype	Length	Mandatory	Comments
DISCUSSION_ID	NUMBER	(15)	Yes	Primary key for the table - generated by POM_DISCUSSIONS_s
ENTITY_NAME	VARCHAR2	(40)	Yes	Table name of the table with which the discussion is associated. The PK fields, below are the Primary Key to the table listed in this Field.
PK1_VALUE	VARCHAR2	(100)		Fields containing the PK of the table specified in ENTITY_NAME. This follows the FND_ATTACHED_DOCUMENTS datamodel.
PK2_VALUE	VARCHAR2	(100)		Fields containing the PK of the table specified in ENTITY_NAME. This follows the FND_ATTACHED_DOCUMENTS datamodel.
PK3_VALUE	VARCHAR2	(100)		Fields containing the PK of the table specified in ENTITY_NAME. This follows the FND_ATTACHED_DOCUMENTS datamodel.
PK4_VALUE	VARCHAR2	(100)		Fields containing the PK of the table specified in ENTITY_NAME. This follows the FND_ATTACHED_DOCUMENTS datamodel.
PK5_VALUE	VARCHAR2	(150)		Same as other PK values, but the filed size is slighly larger to conform with FND_ATTACHED_DOCUMENTS.
SUBJECT	VARCHAR2	(2000)		Simply a header for the discussion.
LANGUAGE_CODE	VARCHAR2	(4)	Yes	A FK to FND_LANGUAGES, so we can support language stripping if necessary.
OWNER_PARTY_ID	NUMBER	(15)		This is a FK to HZ_PARTIES indicating the owner of the disccusion
VALIDATION_CLASS	VARCHAR2	(255)	Yes	This is an implementation of the oracle.apps.pon.discussion ThreadValidationclass discussed below. It will be instantiated in the middle tier using reflection, in order to determine view and post access( and whatever other filtering is required ). Alternatives are discussed below.
LAST_UPDATE_DATE	DATE		Yes	This is a denormalization of the last update date which is stored among the other data tables. It may be useful for polling to have this summary information available.

Query Text

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


SELECT DISCUSSION_ID
,      ENTITY_NAME
,      PK1_VALUE
,      PK2_VALUE
,      PK3_VALUE
,      PK4_VALUE
,      PK5_VALUE
,      SUBJECT
,      LANGUAGE_CODE
,      OWNER_PARTY_ID
,      VALIDATION_CLASS
,      LAST_UPDATE_DATE
FROM PON.PON_DISCUSSIONS;

Dependencies

[top of page]

PON.PON_DISCUSSIONS does not reference any database object

PON.PON_DISCUSSIONS is referenced by following:

PON: PON_DISCUSSIONS#