Establishing Regulatory Regions

While the system is delivered with defined regulatory regions, you might want to add new regulatory regions if you have operations in additional countries. Or you might want to create additional regulatory regions that correspond to regions within countries, such as states or provinces, that impact the way your company does business. For example, you might want to set up regulatory regions for each state in the United States, if you thought that significant regulatory codes or data definitions would vary from state to state. Use the Regulatory Region page to establish these additional regulatory regions.

Note: You don't have to create new regulatory regions. You create new regulatory regions only if there is a special need, perhaps to accommodate specific local regulations. You do have to use the existing regulatory regions that are already in the system. If you have operations in only one country, and you want to limit the impact of Regulatory Region on your data entry users, then you can assign your one region as the default region in the Org Defaults by Permission Lst component (OPR_DEF_TBL_HR).

Note: Although the scope of a regulatory region can be smaller than a country, PeopleSoft recommends that the standard Regulatory Region be at the country level.

To simplify matters and provide consistency, we recommend that you use the following naming standard when creating new regulatory regions:

For new country-level regulatory regions, use the 3-character, ISO-certified country code found in the Country Table component (COUNTRY_TABLE).
For regions that are smaller than a country, use the 3-character country code and concatenate a 2-character unique regional identifier. For example, use CCCSS for state-level or province-level regions, where CCC is the country code and SS is the state or province code. Using this system, the regulatory region code for Canada - British Columbia is CANBC.