Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 295 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
US Sales Tax and Tax Area Primary key
AEklund
Member Posts: 13
There apparantly are many options for the primary key on Tax area.
The Natural key:
Zip - City - County - (Flag for In/Out city) - (Flag for in/out Local)
Basic issue is that the two flags on the end are needed cause there are some specials, and zip is not unique unless you include city and county.. (Zip can span multiple cities, and zip can span multiple counties)..
Considerations:
1. The Natural length ofthe key in navision is 10-20, not 40-60 bytes. THe natural key is too big..
2. Assigning a particular customer/shipto to a tax area needs to be easy.
3. Setting up all of the tax areas and linking them to the tax jurisdictions needs to be easy..
Options:
1. Several vendors have a made up "code" that identifies a zip-city-county. This can be based on the FIPS code(county), Zip code, and a made up key to reflect the rest of it..
2. We might be able to use zip+4 to take on the first part of it.. Zip+4 plus the two flags make a unique code..
What has anyone used out there?
The Natural key:
Zip - City - County - (Flag for In/Out city) - (Flag for in/out Local)
Basic issue is that the two flags on the end are needed cause there are some specials, and zip is not unique unless you include city and county.. (Zip can span multiple cities, and zip can span multiple counties)..
Considerations:
1. The Natural length ofthe key in navision is 10-20, not 40-60 bytes. THe natural key is too big..
2. Assigning a particular customer/shipto to a tax area needs to be easy.
3. Setting up all of the tax areas and linking them to the tax jurisdictions needs to be easy..
Options:
1. Several vendors have a made up "code" that identifies a zip-city-county. This can be based on the FIPS code(county), Zip code, and a made up key to reflect the rest of it..
2. We might be able to use zip+4 to take on the first part of it.. Zip+4 plus the two flags make a unique code..
What has anyone used out there?
Allan Eklund
0