Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szComputerID | CTID | char | REQ | INPUT |
|
szBuilding | MCU | char | OPT | INPUT |
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
might be a warehouse location, job, project, work center, branch, or plant.
You can assign a business unit to a document, entity, or person for
purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by
business unit to track equipment by responsible department.
Business unit security might prevent you from viewing information about business units
for which you have no authority.
|
mnRevisionNumber | RVNB | MATH_NUMERIC | OPT | INPUT |
A number that specifies a unique budget revision. You store multiple revisions of information you set up and calculated budget information
within the system. The system stores each "what-if" scenario according to the budget revision number you assign.
|
szCompany | CO | char | OPT | INPUT |
A code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the Company
Constants table (F0010) and must identify a reporting entity that has a complete balance sheet. At this level, you can have intercompany
transactions.
Note: You can use company 00000 for default values such as dates and automatic accounting instructions. You cannot use company 00000
for transaction entries.
|
szProperty | MCUS | char | OPT | INPUT |
Either a subsequent business unit or a project number.
A subsequent business unit specifies where to charge costs (or revenues) when the
original business unit has been closed or suspended. For example, the subsequent business unit can be used in corporate reorganizations
when you close a business unit and direct all costs to the subsequent business unit. In this situation, you must enter journal entries to transfer
existing balances.
A project number is used to group business units within an overall business unit. For example, you can group jobs by
project. In this case, the project business unit can also have accounts for tracking overhead costs that can be allocated to jobs. |
szUnit | UNIT | char | OPT | INPUT |
The number that identifies the actual space within a building that is or can be leased, such as an apartment, office, retail space, parking
space, and so on. |
mnSquareFootage | USEA | MATH_NUMERIC | OPT | INPUT |
The area of a building, floor, or unit that can be occupied or leased; the net leasable area. This might be different from the rentable area.
|
mnLeaseNumber | DOCO | MATH_NUMERIC | OPT | INPUT |
A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry,
and so on. |
jdLeaseBeginDate | EFTB | JDEDATE | OPT | INPUT |
The date that an address, item, transaction, or table record becomes active. The meaning of this field differs, depending on the program.
For example, the effective date could represent the following:
o When a change of address becomes effective.
o When a lease becomes
effective.
o When a price becomes effective.
o When the currency exchange rate becomes effective.
o When a tax rate becomes effective.
|
jdLeaseEndDate | EFTE | JDEDATE | OPT | INPUT |
The date on which the item, transaction, or table becomes inactive, or through which you want transactions to appear. This field is used
generically throughout the system. It could be a lease effective date, a price or cost effective date, a currency effective date, a tax rate effective
date, or whatever is appropriate.
|
jdBudgetBeginDate | EFTB | JDEDATE | OPT | INPUT |
The date that an address, item, transaction, or table record becomes active. The meaning of this field differs, depending on the program.
For example, the effective date could represent the following:
o When a change of address becomes effective.
o When a lease becomes
effective.
o When a price becomes effective.
o When the currency exchange rate becomes effective.
o When a tax rate becomes effective.
|
jdBudgetEndDate | EFTE | JDEDATE | OPT | INPUT |
The date on which the item, transaction, or table becomes inactive, or through which you want transactions to appear. This field is used
generically throughout the system. It could be a lease effective date, a price or cost effective date, a currency effective date, a tax rate effective
date, or whatever is appropriate.
|
mnLeaseTerm | MATH01 | MATH_NUMERIC | OPT | INPUT |
- - - Good Performance Low Value.
|
cCalculationMethod | CALM | char | OPT | INPUT |
A user-defined code (15L/CM) that calculates the method for tenant improvement and commissions to be paid. Calculation methods 1
through 6 are validated against the amount type. If the amount type is a percent, the calculation method must be a percentage. Likewise, if the
amount type is a fixed amount, the calculation method is also a fixed rate. Calculation method 7 does not use an amount type. Calculation
methods are defined by PeopleSoft, and should not be changed.
Note: Calculation method is not used when the Assumption Type is Other
Assumptions (OT), and no validation will occur. The allowable combinations are:
AMOUNT TYPE
CALC METHOD
Percentage (PC)
1.
Percentage of Base Rent
2. Percent Base Rent Compounded
Square Foot (SF)
3. Square Foot Market Rate
Fixed Amount (FX)
4. Fixed Base Rent
Compounded
5. Monthly Fixed Market Rate
6. Fixed Market Rate
|
szDetailAsmpType | ASTP | char | OPT | INPUT |
A user defined code (15L/AT) that specifies a type of expense incurred on a lease. The assumption type is associated with a bill code.
Values are defined by PeopleSoft and should not be changed. Values include:
EC
External commissions
IC
Internal commissions
OC
Other
commissions
OT
Other assumptions
TI
Tenant improvements
|
szDetailRetrievalBC01 | RBC01 | char | OPT | INPUT |
The bill code for which the system retrieves the associated amount from the Recurring Billings Master table (F1502B) to use as the base
amount in the calculation for the assumption detail. The system adds together the amounts for the retrieval bill codes that you specified. If you
do not specify any retrieval bill codes, the system calculates the base amount by multiplying the market rate from the assumption header by
the area of the unit.
|
szDetailRetrievalBC02 | RBC02 | char | OPT | INPUT |
The bill code for which the system retrieves the associated amount from the Recurring Billings Master table (F1502B) to use as the base
amount in the calculation for the assumption detail. The system adds together the amounts for the retrieval bill codes that you specified. If you
do not specify any retrieval bill codes, the system calculates the base amount by multiplying the market rate from the assumption header by
the area of the unit.
|
szDetailRetrievalBC03 | RBC03 | char | OPT | INPUT |
The bill code for which the system retrieves the associated amount from the Recurring Billings Master table (F1502B) to use as the base
amount in the calculation for the assumption detail. The system adds together the amounts for the retrieval bill codes that you specified. If you
do not specify any retrieval bill codes, the system calculates the base amount by multiplying the market rate from the assumption header by
the area of the unit.
|
szDetailGrowthPattern | GRPA | char | OPT | INPUT |
A number that specifies a defined growth pattern. Growth patterns are used to anticipate increasing amounts for lease revenue and
expenses based on several market factors, including the following:
o Square feet
o Flat amount
o Percentage amount
o Specified number of
years
The Advanced Real Estate Forecasting account definition provides starting values that increase by the growth pattern assigned to the building.
|
szDetailGPType | GPTT | char | OPT | INPUT |
A user defined code (15L/GT) that identifies the amount type for the associated growth pattern. The following amount types are defined by
J.D. Edwards and should not be changed.
FX
Fixed Amount
PC
Percentage Amount
SF
Square Foot
|
mnDetailMarketRate | GA01 | MATH_NUMERIC | OPT | INPUT |
A number that specifies the expected growth rate for a new assumption in the base year. The new assumption value can be defined as a
currency, a percentage, or an amount per square foot.
|
szExpressionLine01 | D200 | char | OPT | OUTPUT |
A free form 200 character description. |
szExpressionLine02 | D200 | char | OPT | OUTPUT |
A free form 200 character description. |
szExpressionLine03 | D200 | char | OPT | OUTPUT |
A free form 200 character description. |
szExpressionLine04 | D200 | char | OPT | OUTPUT |
A free form 200 character description. |
szExpressionLine05 | D200 | char | OPT | OUTPUT |
A free form 200 character description. |
cLeaseType | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
szDetailBuilding | MCU | char | OPT | INPUT |
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
might be a warehouse location, job, project, work center, branch, or plant.
You can assign a business unit to a document, entity, or person for
purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by
business unit to track equipment by responsible department.
Business unit security might prevent you from viewing information about business units
for which you have no authority.
|
cAsmp1TermCalculation | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
cAddDowntime | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
jdOriginalBudgetEndDate | EFTE | JDEDATE | OPT | NONE |
The date on which the item, transaction, or table becomes inactive, or through which you want transactions to appear. This field is used
generically throughout the system. It could be a lease effective date, a price or cost effective date, a currency effective date, a tax rate effective
date, or whatever is appropriate.
|