E1: 15: Frequently Asked Questions about Lease Master Information (P1501) (Doc ID 1293973.1)

Last updated on MARCH 06, 2024

Applies to:

JD Edwards EnterpriseOne Real Estate Management - Version XE and later
Information in this document applies to any platform.

The Purpose of this document is to answer questions on the Lease Information, P1501

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Purpose

Question 1: Please provide information on the P1501 application for fields Rent Year Begin Month (RYRB) and Lease 1 Year Begin Month (LYBM). Where are the default values set and what function do they provide?

Question 2: Explain how the Lease Master Revisions (P1501) functions with other applications if there are multiple units selected for the lease.

Question 3: In Lease Master Revisions (P1501), Tenant does not have the address book visual assist. Why and how to correct?

Question 4: How are the ALP, DUP and TOTD fields populated in the F1501B?

Question 5: Is there a way to release a user in Lease Maintenance screen (P1501) when a user is timed out?

Question 6: How to clear the '1' in the version field of the Lease Master (P1501) or the Unit Master grid (P15217)?

Question 7: How to change or clear the value in the Moved Out Date field, MODT, in the Unit Master (P15217)?

Question 8: Can the Transaction Currency Code be changed in Lease Information (P1501) and what is the impact?

Question 9: Why is it no longer possible to have more than one person view the Lease Master (P1501) at the same time? This functionality was not in previous releases.

Question 10: Why doesn't the paper clip appear when adding text to a new log detail in Lease Information (P1501)?

Question 11: Is it possible to copy the leases from one building to another?

Question 12 : What is the relevance of the Primary Lease Number (PLNM) field in F1501B table?

Question 13: Changing a lease status to terminated in Lease Master Information (P1501) does not prevent the entry of a cash receipt in RE Cash Receipts (P15103) or creating a Manual Billing (P1511), why?

Question 14: Is there a Business Service (BSSV) available to create/update Lease Master (P1501) records? If not, is there any plan to release it soon?

Question 15: Is there an automated method to transfer a building between companies within E1? It will require an update to the unit master, security deposit, recurring billing, etc. and it is necessary to keep historical data in old company but also move it to a new company.

Question 16: How is it possible to set up an Open Ended Lease in Lease Master Information (P1501)?

Question 17: Why is the CRRM field ( Domestic/Foreign) in the F1501B Blank when adding a new Lease using P1501 in a multi-currency environment?

Question 18: Is it possible to reuse a Unit number on the same lease with a different date range?

Question 19: Does Oracle has an application for Batch Upload for Lease Information (P1501)? If not what is the recommendation?

Question 20: When updating the Rentable or Useable Area values in the Lease Master (P1501), are these values updated to the Unit Master table (F1507)?

Question 21: When entering a non-property lease with an asset. An Error Building Invalid (15LE) is produced?

Question 22: Is it necessary to populate the Lease Status field in Lease Information for either Lease or Lessee leases? Is there a purpose for this field?

Question 23: When updating the Unit Area screen (P15217) every time the update button is pressed a popup window is displayed saying JAS_MSG346: JAS database failure: (No-Set_Clause_for_Update), update cannot be executed without a set clause.

Question 24: Is there a mass upload or update feature for lease changes in Version 9.0?

Question 25: When updating the Lease Master, the form throws 'Overlapping Occupancy for Unit Invalid" error? How do I resolve this?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.