Impact of Disabling Address Validation and Making Address related attributes as non mandatory — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Impact of Disabling Address Validation and Making Address related attributes as non mandatory

edited Jun 3, 2025 10:00AM in Supplier Management 2 comments

Summary:

Impact of Disabling Address Validation and Making Address related attributes as non mandatory

Content (please ensure you mask any confidential information):

Please let us know the impact of below 2 items functionally.

1. Disabling address validation - Our Business requested to disable the address validation in Oracle Fusion, We believe this will only disable the validation of the combination or the values within oracle defined geographies (city/province, state, postal code), if yes, what is the impact to other modules or functionalities if we disable this. Is this recommended option?

2. Making required address fields (city/state/province/postal code) not mandatory - For example, not passing province in case of country equals to non-US (eg. Canada) - What is the impact of making these fields as non-mandatory and not populating during the conversion/migration load from legacy system to Oracle fusion... does Oracle Fusion allow this? and is this recommended?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!