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: XNP.XNP_CALLBACK_EVENTS

Object Details

Object Name:	XNP_CALLBACK_EVENTS
Object Type:	TABLE
Owner:	XNP
FND Design Data:	XNP.XNP_CALLBACK_EVENTS
Subobject Name:
Status:	VALID

XNP_CALLBACK_EVENTS stores a registry of callbacks for instances of message types (messages or events). This enables the Event Manager to invoke the callback procedure specified in the particular instance of the program which is awaiting the data rather than the default callback procedure which is specified as part of definition of the message type.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
XNP_CALLBACK_EVENTS_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	CALLBACK_EVENT_ID ZD_EDITION_NAME
XNP_CALLBACK_EVENTS_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	MSG_CODE
XNP_CALLBACK_EVENTS_N3	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	ORDER_ID
XNP_CALLBACK_EVENTS_N5	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PROCESS_REFERENCE STATUS CLOSE_REQD_FLAG
XNP_CALLBACK_EVENTS_N6	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	REFERENCE_ID MSG_CODE STATUS
XNP_CALLBACK_EVENTS_N7	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	STATUS WI_INSTANCE_ID

Columns

Name	Datatype	Length	Mandatory	Comments
CALLBACK_EVENT_ID	NUMBER		Yes	Callback registration identifier
MSG_CODE	VARCHAR2	(20)	Yes	Short name of the message or event that is expected
STATUS	VARCHAR2	(10)	Yes	Registration status. Application can register for one or more messages and each registration has a well defined status.
PROCESS_REFERENCE	VARCHAR2	(512)	Yes	Process that actually registered for this message. The process reference can be a workflow key, workflow item, workflow activity or all of them. This data will be passed to the callback procedure when delivering the message.
REGISTERED_TIMESTAMP	DATE		Yes	Timestamp when this callback was registered.
CALLBACK_TYPE	VARCHAR2	(20)	Yes	Type for the Callback procedures. It can be PL/SQL, JAVA or external C procedures. The callback type is used by the Message Processor or the Event Manager to use the right invocation method on the callback procedure.
CALLBACK_PROC_NAME	VARCHAR2	(80)	Yes	The procedure to be invoked by the Message Processor for delivering the message
CALLBACK_TIMESTAMP	DATE			Date and time the message was delivered to the registered program
REFERENCE_ID	VARCHAR2	(80)		Unique identifier for which a message or an event is expected
CLOSE_REQD_FLAG	VARCHAR2	(1)	Yes	Indicates if the registration should be closed after processing
ORDER_ID	NUMBER			Order ID to which an event belongs
WI_INSTANCE_ID	NUMBER			Work Item Instance ID
FA_INSTANCE_ID	NUMBER			Fulfillment Action Instance ID
CREATED_BY	NUMBER	(15)	Yes	Standard who column
CREATION_DATE	DATE		Yes	Standard who column
LAST_UPDATED_BY	NUMBER	(15)	Yes	Standard who column
LAST_UPDATE_DATE	DATE		Yes	Standard who column
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard who column
SECURITY_GROUP_ID	NUMBER			Used in hosted environments
ZD_EDITION_NAME	VARCHAR2	(30)	Yes

Query Text

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


SELECT CALLBACK_EVENT_ID
,      MSG_CODE
,      STATUS
,      PROCESS_REFERENCE
,      REGISTERED_TIMESTAMP
,      CALLBACK_TYPE
,      CALLBACK_PROC_NAME
,      CALLBACK_TIMESTAMP
,      REFERENCE_ID
,      CLOSE_REQD_FLAG
,      ORDER_ID
,      WI_INSTANCE_ID
,      FA_INSTANCE_ID
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      SECURITY_GROUP_ID
,      ZD_EDITION_NAME
FROM XNP.XNP_CALLBACK_EVENTS;

Dependencies

[top of page]

XNP.XNP_CALLBACK_EVENTS does not reference any database object

XNP.XNP_CALLBACK_EVENTS is referenced by following:

XNP: XNP_CALLBACK_EVENTS#