You can combine the two logical views of infotype data, the join and the projection.

We read the data from several infotypes and create new partial periods. We select the infotype fields that are important for the evaluation and combine these partial periods again.

The following example illustrates this.
An employee works as a programmer in the current year and marries in May. Her name does not change.

Organizational assignment:

Personal data:

When the data from both infotypes is read concurrently, the result is:

Since we can disregard her marital status in the evaluation, we project on her first and last names:

The following report exemplifies the above case:

REPORT RPDEMO04.
TABLES: PERNR.
INFOTYPES:  0001,
            0002.
GET PERNR.
  PROVIDE STELL FROM P0001
    NACHN VORNA FROM P0002
    BETWEEN PN-BEGDA AND PN-ENDDA
    IF P0001_VALID = 'X'.
      WRITE:  / P0002-NACHN, P0002-VORNA,
                P0001-BEGDA DD/MM/YYYY,
                P0001-ENDDA DD/MM/YYYY,
                P0001-STELL.
    ENDIF.
  ENDPROVIDE.

This report combines the associated validity periods and provides the data of relevant infotype fields for a specific period.

Provision of data for a specific partial period is especially important for partial period factoring in payroll.

If an employee's basic pay or the cost distribution changes during the payroll period, you must calculate the salary proportionately for the resulting partial periods.

However, if the payroll administrator of the organizational unit changes, this has no effect on payroll.

By linking a join and a projection, you can read the master data for a specific partial period.