This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 . It is not the current version, and thus it cannot be edited.

Back to current versionRestore this version

Frequently Asked Questions - Personnel Actions#

Personnel Action FAQ’s#

This section contains the most frequently asked questions and answers related to Personnel Actions.

Q: Where are PA’s generated from?#

A: Personnel Actions are automatically created when changes are made in Self Service in certain client specified Functions.

Q: What Functions can generate PA’s?#

A: PA’s may be used in any functions that allow updates that use any combination of the following tables:

• DDS - Distributions
• EAL - Aliases
• EAS - Assignment
• EASD - Assignment Details
• EEM - Employments
• EID - Identities
• EMT - Military Data
• EPS - Personal Information
• EPP - Property
• EST - Statistics
• PPRC - CDN Pay Rules
• PPRD - Payment Rule Details
• SPMU - Premium Usages

Q: How are PA Types created?#

A: PA Types are manually created in the ISPY form.

Q: How are PA Types maintained?#

A: All appropriate fields and tables are added manually, so if the client sets it up correctly the first time, there should be little reason to maintain the PA Type after that. In the previous methodology, the PA Type evolved as new types of changes were made, currently ‘PA Types’ are static until the client chooses to update it.

Q: How do clients specify which Functions generate PA’s?#

A: There is a new field on the IMFN form called PA Type that has a list of values containing all PA Types that have been defined. It is recommended that the PA Type names include the name of the function, e.g. the PA Type for WEEPP should be PA_WEEPP so that only appropriate ones are chosen.

Q: What columns appear on Change Requests?#

A: This is managed on the ISPY form through the PA Column specifications.

Q: How are PA’s processed?#

A: PA’s can be processed (i.e. finalized in the database) by the final Approver using the Process PA action or via the USPPA batch process. USPA is required to be run for any back-end type PA’s such as USEP, USMC, etc.
USPPA is required for all Java created PA’s through forms such as ISPA, SS forms, etc.

Q: Can PA’s be processed individually?#

A: Yes, by the final Approver.

Q: Can PA’s be processed in mass?#

A: Yes, using the USPPA batch process.

Q: Can the PA effective date be changed after a PA has been approved?#

A: Yes, through the ISPA screen.

Q: Do all changes on a Function trigger a PA?#

A: No. The PA Type definition can be selective with which Tables are used. For example, on WEEPP there are 2 tables: EID and EPS. If a table is not included in the PA Type, changes to columns on that table will not generate the PA. However, removing individual columns from the table listed under the PA Type will cause errors.

Q: Are all columns automatically added to tables included in a PA Type?#

A: Yes. All columns are added as soon as the table is added to a PA Type.

Q: What if someone else makes a change to a record that has a PA?#

A: When the PA Type defined on ISPY has the Track Changes toggled on, changes made to a PA of that type by a User other than the Originator will have a copy of the PA made before the changes are applied. The copy will be associated with the original PA. PA copies will have PA numbers starting at -1 and decreased by 1 for each copy.

The PA Status on copies use a new lexicon value “95-Tracked Copy”. Tracked copies are not subject to approval. ISPA has new fields added to view the tracked copies - Logged From PA # and Logged By.

Q: Can notes/comments be added to PA’s?#

A: Yes, through the User Notes facility.

Q: Are User Fields included for use with PA’s?#

A: User fields work similar to standard table columns. They are automatically included on PA's generated from screens that have an associated PA Type.

When a PA Type is created in ISPY, for each table selected, all of its user fields appear at the bottom of the table column list with the User Field indicator toggled on. These user fields are eligible to be tracked on PA’s just like any other field on the table.

If a new user field is created, the columns on ISPY for that PA Type must be refreshed.

Q: Is the PA Allowed toggle still used on Execution Rights?#

A: No.