Creating Country-Specific Check Classes

Procedure

As you create country-specific check classes, remember the following two rules of thumb:

In general, the country-specific version of any infotype tends to store and process data – in other words, “behave” – in a manner that is similar to the international version of that infotype.
Views are considered to represent particular examples of country-specific check classes.

As the logical result of these rules of thumb, country-specific check classes inherit the properties of the international check class, which in turn inherits its properties from check class CL_HRPA_INFOTYPE_NNNN .

Example Example

Check class CL_HRPA_INFOTYPE_0011 is assigned to the External Transfers infotype (0011). Check class CL_HRPA_INFOTYPE_NNNN is defined as the superclass for this check class. Because of this definition, check class CL_HRPA_INFOTYPE_0011 inherits its properties from check class CL_HRPA_INFOTYPE_NNNN .

Check class CL_HRPA_INFOTYPE_0011 , in turn, is defined as the superclass for five country-specific check classes, as demonstrated below:

CL_HRPA_INFOTYPE_ NNNN
- CL_HRPA_INFOTYPE_ 0011
  - CL_HRPA_INFOTYPE_0011_ BE
  - CL_HRPA_INFOTYPE_0011_ CH
  - CL_HRPA_INFOTYPE_0011_ NO
  - CL_HRPA_INFOTYPE_0011_ NZ
  - CL_HRPA_INFOTYPE_0011_ ZA

If you want country-specific infotypes to be able to inherit the check class of the international version, then you must not the select the Final checkbox (VSEOCLASS-CLSFINAL) while you define the attributes of the international check class.

End of the example.

To simplify the creation (or migration) of infotypes in(to) this release, we recommend that you design the methods of the new check class such that the specific classes of country-specific infotypes can be easily derived. Thus, if you are responsible for the international version of an infotype, refer to Implementing Checks and subsequent topics for a detailed overview of the technical issues at hand. Moreover, you may wish to review country-specific versions of other infotypes to familiarize yourself with concrete examples of these technical issues. Finally, whenever you are working with international check classes, we recommend that you thoroughly search all entries in the views Assignment of Infotypes to Views (V_T582V) and Assigns Infotype View to Primary Infotype (V_T582W) to ensure that unknown infotype views do not interfere with your work.

To summarize, you should use care when performing the creation (or migration) of check classes for infotypes with several country versions, lest errors subsequently arise in the country-specific versions of the infotypes.