Setting Up the Real Estate Management System

This chapter provides an overview of setup for the JD Edwards EnterpriseOne Real Estate Management system and discusses how to:

• Set up constants Real Estate Management constants.

• Set up automatic accounting instructions (AAIs).

• Set up user-defined codes (UDCs) for Real Estate Management.

• Set up bill codes and adjustment reasons.

• Set up billing frequency information.

• Set up tax rate area information.

• Set up logs and legal clauses.

• Set up statement messages.

Understanding Setup for the Real Estate Management System

Before you can use the JD Edwards EnterpriseOne Real Estate Management system, you need to define information that the system uses during processing.

This table describes the information that you must set up for the Real Estate Management system:

Note. Because you generate invoices and vouchers from the JD Edwards EnterpriseOne Real Estate Management system, you must also set up the Accounts Receivable (AR) and Accounts Payable (AP) constants.

See Also

Setting Up Constants for Accounts Receivable

Setting Up Real Estate Management System Constants

This section provides an overview of Real Estate Management system constants and discusses how to set up system constants.

Understanding Real Estate Management System Constants

System constants are default settings that the JD Edwards EnterpriseOne Real Estate Management system uses to process requests, generate billings, and perform other tasks. You set up system constants to define how the system processes information. You must define certain constants before you enter information for tenants, facilities, and leases.

You can set up JD Edwards EnterpriseOne Real Estate Management constants by building and company:

• If the constants are not defined for the building, the system uses the company constants.

• If the constants are not defined for the company, the system uses the information that is set up for company 00000, which is the default company.

When you set up constants for company 00000, not only do you provide default information that can be used by all companies and buildings, you also establish system constants. The options that define the constants for the system, such as versions, area types, and area validations, appear only on the form for company 00000. When you use a company number other than the default company value of 00000, you use an abbreviated version of the Real Estate Management Constants Revisions form.

The system stores information about the real estate constants in the F1510B table.

Changes to the Real Estate Management constants take effect after you quit the system and access it again.

Important! In general, do not change system constants after you set up the system. If you do make changes, you must be thoroughly familiar with the information that is involved because it is central to the system processes. You should also ensure that only authorized personnel can access and maintain the constants.

Forms Used to Set Up System Constants

Setting Up System Constants

Access the Real Estate Management Constants Revisions page.

Revenue Business Unit Flag	Enter the code that specifies the method that the system uses to retrieve the business unit, which determines the revenue account. Values are: 0: The system uses the building number as the revenue business unit, regardless of any business unit that is defined in the AAIs. 1: The system uses the business unit that is defined in the PMxxxx AAIs. If no business unit is defined in these AAIs, the system uses the building number. To direct revenues to business units other than the building, you must enter a value of 1. Note. The Expense Account AAIs (RMxxxx) are used in the same way during Accounts Payable processing as the Revenue Account AAIs (PMxxxx) are used during Accounts Receivable processing.
Lease Year Beginning Month	Enter the code that specifies the beginning month of a standard lease year. Although various leases may start on different dates throughout the year, they can share the same annual schedule that the property manager establishes. When the beginning month is unknown, enter 01 for January.
Report Year Begin Month	Enter the month that defines the beginning of the year for tenant sales analysis purposes. It is used in sales analysis processing to determine which months are to be included in quarter-to-date (QTD) and year-to-date (YTD) numbers. If in doubt, enter 01.
Tax Suppress	Enter a value that specifies whether the JD Edwards EnterpriseOne Real Estate Management system uses tax processing. A value of Y or 1 in this field causes the system to bypass processing of taxes and not to display fields that are related to such processing. Any other value causes the system to process taxes. Individual forms and reports may have processing options that override the value that is entered here.
Activate Versioning	Indicates whether the edits and options for lease versioning are active. If this option is selected, versioning is active.
Hard Versioning Error	Select this option to allow the system to make changes only to the latest version of a lease. When you access any other versions of the lease, the system displays a message that indicates that the version is locked. If you clear this option, the system allows you to make changes to all versions of a lease. This option appears only if you have selected the Activate Versioning option.
Rentable Area Type	Enter the UDC that defines the rentable area.
Validate Rentable Area	Validates the rentable area when you are entering building, floor, and unit information. Note. When the system validates the rentable area, the total square footage of the floors cannot exceed the total square footage of the building.
Usable Area Type	Enter the UDC that defines the usable area.
Validate Usable Area	Select to have the system validate the usable area when you enter building, floor, and unit information. Note. The total square footage of the floors cannot exceed the total square footage of the building.
Alt. Area Type 1 (alternate area type 1)	Enter the UDC (15/AR) that specifies an area type other than the rentable or usable area types.
Validate Alt. Area 1 (validate alternate area 1)	Select this option to have the system validate alternate area 1 when you enter building, floor, and unit information. Note. For validation purposes, the total square footage of the floors cannot exceed the total square footage of the building.
Alt. Area Type 2 (alternate area type 2)	Enter the UDC (15/AR) that specifies an area type other than the rentable or usable area types.
Validate Alt. Area 2 (alternate area type 2)	Select to have the system validate alternate area 2 when you enter building, floor, and unit information. Note. For validation purposes, the total square footage of the floors cannot exceed the total square footage of the building.
Alt. Area Type 3 (alternate area type 2)	Enter the UDC (15/AR) that specifies an area type other than the rentable or usable area types.
Validate Alt. Area 3 (validate alternate area 3)	Select to have the system validate alternate area 3 when you enter building, floor, and unit information. Note. For validation purposes, the total square footage of the floors cannot exceed the total square footage of the building. The total square footage of the units cannot exceed the total square footage of the floors.

