Processing a Request for Personnel Action (RPA)

The process for completing an RPA follows the steps you usually take when processing the paper version.

If your role is an initiator, you create an RPA; otherwise you respond to an RPA routed to you. You enter the information required by your role on the RPA and when you have entered that information, you route the RPA to the Human Resource Office for regulatory data and signatures. When the action has been approved by the Personnelist and the record updated, you can print the Notification of Personnel Action, send a copy to the employee, and file it in the employee's Official Personnel Folder.

Use the Request for Personnel Action window.

arrow icon   To complete a Request for Personnel Action (RPA):

  1. If you are an Initiator, select a Nature of Action (NOA) family from the Navigator.

    The application enters the name of the NOA family in the Action Requested field and shows you which fields to enter for that NOA family. If there is only one Nature of Action code for the family, such as Change in FEGLI, the application enters the Action Requested and NOA code and description.

    Note: If you are not an Initiator, open your Workflow worklist, and open an RPA routed to you or your groupbox, as described in Querying Notifications from Your Worklist.

  2. Choose a routing group, if necessary.

    When you initiate an RPA, the application uses the default routing group to which you belong. If you want to route the RPA using a different routing group, choose the Routing Group icon (located on the upper left corner of the form), and select a different routing group from the Routing Groups list.

    Warning: You cannot change the Routing Group after you have saved the RPA to your personal worklist or routed it to the next destination.

  3. Select a person by entering his or her last name or social security number. (The application does not allow you to select your own name.)

    As a shortcut, you can choose the person's name from the List of Values. Last names are listed alphabetically and by case so that, for example, the last name 'Young' precedes the last name 'de Rosa.'

    The application lists any pending actions it finds for the user. Pending actions include current and future actions that haven't been updated to the database.

  4. Complete the fields appropriate to the personnel action that you are processing.

    Many of the fields have Lists of Values that you can choose to quickly complete the required data. If the field requires information, such as Remarks, the application displays an insertion dialog prompting you for information. Enter the requested information.

    Note: Until you enter an effective date, the application date determines the information the application populates on the RPA form and the values displayed on the List of Values.

  5. Use the tabs to navigate to the other RPA pages. Complete the information requested in each window.

    Note: At any time, you can save the RPA to your Workflow worklist and complete it later.

  6. Click the Extra Information button to save the information you have entered so far and to enter the additional data that accompanies the RPA.

    Note: If you navigate to the Position or People window to change the extra information, before you begin entering data, confirm that the effective date corresponds to the action's effective date. If necessary, reset the date. See: Extra Information and the RPA.

  7. If you are assigned the role of Requester or Authorizer, enter your signature in Part A of the RPA by choosing your name from the List of Values.

  8. When you are done, save the RPA, and when presented with the choice of routing the RPA, choose Yes.

    The RPA dialog presents you with the options to save the RPA to your workflow worklist. You can indicate your interim approval and continue routing the RPA to a person, groupbox, or routing list.

  9. If you are assigned the role of Approver, you can choose the Approval box on the Routing dialog box.

    The printed Notification of Personnel Action (SF50) includes the name, working title, and approval date of the Approver who last approved the action.

  10. Update the RPA to the database.

    Approvers can update the RPA to the HR database, or route the RPA to the person responsible for updating RPAs.

    See: Signing, Approving, and Updating an RPA

  11. To have the application print the Notification of Personnel Action (SF50) when it updates the RPA, choose Print Notification from the Routing dialog box.

    The option to Print the Notification of Personnel Action is only available after you submit the action for update to HR. See: Printing the Notification of Personnel Action