rqm Table: CCA Asset Master
Sybase DBMS

Specifies the columns and rows with Sybase data type information for the rqm CCA Asset Master table.

rqm Columns

Description	Column Name	Data Type ?	Characteristics ?
CCA tax entity	tax_ent_s	char	length 4
CCA class	cca_cls_s	char	length 4
CCA type (L/O/P) L - Specified leasing property O - Separate class P - Pool	cca_typ_c	char	length 1
Asset	unit_s	char	length 10
Record modification stamp	timestamp	timestamp
Date of last update	d_lup_s	datetime	format YYYYMMDD
Time of last update	t_lup_s	char	length 6
Accrued to date	d_acc_s	datetime	format YYYYMMDD
CCA accrual method	cca_acc_s	char	length 4
CCA disposition method	cca_disp_s	char	length 4
Add-on rate	p_addon_d	double	scale 5
Schedule percentage	p_sch_prcnt_d	double	scale 5
CCA capital cost	cap_cost_d	double	scale 2
Adjustment L-T-D (for types L, O)	adj_ltd_d	double	scale 2
CCA ITC (investment tax credit)	cca_itc_d	double	scale 2
Undepreciated capital cost balance opening balance for the next fiscal year = cap_cost - cca taken L-T-D - adjustment L-T-D	balance_d	double	scale 2
Ordinary CCA L-T-D as of last year end (CCA would have been, had the asset been the only asset in the class and fully depreciated at all times)	ord_ltd_d	double	scale 2
CCA taken L-T-D (for types L,O)	taken_ltd_d	double	scale 2
Principal accrued L-T-D on current lease at last year end This field is cleared when asset is placed on a new lease.	prn_ltd1_d	double	scale 2
Principal accrued Y-T-D on current lease at last year end This field is cleared when asset is placed on a new lease. This field is updated in accruals when payments are due. It is added to the prn_ltd_d during year end and then cleared.	prn_accrued_ytd_d	double	scale 2
CCA taken L-T-D on current lease This field is cleared when asset is placed on a new lease.	prn_ltd_taken_d	double	scale 2
Prorated ordinary CCA L-T-D on current lease For type = L only	prorated_ltd_d	double	scale 2
CCA original capital cost	org_cap_cost_d	double	scale 2

rqm Indexes

Index Name	Piece 1	Piece 2	Piece 3	Piece 4
rqm_idx0	tax_ent_s	cca_cls_s	cca_typ_c	unit_s
rqm_idx1	cca_cls_s	cca_typ_c	unit_s
rqm_idx2	unit_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:

• 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 varbinary data type storing raw binary data. Whenever a table includes a timestamp column, Sybase updates the information in timestamp each 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 6.0a Documentation Suite

© 2008 by McCue Systems Incorporated. All rights reserved.

The information contained in this document is the property of McCue Systems, Inc. Use of the information contained herein is restricted. Conditions of use are subject to change without notice. McCue Systems, 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 McCue Systems, Inc. is prohibited.