Setting Up Automatic Accounting Instructions

You can create AAIs for each unique combination of company and either a billing or adjustment code, or general ledger (GL) offset code that you plan to use:

• Billing and GL offset codes can be one to four characters.

• Adjustment reason codes can be only two characters.

You can also set up AAIs for company 00000, which the system uses as a default, if a specific AAI is not defined. Each AAI is associated with a GL account that consists of a business unit, object, and optionally, a subsidiary.

This table outlines the AAI items that are used in the JD Edwards EnterpriseOne Real Estate Management system, the type of code that can be used with each AAI item, and a description of the account that should be associated with it:

In the Automatic Accounting table (F0012), the AAIs that are related to the Real Estate Management system have sequence numbers between 15.000 and 15.999.

This table contains some of the AAIs that are defined in the system for demonstration purposes:

See Also

Setting Up Automatic Accounting Instructions

Setting Up UDCs for Real Estate Management

Many fields throughout the JD Edwards EnterpriseOne Real Estate Management system require UDCs. In these fields, the system does not accept codes that are not defined in a UDC table. You can define these UDCs to meet the needs of the organization. Some UDCs contain a special handling code, which directs the system to perform a specific function.

This table lists the UDCs that are used by the Real Estate Management system:

See Also

JD Edwards EnterpriseOne Tools 8.96 Foundation Guide

Setting Up Bill Codes and Adjustment Reasons

This section provides an overview of bill codes and adjustment reasons, lists prerequisites, and discusses how to:

• Set processing options for Bill Codes / Adjustment Reasons (P1512).

• Set up bill codes and adjustment reasons.

Understanding Bill Codes and Adjustment Reasons

You use bill codes and adjustment reasons to identify the AAIs that the system uses when you post transactions.

The JD Edwards EnterpriseOne Real Estate Management system uses adjustment reasons that are specific to the system. They must be defined both as adjustment reason codes in the F1512 table, and as adjustment classifications in UDCs (15/AD).

Important! The Accounts Receivable system also uses reason codes. Do not use the AR reason codes unless they have also been set up in the Real Estate Management system. To prevent errors, you should set up identical codes for both systems.

You can define a bill code or adjustment reason for a specific property or building. Otherwise, all information is true for all properties. You can also revise bill codes and adjustment reasons. If you acquire new properties or sell properties, you typically need to revise the bill code and adjustment reason information.

You can add new bill codes after you add the appropriate AAI; however, after the code is entered, you cannot change it. You must delete it and add another bill code.

Prerequisite

