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
Skip to content
  • Register

    • Oracle Additional Address Attribute Clarification

    in Sales 3 comments

    Hi Team,

    We have a business requirement to load Community data meaning (Autonomous communities data: Andalusia, Aragon, Asturias, the Balearic Islands, the Basque Country, the Canary Islands etc..) for Spain (ES). Given that we have already utilized the AdditionalAddressAttribute1 for the AttentionLine, we have mapped the Community data to AdditionalAddressAttribute2.

    During testing, we loaded sample data and expected, based on Oracle documentation (https://docs.oracle.com/en/cloud/saas/sales/oacdm/seeded-address-formats-for-countries.html), that Loqate would not process this address element. However, we observed that Loqate is also cleansing the data in AdditionalAddressAttribute2.
    Conversely, when we tested by placing the Community data in AdditionalAddressAttribute1, Loqate did not process it.

    Tagged:

    Howdy, Stranger!

    Log In

    To view full details, sign in.

    Register

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