Implementing Cloud Financials: From Empty Pod to Go-Live · Module 3 · Common Configuration
Lab: build the foundation layer
Lesson 28 of 153 · 1 min
About an hour, and every later module depends on it. Five deliverables. Geography structure and hierarchy configured for two countries. Address validation enabled, with a documented rationale for the level chosen. Three currencies enabled, one custom rate type created, and daily rates loaded for two pairs. One additional reference data set created, with a written justification of why it is needed. And evidence: a successfully validated address and a deliberately rejected one, screenshotted. Four acceptance criteria. Both countries have a populated hierarchy to at least city level. Validation demonstrably rejects a bad address. Daily rates are present for the current month. And the reference data set justification names a concrete business requirement. That last criterion is the one that fails submissions. "For flexibility" is not a requirement — and a set created for flexibility is maintenance you pay for every month without ever using.
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.