Set up the real estate AAIs that you want to use. Because of the relationship among AAIs, bill codes, and adjustment reason codes, you must set up AAIs before you set up bill codes and adjustment reason codes.

Forms Used to Set Up Bill Codes and Adjustment Reasons

Setting Processing Options for Bill Codes / Adjustment Reasons (P1512)

Set this processing option to specify the default processing for this program.

Versions

This processing option specifies the version of the AAIs program (P0012) that the system uses.

Setting Up Bill Codes and Adjustment Reasons

Access the Bill Codes/Adjustment Reasons Revisions form.

Bill Code or Adj (bill code or adjustment reason code)	Enter the code that specifies whether the bill code record is a bill code or an adjustment reason code. The AAIs that you set up vary depending on whether the bill code record is assigned B or A. Values are: B: Bill code. A: Adjustment reason code. If you enter A, you must complete the Adj. Classifications field.
Subject to GPR (subject to gross potential rent)	Future use.
Bill to Tenant	Future use.
Priority Application	Enter the two-character numeric code that indicates the order in which the system applies the receipt to the invoice pay item based on the bill code. The system applies the payment to invoice pay items with bill codes that are assigned a lower number (higher priority) first. For example, if one invoice has three bill codes with priorities 1, 2, and 3, the system applies the receipt to the pay item that has a bill code with a priority of 1 first. Note. The priority application code is applicable only when you load invoices for receipt entry, and only when the corresponding option, Priority Code Application, is selected. These priority codes are hard-coded for special processing: 00: Assign 00 to bill codes that you use on credit memos (negative invoices) when you want to use the feature to automatically apply receipts to specific credit memos only. This is based on a processing option for the RE Receipts Entry program (P15103). The system displays only those credit memos with a priority code that is equal to 00. 99: Assign 99 to bill codes that you use on invoices that you want the system to bypass when you use the feature to automatically apply receipts to invoices. This is based on a processing option for the RE Receipts Entry program (P15103). The system will not automatically apply receipts to invoices, regardless of the setting of the corresponding processing option, if the priority application code assigned to the bill code is 99.
Apply to Aging	Future use.
Security Group	Enter the UDC (15/SG) to specify the security group to which you assign the bill code record. Complete this field only for bill codes that are used to identify security deposits.
Subject to Late Fees	Enter the code that indicates whether the bill code is subject to fee and interest calculations. Values are: Y: Subject. N: Not subject.
Adj Classifications (adjustment classifications)	Enter the UDC (15/AD) to further classify adjustment codes for reporting purposes. You must complete this field if you entered A (for adjustment) in the Bill Code field or the Adj field.
Commer/Resid/Both (commercial, residential, or both)	Future use.
Used for Unit GPR (used for unit gross potential rent)	Future use.
Auto Suspend	Future use.
Special Processing Code	Enter the code that specifies whether to use the bill code as the default value for unapplied receipts if the Unapplied Bill Code field (GLC) is blank. If more than one bill code is set up as a default, the system uses the bill code that it locates first in alphabetical order. If none of the bill codes are set up as a default, the system uses the bill code UC. Values are: Blank: Do not use. UNC: Use.
Subject to Sales Tax	Future use.
Spread Code	Enter the code that specifies whether to allow the invoices that are generated with the bill code to be paid. For example, you might need to prevent invoices for security deposits from being paid. Values are: Y: Allow. N: Do not allow. The system does not display invoices with this bill code on the Receipts Entry form, regardless of whether they were selected for payment using the Load feature and the Select features. W: Allow invoices that generated with this bill code to be paid, but issue a warning message.
Subject to Management Fees	Future use.
Comment Required	Enter the code that specifies whether invoices for the bill code require a value in the Remark field of the detail line on the Receipts Entry form. The system assigns the description of the bill code by default. Values are: Y: Requires a value. N: Does not require a value.

Setting Up Billing Frequency Information

This section provides an overview of billing frequency information and discusses how to:

• Set up periodic billing cycles.

• Set up weekly billings.

Understanding Billing Frequency Information

You set up billing frequency information, or cycles, for recurring and irregular billings such as rent, expense participation, escalations, sales overage, and so on. For such billings, the billing cycle determines how often and when an account is billed.

