Welcome to Release 12.2 of the Oracle Property Manager Implementation Guide.
This guide contains the information you need to implement Oracle Property Manager.
See Related Information Sources for more Oracle Applications product information.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customer access to and use of Oracle support services will be pursuant to the terms and conditions specified in their Oracle order for the applicable services.
This chapter provides an overview of the implementation of Oracle Property Manager. It also includes an overview of the lease administration and space management tasks you can accomplish with Oracle Property Manager and the Oracle applications with which it is linked.
This chapter describes the prerequisite and optional setups steps that you need to complete in other Oracle products before you can set up Oracle Property Manager for your organization.
When you first install and set up Oracle Property Manager for your business, you must configure several components, including flexfields, lookups, and system options. After these components are properly configured, you can use Oracle Property Manager without making any routine modifications.
For the order in which the Oracle Property Manager setup steps should be performed, see Oracle Property Manager Setup Checklist.
This chapter describes the rules and templates you define to help users create, abstract, and administer leases effectively using Oracle Property Manager.
This chapter describes the open interfaces in Oracle Property Manager.
Views are customized presentations of the data in one or more tables. In other words, views are logical tables whose data are not stored permanently. Public views provide read-only access so you can use them for custom reporting and similar requirements. For information on how to modify Oracle Property Manager data using third-party software, see Oracle Property Manager Open Interfaces.
This appendix outlines the steps required to convert legacy lease data into the Oracle Property Manager schema.
This appendix describes how you can use function security to control user access to Oracle Property Manager.
The Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets users easily discover and deploy the appropriate business service interface for integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the Oracle E-Business Suite. As your instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.
Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data Browser, database triggers, or any other tool to modify Oracle E-Business Suite data unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and maintain information in an Oracle database. But if you use Oracle tools such as SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of your data and you lose the ability to audit changes to your data.
Because Oracle E-Business Suite tables are interrelated, any change you make using an Oracle E-Business Suite form can update many tables at once. But when you modify Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle E-Business Suite.
When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite automatically checks that your changes are valid. Oracle E-Business Suite also keeps track of who changes information. If you enter information into database tables using database tools, you may store invalid information. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes.