Copyright 2024 - BV TallVision IT

The data that should be interfaced is to be selected. This is a task for the data factory classes of the interface and - due to the re-useable nature of the setup - the selection should be fully controlled by selection screen parameters and select-options. 

PA - Personnel Administration

Logical database PNP plays a very important role here: for the PA (Personell Administration) information that is on the database virtually all of is is available via logical database PNP. A great opportunity to utilize what is probably the largest logical database available, for our HR interface. The interface supports over 20 infotypes and more can be added where required. All the lcl_Data_Employee class needs to do is absorb the information on the new infotype in it's internal (employee-specific) storage, which makes it available for the lcl_Selectnnnn classes.

Cluster data

The system also provides in "cluster data", including time schedules, clocked hours and much much more. Cluster data can be made available in the interface as well. The interface taps into this information via a call to HR_FORMS_TIM_GET_B2_RESULTS for the date-range that can be specified on the selection screen. Over 30 sets of data (read: tables) are available from this module.

Organization data

For organizational data there is another module that can be utilized in the interface. Organization data can be accessed through evaluation paths which define whether you are looking for the boss of an organization or the overall structure of all organizations (HR_STRUCTURE_GET.

The selection screen - define the selection

As it is not likely you need all of the information on the system to be interfaced, the selection screen of the interface needs to be carefully populated. The overall output of the interface does not need to be composed in a single run.

Like with any interface, it is also possible to apply a lot more selection logic embedded into the data factory classes - but this also implies taking away controls from the user effectively damaging the versatile mapping setup.

Then there is this: the interface supports PA data and non-PA data. The non-PA data will only be selected if needed, so a checkbox is available in each block of non-PA data relates parameter or select option settings. The checkbox can be used to indicate the interface won't need e.g. Cost center settings. When more selection and thus selection blocks are added, it is good to realize they can be switched on and off individually.