You can set up billing cycles in this way:

• Periodic for monthly, quarterly, semiannual, annual, and irregular billing cycles.

• Weekly.

Regardless of the type of billing cycle that you set up, you must assign it a fiscal date pattern code so that the system can correlate the period that you define with a calendar. For example, if you specify that annual billing should occur in period 12, you must indicate whether period 12 is December or May. The fiscal date pattern code defines the beginning and ending of the fiscal year, as well as the number and length of each period for that year.

Note. You can use a regular fiscal pattern for all billings that you may process through the Real Estate Management system. Each billing process will post transactions to the correct period in the general ledger based on the fiscal pattern that is associated with the company on the lease. Billing frequencies that are attached to sales overage information must always be assigned a calendar fiscal pattern as sales are processed by calendar year.

You must assign a fiscal date pattern code that is set up; otherwise, the system returns an error message when you post billings:

• For periodic frequencies, the date pattern code must be set up in the F0008 table.

  You can add new date pattern codes or revise existing codes by accessing the Date Patterns form. It is accessible from the Form menu from the Company Names & Numbers program (P0010).

• For weekly billings, the date pattern code that you assign must be set up in the F0008B table.

  You can verify whether the 52-period date pattern exists by selecting the corresponding option when you set up the weekly billing frequency. If a date pattern does not exist, you can set one up by using the Set 52 Period Dates program (P0008B).

The system stores billing frequency information in the F15019 table.

Prerequisite

Set up the fiscal date patterns that you want to use.

See Also

Setting Up Fiscal Date Patterns

Setting Up 52 Period Fiscal Date Patterns

Forms Used to Set Up Billing Frequency Information

Setting Up Periodic Billing Cycles

Access the Billing Frequency Code Revisions form.

Billing Frequency Code	Enter the code that specifies how often the system generates billing records. The code that you enter must exist in the F15019 table.
Fiscal Date Pattern	Enter the code that identifies date patterns. You can use one of 15 codes. You must set up special codes (letters A through N) for 4-4-5, 13-period accounting, or any other date pattern that is unique to the environment. The letter R, the default, identifies a regular calendar pattern.
Periodic	Enter the number of days that are added to a collection transaction date to calculate the due date for the next action.
Per 1 through Per 14 (period 1 through period 14)	Select the period options that apply to the frequency code, and click OK.

Setting Up Weekly Billings

Access the Set Up 52 Periods form.

Fiscal Date Pattern	Enter the same code that you entered when you set up the billing frequency code.
Weekly	Enter the number of days that are added to a collection transaction date to calculate the due date for the next action. When you select the Weekly option, the Set 52 Period Pattern option becomes available.
Set 52 Period Pattern	Select this option to prompt the system to display the 52-period pattern.
Date Yr Beg (date fiscal year begins)	Enter the first day of the fiscal year.
End Of Per 01 (end date of period 1)	Enter the month end date in 12-period (monthly) accounting. The period end date in 13-period, or 4-4-5 period, or 52-period accounting. Based on the ending date of period one, the system calculates ending dates for each of the 52 periods, in seven-day increments. The system assigns the same ending day for periods 52, 53, and 54.

Setting Up Tax Rate Area Information

This section provides an overview of tax rate area information and discusses how to set up tax rate areas.

Understanding Tax Rate Area Information

The JD Edwards EnterpriseOne Real Estate Management system enables you to set up and work with the areas, rates, and effective dates for current and future taxes. Each tax area can have its taxes assessed by different tax authorities for different purposes and rates. The system uses this information in conjunction with a tax explanation code to calculate the tax amounts for billings when tax processing is in effect. As tax rates change, you can update the tax rate and area information.

The system does not check for duplicate tax rate and area information. Consequently, you can set up different tax rates and effective date ranges for the same tax rate and area. The system checks for overlapping effective date ranges. When an overlap exists, the system issues an error message.

When you process taxes in the JD Edwards EnterpriseOne Real Estate Management system, note that:

• The Tax Suppress field in the F1510B table controls whether tax processing is in effect and whether the tax-related fields are displayed.

  Processing options for specific billing programs also control tax processing.

