Business Logic Guidelines for Creating and
Migrating Infotypes
This section discusses important guidelines that apply to standard business logic in a de-coupled environment, and therefore relates to the creation of new Personnel Administration infotypes in this and every subsequent release. We recommend that you review these guidelines, as needed, whenever you execute the Create Infotype transaction (transaction code PM01) to create new Personnel Administration infotypes and compose the corresponding business logic.
The programming guidelines set forth below solely apply to standard Personnel Administration infotypes. Infotypes in other functional areas (for example, Time Management) are not affected.
At Release 4.6C and in prior releases, Personnel Administration infotypes were created in a previous framework, where the business logic was not de-coupled from the corresponding user interface. That framework remains operative in this and every subsequent release, meaning that customer-specific infotypes or individual infotype records that were created at Release 4.6C or below will continue to function in this release, or any release thereafter.
In the revised framework for creating infotypes, the business logic of any infotype is completely de-coupled from the corresponding user interface. To enhance master data consistency and improve performance, you may therefore wish to “migrate” existing infotypes from Release 4.6C and below (henceforth described as “prior releases”) into this release – that is, adjust the business logic of the infotypes that were created in the previous framework to make them compatible with the revised framework for the de-coupled environment.
To the extent that you wish to adjust the business logic of infotypes from prior releases, this section also discusses important information to consider and necessary actions to take whenever you migrate infotypes from prior releases into this release.
Although you
are not required to migrate infotypes from the previous framework, it is
important to note that infotypes that have not been migrated cannot be
processed by applications – for example,
HR Administrative
Services – introduced in the standard system after or in tandem with
the revised framework.
In summary, this section discusses the business logic guidelines that apply to the creation of new Personnel Administration infotypes, whether standard or customer-specific, in this (or any subsequent) release. This section also discusses the migration of existing infotypes from prior releases into this release.
To this end, this section is divided into the following five subsections:
● Assigning Check Classes to Containers and Infotype Versions
If you wish to follow the revised framework and create new Personnel Administration infotypes in this release, then we recommend that you observe the business logic guidelines set forth below, along with the corresponding UI Programming Guidelines for Infotypes.