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: IBY.IBY_TRANSMIT_PARAMETERS_B

Object Details

Object Name:	IBY_TRANSMIT_PARAMETERS_B
Object Type:	TABLE
Owner:	IBY
FND Design Data:	IBY.IBY_TRANSMIT_PARAMETERS_B
Subobject Name:
Status:	VALID

IBY_TRANSMIT_PARAMETERS stores a transmission protocol's input parameters. For example, this table is used to indicate that the FTP protocol requires a destination IP address and a destination directory, among other parameters. It is referred to by the transmission configuration table.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
IBY_TRANSMIT_PARAMETERS_B_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	TRANSMIT_PROTOCOL_CODE TRANSMIT_PARAMETER_CODE ZD_EDITION_NAME

Columns

Name	Datatype	Length	Mandatory	Comments
TRANSMIT_PARAMETER_CODE	VARCHAR2	(30)	Yes	User entered primary key
TRANSMIT_PARAMETER_TYPE	VARCHAR2	(30)	Yes	Data type of the parameter. Values, from the lookup IBY_PARAMETER_TYPES, include VARCHAR2, NUMBER, and DATE.
TRANSMIT_PROTOCOL_CODE	VARCHAR2	(30)	Yes	Identifier of the transmission protocol for which this parameter is needed
MANDATORY_FLAG	VARCHAR2	(1)	Yes	Y or N flag indicating whether this parameter is mandatory.
DYNAMIC_FLAG	VARCHAR2	(1)		Y or N flag indicating whether this parameter is dynamically generated using transactional data
DYN_CODE_LANGUAGE	VARCHAR2	(30)		Language of the code that is used for dynamic parameter value generation. Possible values would be 'PL/SQL' and 'Java'.
DYN_CODE_PACKAGE	VARCHAR2	(255)		Package used for dynamic parameter value generation; in PL/SQL this corresponds to a package name, in Java a class name
DYN_CODE_ENTRY_POINT	VARCHAR2	(255)		Code entry point used for dynamic parameter value generation. For example, this could be in the form of a PL/SQL package and procedure, or a Java class and method.
SECURED_FLAG	VARCHAR2	(1)		Y or N flag that indicates whether the transmission parameter is security-sensitive
DISPLAY_ORDER	NUMBER	(15)	Yes	Display order within the set of all options for protocol
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
OBJECT_VERSION_NUMBER	NUMBER	(15)	Yes	Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application.
ZD_EDITION_NAME	VARCHAR2	(30)	Yes

Query Text

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


SELECT TRANSMIT_PARAMETER_CODE
,      TRANSMIT_PARAMETER_TYPE
,      TRANSMIT_PROTOCOL_CODE
,      MANDATORY_FLAG
,      DYNAMIC_FLAG
,      DYN_CODE_LANGUAGE
,      DYN_CODE_PACKAGE
,      DYN_CODE_ENTRY_POINT
,      SECURED_FLAG
,      DISPLAY_ORDER
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      OBJECT_VERSION_NUMBER
,      ZD_EDITION_NAME
FROM IBY.IBY_TRANSMIT_PARAMETERS_B;

Dependencies

[top of page]

IBY.IBY_TRANSMIT_PARAMETERS_B does not reference any database object

IBY.IBY_TRANSMIT_PARAMETERS_B is referenced by following:

IBY: IBY_TRANSMIT_PARAMETERS_B#