Implementing Cloud Financials: From Empty Pod to Go-Live · Module 3 · Common Configuration
Reference data sets
Lesson 25 of 153 · 2 min
Some setup data should be shared across the whole enterprise, and some should differ by business unit. Payment terms might be global; transaction types might be country-specific. Sets are the mechanism. Set-enabled objects are the list of what can be partitioned this way — the finance-relevant ones being payment terms, transaction types, memo lines, receivables activities and others. The common set is delivered, shared and the default, and most clients over-use it, which is usually fine. Determinant type is how the application decides which set applies to a transaction, usually via the business unit. Then four rules, which are the part worth paying for. Start with everything in the common set. Create a separate set only when you have a concrete, stated reason. A country with different statutory requirements is a reason. "It feels tidier" is not. Every extra set multiplies your maintenance: a new payment term is now created…
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.