This discussion is archived
7 Replies Latest reply: Aug 12, 2013 3:57 PM by DipanjanMaitra RSS

Error: Ship to/Bill To Address is Invalid. Please review the Address Setup

DipanjanMaitra Explorer
Currently Being Moderated
After Upgrading to 12.1.3, Orders are failing during Import/Scheduling with "Error: Ship to/Bill To Address is Invalid. Please review the Address Setup" whenever Tax Engine is called. And this is happening for only specific addresses (that are vaild). I will appreciate any experience/suggestion on this regard.

Thanks,
Dipanjan
  • 1. Re: Error: Ship to/Bill To Address is Invalid. Please review the Address Setup
    977003 Newbie
    Currently Being Moderated
    I am also facing the same issue after 12.1.3 upgrade. Please let me know if any one found a solution to this issue.

    Thanks,
    Prasanth
  • 2. eTax-Ship to/Bill To Address is Invalid. Please review the Address Setup
    user485910 Newbie
    Currently Being Moderated
    We have an AR Invoice that has been autoinvoiced from OM. The invoice has been created but the tax has not been calculated. When reviewing the log states the following:

    Calculate Tax Error:
    Ship to/Bill to Address is Invalid: Please review the Address Setup

    Failed in Calculate_Tax procedure

    We have checked the Ship To and Bill To address with the customer as all is correct.

    Anyone experienced this issue?
  • 3. Re: eTax-Ship to/Bill To Address is Invalid. Please review the Address Setup
    Hussein Sawwan-Oracle Employee ACE
    Currently Being Moderated
    Please see if (RAXTRX: Encountered Error During Autoinvoice When Integration is with Vertex [ID 1531477.1]) helps.

    Thanks,
    Hussein
  • 4. Re: eTax-Ship to/Bill To Address is Invalid. Please review the Address Setup
    user485910 Newbie
    Currently Being Moderated
    Thanks for the ml note. Will update post accordingly.
  • 5. Re: Error: Ship to/Bill To Address is Invalid. Please review the Address Setup
    DipanjanMaitra Explorer
    Currently Being Moderated

    Hi,

     

    There has been multiple causes for this issue, namely:
    (1) Invalid Address as per Vertex - Resolution here would be to find the alias name of the city for the given Zip code (Google, zip-codes.com, etc.) and use that. You should see the result instantly.

    (2) Texas or Forida Addresses where there's no Nexus - Often we see that there are multiple records in vertex for the given city, and it throws an error. The safest option here is to obtain the Geography Code from vertex for such combinations and then update the same in Oracle as the GeographyCode Override (Default value = '77000000') to suppress vertex call. Alternatively we can create a AR Txn type with Tax Classification as 'No' and then tie that to a new Order Type. Any order with such order type will not call vertex.

    (3) Millitary Addresses - Resolution is same as 2 above.

     

    Dipanjan

  • 6. Re: Error: Ship to/Bill To Address is Invalid. Please review the Address Setup
    c156e504-721e-4b8b-9b98-2b763884148b Newbie
    Currently Being Moderated

     

  • 7. Re: Error: Ship to/Bill To Address is Invalid. Please review the Address Setup
    DipanjanMaitra Explorer
    Currently Being Moderated

    ---  Here's a skeleton structure of the PLSQL that you should use----

     

    l_location_rec          APPS.HZ_LOCATION_V2PUB.LOCATION_REC_TYPE;

    -----Use this to find a good address from existing TCA in Oracle, by passing only the zip code:

    SELECT hgi.identifier_value,hg.geography_element4_id

                       ,hg.geography_element1 country

                       ,hg.geography_element2 state

                       ,hg.geography_element3 county

                       ,hg.geography_element4 city

                       ,hg.geography_element5 postal_code

                 FROM apps.hz_geographies hg,apps.hz_geography_identifiers hgi

                WHERE hgi.geography_id  = hg.geography_element4_id

                  AND hg.geography_name = :pp_zip_code

                  AND hg.geography_type = 'POSTAL_CODE'

                  AND primary_flag='Y';

     

    -----The Update the Location

                 l_location_rec.CITY  := rec_get_geo_elements.city;

                 l_location_rec.COUNTY := rec_get_geo_elements.county;

                 l_location_rec.STATE := rec_get_geo_elements.state;

                   hz_location_v2pub.update_location (p_init_msg_list           => FND_API.G_TRUE,

                                           p_location_rec            => l_location_rec,

                                           p_object_version_number   => l_object_version_number,

                                           x_return_status           => l_return_status,

                                           x_msg_count               => l_msg_count,

                                           x_msg_data                => l_msg_data);

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points