IBY_TRANSMIT_PARAMETERS_B_
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.
Details
-
Schema: FUSION
-
Object owner: IBY
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
| Name | Columns |
|---|---|
|
IBY_TRANSMIT_PARAMETERS_B_PK_ |
LAST_UPDATE_DATE, LAST_UPDATED_BY, TRANSMIT_PROTOCOL_CODE, TRANSMIT_PARAMETER_CODE |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| TRANSMIT_PARAMETER_CODE | VARCHAR2 | 30 | Yes | User-entered primary key. | |
| TRANSMIT_PARAMETER_TYPE | VARCHAR2 | 30 | 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 | Y or N flag indicating whether this parameter is mandatory. | ||
| DYNAMIC_FLAG | VARCHAR2 | 1 | Yes or No 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. | ||
| DISPLAY_ORDER | NUMBER | 18 | Display order within the set of all options for protocol | ||
| CREATED_BY | VARCHAR2 | 64 | Who column: indicates the user who created the row. | ||
| CREATION_DATE | TIMESTAMP | Who column: indicates the date and time of the creation of the row. | |||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| OBJECT_VERSION_NUMBER | NUMBER | 9 | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | ||
| SECURED_FLAG | VARCHAR2 | 1 | Indicates if the parameter should be secured-i.e. is sensitive | ||
| SEED_DATA_SOURCE | VARCHAR2 | 512 | Source of seed data record. A value of 'BULK_SEED_DATA_SCRIPT' indicates that record was bulk loaded. Otherwise, specifies the name of the seed data file. | ||
| AUDIT_ACTION_TYPE_ | VARCHAR2 | 10 | Action Type - have values like INSERT, UPDATE and DELETE. | ||
| AUDIT_CHANGE_BIT_MAP_ | VARCHAR2 | 1000 | Used to store a bit map of 1s and 0s for each column in the table. | ||
| AUDIT_IMPERSONATOR_ | VARCHAR2 | 64 | Original Impersonator User. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| IBY_TRANSMIT_PARAMETERS_B_U1_ | Unique | Default | LAST_UPDATE_DATE, LAST_UPDATED_BY, TRANSMIT_PROTOCOL_CODE, TRANSMIT_PARAMETER_CODE |
| IBY_TRANSMIT_PARAMS_BN1_ | Non Unique | Default | TRANSMIT_PROTOCOL_CODE, TRANSMIT_PARAMETER_CODE, LAST_UPDATE_DATE |