MSAMM
Back to course

Implementing Cloud Financials: From Empty Pod to Go-Live · Module 3 · Common Configuration

Why this module comes first

Lesson 21 of 153 · 1 min

Nobody is excited about geographies. Getting that out of the way is what buys the rest of this module. Here is the argument, as a chain. You cannot load a supplier without a valid address. You cannot validate an address without a geography hierarchy. You cannot transact in a foreign currency without a rate type and a rate. And you cannot assign a business unit without reference data sets. Now the cost of doing it late: skip geographies, load four hundred suppliers, watch the addresses fail, clean the data, reload. Two days lost to a two-hour task. There are four independent foundations here — geography, currency, reference data, and a preview of enterprise structure — and none of them depends on the others, so you can do them in any order you like. One more thing worth knowing before you start: this is the shortest configuration module in the course.

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.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 3 · Common Configuration

  1. 1Why this module comes first
  2. 2Geographies and address validation
  3. 3Building a geography hierarchy
  4. 4Currencies and conversion rate types
  5. 5Reference data sets
  6. 6Configuring reference data sets
  7. 7What breaks
  8. 8Lab: build the foundation layer
Why this module comes first — Implementing Cloud Financials: From Empty Pod to Go-Live — MSAMM