• When tax processing is in effect, you can assign the necessary tax information for a billing in the Tax Explanation Code, Tax Rate/Area, and Service/Tax Date fields.

  The service and tax date must occur within the effective date range that is defined for the tax rate and area.

• The system automatically supplies the tax rate area for a tenant from either the Customer Master by Line of Business table (F03012) or Supplier Master table (F0401).

  You can also manually assign a different tax rate area for a particular billing.

In addition to the tax explanation codes that are used in the JD Edwards EnterpriseOne Accounts Payable and Accounts Receivable systems, the Real Estate Management system uses the tax explanation code AR.

The system calculates taxes for tax explanation code AR in the same manner that it does for S, with these differences:

• The system creates a separate pay item for each tax rate that is specified.

• The system uses the GL offset from the tax rate area in conjunction with PM/RC AAIs (for invoices) and RM/PC AAIs (for vouchers) to locate the tax account and tax offset account to use.

For example, suppose that you want to charge a county tax of 2 percent and a city tax of 3 percent on an invoice with a taxable amount of 1,000. Using the code AR and the appropriate tax rate area, the system automatically creates two pay items for the tax information.

The resulting invoice has these pay items:

• 1,000 for the invoice.

• 20 for the county tax.

• 30 for the city tax.

If the tax explanation code S is used, the resulting invoice has only one pay item for 1,000 with a tax amount of 50.

Important! Any tax explanation codes other than AR that you use in the JD Edwards EnterpriseOne Real Estate Management system are subject to the standard financial tax processing and setup.

See Understanding Tax Explanation Codes.

The system stores tax rate and area information in the Tax Areas table (F4008).

Prerequisite

Before you complete the tasks in this section:

• Set up tax authorities.

• Set up the appropriate tax AAIs.

See Also

Setting Up Tax Authorities

Setting Up AAIs for Taxes

Forms Used to Set Up Tax Rate Area Information

Setting Up Tax Rate Areas

Access the Tax Rate/Area Revisions form.

Tax Rate/Area	Enter the code that identifies a tax or geographic area that has common tax rates and tax authorities. The system validates the code that you enter against the Tax Areas table (F4008). The system uses the tax rate area in conjunction with the tax explanation code and tax rules to calculate tax and GL distribution amounts when you create an invoice or voucher.
Effective Date and Expiration Date	Enter the date when a transaction, contract, obligation, preference, or policy rule becomes effective or ceases to be in effect.
Tax Authority Address	Enter the Address Book number of the tax authority.
G/L Offset (general ledger offset code)	Enter the code that indicates how to locate the tax account for general ledger entries. This field points to AAIs that, in turn, point to the tax account. Examples are: PTyyyy for AP (VAT only). RTyyyy for AR (VAT only). GTyyyy for GL (VAT only). 4320 for sales orders 4400 and 4410 for purchase orders. When setting up VAT and Canadian GST, PTyyyy, RTyyyy, and GTyyyy are the only valid values. For the AP system, a second GL offset (PTxxxx) is required when the tax setup involves VAT plus use taxes (tax explanation code B). Use the AAI PTxxxx to designate the use tax portion of the setup. For sales taxes, the Accounts Payable and Accounts Receivable systems do not use the values in this field. However, the Sales Order Management and Procurement systems require values in this field. You must complete this field for tax rate areas that are used with tax explanation code AR.
Tax Rate	Enter the percentage of tax that is assessed or paid to the corresponding tax authority, based on the tax area. Enter the percentage as a whole number and not as the decimal equivalent. For example, to specify 7 percent, enter 7, not .07. If the tax rate area is used with tax explanation codes B (VAT plus use) or C (VAT plus sales), you must enter the VAT tax authority and tax rate on the first line of the tax rate area.

Setting Up Logs and Legal Clauses

This section provides overviews of logs and legal clauses, log standards, and lease options and discusses how to:

• Enter log standards

• Enter lease option types

Understanding Logs and Legal Clauses

The system provides two methods for tracking information: logs and legal clauses.

You can use either or both methods, depending on the type of information that you want to track:

• Logs enable you to track information by lease, building, floor, or unit.

