Implementing Cloud Financials: From Empty Pod to Go-Live · Module 3 · Common Configuration
Geographies and address validation
Lesson 22 of 153 · 2 min
Three layers, and keeping them separate is most of the lesson. Country structure is which address levels a country uses, in order — country, state, county, city, postal code, or whatever that country actually uses. Not every country has all of them. Geography hierarchy is the populated values: state names, city names, postal ranges. Geography validation is which levels are checked when somebody enters an address, and how hard the check is — error, warning, or none. Then the trade-off, stated plainly. Strict validation means clean data and blocked data loads. Loose validation means fast loading and a customer master full of typos. Ask the client which pain they prefer, because they will get one of them. Geography data comes from delivered content for some countries, from licensed third-party data, or from manual and spreadsheet loading. All three are covered. And the reason this stops being cosmetic: geography feeds tax…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Cloud Financials: From Empty Pod to Go-Live, with a certificate on completion and a fourteen-day refund window.