Trouble Shooting
To Rollback or not to Rollback
Identification
Identification 2
Tie Break/Bonus
100

Based on the information in Scenario 7, why didn't the relocation move out generate correctly?

The Version End Date is missing.

100

An incorrect table was generated as of 7/1/26. Batch was not posted. Current accounting month is still July.

Rollback and Recast

100

This Code 5 Flips to 2 when SLR is generated

Code 5 = D

100

This Code flips to 1 when SLR is generated

P

200

Based on the information in Scenario 4, why didn't the relocation move out generate correctly?

Version Effective Date in Processing Option was not set to prior to Version End Date.

200

Inline Lease (SF < 7500) Current Accounting Month is July 2026

RCD of 2/4/26 was never supposed to be processed. New RCD to be provided eventually

Rollback

200

Using Scenario 1, Identify the FOFF amount for a rent adjustment effective 4/1/26

$4,427.84

200

This Code 5 flips to 9 when SLR is generated

H or M

300

A lease with a flat table expiring 12/31/26 is being renewed for the current month for 12 Months Eff 1/1/27 - 12/31/27 at a higher flat rate. Are we expecting a SLR batch?

Yes, new table will be generated as of the current month, which would capture the rent increase, causing SLR to have to calculate the mean

300

Ground Lease. 

RCD revised from 8/21/26 to 7/7/26. 

Delivery = 12/2/25. Code 5 = P

No Rollback. FCNV to correct.

300

Using Scenario 8, Identify the Balance Forward amount for a future termination with a notice date of 2/7/26

$4,828.70
400

Based on the information in Scenario 2, why didn't the correct table generate correctly?

Process Option 4 is set to use lease begin date (RCD: 7/7/26) which is causing the system to prorate July SLR when it shouldn't.

400

Inline Lease (SF < 7500) Current Accounting Month July 2026

RCD Revised from 6/5/26 to 7/10/26.

Delivery = 1/1/26. Code 5 = D

No table should exist

400

This Setting Prevents FTRN lines from being suspended when generating Relocation Move Out.

Pre-Conversion Entry Setting (Reference 1)


500

Based on the information in Scenario 3, why would the table generated be blank

Ballard Property needs their Bill Code Accrual status removed temporarily in order for SLR to pull in BASZ codes.


500

Based on the information in Scenario 5, what should code 5 be?

X

500

Based on the information in Scenario 6, why is this table incorrect?

We don't bill NNN for Ballard Properties