Handling of Data Records with Errors

Use
On the Update tab page in the data transfer process (DTP), the error handling settings allow you to control how the system responds if errors occur in the data records when data is transferred from a DTP source to a DTP target. These settings were previously made in the nfoPac!age. "hen using data transfer processes, nfoPac!ages only write to the P#$. Therefore, error handling settings are no longer made in the nfoPac!age but in the data transfer process.

Features
Settings for Error Handling %or a data transfer process (DTP), you can specify how you want the system to respond when data records contain errors. f you activate error handling, the records with errors are written to a re&uest'based database table (P#$ table). This is the error stac!. (ou can use a special data transfer process, the error DTP, to update the records to the target. Temporary storage is available after each processing step of the DTP re&uest. This allows you to determine the processing step in which the error occurred. Checks for Incorrect Data Records The following table provides an overview of where chec!s for incorrect data records can be run) Where Is Check Run? n the transformation Exam les of Incorrect Data Records %ield contains invalid characters or lowercase characters *rror during conversion *rror during currency translation $ routine returns a return code +, .haracteristic value is not found for master data *rror reading master data .ustomer'specific formula results in error nvalid characters in !eys or navigation attributes f no # D e/ists for the value of the navigation attribute f no language field is defined for te/ts nvalid 0from0 and 0to0 dates Duplicate data records with relation to !eys Overlapping and invalid time intervals f no # D e/ists for the characteristic value f no # D e/ists for the characteristic value

"hen data is updated to the master data table or te/t table

"hen data is updated to the nfo.ube "hen chec!ing referential integrity of an nfoOb1ect against master data tables or Data#tore ob1ects

!Re airing! with Error D"# (ou create an error DTP for an active data transfer process on the Update tab page. (ou run it directly in the bac!ground or include it in a process chain so that you can schedule it regularly in the conte/t of your process chain. The error DTP uses the full update mode to e/tract data from the error stac! (in this case, the source of the DTP) and transfer it to the target that you have already defined in the data transfer process.

$cti%ities
...

2. On the Extraction tab page under Semantic Groups, define the !ey fields for the error stac!. This setting is only relevant if you are transferring data to Data#tore ob1ects with data fields that are overwritten. f errors occur, all subse&uent data records with the same !ey are written to the error stac! along with the incorrect data record3 they are not updated to the target. This guarantees the seriali4ation of the data records, and consistent data processing. The seriali4ation of the data records and thus the e/plicit definition of !ey fields for the error stac! is not relevant for targets that are not updated by overwriting. The default value and possible entries for the !ey fields of the error stac! for Data#tore ob1ects that overwrite are shown below) Default &alue'#ossi(le Entries Default value for the !ey fields of the error stac! (fields selected by the system) Which Fields of the Source? $ll fields of the source that are uni&uely assigned to a !ey field of the target. That is, all the fields of the source that are directly assigned to a !ey field of the Data#tore ob1ect in the transformation. Those fields of the source that are assigned to !ey fields of the Data#tore ob1ect, but whose assignment is not uni&ue. $n assignment is not uni&ue if it is not a direct assignment. f the assignment is direct, it is also considered to be not uni&ue if there is a start or end routine. Those fields of the source that are assigned to a non'!ey field of the target, that is to a data field of the Data#tore ob1ect.

%ields that can also be selected as !ey fields for the error stac!

%ields that cannot be selected as !ey fields for the error stac!

The !ey should be as detailed as possible. $ ma/imum of 25 !ey fields is permitted. The fewer the number of !ey fields defined, the more records are updated to the error stac!. The system automatically defines the !ey fields of the target as !ey fields of the error stac! for targets that are not updated by overwriting (for e/ample for nfo.ubes or Data#tore ob1ects that only have fields that are updated cumulatively). n this case you cannot change the !ey fields of the error stac!. 6ore information) *rror #tac! and */amples for Using the *rror #tac! 7. On the Update tab page, specify how you want the system to respond to data records with errors) a. 8o update, no reporting (default) f errors occur, the system terminates the update of the entire data pac!age. The re&uest is not released for reporting. 9owever, the system continues to chec! the records.

b. Update valid records, no reporting (re&uest red) This option allows you to update valid data. This data is only released for reporting after the administrator chec!s the incorrect records that have not been updated and manually releases the re&uest by setting the overall status on the Status tab page in the monitor (:6 action). c. Update valid records, reporting possible ;alid records can be reported immediately. $utomatic follow'up actions, such as ad1usting the aggregates, are also carried out. <. #pecify the ma/imum number of incorrect data records that are allowed before the system terminates the transfer process. f you do not ma!e an entry here, handling for incorrect data records is not activated and the update is terminated when the first error occurs. =. Under No Aggregation, select how you want the system to respond if the number of data records received differs from the number of data records updated. $ difference between the number of records received and the number of updated records can occur if the records are sorted, aggregated, or added in the transformation rules or during the update. f you set this indicator, the re&uest is interpreted as incorrect if the number of received records differs from the number of updated records. f the number of selected records differs from the number of records received, this is interpreted as an error regardless of whether or not the indicator is set. >. 6a!e the settings for the temporary storage by choosing Goto Settings for DTP Temporary Storage. n these settings, you specify the processing steps after which you want the system to temporarily store the DTP re&uest (such as e/traction, filtering, removing new records with the same !ey, and transformation). (ou also specify when the temporary storage should be deleted. This can be done either after the re&uest has been updated successfully to the target, when the re&uest is deleted, or after a specific interval has passed since the re&uest was processed. Under Level of Detail, you specify how you want to trac! the transformation. 5. Once the data transfer process has been activated, create an error DTP on the Update tab page and include it in a process chain. f errors occur, start it manually to update the corrected data to the target.