Customers with numerous subsidiaries and installations often want to establish an SAP system landscape based upon a common standardized core, otherwise known as a global template, which reflects all of the R/3 settings and data that are specific to a corporate entity. Descriptions of common company processes, instructions regarding how (and how often) subsidiaries should implement (and update) the template, transport files, customizing settings, test descriptions, and test plans are all fair game for a global template. Some of these elements address the methodology that must be adhered to by subsidiaries as the corporate headquarters location rolls out the template, and some, particularly the customizing and testing elements, are about concrete R/3 settings and data. It’s this latter category of elements — the ones that require you to capture specific customizing settings and then, through proper testing, ensure that they can be properly invoked at subsidiary locations — that I will address in this article. Even if you are not undertaking a global rollout, this article provides valuable information that can be applied in other customizing contexts.