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_THREAD_ENTRIES

Object Details

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

PON_THREAD_ENTRIES stores the message content, subject, poster, discussion/thread, and other metadata associated with a specific message. The PK is ENTRY_ID, driven by the sequence PON_THREAD_ENTRIES_S.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
PON_THREAD_ENTRIES_N4	NORMAL	UNIQUE	APPS_TS_TX_IDX	ENTRY_ID
SYS_IL0000202885C00006$$	LOB	UNIQUE	APPS_TS_TX_DATA
PON_THREAD_ENTRIES_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PARENT_ENTRY_ID
PON_THREAD_ENTRIES_N3	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	DISCUSSION_ID THREAD_NUMBER

Columns

Name	Datatype	Length	Mandatory	Comments
ENTRY_ID	NUMBER	(15)	Yes	This is the PK for the table. The number should be generated by a sequence PON_THREAD_ENTRIES_S.
FROM_ID	NUMBER	(15)	Yes	This is a FK to HZ_Parties for the identity of the user who sent the message.
FROM_FIRST_NAME	VARCHAR2	(150)		This is denormalized from HZ_PARTIES, to keep it consistent if the user's name is updated, and for performance reasons.
FROM_LAST_NAME	VARCHAR2	(150)	Yes	This is denormalized from HZ_PARTIES, to keep it consistent if the user's name is updated, and for performance reasons.
POSTED_DATE	DATE		Yes	This is the date the message was posted. For audit and header purposes.
CONTENT	CLOB	(4000)		This is the content of the message. It is a CLOB in order to support UI requirements that request we keep the entire thread history for each message.
THREAD_NUMBER	NUMBER	(15)	Yes	Indexed with DISCUSSION_ID, this is part os the FK for PON_THREADS.
DISCUSSION_ID	NUMBER	(15)	Yes	Indexed with THREAD_NUMBER(as well as on its own) this is part of the FK for PON_THREADS.
BROADCAST_FLAG	VARCHAR2	(1)		Flag indicating that this is a broadcast message. A broadcast message is one that is sent to all participants, all collaboration team members, all scoring teams or to all members of a scoring team.
PARENT_ENTRY_ID	NUMBER	(15)	Yes	This is the recursive FK back to this table, which tracks hierarchy for the thread. Messages with PARENT_ENTRY_ID = -1 are root level messages.
SUBJECT	VARCHAR2	(2000)		This is for header purposes. Not being used in the negotiations case. Probably should be indexed if/when it is used.
MESSAGE_TYPE	VARCHAR2	(30)		Stores the message type. It can be EXTERNAL or INTERNAL
FROM_COMPANY_NAME	VARCHAR2	(360)		Stores the company name of the message sender
VENDOR_ID	NUMBER			Stores the vendor_id for Supplier's messages
FROM_COMPANY_ID	NUMBER			Stores the trading partner id of the sender's company
SCORING_TEAM_ID	NUMBER			Identifier of the scoring team if the message was sent to a scoring team. If the message is sent to all scoring teams, then this column contains -1.

Query Text

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


SELECT ENTRY_ID
,      FROM_ID
,      FROM_FIRST_NAME
,      FROM_LAST_NAME
,      POSTED_DATE
,      CONTENT
,      THREAD_NUMBER
,      DISCUSSION_ID
,      BROADCAST_FLAG
,      PARENT_ENTRY_ID
,      SUBJECT
,      MESSAGE_TYPE
,      FROM_COMPANY_NAME
,      VENDOR_ID
,      FROM_COMPANY_ID
,      SCORING_TEAM_ID
FROM PON.PON_THREAD_ENTRIES;

Dependencies

[top of page]

PON.PON_THREAD_ENTRIES does not reference any database object

PON.PON_THREAD_ENTRIES is referenced by following:

PON: PON_THREAD_ENTRIES#