Termination Action and Reason Mapping to Service History End Reasons

This task applies to monthly interface reporting only; it does not affect cutover.

Whether you use only actions, or a combination of actions and reasons for terminations or the ending of an assignment or employment terms, you must map them to service history end reasons to trigger the appropriate ended service history records and report the correct MyCSP code.

There must be a one-to-one relationship between the action (or action and action reason combination) and a MyCSP End Reason, otherwise the service history record will not contain an end reason code.

Note: Action reasons are not mandatory in the UI. If you decide to use action reasons, you must ensure you select a reason when you terminate an employee.

1. Use the Extended Lookup Codes task to create the mapping.
2. Click Add and select the CSP Action and Reason Mapping in the Lookup Types list.
3. Complete one row for each action (or action and reason combination).

   Action and Reason Extended Lookup Mapping

   FIELD	DESCRIPTION
   Country	United Kingdom
   Lookup Code	CSP action and reason mapping (the only value available)
   Extended Code	User-defined code. Not reported in the Service History file. You could use the leaving reason code to identify which row maps to the leaving reason selected in the flexfield context. For example, if you are mapping to leaving reason 25 in the DDF, you could enter 25 here.
   Extended Name	User-defined name. Not reported in the Service History file. You could use the action or action reason to identify which row maps to the leaving reason selected in the flexfield context. For example, if you are mapping action reason “Dismissed for Gross Misconduct”, you could enter something similar here.
   All Enterprises	No

4. Select the UK MyCSP Action and Reason Reporting Mapping context in Additional Information.
5. Select a termination or end assignment/end employment terms action (or an action and action reason combination) and the MyCSP code against which it should be reported:
6. If you use an action without a reason when terminating employees or ending assignments or employment terms, select only the action and CSP End Reason. If you use action reasons, you must select both the action and the reason with which it is associated in your setup.

Note: The Action and Action Reason fields list all available actions and reasons, not just those that you have configured. You must use the Action Reasons task to associate an action with a reason in addition to selecting it here.

In the above example, the user has configured termination and end assignment/employment term actions to use action reasons. Their action reason Dismissal for gross misconduct will be reported with code 25, as shown in the CSP End Reason field.

Note: The code description in the field is provided for information only; it is not reported.

You can map multiple actions (or action reasons) by creating one row for each and selecting the appropriate MyCSP end reason code in Additional Information.