Use
The check for referential integrity occurs for transaction data and master data if they are flexibly updated. You determine the valid InfoObject values.
Prerequisites
The check for referential integrity functions only in conjunction with the function Error Handling on the scheduler tab page Update.
See also Handling Data Records with Errors.
In order to use the check for referential integrity, you have to choose the option Always Update Data... . If you choose the option Do Not Update Data..., you override the check for referential integrity. This is valid for master data (with flexible updating) as well as for transaction data.
Difference in Treating Data Records with Errors
Checking for Referential Integrity | Treating data records with errors |
For all InfoProviders | For all InfoProviders |
Check in the transfer rules | Check according to update rules for each InfoProvider |
Only for selected InfoObjects | For all InfoObjects |
Error Handling | Terminates after first incorrect record |
Possible for all DataStore objects | BW 2.0: Only for DataStore objects for which BEx Reporting is switched on |
Check against master data table or against a DataStore object possible | Checked against master data table |
Features
The verification occurs after filling the communication structure and before filling the update rules. What is displayed in the InfoObject metadata is checked against the master data table (meaning the SID table) or against another DataStore object.
If you create a DataStore object for checking the characteristic values in a characteristic, in the update rules, and in the transfer rules, the valid values for the characteristic are determined from the DataStore object and not from the master data.
No comments:
Post a Comment