Maintain Personnel Actions

In this step, you make the system settings necessary for setting up a personnel action.

A personnel action is a collection of several logically connected infotypes in the system which, in an exact sequence, are used for processing and are used for a particular system activity (see "Create Organizational Unit", for example).

Personnel actions are identified by a key.

You assign the following to each step of a personnel action:

a plan version

an object type

an infotype or subtype

a status

default values for screen entry

You also control, which Function codes are used by an infotype (within a personnel action).

In a transaction controlled by a personnel action (PQ**) , you must determine the object types for which the action is to be executed. For each transaction related to an object type and controlled by a personnel action, specify which default personnel action(PQ**M) is to be processed by the corresponding transaction.

For each default personnel action within a transaction controlled by personnel actions, you can access a Process description.

Example

Personnel action "Create organizational unit":

Personnel action	Plan ver.	ObjType	Infotype	Subtype	FCode	VarField
O	**	O	1000			INSE
O	**	O	1002	0001	INSE
O	**	O	1003			INSE
O	**	O	1001	A011	INSE	K

The personnel action "Create organizational unit" includes the following steps:

Creating the "Object" infotype (1000)

Creating the "Description" infotype (1002) with the "General Description" subtype (0001)

Creating the "Department/Staff" infotype (1003)

Creating the "Relationship" infotype (1001) with the "Cost Center Assignment" subtype (A011) for object type "K" (Cost Center).

Activities

Create the required personnel actions.

For each personnel action, determine the following:

Corresponding object type

Required infotypes and subtypes

Function code (INSERT, COPY)

The plan versions for which the personnel action is to be valid

The planning status in which the objects are to be created.

Entering default values is optional.

Enter the object type that is to be processed as well as the key of the personnel action for the transaction to be controlled by a personnel action.

Further Notes

Ensure that you arrange infotypes in a logical order when defining a personnel action. The "Object" infotype must always be processed first and must have line number "001".

A personnel action may only be defined for one object type.

You can create three-digit personnel actions between "001" and "999".