Associating a Regulatory Region with a Transaction

These topics provide an overview of regulatory regions and transactions and discuss how to:

Maintain regulatory regions.
Use regulatory regions for transaction processing.
Establish default regulatory regions.
Assess the impact on PeopleCode transaction processing.
Create prompt edit transaction views for REG_REGION.
Add REG_REGION to human resources transactions.

Regulatory Region is used as a control field on pages throughout your PeopleSoft Human Resources system. It is almost always a required field.

PeopleCode is used to associate the desired Regulatory Transaction type or view with the specific transactions that are processed on a page. Regulatory Region fields have an edit prompt off the transaction specific view. The view displays to a user only those countries that are available for that Regulatory Transaction type and for which the user has security access.

A system of standard defaults assists the user in selecting the appropriate regulatory region and transaction.

Note: Usually you can override the defaults to ensure that the proper regulatory region is assigned to a transaction.

The size and definition of a regulatory region can be smaller or larger than a country, varying by the transaction or application. However, the standard region is a Country Code.

You can create additional transaction or application views that display only the applicable regions for that transaction. Place the Regulatory Region field on that transaction record and define an edit prompt in the transaction-specific view. The view should display only those countries that are available to the user (either Available to All or With Global Security Only, joined with user Global Security). For example, the following table shows some regulatory regions that are already in the system:

Transaction Type	Reg Region (Char 10)	Description (Descr)	Country Code (Alt-Search)	Security Availability Status
Standard	BEL	Belgium	BEL	With Global Security Only
Health and Safety	BEL	Belgium	BEL
Standard	CAN	Canada	CAN	Available to All
Health and Safety	CANBC	Canada - British Columbia	CAN
Standard	DEU	Germany	DEU	Available to All
Standard	FRA	France	FRA	Not Available to Anyone
Standard	GBR	UK	GBR	With Global Security Only
Standard	JPN	Japan	JPN	Not Available to Anyone
Standard	NLD	Netherlands	NLD	Not Available to Anyone
Health and Safety	QC	Canada - Quebec	CAN
Standard	USA	United States	USA	Available to All

You can add regulatory regions for your own configuration. For example, you can add the 50 U.S. states and differentiate at that level for most transactions.

The system identifies the general regulatory region for a person by looking at the current effective Job Data record for each EmplID and employee record number combination.

For PeopleSoft Human Resources business process functions that need a different regulatory region for a transaction than is generally associated with a person, add Regulatory Region to that transaction. Use a Transaction view (normally STANDARD) from the Regulatory Region table to provide the appropriate prompt of Regulatory Regions for that transaction.

Once REG_REGION is in a page buffer, you can perform regional edits and set processing.

Note: Be sure to use the Country field (related display) of the region for all country specific edits to ensure that the user can go to a finer level of detail for other edits.

Regulatory Region is almost always a required field. The system establishes the default Regulatory Region in different ways, depending on the PeopleSoft Human Resources business process. You can always override these defaults. The following table lists the components that default a Regulatory Region value and the pages the value defaults from.

Component	Default regulatory region value from:
Position Data (POSITION_DATA)	Org Defaults by Permission Lst
Job Data (JOB_DATA)	Position Data (if the worker is assigned to a position) or Org Defaults by Permission Lst (if the worker is not assigned to a position)
Incident Details (HS_INCIDENT)	Org Defaults by Permission Lst
Disability (DISABILITY)	Job Data
Establishment (ESTABLISHMENT_DATA)	Org Defaults by Permission Lst
Job Openings (HRS_JOB_OPENING)	Position Data (if the job opening is assigned to a position) or Org Defaults by Permission Lst (if the job opening is not assigned to a position)

Most transactions involve the Regulatory Transaction type STANDARD. The system performs PeopleCode edits against the person's Regulatory Region in the Job Data component and establishes the appropriate transaction PeopleCode that the system should apply to page processes, based on the regulatory region that you enter.

Note: The Regulatory Region field is required on the Job Data pages. On the Job Data pages, you see only the STANDARD list of regulatory regions to which you have security access.

For Health and Safety transactions or incidents, the Regulatory Transaction type HANDS is used because it includes the Canadian provinces as regulatory regions. The Regulatory Region value on the Org Defaults by Permission Lst component appears by default on the Incident Data and Incident Reporting pages.