• Legal clauses enable you to track information by lease or tenant.

Although you can use logs to track lease information, the legal clause applications provide a more robust means of tracking because you can associate the clause directly with a unit, and you can group all the clauses by tenant instead of by lease only.

You can set up templates both for legal clauses and for logs. You set up the templates for legal clauses by using lease option types; you set up the templates for logs by using log standards.

This table describes some of the differences between legal clauses and logs, as well as providing information that is specific to the template:

Understanding Log Standard Information

Log standards are templates or models that you can set up so that you can track the same information for the same types of leases, buildings, floors, and units.

This table lists the log standard and type, and the information that you might set up:

When you use logs, each type of information that you track is a log class. You set up the logs by log class by lease, building, floor, or unit.

Log information further describes a lease or facility. For leases, the log information defines the terms and conditions of the lease, such as critical dates, lease options, text descriptions, and so on. For facilities, it might define the areas that you use for expense participation, critical dates, the number of units within a building or on a floor, tenant improvements, inspection of the sprinkler system, and so on.

If you use the same logs to track similar information on the lease or facility, you can set up log standards to use as a template.

Log standards are useful because they:

• Simplify the setup process for individual leases and facilities.

• Enable you to efficiently set up a large number of leases or facilities.

• Maintain uniformity.

• Reduce the possibility of errors.

When you set up log standards, you must set up the log standard level to identify whether the log pertains to the lease, building, floor, or unit.

You use these UDCs to further identify the type of lease, building, floor, or unit to which the log pertains:

• Tenant Lease Type (15/LT) for leases.

• Business Unit Types (00/MC) for properties and buildings.

• Grouping Code (15/GC) for floors.

• Unit Type (15/UT) for units.

When you set up log lines, you can specify whether they are required. For example, you might make the log line for insurance information that is required so that a critical date is entered to indicate when insurance information must be received.

You can update log information when necessary by revising log lines, deleting lines within logs, and adding more lines to the log. When you revise the log standard, you change the current information for that log standard from that point forward. Logs that are already attached to leases or facilities do not change.

Additionally, you can attach a media object (for example, a lease abstract) to a log standard. Every time that you copy the log standard, the system includes the attached media object.

The system provides processing options that enable you to copy log standards automatically when you add a new lease, building, floor, or unit.

Note. You can still copy log standards manually if the processing option is not set to copy log standards automatically.

Understanding Lease Option Type Standards

For legal clauses, you use lease options as the model or template for the type of information that you track. You can set up options for each lease type that you use, or for specific tenants, but not for both. For example, you might offer an option for parking on commercial leases that you do not offer on leases for restaurants.

Option types include lease details such as mortgage information, options to renew, lease terms, right of first refusal, and insurance information. You can define these options as standard for a tenant or a lease type.

Lease option type information is stored in these tables:

• F157011

• F157012

Prerequisites

Ensure that these UDCs are set up:

• Tenant Lease Type (15/LT)

• Business Unit Types (00/MC)

• Grouping Code (15/GC)

• Unit Type (15/UT)

• Log Class (15/LG)

• Amenity Identification (15/AM)

See Also

Setting Up Legal Clause Information

Forms Used to Enter Log Standards and Lease Options

Entering Log Standards

Access the Log Standards Revisions form.

