
The Personnel Planning Infotype Copier
Definition
The Personnel Planning Infotype Copier (Transaction PPCI)
For more information on the infotype copier, see
Creating Field Infotypes Creating Table Infotypes Creating Transparent Tables Enhancing Infotypes Generating Infotypes: Environment CheckUse

To use the infotype copier, you must be able to program in ABAP, be familiar with the ABAP Dictionary, the ABAP Screen Painter and the ABAP Menu Painter.
The Personnel Planning infotype copier allows you to create customer specific infotypes and transparent tables for existing customer infotypes.
You can create the following kinds of infotypes:
You can also specify whether an infotype is country-specific or not.
You should create your infotypes using only the transaction described here since this enables you to check that the Repository objects and table entries required for the infotypes exist. This check is carried out using the function
Check EnvironmentStructure

In this release, the infotype copier does not support development classes with name space prefixes.
Starting from an DDIC-structure created by the customer, the infotype copier creates all of the Repository objects necessary for an infotype, module pools, IDOC segments or dialog modules for example. These new objects are copied from existing objects and then modified according to the developer’s requirements. In addition, the infotype copier creates the required entries in the following tables:
T777T (Infotype texts)
T778T (Infotypes)
Once the infotype has been created, the user must add an entry to table T777I (Infotypes per object type).
This is done using the function
Check environment.

Creating infotypes with name range enhancement:
Note the following information when creating infotypes with name range enhancement and proceed as follows:
If you are creating an infotype with a name range enhancement (/Company 1/9000, for example), make sure that your entries are overwritten by those of another imported infotype with name range enhancement (Partner 1/9000, for example), if the infotype number of the imported infotype is the same as your infotype. For this reason, make sure before you import infotypes with name range enhancements that there are no conflicts between the infotype numbers available and those that are to be imported.