X hits on this document





32 / 190

The Student Lifecycle Management system creates the HR object

(object type ST) and an SAP

business partner for each student. When you create a student, the system assigns him/her the following business partner roles:

  • Student

  • Contract partner

The term studies there.

is the superordinate term for all persons who apply to the university and pursue their

Student Lifecycle Management uses the following identifiers for students: Object ID Student number

  • Business partner number

Depending on customer requirements, the student number and business partner number may be identical. In configurations like this, you must be aware of the fact that the two number ranges may overlap.

Subsequent changes in number range settings can lead to data inconsistencies.

Changes in number range settings for the object ID have a negative effect on other components that use HR objects (Organizational Management, Personnel Development).

Changes in the number range settings for business partner numbers have a negative effect on other components that use business partners (Financial Accounting).

You can display the three identifiers of a student in the student file or in student master data. To do so,

choose a student and then choose


The object ID is the technical key for the object

(ST): It has the following attributes:

8-digit numeric key Key field in database tables for the object The system does not display the object ID in Student Lifecycle Management dialog transactions. When you create a student using a dialog transaction, the system supports only internal object ID

assignment for the object type


  • The object ID cannot be changed once it is assigned.

  • Students can only be created for the active plan version.

We recommend that you use a numbering system for Student Lifecycle Management which is valid for all plan versions. As this Customizing setting applies to all HR object types, you first must make sure that all departments that use HR object types have agreed to this setting. These include the components

, You should use object type-specific numbering for the object type ,

, etc. (ST), if possible.

© 2009 SAP AG

| sdn.sap.com

| bpx.sap.com 32

Document info
Document views604
Page views626
Page last viewedWed Jan 18 15:02:19 UTC 2017