rfs Table: Application Field Security
Sybase DBMS
Specifies the columns and rows with Sybase data type information for the rfs Application Field Security table.
rfs Columns
| Description | Column Name | Data Type ? | Characteristics ? |
|---|---|---|---|
| Field security code | fsec_cd_s | char | length 4 |
| Record modification stamp | timestamp | timestamp | |
| Allow update (Y/N/T) Y - application field may be modified N - application field may not be modified T - application field may be modified within certain tolerance percent or amount of the approved application value | updt1_s | char | length 200 |
| Allow update (Y/N/T) | updt2_s | char | length 200 |
| Allow update (Y/N/T) | updt3_s | char | length 200 |
| Field security description | fsec_desc_s | char | length 20 |
| Percent tolerance of approved application value [1] | p_tolpct1_d | double | scale 1 |
| Percent tolerance of approved application value [2] | p_tolpct2_d | double | scale 1 |
| Percent tolerance of approved application value [3] | p_tolpct3_d | double | scale 1 |
| Percent tolerance of approved application value [4] | p_tolpct4_d | double | scale 1 |
| Percent tolerance of approved application value [5] | p_tolpct5_d | double | scale 1 |
| Percent tolerance of approved application value [6] | p_tolpct6_d | double | scale 1 |
| Percent tolerance of approved application value [7] | p_tolpct7_d | double | scale 1 |
| Percent tolerance of approved application value [8] | p_tolpct8_d | double | scale 1 |
| Percent tolerance of approved application value [9] | p_tolpct9_d | double | scale 1 |
| Percent tolerance of approved application value [10] | p_tolpct10_d | double | scale 1 |
| Percent tolerance of approved application value [11] | p_tolpct11_d | double | scale 1 |
| Percent tolerance of approved application value [12] | p_tolpct12_d | double | scale 1 |
| Percent tolerance of approved application value [13] | p_tolpct13_d | double | scale 1 |
| Percent tolerance of approved application value [14] | p_tolpct14_d | double | scale 1 |
| Percent tolerance of approved application value [15] | p_tolpct15_d | double | scale 1 |
| Percent tolerance of approved application value [16] | p_tolpct16_d | double | scale 1 |
| Percent tolerance of approved application value [17] | p_tolpct17_d | double | scale 1 |
| Percent tolerance of approved application value [18] | p_tolpct18_d | double | scale 1 |
| Percent tolerance of approved application value [19] | p_tolpct19_d | double | scale 1 |
| Percent tolerance of approved application value [20] | p_tolpct20_d | double | scale 1 |
| Tolerance amount allowed to exceed approved value [1] | tolamt1_l | integer | |
| Tolerance amount allowed to exceed approved value [2] | tolamt2_l | integer | |
| Tolerance amount allowed to exceed approved value [3] | tolamt3_l | integer | |
| Tolerance amount allowed to exceed approved value [4] | tolamt4_l | integer | |
| Tolerance amount allowed to exceed approved value [5] | tolamt5_l | integer | |
| Tolerance amount allowed to exceed approved value [6] | tolamt6_l | integer | |
| Tolerance amount allowed to exceed approved value [7] | tolamt7_l | integer | |
| Tolerance amount allowed to exceed approved value [8] | tolamt8_l | integer | |
| Tolerance amount allowed to exceed approved value [9] | tolamt9_l | integer | |
| Tolerance amount allowed to exceed approved value [10] | tolamt10_l | integer | |
| Tolerance amount allowed to exceed approved value [11] | tolamt11_l | integer | |
| Tolerance amount allowed to exceed approved value [12] | tolamt12_l | integer | |
| Tolerance amount allowed to exceed approved value [13] | tolamt13_l | integer | |
| Tolerance amount allowed to exceed approved value [14] | tolamt14_l | integer | |
| Tolerance amount allowed to exceed approved value [15] | tolamt15_l | integer | |
| Tolerance amount allowed to exceed approved value [16] | tolamt16_l | integer | |
| Tolerance amount allowed to exceed approved value [17] | tolamt17_l | integer | |
| Tolerance amount allowed to exceed approved value [18] | tolamt18_l | integer | |
| Tolerance amount allowed to exceed approved value [19] | tolamt19_l | integer | |
| Tolerance amount allowed to exceed approved value [20] | tolamt20_l | integer | |
| Highlighted field | hilight1_s | char | length 200 |
| Highlighted field | hilight2_s | char | length 200 |
| Highlighted field | hilight3_s | char | length 200 |
rfs Indexes
| Index Name | Piece 1 |
|---|---|
| rfs_idx0 | fsec_cd_s |
Data Type Definitions and Characteristics
Following are descriptions of the Sybase data types used in the LeasePak database. Note that LeasePak does not use all the Sybase data types.
- char
- Sybase fixed length character string. Typically used to store short and medium-length string data such as keys, names,
addresses, descriptions, four-character codes, and single-character switch values.
Characteristics:- length - The maximum number of ASCII or ISO-8859-1 characters the string can contain.
- datetime
- Sybase date and time, containing century, year, month, day, hour, minute, second, and second fraction (to 1/300 second)
information.
Characteristics:- format - The date format for the LeasePak database. For example, format YYYYMMDD is the 4-digit year number followed by the 2-digit month number followed by the 2-digit day number with no intervening punctuation.
- double
- Sybase numeric data type. Typically used to store percentage, rate, and dollar amount information.
Characteristics:- precision - The magnitude and fractional granularity together, meaning the maximum number of places available to both the left and right of the decimal point. Use precision minus scale to determine the maximum number of places available to the left of the decimal point.
- scale - The fractional granularity, meaning the number of places available to the right of the decimal point.
- integer
- Sybase numeric data type. Typically used to store counter and whole number information--term length, payment due day, number of units on lease, number of times delinquent, etc.
- timestamp
- Sybase data type based on the
varbinarydata type storing raw binary data. Whenever a table includes atimestampcolumn, Sybase updates the information intimestampeach time a user inserts or updates a record, preventing multiple-user cross-update data corruption. - text
- Sybase expandable character data type. Typically used to store long-length string data such as notebook entries.
LeasePak Documentation Suite
©
by NetSol Technologies Inc. All rights reserved.
The information contained in this document is the property of NetSol Technologies Inc. Use of the information contained herein is restricted. Conditions of use are subject to change without notice. NetSol Technologies Inc. assumes no liability for any inaccuracy that may appear in this document; the contents of this document do not constitute a promise or warranty. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of said license. Unauthorized use, alteration, or reproduction of this document without the written consent of NetSol Technologies Inc. is prohibited.