The Target Rejection Threshold is a value defined for the number or percentage of records with errors that are allowed before the execution is configured to fail when you move records from the Source Database to the Target Database. It can be entered as an absolute value or as a percentage in the Connector Properties Window.
The AFCS Application creates the Error Table duplicating the Target Table Name and appending it with _ERR during the execution process. The records with errors are logged into the Error Table and the valid records are moved to the relevant table in the Target. The errors can be of the types notional, public key, or data. For example, if the Target Table Name is STG_CASA, then the Error Table Name is created as STG_CASA_ERR. The objective is to log only a required number of errors and then correct them in the Source Table. After correcting the errors, rerun the execution. In the process, you can iteratively collect the errors and correct them, making the task of correcting the errors in the Source Table much simpler.
You can also move records from File table to the Target Database and the structure of the table remains same as File table added with five additional columns. For example, if the File Table Name is EDD12_THRESHOLD_VOLUMETEST, then the Error Table Name is created as EDD12_THRESHOLD_VOLUMETEST_ERR.
Let us look at the process with the help of the following example:
1. Enter 10 in the Target Rejection Threshold Field.
NOTE:
1. To enter the value as 10 percent of the records in the execution, enter 10%.
2. If you leave the field blank or enter 0, the AFCS Application reads the threshold as 0 and the execution fails when an error is encountered.
On execution of the process, the AFCS Application permits up to 10 records with errors to process to the Target Table and any number of valid records. If the number exceeds 10, the execution process fails and stops. The records with errors are available in the Target Table Name appended with _ERR.
2. In the SLA home page, under any SLA, click Data Ingestion and select View Data. This will display Data Visualization window the where user can search for the Target Table Name appended with _ERR.
3. Check the details in the Error Table.
For information on how to read the error table, see the Reading the Error Table section.
4. After checking the Error Table Details, you can navigate to the Source Table and troubleshoot the errors.
5. After correcting the errors, rerun the execution.
6. Repeat the process iteratively and correct the errors.
The AFCS Application creates the Error Table in the Data Service Execution Layer/Schema to store records with errors. The structure of the Error Table is similar to the Target Table with five additional columns. You can refer to the following column for executions:
· ORA_ERR_NUMBER$ - The Error Number.
· ORA_ERR_MESG$ - The ORA Error Message with the description of the error.
· ORA_ERR_ROWID$ - The Row ID of the Error.
· ORA_ERR_OPTYP$ - The Operation type.
· ORA_ERR_TAG$ - This column stores the Execution ID. You can use this column to filter and view error records for a specific execution.