Business Unit Log Standards, Floor Log Standards, Unit Type Log Standards, and Lease Type Log Standards	Enter the type of processing for an event.
Type Business Unit	Enter the UDC (00/MC) that identifies the classification of the business unit.
Area Grouping Code	Enter the code that the system uses to reconcile the total area of the group to the total area of the floor. If you leave this field blank, the system automatically uses FLOR. A processing option in this program controls the kind of floor that the form displays, based on the grouping code.
Unit Type	Enter the UDC (15/UT) that identifies the type of unit for billing and reporting purposes. Examples include: OFFCE: Office space RSALE: Retail space RESTR: Restaurant CONDO: Condominium
Lease Type	Enter the UDC (15/LT) that identifies the type of lease for billing and reporting purposes. Examples of values include: AP: Apartment. CO: Commercial office. RT: Retail store. SB: Sublease.
L C (log class)	Enter the UDC (15/LG) that identifies the type of information that the log contains. Examples of values include: OP: First renewal option. IN: Insurance. PK: Parking spaces. TI: Tenant improvements.
AM ID (amenity ID)	Enter the four-character UDC (15/AM) that is used to provide additional information about the class to which the log belongs. For example, if the log class represents building features, the amenity ID can be used to further define a feature, such as atrium. Examples include: F01: Number of rentable units F02: Seating capacity INS: Insurance renewal SEWR: Sewer hookups
Explanation -Remark-	Enter a name or remark that describes the purpose for using an account or that conveys any other information about the transaction.
R S (required standards)	Enter the code that specifies whether the log line is a required standard for the lease. Values are: Blank or N: The log line is not a required standard. Y: The log line is a required standard and cannot be deleted from the model. If you select this value, the system disables the LC (log class), AM ID (amenity ID), and UM (unit of measure) fields for revisions.
E.P. Code (expense participation code)	Enter the UDC (15/EP) that specifies an area that the system uses to calculate expense participation.
RP1 (reporting code pm log 01)	Enter the UDC (system 15, types L1–L10) that specifies a group for reporting purposes. You can set up the field names in vocabulary overrides.

Entering Lease Option Types

Access the Option Type Revisions form.

Option Type	Enter the code that you set up in the Lease Option Type Information program (P157011) that specifies the type of option that is offered on a legal clause.
Detail Type	Enter the code that identifies individual items within an option type.
Detail Description	Enter the code that specifies details about an option type, such as the number of parking spaces.
Std Opt (standard option)	Enter the code that specifies whether an option is standard. The system automatically copies options that are standard when a new lease is added based on the setting of the processing option. Values are: Blank: Not standard. Y: Standard.
Std Lvl (standard option level)	Enter the UDC (15/SL) that indicates whether an option is defined as standard for the lease or the tenant. If the option is a standard for leases, the lease type must also be defined. If the option is a tenant standard, the tenant number must also be defined. Values are: L: Lease. You must also specify the lease type if you select this option. T: Tenant. You must also specify the tenant's address book number if you select this option.
Lse Type (lease type)	Enter the UDC (15/LT) that identifies the type of lease for billing and reporting purposes. Examples include: AP: Apartment. CO: Commercial office. RT: Retail store. SB: Sublease.
Recurring Option	Enter the UDC (15/RO) that can be used for informational purposes.

Setting Up Statement Messages

This section provides an overview of statement messages, lists the form used to set up statement messages, and discusses how to set processing options for Generic Message/Rates Records (P00191).

Understanding Statement Messages

You can set up the system to print user-defined messages on statements that you send to customers. The Statement Messages program (P00191) uses UDCs (15/MS) as identifiers for the associated text that prints on the statement.

Although you can set up an unlimited number of statement messages, the print statement program limits the number of messages that are printed in these locations on the statement:

• The header portion of the statement.

• The portion to the left of the total following the statement detail.

• The aging portion of the statement if you specify to print aging information.

  You can specify a different message to print according to the aging category. For example, you might include a message on statements with invoices in the fifth aging category that is more strongly worded than the message on statements with invoices in the first aging category. If one statement has invoices in multiple aging categories, the system prints the message that is associated with the oldest aging category.

The Statement Message program uses processing options that enable you to specify either a 60- or 80-character message to print on the statement. Although the processing options enable you to specify a different UDC table to use, the Print Statements program accesses codes from table 15/MS only.

The system stores the statement message codes and associated text in the General Message Detail table (F00192).

Prerequisite

Verify the processing option settings:

• Ensure that you enter 15 in the System Code processing option and MS in the Record Type processing option.

  These two processing options are located on the Defaults tab.

• Ensure that you enter 2 in the Text Type processing option on the Display tab.

See Also

Printing Statements for Real Estate Management

Forms Used to Set Up Statement Messages

Setting Processing Options for Generic Message/Rates Records (P00191)

Set these processing options to specify the default processing for this program.

Defaults

Use these processing options to specify the default information that the system uses.

Display

Use these processing options to specify how the text appears.