rtp Table: Tax Payable
Oracle DBMS
Specifies the columns and rows with Oracle data type information for the rtp Tax Payable table.
rtp Columns
| Description | Column Name | Data Type ? | Characteristics ? |
|---|---|---|---|
| Payable type 00 - Use tax 01 - Property tax 02 - Federal highway use tax 03 -- 17 - Recurring charge 1-15 | pay_typ_s | CHAR(2) | |
| Payable recipient If payable type is use tax, property tax, or FHUT then recip_s = State(2)/County(4)/City(4) If payable type is recurring charge then recip_s = Broker/vendor number + " " | recip_s | CHAR(10) | |
| Asset or lease: If payable type is use tax, property tax, or FHUT then unit_lse_s = asset number If payable type is recurring charge then unit_lse_s = lease number | unit_lse_s | CHAR(10) | |
| Payment due date | d_pmtdu_s | DATE | |
| Unique portion for key | unique_s | CHAR(5) | |
| Record modification stamp | stamp_l | NUMBER(10) | |
| Invoice number | invo_s | CHAR(8) | |
| Asset | unit_s | CHAR(10) | |
| Property tax description code | ptax_desc_s | CHAR(4) | |
| Federal highway use tax (FHUT) description code | fhut_desc_s | CHAR(4) | |
| Tax accrued 1 (state) (amount payable) | tax_a1_d | NUMBER(15,2) | |
| Tax accrued 2 (county) | tax_a2_d | NUMBER(15,2) | |
| Tax accrued 3 (city) | tax_a3_d | NUMBER(15,2) | |
| Tax paid 1 (state) (amount paid) | tax_p1_d | NUMBER(15,2) | |
| Tax paid 2 (county) | tax_p2_d | NUMBER(15,2) | |
| Tax paid 3 (city) | tax_p3_d | NUMBER(15,2) | |
| Gross receipts (taxable) | gross_d | NUMBER(15,2) | |
| Manual update flag '*' - flags records updated in LAU0105 ' ' - all other records | man_updated_c | CHAR(1) |
rtp Indexes
| Index Name | Piece 1 | Piece 2 | Piece 3 | Piece 4 | Piece 5 | Piece 6 | Piece 7 |
|---|---|---|---|---|---|---|---|
| rtp_idx0 | pay_typ_s | recip_s | unit_lse_s | d_pmtdu_s | unique_s | ||
| rtp_idx1 | pay_typ_s | invo_s | unit_s | recip_s | unit_lse_s | d_pmtdu_s | unique_s |
Data Type Definitions and Characteristics
Following are descriptions of the Oracle data types used in the LeasePak database. Note that LeasePak does not use all the Oracle data types.
- char
- Oracle fixed length character string. Typically used to store short-length string data such as keys, four-character codes,
and single-character switch values.
Characteristics:- length - The maximum number of ASCII or ISO-8859-1 characters the string can contain.
- date
- Oracle date and time, containing century, year, month, day, hour, minute, and 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.
- number
- Oracle numeric data type. Used for all numbers.
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 maximum number of places available to the right of the decimal point.
- varchar2
- Oracle variable length character string. Typically used to store medium and long-length string data such as names,
addresses, descriptions, and notebook entries.
Characteristics:- length - The maximum number of ASCII or ISO-8859-1 characters the string can contain.
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.