Because there are two types of transactions in PeopleSoft Human Resources (STANDARD for employee transactions and HANDS for Health and Safety transactions), there are two different prompt views for those transactions. When you add a transaction to your system, you include a new prompt view that can be built from the views that are included in the system.

REG_STANDARD_VW

SELECT

S.OPRID,

R.REG_REGION,

R.DESCR50,

R.COUNTRY

FROM PS_REG_REGION_TBL R,

      PS_REG_TRX_REGION  T,

      PSOPRDEFN S

WHERE T.REG_TRX = 'STANDARD'

AND T.REG_REGION =   R.REG_REGION

      AND (R.REG_AVAIL = 'ALL'

          OR (R.REG_AVAIL = 'GBL'

              AND S.OPRID = (SELECT OPRID FROM PS_SCRTY_TBL_GBL G

              WHERE S.OPRID = G.OPRID

              AND G.COUNTRY = R.COUNTRY)))

REG_HANDS_VW

SELECT

S.OPRID,

R.REG_REGION,

R.DESCR50,

R.COUNTRY

FROM PS_REG_REGION_TBL R,

      PS_REG_TRX_REGION  T,

      PSOPRDEFN S

WHERE T.REG_TRX = 'HANDS'

AND T.REG_REGION =   R.REG_REGION

      AND (R.REG_AVAIL = 'ALL'

          OR (R.REG_AVAIL = 'GBL'

              AND S.OPRID = (SELECT OPRID FROM PS_SCRTY_TBL_GBL G

              WHERE S.OPRID = G.OPRID

              AND G.COUNTRY = R.COUNTRY)))

Note: You can create new transaction views by doing a Save As and changing the hard-coded transaction name.

The following two examples show how to associate regulatory regions with human resources transactions:

Example - Job Data

To associate REG_REGION to a person on the Job Data pages:

Add the REG_REGION field to the record JOB.
Make the REG_REGION field a required field.
After adding the field to the record, define a prompt edit from the standard view (REG_STANDARD_VW).
Add this field to the page JOB_DATA1.

Now, when you prompt on the Regulatory Region, you see only those Regulatory Regions to which you have security access.

Example - Health and Safety

We associated Regulatory Region with incidents in Health and Safety. Regulatory Region is a required field that controls the values that are returned by all the Health and Safety setup pages that have Set ID as their primary key. For example, if the Regulatory Region for an incident is specified as GBR (United Kingdom), then only GBR codes for Dangerous Occurrences appear on the Incident Details - Description page (HS_INC_DESCRIPTION). Health and Safety incidents have REG_HANDS_VW as the prompt edit.

Warning! All linked setup values for an incident must belong to the same regulatory region. If the Regulatory Region is altered (such as when you are operating in update/display mode), and the Set ID for the new Regulatory Region is different from the original, all linked setup fields and values are deleted to prevent inconsistent data. For example, the Set ID for the Regulatory Region USA is USA, and for GBR it is GBR.. If the Regulatory Region for an already established USA incident is changed to GBR, then all of the linked details on the Incident Details pages are lost. The system prompts you that the Regulatory Region is about to be changed, and you can choose whether to proceed before the values are deleted or not.

In Health and Safety, the following Set IDs are mapped for each regulatory region, as shown:

Regulatory Region	Set ID
BEL	STD
CANAB	CAN
CANBC	CANBC
CANMB	CAN
CANNB	CAN
CANNF	CAN
CANNS	CAN
CANON	CAN
CANQC	CAN
CANSK	CAN
DEU	DEU
FRA	FRA
GBR	GBR
JPN	STD
NLD	STD
USA	USA

These regulatory regions were mapped to these Set IDs on the TableSet Control − Record Group page (SET_CNTRL_TABLE1).

All regulatory regions that have region-specific sets of codes or values in the Health and Safety system are mapped to a Set ID of the same name. This group includes CANBC, DEU, FRA, GBR, and USA.

The other regulatory regions that aren't mapped to a Set ID of the same name fall into two additional categories. Except for British Columbia, the Canadian provinces have no specific provincial codes or values in the system and are mapped to the Set ID CAN.

All the other countries that are supported directly in PeopleSoft Human Resources and that don't have any region specific codes or values in the system are mapped to a generic Set ID value of STD. This group includes JPN, BEL, and NLD.