eRA COMMONS FORMATTING AND VALIDATION REQUIREMENTS‌ Sample Clauses

eRA COMMONS FORMATTING AND VALIDATION REQUIREMENTS‌. The following are formatting requirements and system validations required by eRA Commons and will result in errors if not met. The application must be ‘error free’ to be processed through the eRA Commons. There may be additional validations which will result in Warnings but these will not prevent the application from processing through the submission process. (See Appendix A, Section 4.2)

eRA COMMONS FORMATTING AND VALIDATION REQUIREMENTS‌. The following table is a list of formatting requirements and system validations required by eRA Commons and will result in errors if not met. The application must be ‘error free’ to be processed through the eRA Commons. There may be additional validations which will result in Warnings but these will not prevent the application from processing through the submission process. If you do not adhere to these requirements, you will receive an email notification from xxx-xxxxxx@xxxx.xxx.xxx to take action and adhere to the requirements so that your application can be processed successfully. It is highly recommended that you submit your application 24-72 hours before the submission deadline to allow for sufficient time to correct errors and resubmit the application. If you experience any system validation or technical issues after hours on the application due date, contact the eRA Help Desk and submit a Web ticket to document your good-faith attempt to submit your application. # eRA Validations Action if the Validation is not met

eRA COMMONS FORMATTING AND VALIDATION REQUIREMENTS‌. The following table is a list of formatting requirements and system validations required by eRA Commons and will result in errors if not met. The application must be ‘error free’ to be processed through the eRA Commons. There may be additional validations which will result in Warnings but these will not prevent the application from processing through the submission process. If you do not adhere to these requirements, you will receive an email notification from xxx-xxxxxx@xxxx.xxx.xxx to take action and adhere to the requirements so that your application can be processed successfully. It is highly recommended that you submit your application 24-72 hours before the submission deadline to allow for sufficient time to correct errors and resubmit the application. If you experience any system validation or technical issues after hours on the application due date, contact the eRA Service Desk and submit a Web ticket to document your good faith attempt to submit your application. Applicant Identifier (Item 4 on the SF-424): The PD/PI Credentials must be provided Username provided must be a valid Commons account Username must be affiliated with the organization submitting the application and or have the PI role The Commons Username must be provided in the Applicant Identifier field for the PD/PI. The Commons Username provided in the Applicant Identifier is not a recognized Commons account. The Commons account provided in the Applicant Identifier field for the PD/PI is either not affiliated with the applicant organization or does not hold the PI role. Check with your Commons Account Administrator to make sure your account affiliation and roles are set-up correctly. The DUNS number provided must include valid characters (9 or 13 numbers with or without dashes) The DUNS number provided has invalid characters (other than 9 or 13 numbers) after stripping of dashes The documentation (forms) required for the FOA must be submitted The format of the application does not match the format of the FOA. Contact the eRA Service Desk for assistance. If a change or correction is made to address an error, “Changed/Corrected” must be selected. (Item #1 on the SF-424) Refer to Section II-5.4 for more information on resubmission criteria. This application has been identified as a duplicate of a previous submission. The ‘Type of Submission’ should be set to Changed/Corrected if you are addressing errors/warnings.