Implementing Cloud Financials: From Empty Pod to Go-Live · Module 3 · Common Configuration
What breaks
Lesson 27 of 153 · 2 min
Five failures, each with a cause and a prevention. Four hundred of five hundred supplier addresses rejected on load. Geography validation is enabled at a level the legacy data does not populate. Clean the data or relax the validation. Prevention: run a sample load of twenty records before the full load. Always. Foreign currency invoice will not validate. No daily rate for that date and rate type. Prevention: an automated rate load. Payment terms do not appear for the new business unit. The business unit is assigned to a set that does not contain them. Prevention: a set strategy decided in design, not discovered in testing. Tax jurisdiction will not determine. The geography hierarchy is incomplete below state level. Prevention: a geography completeness check before tax configuration. We need to add a city level after go-live. A structural change to a country that already has live addresses, and it is…
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.