GB FlexBens: Mass Generation of Adjustment Reason (RPUFBNADJRSN) Report
GB FlexBens: Mass Generation of Adjustment Reasons
is an extension of the
International Benefits
report
Mass Generation of Adjustment Reasons
(RPUBENADJRSN). Compared with RPUBENADJRSN, this report also mass generates adjustment reasons for a group of employees, but it also incorporates a special plan check.
The report checks for any selected employees who have an active plan of the specified plan type within the specified period. For these employees, an adjustment reason will not be generated. This check therefore provides a convenient tool for Benefits Administrators to control adjustment reason generation.
The adjustment reasons generated by report RPUFBNADJRSN are pre-configured in the SAP system.
You perform adjustment reason configuration in the
Benefits Administration
IMG, under:
Benefits Adjustment Reasons
.
You specify a begin date for the adjustment reason on the report RPUFBNADJRSN selection screen. This date can be either a system date (
Today
) or a user-specified date (
Key Date
).
You can also run the report for a group of employees by entering one of the following:
You must also specify the specific adjustment reason that needs to be generated.
Benefits Plan Check
If you want to perform a plan check for the adjustment reason generation, select the pushbutton
With Plan Check
. The group box
Plan Check
is now generated. In this group box, specify the plan type and checking period in the relevant fields.
The report will now also check for employees who have are enroled in an active benefit plan of the type you specified, within your selected checking period. For each employee identified by this check, no adjustment reason will be generated.
On execution from the selection screen, report RPUFBNADJRSN outputs a tree structure view that lists all employees within your selection criteria. Employees are displayed as follows on the output screen:
Activities, below.
There are also a further three groups of employees in the tree structure, for whom the generation of adjustment reasons is not possible:
Status.
Further information is also given in the column
Comment
. These employees are excluded from the mass generation of your specified adjustment reason.
Status. Specific infotype information is also displayed in the column
Comment, for these employees.

Because the report performs an infotype operation, any employee locked by another master data transaction cannot be included in the current report run.
On the selection screen for report RPUFBNADJRSN:
Key dategroup box.

The end date of the adjustment reason is calculated by configuration of the adjustment reason, in the IMG (see
Prerequisites
, above).
With Plan Check.
The group box
Plan Check
is now generated.
Plan Check, specify the plan type and checking period in the relevant fields.
The output screen
Mass Generation of Adjustment Reasons
is now displayed.
Create Adjustment Reasonpushbutton.
Adjustment Reasons for the employees you selected in Step 7 are now created [an infotype
Adjustment Reasons
(0378) record].
Example 1: Private Medical Insurance Plan
[Mass generation of adjustment reason without plan check]
For employees who experience a life event (for example, newborn baby) in a given month, you:
New Baby, and assign the Private Medical Insurance Plan to this adjustment reason.
Example2: Personal Computer (PC) Plan
[Mass generation of adjustment reason with plan check]
Your organisation administers a Flexible Benefits scheme, with a benefits year running from 01 January to 31 December. Open enrolment for the forthcoming benefits year is between 01 and 31 December in the previous year. You offer a three-year PC Plan to your employees, who mustenrolthe plan outside of the open (annual) enrolment period, using a PC Plan adjustment reason assigned to them.
You also are required by your PC plan provider to submit your lists of newly-enroled employees only on a quarterly basis.
In order to administer the PC Plan for the first quarter of the new benefits year, you carry out the following:
Activities) to create PC Plan adjustment reasons for your selected employees.
During the generation of the adjustment reasons, the system checks for any employees already enroled in the PC Plan. For these employees, no adjustment reason is generated.
Employees can now enrol in the PC Plan using Employee Self Service, until 12 March.
Provider Report For Flexible Benefits(RPUFBN71) on 14 March.
This produces a listing of newly-enroled employees in the PC Plan for the first quarter of the current benefits year.
The PC Plan provider supplies PCs to the specified employees by 01 April, the date when the PC Plan becomes effective.

The effective dates for this PC plan will be 01.04.XXXX to 31.03.XXXX+3, where XXXX denotes the current benefits year.
You can set your own start date for
Flexible Benefits
Plans in this situation, as follows:
For Health and Insurance Plans: Use the
International Benefits
User Exit
PBEN0022
For Miscellaneous Plans (including PC Plans): Use the Flexible Benefits Business Add-In PFBN0004.

Increasing numbers of benefits providers are requiring organisations to submit PC requests only on a quarterly basis. Therefore, it is likely that you will need to create PC Plan adjustment reasons and run report RPUFBNADJRSN on a quarterly basis, with timeframes similar to those given for the first quarter of the benefits year in Example 2.