KRACOEUS-7048:,Performed changes similar to those made for KRACOEUS-6801 for both IRB and IACUC due to required base classes needing to be modified.,For IRB:,It was determined that additional modifications were also required because the same sequence (SEQ_VALID_SUBM_REVW_TYPE_QUAL) was being used to load initial data via the data load scripts for two different IRB maintenance data tables (VALID_PROTO_SUB_REV_TYPE and VALID_PROTO_SUB_TYPE_QUAL) but the application data dictionary was configured to use a different sequence SEQ_PROTOCOL_ID) for the maintenance document data inserts on both of those tables.  SQLException?226?128?153s were resulting when attempting to create new data rows via the maintenance document because sequence SEQ_PROTOCOL_ID had a value lower than the maximum value of sequence SEQ_VALID_SUBM_REVW_TYPE_QUAL used for the initial data load.,To solve this issue, the following was done per Gayathri?226?128?153s request:,1. Two new sequences were created for both IRB tables.,2. These new sequences were set to start at 200 for now.,3. JIRA KRACOEUS-7128 was created and assigned to her to look at this issue further.,For IACUC:,IACUC did not exhibit the SQLException?226?128?153s because there was no initial data being loaded and the two IACUC maintenance data tables (VALID_IACUC_PROTO_SUB_REV_TYPE and IACUC_VALID_PROTO_SUB_TYP_QL) each have their own sequence (SEQ_VAL_IAC_PRO_SUB_REV_TYP_ID and SEQ_VALID_PRO_SUB_TYPE_QUAL_ID) defined in the application data dictionary.