You can determine how the system reacts to data records having the following errors. You can do this in the Scheduler, on the tab page Update, via Error Handling.
Errors in transfer rules:
- A record has fields that contain characters that are not allowed in updates
A key field contains lower-case letters.
- A record is not technically plausible
A date field contains an eight-digit number that does not represent an actual date.
- A user-defined routine in the transfer rules does not consider the record to be plausible
Technically not plausible: A postal code does not correspond to the five-place format.
Implausible in a business context: An amount is clearly too high.
- A record contains (quantity) conversion errors.
Errors in update rules:
- A record contains (quantity) conversion errors.
- No characteristic value is found when master data is read.
- Errors are found when master data is read
- Errors are found in currency translation
- Errors are found in time conversion (conversion of an empty field)
- A user-defined routine in the transfer rules does not consider the record to be plausible
Errors when updating into an InfoCube:
- No SID exists for characteristic value
Errors in hierarchy updates:
- The hierarchy structure contains errors
- The hierarchy contains overlapping time intervals
Errors in master data table updates or text table updates:
- Attributes and navigation attributes contain characters that are not permitted
- No SID exists for navigation attribute values
- No language is specified in text upload
- Record contains unfeasible from and to dates
- There are duplicated records relating to the key
- Time intervals overlap
- Data does not match with the selections made in the Scheduler
Errors in referential integrity:
- No SID exists for characteristic value
