Definition

The Requirements subprofile creates a relationship between the following objects and a requirement:

Use

The Requirements subprofile enables you to map the typical requirements of an object on the basis of the type of requirement and the degree of proficiency involved. The qualifications catalog is used to create this subprofile.

You can compare the requirements and qualifications of objects against each other and thus establish whether objects are suitable (for example, persons for positions) or whether qualification deficits exist. For more information, see Profile Matchups .

Your qualifications catalog must contain entries, otherwise you will not be able to create a Requirements subprofile. For further information about creating and changing the qualifications catalog, refer to the Implementation Guide (IMG) for Personnel Development under  Master Data Edit qualifications catalog.

Structure

You can assign any of the qualifications from the qualifications catalog to the subprofile of an object as a requirement (or use another requirements profile as a basis for this).

You can import requirements (qualifications) – that is, transfer them from one position to another position, for example, or from a person to a position.

The following table shows you how requirements are passed on (inherited) in the standard system:

You can go straight from a requirement to the profile of the object from which the requirement was inherited, and then display the inheritance hierarchy.

You can decide to what degree of proficiency a requirement is required by an object. The proficiency scale used is determined by the qualification group to which the qualification belongs.

You can decide whether a requirement is mandatory (essential requirement), or desirable (optional requirement). You can take this into account in career and succession planning (see User-Specific Settings ). This will mean that only objects with the qualifications that have been defined as essential requirements will be included in evaluations.

You can specify a validity period for every requirement.

You can enter comments (notes) for every requirement.

Integration

You can also define a Requirements subprofile for object types other than those for which standard settings have been made. For further information about defining profiles, refer to the Implementation Guide (IMG) for Personnel Development under  Functions Define profile view.

See also:

Creating a Profile

Creating a Requirements Subprofile for a Position: Example

Creating a Profile (Starting Out From the Structural Display for an Organizational Unit)

Displaying a Profile

Displaying a Profile (Starting Out From the Structural Display for an Organizational Unit)

Profile Matchups