The product supports a centralized address repository. All address records are stored in a common table and may be linked to persons, tax roles and assets. Refer to the documentation for each object for more information about how addresses are linked.
The following points highlight some information about centralized address functionality:
The address object displays and captures address constituents based on the configuration on the country defined for the address. Your implementation must define the valid countries and the expected address constituents to capture for that country.
The address object does not have a related Type object that governs the behavior of the address as is found with many other master and transaction objects in the system.
There is an Address Type extendable lookup supplied. This is used to define how / why an address is linked to another object. For example, a person may have a "legal" address and a "mailing" address. In order to link addresses to a person or a tax role, the valid address types must be configured on the respective person types and tax types.
The address object does not have a configurable business object lifecycle. Rather it has a simple Active / Inactive flag. When changing an address to be inactive, the system prompts for an inactive reason, which are defined using the Address Inactive Reason extendable lookup
The system supplies a Find address algorithm plug-in spot on the installation record. If your implementation receives information from an external source related to a change to a taxpayer’s address, the plug-in spot may be used to determine if the address is already in the centralized address repository.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]