Loading Data into Derived Question Fields

Batch Data Load does not prevent you from loading data into a derived field. However, this can cause problems. This section covers a few examples.

Target field is a derived question that is associated with a Thesaurus DVG

If Batch Data Load completes successfully and adds data for a derived question that is associated with a Thesaurus DVG and the loaded response is not valid in the DVG, this raises a thesaurus univariate discrepancy.

Subsequently, when the derivation procedure updates the response, the response record is not versioned, DISCREPANCY_INDICATOR = U for the derived question response record, VALIDATION_STATUS = CNN, and the Thesaurus univariate discrepancy is obsoleted with the resolution DATA CHANGE, but the discrepancy indicator does not update.

Lastly, if a second Batch Data Load targets the question, the Transfer stage fails with the error:

Updating discrepancy entries - rows to update
Fatal error: No rows in Discrepancy Entries table updated.

Target field is a TMS-validated derived question that is associated with a Thesaurus DVG

If Batch Data Load completes successfully and adds data for a TMS-validated derived question that is associated with a Thesaurus DVG, Batch Validation fails and the .out file contains the following:

Derived questions exist for TMS. Calling TMS_OCL_DERV.DERIVATION second time
value of :last_tms_deriv_ts 16-SEP-2016 08:17:42
Error during TMS Thesaurus Validation
Batch Validation aborted due to an error
SQL error during TMS Thesaurus Validation: SQLERROR ORA-00001: unique constraint (RXC.RESPONSE_PK_IDX) violated
ORA-06512:

Running Batch Validation a second time completes successfully.

This unique constraint error interrupts TMS derivation which can lead to data not being derived back for other documents which should have been processed in the same Batch Validation run. A Force Rederivation is required to correct this.