The entities that capture addresses in the product break down the constituents into separate fields. An implementation defines the appropriate constituents for each Country and allows for each constituent to have an appropriate label. This way, when displaying addresses in the system, the appropriate fields appear with the appropriate labels.
When considering addresses captured by tax forms or registration forms, implementations should consider how the data is captured and how this data is later mapped to the appropriate constituents based on the country defined on the form. The following points should be considered:
Should all possible countries be loaded in the Country table? For validation purposes, an implementation may choose to load all countries. However, for countries that are not common, it is recommended to choose a consistent set of constituents for mapping from the form and capturing in the master data in the system. If implementations do not wish to load all the countries in the country table, an alternative is to define a special "Other" or "Unknown" country. In this case one of the free format constituents available may be used to capture the country value.
Consider the definition of State. The product provides a constituent for State and in this case it expects valid states to be defined in the State table (also on the Country page). Implementations will probably not want to define the valid states for all the countries defined in the Country table. However, the Country table provides many free-format fields that available to define the "state" for a country where the list of possible states is not maintained. For example, assuming County information is not captured for most foreign countries, the County field can be used. It's label can be configured to be "State" or "Province" or whatever is appropriate. Address 4 is another possibility if it is rarely used.
Once the address constituents for different countries are defined, consider forms processing. Forms have a defined set of fields for capturing addresses. When attempting to map those form lines to the system's address components, the address columns on the Form need to be populated based on the country configuration. For countries where the State checkbox is checked, the data on the form representing the State should go into the STATE column and will be validated. For countries where the State checkbox is not checked, the data on the form representing the State should go into the agreed upon other column (for example. COUNTY).
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]