Change Validation
The following graphic shows at which point the change validation takes place in the Interface Toolbox:
Use
Most of the data exported to a third-party system using the Interface Toolbox does not change in every payroll period . For example, an employee’s personal details (name, first name, personnel number, and so on) rarely differ from one period to the next.
If the Interface Toolbox transfers all data for a payroll period for every data export, the following disadvantages arise:
Increased redundancy of exported data (larger volume of data)
Increased transfer load during the data export
Increased processing
The receiver must process all transferred information as it is not possible to determine in advance whether or not the information has changed during the payroll periods.
High probability of errors made by the Interface Toolbox during data export and during the processing of the information by the receiver
It is therefore a good idea to only export data that has changed since the last data export. The third-party system can use the data that has not changed since the last data export again since this data already meets your requirements. Only changes to the data must be transferred to the third-party system for further processing.
The
Change Validation
function allows you to avoid exporting unchanged data.
Prerequisites
You have created an Interface Format and can only call the objects assigned to the Interface Format for
change validation
. The objects for
change validation
include:
Table objects (internal tables, field strings, and infotypes)
Note
For more information on the interface format and objects, see
Interface Format
.
Scope of Function
To deal with this problem, the Interface Toolbox has a
change validation
function with a wide range of functions.
Caution
There are special rules for the change validation of wage types from the corresponding wage type tables. For more information, see
Wage Type Processing in the Interface Toolbox
.
See also: