Determining the Validity Period of a Personal Computer Plan

Purpose

This document refers only to the SAP-recommended process of implementing a personal computer plan (PC plan) as a separate event using an adjustment reason.

Critically, when implementing a PC plan in Flexible Benefits for Great Britain (GB FlexBens), you must also determine the validity period of this plan. The documentation below outlines in greater detail your possible options for setting this validity period, including SAP recommendations for the process.

For the non-recommended implementation method for PC plans, you set the validity period for each of your miscellaneous plans (including the PC plan) in months, in the Benefits Administration IMG step, under:

Start of the navigation path Plans Next navigation step MiscellaneousPlans Define Flexible Benefits Miscellaneous Plan Attributes (FLEX) End of the navigation path

Prerequisites

In the GB FlexBens system, you must have previously:

Set up a PC plan in Customising

See: Activities , under Personal Computer

Created a personal computer adjustment reason to allow eligible employees to enrol in your PC plan

See: Implementing a GB FlexBens Personal Computer Plan

Process Flow

In theory, once the dates of your personal computer adjustment reason have been assigned, the validity period of the active PC plan can be any combination of the following begin and end dates within the GB FlexBens system :

	Begin date		End date
A	Adjustment Reason Date: The system takes the begin date of the adjustment reason as the start date for the employee enrolment records. This applies to records created during processing, for employees who have an adjustment reason of this type.	D	Default Date: This indicates that the default end date is used for all employee enrolments created during adjustment reason processing. This date is originally defined in Customizing, under: BenefitsAdministration FlexibleAdministration Define Administrative Parameters .
B	Date of Offer: The system takes the date adjustment reasons that are processed by the HR Benefits Administrator as the start date for the employee enrolment records. This applies to records created during adjustment reason processing, for employees who have an adjustment reason of this type.This is also technically known as the 'system date'.	E	End of Time: This indicates that the system ‘high-date’ (31/12/9999) is used as the end date for all employee enrolments created during adjustment reason processing, for employees who experienced an adjustment reason of this type.
C	Other Date: Begin date of employee enrolments created during adjustment reason processing for this adjustment reason type. This is configurable.	F	Other Date: This is the end date of employee enrolments created during adjustment reason processing for this adjustment reason type. It overrides the default date above. This date is configurable.

Begin date

End date

Adjustment Reason Date:

The system takes the begin date of the adjustment reason as the start date for the employee enrolment records. This applies to records created during processing, for employees who have an adjustment reason of this type.

Default Date:

This indicates that the default end date is used for all employee enrolments created during adjustment reason processing. This date is originally defined in Customizing, under: Start of the navigation path BenefitsAdministration Next navigation step FlexibleAdministration Define Administrative Parameters End of the navigation path .

Date of Offer:

The system takes the date adjustment reasons that are processed by the HR Benefits Administrator as the start date for the employee enrolment records. This applies to records created during adjustment reason processing, for employees who have an adjustment reason of this type.This is also technically known as the 'system date'.

End of Time:

This indicates that the system ‘high-date’ (31/12/9999) is used as the end date for all employee enrolments created during adjustment reason processing, for employees who experienced an adjustment reason of this type.

Other Date:

Begin date of employee enrolments created during adjustment reason processing for this adjustment reason type. This is configurable.

Other Date:

This is the end date of employee enrolments created during adjustment reason processing for this adjustment reason type. It overrides the default date above. This date is configurable.

Based on the date options contained in the above table, nine possibilities exist for setting the validity period of your PC plan. These are described below, using the example of an employee assigned a PC adjustment reason from May 1 2003 to May 31 2003 . The current system date is May 8 2003 :

A-D:

One of the administrative parameters configured in the IMG step Define Administrative Parameters is defaulted to December 31 2004 (Note: there is only one date setting for one benefit area). Therefore, after the employee enrols in a PC plan, the active PC plan validity period will be from May 1 2003 to December 31 2004 .

A-E:

After the employee enrols in a PC plan, the active PC plan validity period will be from May 1 2003 to December 31 9999 .

A-F:

The configurable end date (there is only one date setting for one adjustment reason) is assumed to December 31 2005 . Therefore, after the employee enrols in a PC plan, the active PC plan validity period will be from May 1 2003 to December 31 2005 .

B-D:

One of the administrative parameters configured in the IMG step Define Administrative Parameters is defaulted to December 31 2004 (Note: There is only one date setting for one benefit area). Therefore, after the employee enrols in a PC plan, the active PC plan validity period will be from May 8 2003 to December 31 2004 .

B-E:

After the employee enrols in a PC plan, the active PC plan validity period will be from May 8 2003 to December 31 9999 .

B-F:

The configurable end date (there is only one date setting for one adjustment reason) is assumed to be December 31 2005 . Therefore, after the employee enrols in a PC plan, the active PC plan validity period will be from May 8 2003 to December 31 2005 .

C-D:

The configurable begin date (there is only one date setting for one adjustment reason) is assumed as April 1 2004 . In addition, one of the administrative parameters configured in the IMG step Define Administrative Parameters is defaulted to 31/12/2004 . (There is only one date setting for one benefit area). Therefore, after the employee enrols in a PC plan, the active PC plan validity period will be from April 1 2004 to December 31 2004 .

C-E:

The configurable begin date (there is only one date setting for one adjustment reason) is assumed as April 1 2004 . In addition, one of the administrative parameters is defaulted to 31/12/2004 . (There is only one date setting for one benefit area). Therefore, after the employee enrols in a PC plan, the active PC plan validity period will be from April 1 2004 to December 31 9999 .

C-F:

The configurable begin date and end dates (there is only one date setting for one adjustment reason) are assumed as April 1 2004 and December 31 2005 , respectively. In addition, one of the administrative parameters is defaulted to December 31 2004 . (There is only one date setting for one benefit area). Therefore, after the employee enrols in a PC plan, the active PC plan validity period will be from April 1 2004 to December 31 2005 .

SAP strongly recommends the combinations of A-F , B-F , or C-F for implementation of PC plans. Implementing the C-F combination, in particular, will reduce the workload for your Benefits Administrator when assigning personal computer adjustment reasons to employees and adjusting date parameter settings.

Result

You have determined your required begin and end dates for the validity period of your personal computer plan within the GB FlexBens system .