Use the following table to see the layout details for the table named LeasingHistoryAddenda.

Column Name	Datatype	Length	Precision	Identity
LHKey	int	4	10	0
LineID	int	4	10	0
ActivitySource	varchar	2	0
ActivityCode	varchar	1	0
RecordType	varchar	1	0
Desc	varchar	40	0
Value	varchar	40	0
Freq	varchar	1	0

Each of the database fields in the LeasingHistoryAddenda table is designed for a specific function.

LH Key

Points back to the corresponding record in the LeasingHistory table.

LineID

The unique identity field for each record i the LeasingHistoryAddenda table.

ActivitySource

Identifies the source code; for Manufactured Housing this is MD.

Record Types

Use the following table to see a list of possible record types and their respective details.

Type Code	Desc	Value	Frequency
B (Balance)	Income Code	Delinquency Amount	Months Delinquent 0 = current 1 = 30 days 2 = 60 days 3 = 90 days 4 = more than 90 days
C (Recurring Charge)	Income Code	Recurring Charge Amount	Charge Frequency
K (Marketing Source)	Marketing Source	Marketing Source Cost	Marketing Source Cost Frequency
L (Lease Dates)	Date Description ExpMoveIn ActMoveIn ExpMoveOut ActMoveOut Resale	Date	Not Used
M (Memo)	Memo Prompt	Memo Data	Not Used
N (Primary Lease Name)	Last Name	First Name	Middle Initial
R (Resale Cross Reference)	Resales uses the activity code, 102 to create two records in the LeasingHistoryAddenda table. One for the seller and one for the buyer. These records link the two leasing history records together.
Seller (Resident Moving Out)	Buyer	LHKey of Buyer in the leasing history record.	Not Used
Buyer (New Resident Moving In)	Seller	LHKey of Seller in the leasing history record.	Not Used

You can expect one record for each item of data, including one for the following:

• Each balance due to a specific income code

• Each recurring charge in the lease

• The marketing source (for Move-Ins only)

• Each date reported under Lease Dates

• Each field defined in the HOME memo form

• Each primary lease name (two names reported when a resale occurs)

Leasing History Addenda records were designed as permanent records to enable historical analysis and reporting of this data. In addition, the system also prevents leasing history records associated with the LeasingHistoryAddenda table from being deleted to further safeguard data integrity.

 

Copyright © 2018 Infor. All rights reserved. www.infor.com.